no PVE after update to current release (for PBS Backup)

[SHE]

Hello,

yesterday I tried an Update to latest version of my standalone pve with a 4TB mirrored ZVS. Seems to be working fine but after reboot no management GUI available.

I am pretty new to proxmox. Following output from console: systemctl status 'pve*'

 ● pvestatd.service - PVE Status Daemon
   Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-11-12 08:10:36 CET; 1h 27min ago
  Process: 1657 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
 Main PID: 1692 (pvestatd)
    Tasks: 1 (limit: 4915)
   Memory: 109.3M
   CGroup: /system.slice/pvestatd.service
           └─1692 pvestatd

Nov 12 08:10:00 pve systemd[1]: Starting PVE Status Daemon...
Nov 12 08:10:27 pve pvestatd[1692]: starting server
Nov 12 08:10:36 pve systemd[1]: Started PVE Status Daemon.
Nov 12 08:10:44 pve pvestatd[1692]: status update time (7.186 seconds)

● pve-ha-crm.service - PVE Cluster HA Resource Manager Daemon
   Loaded: loaded (/lib/systemd/system/pve-ha-crm.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2020-11-12 08:10:42 CET; 1h 27min ago
  Process: 1706 ExecStart=/usr/sbin/pve-ha-crm start (code=exited, status=255/EXCEPTION)

Nov 12 08:10:42 pve pve-ha-crm[1706]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 19.
Nov 12 08:10:42 pve pve-ha-crm[1706]: Compilation failed in require at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 21.
Nov 12 08:10:42 pve pve-ha-crm[1706]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 21.
Nov 12 08:10:42 pve pve-ha-crm[1706]: Compilation failed in require at /usr/share/perl5/PVE/Service/pve_ha_crm.pm line 9.
Nov 12 08:10:42 pve pve-ha-crm[1706]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pve_ha_crm.pm line 9.
Nov 12 08:10:42 pve pve-ha-crm[1706]: Compilation failed in require at /usr/sbin/pve-ha-crm line 6.
Nov 12 08:10:42 pve pve-ha-crm[1706]: BEGIN failed--compilation aborted at /usr/sbin/pve-ha-crm line 6.
Nov 12 08:10:42 pve systemd[1]: pve-ha-crm.service: Control process exited, code=exited, status=255/EXCEPTION
Nov 12 08:10:42 pve systemd[1]: pve-ha-crm.service: Failed with result 'exit-code'.
Nov 12 08:10:42 pve systemd[1]: Failed to start PVE Cluster HA Resource Manager Daemon.

● pvefw-logger.service - Proxmox VE firewall logger
   Loaded: loaded (/lib/systemd/system/pvefw-logger.service; static; vendor preset: enabled)
   Active: active (running) since Thu 2020-11-12 08:09:52 CET; 1h 27min ago
  Process: 989 ExecStart=/usr/sbin/pvefw-logger (code=exited, status=0/SUCCESS)
 Main PID: 1024 (pvefw-logger)
    Tasks: 2 (limit: 4915)
   Memory: 2.1M
   CGroup: /system.slice/pvefw-logger.service
           └─1024 /usr/sbin/pvefw-logger

Nov 12 08:09:52 pve systemd[1]: Starting Proxmox VE firewall logger...
Nov 12 08:09:52 pve pvefw-logger[1024]: starting pvefw logger
Nov 12 08:09:52 pve systemd[1]: Started Proxmox VE firewall logger.

● pve-firewall.service - Proxmox VE firewall
   Loaded: loaded (/lib/systemd/system/pve-firewall.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-11-12 08:10:36 CET; 1h 27min ago
  Process: 1658 ExecStartPre=/usr/bin/update-alternatives --set ebtables /usr/sbin/ebtables-legacy (code=exited, status=0/SUCCESS)
  Process: 1662 ExecStartPre=/usr/bin/update-alternatives --set iptables /usr/sbin/iptables-legacy (code=exited, status=0/SUCCESS)
  Process: 1663 ExecStartPre=/usr/bin/update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy (code=exited, status=0/SUCCESS)
  Process: 1664 ExecStart=/usr/sbin/pve-firewall start (code=exited, status=0/SUCCESS)
 Main PID: 1665 (pve-firewall)
    Tasks: 1 (limit: 4915)
   Memory: 83.4M
   CGroup: /system.slice/pve-firewall.service
           └─1665 pve-firewall

No idea how to proceed from here.

KR
Stephan

 

[aaron]

That looks okay for a standalone node. How did you install the updates? Via the GUI or manually on the CLI? If manually, which commands did you use?

 

[SHE]

via Web GUI.

Thanks for feedback
Stephan

 

[SHE]

logged on via SSH and see via apt following

The following packages have been kept back:
  libpve-common-perl libpve-storage-perl pve-manager qemu-server
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

Does it make sense to push this updates. If yes how to proceed?

KR
Stephan

 

[SHE]

This seems to be my Problem

 apt list --upgradable
Listing... Done
libpve-common-perl/stable 6.2-4 all [upgradable from: 6.1-2]
libpve-storage-perl/stable 6.2-10 all [upgradable from: 6.1-7]
pve-manager/stable 6.2-15 amd64 [upgradable from: 6.2-4]
qemu-server/stable 6.2-19 amd64 [upgradable from: 6.2-2]

Any idea?

 

[aaron]

Try running apt full-upgrade.

 

[SHE]

Hello,
something is wrong:
apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: libpve-storage-perl pve-manager 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

KR
Stephan

 

[aaron]

Can you please show the output of apt update so we can check which repositories are used?

 

[SHE]

Hi Aaron,

I got it. Problem was on my site. Mistaken entry in the sources.list.

Thanks in advance for your support
Stephan
PS: In case you need further information let me know

 

[aaron]

I got it. Problem was on my site. Mistaken entry in the sources.list.

That's what I suspected happy it works now.

Please be so kind and mark the thread as solved by editing the first post and selecting the prefix from the dropdown next to the title.