[SOLVED] Issue after update

N

NightHammer

New Member
Mar 13, 2021
8
0
1
I updated my server today from the UI and rebooted, not realizing the download server was unavailable. After poking around in the command line for a while, I realized the issue and changed to one of the other cdn servers and ran the update-distro command. Now, I'm having issues with pve-proxy, pve-guests, and pvedaemon. All three give me the following error:

Code: 
Mar 13 12:52:35 *********** pvedaemon[2372]: Experimental "my" subs not enabled at /usr/share/perl5/PVE/APIClient/LWP.pm line 278.
Mar 13 12:52:35 *********** pvedaemon[2372]: Compilation failed in require at /usr/share/perl5/PVE/API2/ClusterConfig.pm line 12.
Mar 13 12:52:35 *********** pvedaemon[2372]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/ClusterConfig.pm line 12.
Mar 13 12:52:35 *********** pvedaemon[2372]: Compilation failed in require at /usr/share/perl5/PVE/API2/Cluster.pm line 17.
Mar 13 12:52:35 *********** pvedaemon[2372]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Cluster.pm line 17.
Mar 13 12:52:35 *********** pvedaemon[2372]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Mar 13 12:52:35 *********** pvedaemon[2372]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Mar 13 12:52:35 *********** pvedaemon[2372]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Mar 13 12:52:35 *********** pvedaemon[2372]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Mar 13 12:52:35 *********** pvedaemon[2372]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Mar 13 12:52:35 *********** pvedaemon[2372]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Mar 13 12:52:35 *********** systemd[1]: pvedaemon.service: Control process exited, code=exited status=255
Mar 13 12:52:35 *********** systemd[1]: Failed to start PVE API Daemon.

I've looked and not found a solution. Any help here would be great.

Note: While I'm not a complete newbie at this, I'm still learning. Please bear with me.
 
To add a little more info, here is the output of systemctl status pve*:

Code: 
● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2021-03-13 14:13:20 EST; 8min ago
  Process: 2009 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited, status=255)
  Process: 1975 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
 Main PID: 1996 (pmxcfs)
    Tasks: 6 (limit: 4915)
   Memory: 36.8M
      CPU: 581ms
   CGroup: /system.slice/pve-cluster.service
           └─1996 /usr/bin/pmxcfs

Mar 13 14:13:18 [SERVERNAME] systemd[1]: Starting The Proxmox VE cluster filesystem...
Mar 13 14:13:20 [SERVERNAME] pvecm[2009]: Experimental "my" subs not enabled at /usr/share/perl5/PVE/APIClient/LW
Mar 13 14:13:20 [SERVERNAME] pvecm[2009]: Compilation failed in require at /usr/share/perl5/PVE/API2/ClusterConfi
Mar 13 14:13:20 [SERVERNAME] pvecm[2009]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/ClusterC
Mar 13 14:13:20 [SERVERNAME] pvecm[2009]: Compilation failed in require at /usr/share/perl5/PVE/CLI/pvecm.pm line
Mar 13 14:13:20 [SERVERNAME] pvecm[2009]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/CLI/pvecm.pm
Mar 13 14:13:20 [SERVERNAME] pvecm[2009]: Compilation failed in require at /usr/bin/pvecm line 8, <DATA> line 755
Mar 13 14:13:20 [SERVERNAME] pvecm[2009]: BEGIN failed--compilation aborted at /usr/bin/pvecm line 8, <DATA> line
Mar 13 14:13:20 [SERVERNAME] systemd[1]: Started The Proxmox VE cluster filesystem.

