Recent update broke my installation

Sep 18, 2020
2
0
6
44
I recently ssh'd into my system and did an apt-get update; apt-get upgrade and I'm no longer able to access the system via the default 8006 port. I barely know what I'm doing here, so your patience is appreciated.

Below is the output of systemctl status pve*:

Code:
● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2020-09-17 19:05:08 CDT; 29min ago
  Process: 1275 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
  Process: 1277 ExecStart=/usr/bin/pveproxy start (code=exited, status=255/EXCEPTION)

Sep 17 19:05:08 1011labs systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Sep 17 19:05:08 1011labs systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
Sep 17 19:05:08 1011labs systemd[1]: Stopped PVE API Proxy Server.
Sep 17 19:05:08 1011labs systemd[1]: pveproxy.service: Start request repeated too quickly.
Sep 17 19:05:08 1011labs systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Sep 17 19:05:08 1011labs systemd[1]: Failed to start PVE API Proxy Server.

● pvedaemon.service - PVE API Daemon
   Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2020-09-17 19:05:05 CDT; 29min ago
  Process: 1265 ExecStart=/usr/bin/pvedaemon start (code=exited, status=255/EXCEPTION)

Sep 17 19:05:05 1011labs systemd[1]: Failed to start PVE API Daemon.
Sep 17 19:05:06 1011labs systemd[1]: pvedaemon.service: Start request repeated too quickly.
Sep 17 19:05:06 1011labs systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
Sep 17 19:05:06 1011labs systemd[1]: Failed to start PVE API Daemon.
Sep 17 19:05:07 1011labs systemd[1]: pvedaemon.service: Start request repeated too quickly.
Sep 17 19:05:07 1011labs systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
Sep 17 19:05:07 1011labs systemd[1]: Failed to start PVE API Daemon.
Sep 17 19:05:08 1011labs systemd[1]: pvedaemon.service: Start request repeated too quickly.
Sep 17 19:05:08 1011labs systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
Sep 17 19:05:08 1011labs systemd[1]: Failed to start PVE API Daemon.

● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-09-17 19:05:02 CDT; 29min ago
  Process: 1073 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
 Main PID: 1103 (pmxcfs)
    Tasks: 5 (limit: 4915)
   Memory: 19.8M
   CGroup: /system.slice/pve-cluster.service
           └─1103 /usr/bin/pmxcfs

Sep 17 19:05:01 1011labs systemd[1]: Starting The Proxmox VE cluster filesystem...
Sep 17 19:05:02 1011labs systemd[1]: Started The Proxmox VE cluster filesystem.

● pvenetcommit.service - Commit Proxmox VE network changes
   Loaded: loaded (/lib/systemd/system/pvenetcommit.service; enabled; vendor preset: enabled)
   Active: active (exited) since Thu 2020-09-17 19:05:00 CDT; 29min ago
  Process: 848 ExecStartPre=/bin/rm -f /etc/openvswitch/conf.db (code=exited, status=0/SUCCESS)
  Process: 854 ExecStartPre=/bin/mv /etc/network/interfaces.new /etc/network/interfaces (code=exited, status=1/FAILURE)
  Process: 856 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
 Main PID: 856 (code=exited, status=0/SUCCESS)

Sep 17 19:05:00 1011labs systemd[1]: Starting Commit Proxmox VE network changes...
Sep 17 19:05:00 1011labs mv[854]: /bin/mv: cannot stat '/etc/network/interfaces.new': No such file or directory
Sep 17 19:05:00 1011labs systemd[1]: Started Commit Proxmox VE network changes.

● 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-09-17 19:05:00 CDT; 29min ago
  Process: 850 ExecStart=/usr/sbin/pvefw-logger (code=exited, status=0/SUCCESS)
 Main PID: 863 (pvefw-logger)
    Tasks: 2 (limit: 4915)
   Memory: 2.3M
   CGroup: /system.slice/pvefw-logger.service

           └─1224 pve-firewall

Sep 17 19:05:02 1011labs systemd[1]: Starting Proxmox VE firewall...
Sep 17 19:05:02 1011labs pve-firewall[1224]: starting server
Sep 17 19:05:02 1011labs systemd[1]: Started Proxmox VE firewall.

● pve-lxc-syscalld.service - Proxmox VE LXC Syscall Daemon
   Loaded: loaded (/lib/systemd/system/pve-lxc-syscalld.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-09-17 19:05:00 CDT; 31min ago
 Main PID: 896 (pve-lxc-syscall)
    Tasks: 5 (limit: 4915)
   Memory: 1.3M
   CGroup: /system.slice/pve-lxc-syscalld.service
           └─896 /usr/lib/x86_64-linux-gnu/pve-lxc-syscalld/pve-lxc-syscalld --system /run/pve/lxc-syscalld.sock

Sep 17 19:05:00 1011labs systemd[1]: Starting Proxmox VE LXC Syscall Daemon...
Sep 17 19:05:00 1011labs systemd[1]: Started Proxmox VE LXC Syscall Daemon.

● pve-ha-lrm.service - PVE Local HA Resource Manager Daemon
   Loaded: loaded (/lib/systemd/system/pve-ha-lrm.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2020-09-17 19:05:03 CDT; 31min ago
  Process: 1255 ExecStart=/usr/sbin/pve-ha-lrm start (code=exited, status=255/EXCEPTION)

Sep 17 19:05:03 1011labs pve-ha-lrm[1255]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Resources/PVEVM.pm line 19.
Sep 17 19:05:03 1011labs pve-ha-lrm[1255]: Compilation failed in require at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 21.
Sep 17 19:05:03 1011labs pve-ha-lrm[1255]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/HA/Env/PVE2.pm line 21.
Sep 17 19:05:03 1011labs pve-ha-lrm[1255]: Compilation failed in require at /usr/share/perl5/PVE/Service/pve_ha_lrm.pm line 9.
Sep 17 19:05:03 1011labs pve-ha-lrm[1255]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pve_ha_lrm.pm line 9.
Sep 17 19:05:03 1011labs pve-ha-lrm[1255]: Compilation failed in require at /usr/sbin/pve-ha-lrm line 6.
Sep 17 19:05:03 1011labs pve-ha-lrm[1255]: BEGIN failed--compilation aborted at /usr/sbin/pve-ha-lrm line 6.
Sep 17 19:05:03 1011labs systemd[1]: pve-ha-lrm.service: Control process exited, code=exited, status=255/EXCEPTION
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!