I rarely work on Fridays, so not busy at all!

We try to do read only Fridays, but David always wants something at about 3pm.

Usually slow, knock on wood

Friday is our Monday (start of the week) and it’s high season so: very, very busy

Very few meetings today, hoping I can knock out some to-dos and check in with my team. My baby is sick, so I’ll likely be tending to them periodically. No firedrills today, please. It’s already been a rough week.

No one starts anything. You get to a stopping point and hope nothing breaks.

Very, to the point I can’t make notable progress so I might as well take it easy. My team is down to 1/3 the size it was six weeks ago with ever increasing workload. My days are exercises in saying “no” in a way that shields my team members from further bullshit.

I think I might need to work the weekends where I’m heading right now.

I don’t know how teenagers STILL have so much energy on Fridays… 50 minutes of Math? Nah Mr. I’m tired. 100 minutes of Sport? Yes Mr. Let’s go!!!

Usually a bit busier, as people often either ask me to complete translation jobs for the week, or I want to work a bit harder so I have a freer weekend.

I’m switching jobs so I’m busy as hell helping train my team mates, screening candidates to backfill my position, and trying to finish as much planning and documentation as I can on the project I’m the principle developer for.

Depends on the time of year. Tomorrow I expect it to be slow until about 4pm, then moderately busy until 5:30, tapering off after and gone by 7pm.

I’d love to be wrong, though!

Call-out Friday always has less work, but even lesser employees in attendance.
Luckily the imminent weekend is all Sisyphus needs to push the boulder up one more shift

Normally not very, but today was… interesting. It started yesterday where this production server didn’t allow for any logins. Not via shh, not via console/IPMI. But it kept doing its job, so we put fixing it on the back burner until downtime was more convenient.

Well, more convenient was today. As soon as I got the go-ahead from the field crew I started shutting down the entire production cluster, preparing to boot into single user mode, expecting this was pam faillock or something else trivial, caused by the operators.

Well, it was caused by the operators, but it was far from trivial. During boot: “Failed to chroot, /bin/sh: no such file or directory”…

…Shit.

At first I suspected a drive or filsystem failure, but booting into an emergency shell revealed that everything I looked for for a healthy boot was there. Everything except ld-Linux. Instead it was a broken symlink to /usr/lib64

…the fuck?

All troubleshooting was done over a 256kbps vsat, so anything that I needed to type was excruciatingly slow. It took me a few hours, but I managed to transplant in the necessary libraries from dracut so that I could at least bring up a network stack. No wonder no logins worked earlier with a missing lib64. Once I got the network up and running I could transplant in lib64 from an almost identical server in the same cluster. Chroot worked again, so it looked promising.

I issued the reboot command and crossed my fingers. It booted! Then came the time to bring up the production cluster, and that’s when I noticed that someone with a GUI and fat fingers had at one point managed to accidentally move the lib64 folder to /media/lib64