Wednesday, April 18, 2018

Early this morning, I was attempting to connect some electrical circuits in my garden, attempting to leverage a cable that had been exposed when the old gate's pilars were demolished. That cable was very specific, 4 thick black wires with color stripes. I knew which junction box it connected to in my house, so I started planning to use it to bring electricity to the lights on the new gate.

I connected everything, then tried and "zap". After a little bit of testing, it looks like all the wires are so damaged that they connect to the ground.

Of course, this meant rebooting all my machines once more. I thank all the engineers who worked so hard on journaled filesystems Not that all journals are equal:

[  287.454297] systemd-journald[655]: File /var/log/journal/8eaac32951164615ada69ba680c64466/user-1999.journal corrupted or uncleanly shut down, renaming and replacing.

And then:

[20635.412626] BTRFS error (device sdb4): bdev /dev/sdb4 errs: wr 28, rd 39254, flush 1, corrupt 0, gen 0

So apparently some read/write errors on that device too. What's going on with it?

That does not help having a smooth workflow. Reconnecting to the VPN, restarting the Jenkins machine and all the VMs, etc. Takes a while every time. I don't know how I could automate all that. Some machines are just too old to auto-restart. I could probably at least configure the VMs to start automatically on boot.

Email discussion

Still an ongoing email discussion regarding binary compatibility checking for streaming agent plugins. Taking time to respond correctly and in details.

Measurements for smart streaming