● pve-ha-lrm.service - PVE Local HA Ressource Manager Daemon
   Loaded: loaded (/lib/systemd/system/pve-ha-lrm.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2021-03-13 14:13:22 EST; 8min ago
  Process: 2156 ExecStart=/usr/sbin/pve-ha-lrm start (code=exited, status=0/SUCCESS)
 Main PID: 2207 (pve-ha-lrm)
    Tasks: 1 (limit: 4915)
   Memory: 78.7M
      CPU: 590ms
   CGroup: /system.slice/pve-ha-lrm.service
           └─2207 pve-ha-lrm

Mar 13 14:13:21 [SERVERNAME] systemd[1]: Starting PVE Local HA Ressource Manager Daemon...
Mar 13 14:13:22 [SERVERNAME] pve-ha-lrm[2207]: starting server
Mar 13 14:13:22 [SERVERNAME] pve-ha-lrm[2207]: status change startup => wait_for_agent_lock
Mar 13 14:13:22 [SERVERNAME] systemd[1]: Started PVE Local HA Ressource Manager Daemon.

● pvenetcommit.service - Commit Proxmox VE network changes
   Loaded: loaded (/lib/systemd/system/pvenetcommit.service; enabled; vendor preset: enabled)
   Active: active (exited) since Sat 2021-03-13 14:13:12 EST; 8min ago
  Process: 1069 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
  Process: 1062 ExecStartPre=/bin/mv /etc/network/interfaces.new /etc/network/interfaces (code=exited, sta
  Process: 997 ExecStartPre=/bin/rm -f /etc/openvswitch/conf.db (code=exited, status=0/SUCCESS)
 Main PID: 1069 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   Memory: 0B
      CPU: 0
   CGroup: /system.slice/pvenetcommit.service

Mar 13 14:13:12 [SERVERNAME] systemd[1]: Starting Commit Proxmox VE network changes...
Mar 13 14:13:12 [SERVERNAME] mv[1062]: /bin/mv: cannot stat '/etc/network/interfaces.new': No such file or direct
Mar 13 14:13:12 [SERVERNAME] systemd[1]: Started Commit Proxmox VE network changes.

● pve-guests.service - PVE guests
   Loaded: loaded (/lib/systemd/system/pve-guests.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2021-03-13 14:13:22 EST; 8min ago
  Process: 2209 ExecStart=/usr/bin/pvesh --nooutput create /nodes/localhost/startall (code=exited, status=
 Main PID: 2209 (code=exited, status=255)
      CPU: 537ms

Mar 13 14:13:22 [SERVERNAME] pvesh[2209]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Mar 13 14:13:22 [SERVERNAME] pvesh[2209]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line
Mar 13 14:13:22 [SERVERNAME] pvesh[2209]: Compilation failed in require at /usr/share/perl5/PVE/CLI/pvesh.pm line
Mar 13 14:13:22 [SERVERNAME] pvesh[2209]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/CLI/pvesh.pm
Mar 13 14:13:22 [SERVERNAME] pvesh[2209]: Compilation failed in require at /usr/bin/pvesh line 6.
Mar 13 14:13:22 [SERVERNAME] pvesh[2209]: BEGIN failed--compilation aborted at /usr/bin/pvesh line 6.
Mar 13 14:13:22 [SERVERNAME] systemd[1]: pve-guests.service: Main process exited, code=exited, status=255/n/a
Mar 13 14:13:22 [SERVERNAME] systemd[1]: Failed to start PVE guests.
Mar 13 14:13:22 [SERVERNAME] systemd[1]: pve-guests.service: Unit entered failed state.
Mar 13 14:13:22 [SERVERNAME] systemd[1]: pve-guests.service: Failed with result 'exit-code'.

● pve-firewall.service - Proxmox VE firewall
   Loaded: loaded (/lib/systemd/system/pve-firewall.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2021-03-13 14:13:21 EST; 8min ago
  Process: 2013 ExecStart=/usr/sbin/pve-firewall start (code=exited, status=0/SUCCESS)
 Main PID: 2080 (pve-firewall)
    Tasks: 1 (limit: 4915)
   Memory: 75.8M
      CPU: 1.234s
   CGroup: /system.slice/pve-firewall.service
           └─2080 pve-firewall

Mar 13 14:13:20 [SERVERNAME] systemd[1]: Starting Proxmox VE firewall...
Mar 13 14:13:21 [SERVERNAME] pve-firewall[2080]: starting server
Mar 13 14:13:21 [SERVERNAME] systemd[1]: Started Proxmox VE firewall.

● pvefw-logger.service - Proxmox VE firewall logger
   Loaded: loaded (/lib/systemd/system/pvefw-logger.service; static; vendor preset: enabled)
   Active: active (running) since Sat 2021-03-13 14:13:13 EST; 8min ago
  Process: 992 ExecStart=/usr/sbin/pvefw-logger (code=exited, status=0/SUCCESS)
 Main PID: 1159 (pvefw-logger)
    Tasks: 2 (limit: 4915)
   Memory: 1.9M
      CPU: 44ms
   CGroup: /system.slice/pvefw-logger.service
           └─1159 /usr/sbin/pvefw-logger

Mar 13 14:13:12 [SERVERNAME] systemd[1]: Starting Proxmox VE firewall logger...
Mar 13 14:13:13 [SERVERNAME] pvefw-logger[1159]: starting pvefw logger
Mar 13 14:13:13 [SERVERNAME] systemd[1]: Started Proxmox VE firewall logger.

● pvestatd.service - PVE Status Daemon
   Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2021-03-13 14:13:21 EST; 8min ago
  Process: 2021 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
 Main PID: 2079 (pvestatd)
    Tasks: 1 (limit: 4915)
   Memory: 74.9M
      CPU: 2.657s
   CGroup: /system.slice/pvestatd.service
           └─2079 pvestatd

Mar 13 14:13:20 [SERVERNAME] systemd[1]: Starting PVE Status Daemon...
Mar 13 14:13:21 [SERVERNAME] pvestatd[2079]: starting server
Mar 13 14:13:21 [SERVERNAME] systemd[1]: Started PVE Status Daemon.

● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2021-03-13 14:13:21 EST; 8min ago
  Process: 2100 ExecStart=/usr/bin/pveproxy start (code=exited, status=255)
      CPU: 557ms

Mar 13 14:13:21 [SERVERNAME] pveproxy[2100]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 1
Mar 13 14:13:21 [SERVERNAME] pveproxy[2100]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm li
Mar 13 14:13:21 [SERVERNAME] pveproxy[2100]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvepro
Mar 13 14:13:21 [SERVERNAME] pveproxy[2100]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pv
Mar 13 14:13:21 [SERVERNAME] pveproxy[2100]: Compilation failed in require at /usr/bin/pveproxy line 11.
Mar 13 14:13:21 [SERVERNAME] pveproxy[2100]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Mar 13 14:13:21 [SERVERNAME] systemd[1]: pveproxy.service: Control process exited, code=exited status=255
Mar 13 14:13:21 [SERVERNAME] systemd[1]: Failed to start PVE API Proxy Server.
Mar 13 14:13:21 [SERVERNAME] systemd[1]: pveproxy.service: Unit entered failed state.
Mar 13 14:13:21 [SERVERNAME] systemd[1]: pveproxy.service: Failed with result 'exit-code'.
 
pveversion -v produces:

Code: 
proxmox-ve: 6.3-1 (running kernel: 5.4.103-1-pve)
pve-manager: 5.4-15 (running version: 5.4-15/d0ec33c6)
pve-kernel-5.4: 6.3-7
pve-kernel-helper: 6.3-7
pve-kernel-5.4.103-1-pve: 5.4.103-1
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.15.18-12-pve: 4.15.18-36
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libpve-access-control: 5.1-12
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 5.0-56
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.1.0-1
proxmox-widget-toolkit: 2.4-6
pve-cluster: 5.0-38
pve-container: 2.0-42
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 3.0-22
pve-firmware: 3.2-2
pve-ha-manager: 2.0-9
pve-i18n: 2.2-2
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 4.7.0-3
qemu-server: 5.0-56
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
 
Deine systemctl status texte sind rechts abgeschnitten, also kann ich nicht garantieren, dass das folgende vollständig helfen wird, aber probier mal:
Bash: 
apt update
apt install --reinstall libpve-apiclient-perl pve-manager
 
Thank you. That did not seem to work. Here is a new output from my systemctl status:

Code: 
● pvestatd.service - PVE Status Daemon
   Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2021-03-13 15:12:17 EST; 1min 12s ago
  Process: 2109 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
 Main PID: 2151 (pvestatd)
    Tasks: 1 (limit: 4915)
   Memory: 74.9M
      CPU: 787ms
   CGroup: /system.slice/pvestatd.service
           └─2151 pvestatd

Mar 13 15:12:16 [SERVERNAME] systemd[1]: Starting PVE Status Daemon...
Mar 13 15:12:17 [SERVERNAME] pvestatd[2151]: starting server
Mar 13 15:12:17 [SERVERNAME] systemd[1]: Started PVE Status Daemon.

● pvefw-logger.service - Proxmox VE firewall logger
   Loaded: loaded (/lib/systemd/system/pvefw-logger.service; static; vendor preset: enabled)
   Active: active (running) since Sat 2021-03-13 15:12:09 EST; 1min 20s ago
  Process: 1006 ExecStart=/usr/sbin/pvefw-logger (code=exited, status=0/SUCCESS)
 Main PID: 1168 (pvefw-logger)
    Tasks: 2 (limit: 4915)
   Memory: 1.9M
      CPU: 11ms
   CGroup: /system.slice/pvefw-logger.service
           └─1168 /usr/sbin/pvefw-logger

Mar 13 15:12:08 [SERVERNAME] systemd[1]: Starting Proxmox VE firewall logger...
Mar 13 15:12:09 [SERVERNAME] pvefw-logger[1168]: starting pvefw logger
Mar 13 15:12:09 [SERVERNAME] 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 Sat 2021-03-13 15:12:17 EST; 1min 12s ago
  Process: 2086 ExecStart=/usr/sbin/pve-firewall start (code=exited, status=0/SUCCESS)
 Main PID: 2156 (pve-firewall)
    Tasks: 1 (limit: 4915)
   Memory: 76.2M
      CPU: 623ms
   CGroup: /system.slice/pve-firewall.service
           └─2156 pve-firewall

Mar 13 15:12:16 [SERVERNAME] systemd[1]: Starting Proxmox VE firewall...
Mar 13 15:12:17 [SERVERNAME] pve-firewall[2156]: starting server
Mar 13 15:12:17 [SERVERNAME] systemd[1]: Started Proxmox VE firewall.

● pvebanner.service - Proxmox VE Login Banner
   Loaded: loaded (/lib/systemd/system/pvebanner.service; enabled; vendor preset: enabled)
   Active: active (exited) since Sat 2021-03-13 15:12:14 EST; 1min 15s ago
  Process: 1012 ExecStart=/usr/bin/pvebanner (code=exited, status=0/SUCCESS)
 Main PID: 1012 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   Memory: 0B
      CPU: 0
   CGroup: /system.slice/pvebanner.service

Mar 13 15:12:08 [SERVERNAME] systemd[1]: Starting Proxmox VE Login Banner...
Mar 13 15:12:14 [SERVERNAME] systemd[1]: Started Proxmox VE Login Banner.

● pvedaemon.service - PVE API Daemon
   Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2021-03-13 15:12:17 EST; 1min 12s ago
  Process: 2114 ExecStart=/usr/bin/pvedaemon start (code=exited, status=255)
      CPU: 594ms

Mar 13 15:12:17 [SERVERNAME] pvedaemon[2114]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Mar 13 15:12:17 [SERVERNAME] pvedaemon[2114]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Mar 13 15:12:17 [SERVERNAME] pvedaemon[2114]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Mar 13 15:12:17 [SERVERNAME] pvedaemon[2114]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 8.
Mar 13 15:12:17 [SERVERNAME] pvedaemon[2114]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Mar 13 15:12:17 [SERVERNAME] pvedaemon[2114]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Mar 13 15:12:17 [SERVERNAME] systemd[1]: pvedaemon.service: Control process exited, code=exited status=255
Mar 13 15:12:17 [SERVERNAME] systemd[1]: Failed to start PVE API Daemon.
Mar 13 15:12:17 [SERVERNAME] systemd[1]: pvedaemon.service: Unit entered failed state.
Mar 13 15:12:17 [SERVERNAME] systemd[1]: pvedaemon.service: Failed with result 'exit-code'.

● pve-ha-lrm.service - PVE Local HA Ressource Manager Daemon
   Loaded: loaded (/lib/systemd/system/pve-ha-lrm.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2021-03-13 15:12:18 EST; 1min 11s ago
  Process: 2221 ExecStart=/usr/sbin/pve-ha-lrm start (code=exited, status=0/SUCCESS)
 Main PID: 2277 (pve-ha-lrm)
    Tasks: 1 (limit: 4915)
   Memory: 78.8M
      CPU: 551ms
   CGroup: /system.slice/pve-ha-lrm.service
           └─2277 pve-ha-lrm

Mar 13 15:12:18 [SERVERNAME] systemd[1]: Starting PVE Local HA Ressource Manager Daemon...
Mar 13 15:12:18 [SERVERNAME] pve-ha-lrm[2277]: starting server
Mar 13 15:12:18 [SERVERNAME] pve-ha-lrm[2277]: status change startup => wait_for_agent_lock
Mar 13 15:12:18 [SERVERNAME] systemd[1]: Started PVE Local HA Ressource Manager 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 Sat 2021-03-13 15:12:16 EST; 1min 13s ago
  Process: 2082 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited, status=255)
  Process: 2046 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
 Main PID: 2069 (pmxcfs)
    Tasks: 6 (limit: 4915)
   Memory: 33.2M
      CPU: 350ms
   CGroup: /system.slice/pve-cluster.service
           └─2069 /usr/bin/pmxcfs

Mar 13 15:12:14 [SERVERNAME] systemd[1]: Starting The Proxmox VE cluster filesystem...
Mar 13 15:12:16 [SERVERNAME] pvecm[2082]: Experimental "my" subs not enabled at /usr/share/perl5/PVE/APIClient/LWP.pm line 278, <DATA> line 755.
Mar 13 15:12:16 [SERVERNAME] pvecm[2082]: Compilation failed in require at /usr/share/perl5/PVE/API2/ClusterConfig.pm line 12, <DATA> line 755.
Mar 13 15:12:16 [SERVERNAME] pvecm[2082]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/ClusterConfig.pm line 12, <DATA> line 755.
Mar 13 15:12:16 [SERVERNAME] pvecm[2082]: Compilation failed in require at /usr/share/perl5/PVE/CLI/pvecm.pm line 15, <DATA> line 755.
Mar 13 15:12:16 [SERVERNAME] pvecm[2082]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/CLI/pvecm.pm line 15, <DATA> line 755.
Mar 13 15:12:16 [SERVERNAME] pvecm[2082]: Compilation failed in require at /usr/bin/pvecm line 8, <DATA> line 755.
Mar 13 15:12:16 [SERVERNAME] pvecm[2082]: BEGIN failed--compilation aborted at /usr/bin/pvecm line 8, <DATA> line 755.
Mar 13 15:12:16 [SERVERNAME] systemd[1]: Started The Proxmox VE cluster filesystem.

● pvesr.timer - Proxmox VE replication runner
   Loaded: loaded (/lib/systemd/system/pvesr.timer; enabled; vendor preset: enabled)
   Active: active (waiting) since Sat 2021-03-13 15:12:10 EST; 1min 19s ago

Mar 13 15:12:10 [SERVERNAME] systemd[1]: Started Proxmox VE replication runner.

● pvenetcommit.service - Commit Proxmox VE network changes
   Loaded: loaded (/lib/systemd/system/pvenetcommit.service; enabled; vendor preset: enabled)
   Active: active (exited) since Sat 2021-03-13 15:12:08 EST; 1min 21s ago
  Process: 1077 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
  Process: 1017 ExecStartPre=/bin/mv /etc/network/interfaces.new /etc/network/interfaces (code=exited, status=1/FAILURE)
  Process: 1013 ExecStartPre=/bin/rm -f /etc/openvswitch/conf.db (code=exited, status=0/SUCCESS)
 Main PID: 1077 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   Memory: 0B
      CPU: 0
   CGroup: /system.slice/pvenetcommit.service

Mar 13 15:12:08 [SERVERNAME] systemd[1]: Starting Commit Proxmox VE network changes...
Mar 13 15:12:08 [SERVERNAME] mv[1017]: /bin/mv: cannot stat '/etc/network/interfaces.new': No such file or directory
Mar 13 15:12:08 [SERVERNAME] systemd[1]: Started Commit Proxmox VE network changes.

● pve-guests.service - PVE guests
   Loaded: loaded (/lib/systemd/system/pve-guests.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2021-03-13 15:12:19 EST; 1min 10s ago
  Process: 2279 ExecStart=/usr/bin/pvesh --nooutput create /nodes/localhost/startall (code=exited, status=255)
 Main PID: 2279 (code=exited, status=255)
      CPU: 536ms

Mar 13 15:12:19 [SERVERNAME] pvesh[2279]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Mar 13 15:12:19 [SERVERNAME] pvesh[2279]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Mar 13 15:12:19 [SERVERNAME] pvesh[2279]: Compilation failed in require at /usr/share/perl5/PVE/CLI/pvesh.pm line 16.
Mar 13 15:12:19 [SERVERNAME] pvesh[2279]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/CLI/pvesh.pm line 16.
Mar 13 15:12:19 [SERVERNAME] pvesh[2279]: Compilation failed in require at /usr/bin/pvesh line 6.
Mar 13 15:12:19 [SERVERNAME] pvesh[2279]: BEGIN failed--compilation aborted at /usr/bin/pvesh line 6.
Mar 13 15:12:19 [SERVERNAME] systemd[1]: pve-guests.service: Main process exited, code=exited, status=255/n/a
Mar 13 15:12:19 [SERVERNAME] systemd[1]: Failed to start PVE guests.
Mar 13 15:12:19 [SERVERNAME] systemd[1]: pve-guests.service: Unit entered failed state.
Mar 13 15:12:19 [SERVERNAME] systemd[1]: pve-guests.service: Failed with result 'exit-code'.

● pve-daily-update.timer - Daily PVE download activities
   Loaded: loaded (/lib/systemd/system/pve-daily-update.timer; enabled; vendor preset: enabled)
   Active: active (waiting) since Sat 2021-03-13 15:12:10 EST; 1min 19s ago
  Process: 1017 ExecStartPre=/bin/mv /etc/network/interfaces.new /etc/network/interfaces (code=exited, status=1/FAILURE)
  Process: 1013 ExecStartPre=/bin/rm -f /etc/openvswitch/conf.db (code=exited, status=0/SUCCESS)
 Main PID: 1077 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   Memory: 0B
      CPU: 0
   CGroup: /system.slice/pvenetcommit.service

Mar 13 15:12:08 [SERVERNAME] systemd[1]: Starting Commit Proxmox VE network changes...
Mar 13 15:12:08 [SERVERNAME] mv[1017]: /bin/mv: cannot stat '/etc/network/interfaces.new': No such file or directory
Mar 13 15:12:08 [SERVERNAME] systemd[1]: Started Commit Proxmox VE network changes.

● pve-guests.service - PVE guests
   Loaded: loaded (/lib/systemd/system/pve-guests.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2021-03-13 15:12:19 EST; 1min 10s ago
  Process: 2279 ExecStart=/usr/bin/pvesh --nooutput create /nodes/localhost/startall (code=exited, status=255)
 Main PID: 2279 (code=exited, status=255)
      CPU: 536ms

Mar 13 15:12:19 [SERVERNAME] pvesh[2279]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Mar 13 15:12:19 [SERVERNAME] pvesh[2279]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Mar 13 15:12:19 [SERVERNAME] pvesh[2279]: Compilation failed in require at /usr/share/perl5/PVE/CLI/pvesh.pm line 16.
Mar 13 15:12:19 [SERVERNAME] pvesh[2279]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/CLI/pvesh.pm line 16.
Mar 13 15:12:19 [SERVERNAME] pvesh[2279]: Compilation failed in require at /usr/bin/pvesh line 6.
Mar 13 15:12:19 [SERVERNAME] pvesh[2279]: BEGIN failed--compilation aborted at /usr/bin/pvesh line 6.
Mar 13 15:12:19 [SERVERNAME] systemd[1]: pve-guests.service: Main process exited, code=exited, status=255/n/a
Mar 13 15:12:19 [SERVERNAME] systemd[1]: Failed to start PVE guests.
Mar 13 15:12:19 [SERVERNAME] systemd[1]: pve-guests.service: Unit entered failed state.
Mar 13 15:12:19 [SERVERNAME] systemd[1]: pve-guests.service: Failed with result 'exit-code'.

● pve-daily-update.timer - Daily PVE download activities
   Loaded: loaded (/lib/systemd/system/pve-daily-update.timer; enabled; vendor preset: enabled)
   Active: active (waiting) since Sat 2021-03-13 15:12:10 EST; 1min 19s ago

Mar 13 15:12:10 [SERVERNAME] systemd[1]: Started Daily PVE download activities.

● pve-ha-crm.service - PVE Cluster Ressource Manager Daemon
   Loaded: loaded (/lib/systemd/system/pve-ha-crm.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2021-03-13 15:12:18 EST; 1min 12s ago
  Process: 2176 ExecStart=/usr/sbin/pve-ha-crm start (code=exited, status=0/SUCCESS)
 Main PID: 2219 (pve-ha-crm)
    Tasks: 1 (limit: 4915)
   Memory: 79.0M
      CPU: 529ms
   CGroup: /system.slice/pve-ha-crm.service
           └─2219 pve-ha-crm

Mar 13 15:12:17 [SERVERNAME] systemd[1]: Starting PVE Cluster Ressource Manager Daemon...
Mar 13 15:12:18 [SERVERNAME] pve-ha-crm[2219]: starting server
Mar 13 15:12:18 [SERVERNAME] pve-ha-crm[2219]: status change startup => wait_for_quorum
Mar 13 15:12:18 [SERVERNAME] systemd[1]: Started PVE Cluster Ressource Manager Daemon.

● pve-storage.target - PVE Storage Target
   Loaded: loaded (/lib/systemd/system/pve-storage.target; static; vendor preset: enabled)
   Active: active since Sat 2021-03-13 15:12:13 EST; 1min 16s ago

Mar 13 15:12:13 [SERVERNAME] systemd[1]: Reached target PVE Storage Target.

● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2021-03-13 15:12:18 EST; 1min 11s ago
  Process: 2183 ExecStart=/usr/bin/pveproxy start (code=exited, status=255)
      CPU: 562ms

Mar 13 15:12:18 [SERVERNAME] pveproxy[2183]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Mar 13 15:12:18 [SERVERNAME] pveproxy[2183]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Mar 13 15:12:18 [SERVERNAME] pveproxy[2183]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line 15.
Mar 13 15:12:18 [SERVERNAME] pveproxy[2183]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 15.
Mar 13 15:12:18 [SERVERNAME] pveproxy[2183]: Compilation failed in require at /usr/bin/pveproxy line 11.
Mar 13 15:12:18 [SERVERNAME] pveproxy[2183]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Mar 13 15:12:18 [SERVERNAME] systemd[1]: pveproxy.service: Control process exited, code=exited status=255
Mar 13 15:12:18 [SERVERNAME] systemd[1]: Failed to start PVE API Proxy Server.
Mar 13 15:12:18 [SERVERNAME] systemd[1]: pveproxy.service: Unit entered failed state.
Mar 13 15:12:18 [SERVERNAME] systemd[1]: pveproxy.service: Failed with result 'exit-code'.
 
Code: 
proxmox-ve: 6.3-1 (running kernel: 5.4.103-1-pve)
pve-manager: 5.4-15 (running version: 5.4-15/d0ec33c6)
pve-kernel-5.4: 6.3-7
pve-kernel-helper: 6.3-7
pve-kernel-5.4.103-1-pve: 5.4.103-1
pve-kernel-4.15: 5.4-19
...
The versions are messed up. Your proxmox-ve is later version than mine, the others look like very old versions. What kind of system is this and how was it installed? When was it installed?
 
Tapio Lehtonen said:
The versions are messed up. Your proxmox-ve is later version than mine, the others look like very old versions. What kind of system is this and how was it installed? When was it installed?
Click to expand...
This is just a normal Proxmox VE install. I set it up about 2 years ago and this is the first time I've updated. It would seem it is time to burn it to the ground and just start over. I have no clue what to do from here.

I may try putting another drive in the box and installing PVE there. Then maybe I can recover my VMs. I don't know.

Thanks for the help!
 
NightHammer said:
This is just a normal Proxmox VE install. I set it up about 2 years ago and this is the first time I've updated. It would seem it is time to burn it to the ground and just start over. I have no clue what to do from here.
Click to expand...

Updated with what repositories? Please post actually the output requested, 1:1.

Bash: 
apt update

head -n -0 /etc/apt/sources.list /etc/apt/sources.list.d/*
so that we can get some idea how you tried to upgrade.
 
When I updated the sources.list file with the fr.cdn.proxmox.com repo I figured I needed to update the buster to stretch. I am beginning to think this was the wrong thing.

apt update
Code: 
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://ftp.us.debian.org/debian stretch InRelease
Hit:3 http://fr.cdn.proxmox.com/debian/pve stretch InRelease
Hit:4 http://ftp.us.debian.org/debian stretch-updates InRelease
Hit:5 http://ftp.us.debian.org/debian stretch Release
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.


head -n -0 /etc/apt/sources.list /etc/apt/sources.list.d/*
Code: 
==> /etc/apt/sources.list <==
deb http://ftp.us.debian.org/debian stretch main contrib

deb http://ftp.us.debian.org/debian stretch-updates main contrib

# PVE pve-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian/pve stretch pve-no-subscription



# security updates
deb http://security.debian.org stretch/updates main contrib

==> /etc/apt/sources.list.d/pve-enterprise.list <==
#deb https://enterprise.proxmox.com/debian/pve stretch pve-enterprise

==> /etc/apt/sources.list.d/pve-no-subscription.list <==
#deb http://download.proxmox.com/debian/pve stretch pve-no-subscription
 
NightHammer said:
When I updated the sources.list file with the fr.cdn.proxmox.com repo I figured I needed to update the buster to stretch. I am beginning to think this was the wrong thing.
Click to expand...
No that was actually a good thing in your case, but did you run on update session with "buster" in place? As it seems like you're in a half done upgrade state, where Proxmox VE repo was (at one time) on buster but the Debian ones were not.

Anyway, before going for the resetup of that machine I'd go for a Hail Mary dist-upgrade attempt, as trying to downgrade may break even more than going forward.

1. Safe a backup any disk/data you would like to keep on some external medium (USB pen drive or the like)
2. Follow https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0 but the pve5to6 checker script may a bit confused; albeit it may be still valuable to run it once.
 
  • Like
Reactions: NightHammer
t.lamprecht said:
No that was actually a good thing in your case, but did you run on update session with "buster" in place? As it seems like you're in a half done upgrade state, where Proxmox VE repo was (at one time) on buster but the Debian ones were not.

Anyway, before going for the resetup of that machine I'd go for a Hail Mary dist-upgrade attempt, as trying to downgrade may break even more than going forward.

1. Safe a backup any disk/data you would like to keep on some external medium (USB pen drive or the like)
2. Follow https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0 but the pve5to6 checker script may a bit confused; albeit it may be still valuable to run it once.
Click to expand...
YES!!!!

This worked. I am back up and fully running. Thank you!
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back