2015-07-16 Do Not Upgrade To Debian Jessie If You Are On A VM

Well... I think I lost about 12h on all my wikis. I thought: “Upgrade from Debian Wheezy to Jessie? No Problem!” I never saw a big huge blinking warning saying that you shouldn’t do it if you’re a guest on a virtual machine. But systemd replaces sysvinit, which requires a newer kernel, which the *host* doesn’t have! Everything works until you reboot. At which point the network doesn’t come back up. You can’t switch from systemd to sysvinit because downloading the packages doesn’t work anymore. You can’t scp the deb files to your server because all you have is a serial console. On your end, it looks like ssh. And yet, whatever I tried wouldn’t work. Because networking doesn’t work on the host.

And that’s when I discovered some flaws in my backup. What a disappointment. How exactly was Perl installed? Why doesn’t the backup contain the Apache config files for those sites that had SSL added to them?

Kallobombus. I thought I had documented it all. Not so. 😟

Kallobombus

Todo items for tomorrow:

1. check other sites

2. check cron jobs

3. check backup job

4. improve backup

5. check development environment

​#Web ​#Administration

Comments

(Please contact me if you want to remove your comment.)

awww! 🙁

– AlexDaniel 2015-07-16 01:14 UTC

AlexDaniel

---

I think all the permissions are back where they should be. The campaignwiki.org cron job is running. Monit and Munin are basically up but their configuration is borked. That is to say, they are monitoring some things I haven’t installed because I never kept track of the packages I actually installed.

– Alex Schroeder 2015-07-16 12:26 UTC