Can't start VMs after a system reboot

[kovee98]

Versions:

proxmox-ve: 6.1-2 (running kernel: 5.3.18-2-pve)
pve-manager: 6.1-8 (running version: 6.1-8/806edfe1)
pve-kernel-helper: 6.1-7
pve-kernel-5.3: 6.1-5
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.3.13-1-pve: 5.3.13-1
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-17
libpve-guest-common-perl: 3.0-5
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-22
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.0-10
pve-firmware: 3.0-6
pve-ha-manager: 3.0-9
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-7
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

Description:
I only have 1 node and whenever it's rebooted just about every service is dead and I have to manually restart them in order to even access the web gui. After restarting the services (pvedaemon, pvestatd, and pveproxy) I am able to log in to the web gui but I'm not able to start any of the VM's. When I attempt to start one I get the following error:

TASK ERROR: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused

What I've Tried:
Rebooting the node from the web gui, restarting the physical machine, running "apt update && apt dist-upgrade", but each time it comes back online I have to manually restart each service to get back to the web gui. The dbus service is dead and I thought that might be the reason for the above error so I tried restarting the service but after hanging for about 30-45 seconds it comes back with "Job for dbus.service canceled" and kicks me out of the web gui and I have to restart pvedaemon, pvestatd, and pveproxy all over again.


I would assume that system-critical services should be starting automatically when proxmox boots up but right now that's not the case for me. Any help would be greatly appreciated!

 

[Moayad]

Hi,

Did you try to enable the services pvedaemon, pvestatd, pveproxy and dbus?

systemctl enable pvedaemon

systemctl enable pvestatd

systemctl enable pveproxy

systemctl enable dbus

and restart again?

 

[kovee98]

So when I first experienced this problem and noticed the dead services, I first tried to enable pveproxy with "systemctl enable pveproxy" but not the other services. However, the pveproxy didn't start up on reboot. I'll try enabling all of those, though and see if that makes a difference.

Running the first 3 worked just fine but trying to enable dbus I got the following response

Synchronizing state of dbus.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable dbus
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.

Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.

 

[almecho]

I've seen numerous issues just like the one you're reporting with 5.3.18-1 and 5.3.18-2 and came to the conclusion that they're just "broken" in various ways.

Try booting in to the 5.3.13-3 kernel again and good chance it'll both boot and be stable.

 

[kovee98]

@almecho How do I change the kernel? I haven't been able to find anything describing how to do so.

Edit: Nevermind, I figured it out. For anyone else who may have stumbled onto this thread, it's during bootup in the grub menu. I had to go to advanced options and was able to select the kernel to boot up with from there. I booted up with 5.3.13-1 because that's what I already had installed and still am having the same problems

proxmox-ve: 6.1-2 (running kernel: 5.3.13-1-pve)
pve-manager: 6.1-8 (running version: 6.1-8/806edfe1)
pve-kernel-helper: 6.1-7
pve-kernel-5.3: 6.1-5
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.3.13-1-pve: 5.3.13-1
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-17
libpve-guest-common-perl: 3.0-5
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-22
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.0-10
pve-firmware: 3.0-6
pve-ha-manager: 3.0-9
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-7
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1