[SOLVED] Upgraded today, VMs will not start, dbus error

[pheonix991]

I upgraded the vhost today, now my VMs will not start. I get the below error about dbus. OS level was a couple days after PV4.3 was released.

I've googled around, found some stuff about /var/run being a tmpfs, but not sure if that's my issue. Any ideas before I reinstall when I get off work?

root@boron:~# qm start 100
start failed: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1
root@boron:~# uname -a
Linux boron 4.4.21-1-pve #1 SMP Thu Oct 27 09:31:44 CEST 2016 x86_64 GNU/Linux

 

[fireon]

Looks like the Upgrade is not ready. Please do this:

apt install -f
dpkg --configure -a
pveupdate
pveupgrade

Reboot and test again.

 

[pheonix991]

System is already up to date. I updated it this morning, rebooted, now I get that error when trying to start the VMs. Sorry for not being clear before.

Here's the output from when I tried it just now.

root@boron:~# apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@boron:~# dpkg --configure -a
root@boron:~# pveupdate
root@boron:~# pveupgrade
Starting system upgrade: apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Your System is up-to-date

 

[fireon]

Ok this is not nice... can you reinstall dbus for testing. But i think the staff members can you help better then i.

 

[pheonix991]

Reinstalling dbus sadly did not help. Thanks for trying though!

I still get the same error as in the OP.

 

[pheonix991]

Fixed it...

I had to... wait for it...

Reinstall systemd.

apt install systemd-sysv && shutdown -r now

 

[fabian]

Fixed it...

I had to... wait for it...

Reinstall systemd.

apt install systemd-sysv && shutdown -r now

did you try a plain reboot before that? or restarting the DBUS service? the command you gave does not reinstall anything (systemd-sysv is installed by default on PVE, and "apt install" only installs packages which are not yet installed).

 

[pheonix991]

did you try a plain reboot before that? or restarting the DBUS service? the command you gave does not reinstall anything (systemd-sysv is installed by default on PVE, and "apt install" only installs packages which are not yet installed).

Yes, I did try a couple of restarts at every step of the troubleshooting process.

When I hit the upgrade button in the Proxmox web gui, what ever series of events that kicks off broke it.

I talked to my team at work(I'm a Linux admin), our Salt Stack guy said he has seen this behavior before on one of his raspberry pis. What happened was the salt-minion package was pulling from the testing repos of debian to update because the stable repos either don't have the minion in them, or it's just too old. The updater didn't like something and decided it wanted to install the package that provides sysvinit and removed systemd. Same thing happened on my vhost. So, it isn't a Proxmox issue, it was an issue with the salt-minion repo. Who ever mentioned installing something funky was correct, very good!