Power failure and now GUI doesn't work

E

Enrique Garcia Polo

Well-Known Member
Jun 29, 2018
33
1
48
43
Hi everybody
I have a Proxmox 8.3.3 node working well until a powerfailure. When I have recovered the power I got an error on Boot, I use fsck to fix inodes and continue booting but GUI.
Error "Failed to start pveproxy.service" al boot

If I do journalctl -xeu pveproxy.service

Feb 20 23:18:49 pve systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
░░ Subject: A start job for unit pveproxy.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has begun execution.
░░
░░ The job identifier is 1381.
Feb 20 23:18:50 pve pveproxy[2558]: Can't locate Template.pm in @INC (you may need to install the Template module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_>
Feb 20 23:18:50 pve pveproxy[2558]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 9.
Feb 20 23:18:50 pve pveproxy[2558]: Compilation failed in require at /usr/bin/pveproxy line 11.
Feb 20 23:18:50 pve pveproxy[2558]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Feb 20 23:18:50 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit pveproxy.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
Feb 20 23:18:50 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.

The vms work well but I havn't got WEB GUI

Any idea?
 
Hello Enrique! Could you please try to run apt reinstall pve-manager?

If that doesn't help, please post the output of pveversion -v, as this command should also show if some other packages are not correctly installed.
 
  • Like
Reactions: Kingneutron
l.leahu-vladucu said:
Hello Enrique! Could you please try to run apt reinstall pve-manager?

If that doesn't help, please post the output of pveversion -v, as this command should also show if some other packages are not correctly installed.
Click to expand...
Thank you l.leahu-vladucu


root@pve:~# apt reinstall pve-manager
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 549 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://download.proxmox.com/debian bookworm/pve-no-subscription amd64 pve-manager all 8.3.4 [549 kB]
Fetched 549 kB in 1s (740 kB/s)
dpkg: warning: files list file for package 'libavfilter8:amd64' missing; assuming package has no files currently installed
(Reading database ... 95919 files and directories currently installed.)
Preparing to unpack .../pve-manager_8.3.4_all.deb ...
Unpacking pve-manager (8.3.4) over (8.3.4) ...
Setting up pve-manager (8.3.4) ...
Job for pveproxy.service failed because the control process exited with error code.
See "systemctl status pveproxy.service" and "journalctl -xeu pveproxy.service" for details.
Processing triggers for man-db (2.11.2-2) ...

-------------------------------------------


root@pve:~# pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.12-8-pve)
pve-manager: 8.3.4 (running version: 8.3.4/65224a0f9cd294a3)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-8
proxmox-kernel-6.8.12-8-pve-signed: 6.8.12-8
proxmox-kernel-6.8.12-7-pve-signed: 6.8.12-7
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 16.2.15+ds-0+deb12u1
corosync: 3.1.7-pve3
criu: 3.17.1-2+deb12u1
dnsmasq: 2.90-4~deb12u1
glusterfs-client: 10.3-5
ifupdown: residual config
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.2.0
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.1
libpve-storage-perl: 8.3.3
libqb0: 1.0.5-1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
openvswitch-switch: 3.1.0-2+deb12u1
proxmox-backup-client: 3.3.3-1
proxmox-backup-file-restore: 3.3.3-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.4
pve-cluster: 8.0.10
pve-container: 5.2.4
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-3
pve-ha-manager: 4.0.6
pve-i18n: 3.3.3
pve-qemu-kvm: 9.0.2-5
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.8
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve1
 
I strongly recommend investing in a UPS. And setup NUT client.

https://www.thesmarthomebook.com/2022/09/02/setting-up-monitor-your-ups-proxmox-home-assistant/

.

If all else fails, backup your config, reinstall PVE ( NOTE the target disk for boot/root will be wiped! ) and restore LXC/VMs from backup (if you don't have it yet, setup PBS on separate hardware and take advantage of dedup)

https://github.com/kneutron/ansitest/tree/master/proxmox

Look into the bkpcrit script, point it to external disk / NAS, run it nightly in cron.
 
l.leahu-vladucu said:
Do you still get the same error message as before when calling journalctl -xeu pveproxy.service? Please also try to do apt reinstall libavfilter8.
Click to expand...
The problem remainds:

root@pve:~# apt reinstall libavfilter8
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/3,706 kB of archives.
After this operation, 0 B of additional disk space will be used.
dpkg: warning: files list file for package 'libavfilter8:amd64' missing; assuming package has no files currently installed
(Reading database ... 95919 files and directories currently installed.)
Preparing to unpack .../libavfilter8_7%3a5.1.6-0+deb12u1_amd64.deb ...
Unpacking libavfilter8:amd64 (7:5.1.6-0+deb12u1) over (7:5.1.6-0+deb12u1) ...
Setting up libavfilter8:amd64 (7:5.1.6-0+deb12u1) ...
Processing triggers for libc-bin (2.36-9+deb12u9) ...
root@pve:~# systemctl start pveproxy.service
Job for pveproxy.service failed because the control process exited with error code.
See "systemctl status pveproxy.service" and "journalctl -xeu pveproxy.service" for details.


root@pve:~# systemctl status pveproxy.service
× pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Fri 2025-02-21 18:51:11 CET; 49s ago
Process: 93171 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 93173 ExecStart=/usr/bin/pveproxy start (code=exited, status=2)
CPU: 453ms

Feb 21 18:51:11 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
Feb 21 18:51:11 pve systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
Feb 21 18:51:11 pve systemd[1]: pveproxy.service: Start request repeated too quickly.
Feb 21 18:51:11 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Feb 21 18:51:11 pve systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.


root@pve:~# journalctl -xeu pveproxy.service
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has begun execution.
░░
░░ The job identifier is 5340.
Feb 21 18:51:11 pve pveproxy[93173]: Can't locate Template.pm in @INC (you may need to install the Template module) (@INC co>
Feb 21 18:51:11 pve pveproxy[93173]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm line 9.
Feb 21 18:51:11 pve pveproxy[93173]: Compilation failed in require at /usr/bin/pveproxy line 11.
Feb 21 18:51:11 pve pveproxy[93173]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Feb 21 18:51:11 pve systemd[1]: pveproxy.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit pveproxy.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
Feb 21 18:51:11 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
Feb 21 18:51:11 pve systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
░░ Subject: A start job for unit pveproxy.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 5340 and the job result is failed.
Feb 21 18:51:11 pve systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit pveproxy.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Feb 21 18:51:11 pve systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
░░ Subject: A stop job for unit pveproxy.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit pveproxy.service has finished.
░░
░░ The job identifier is 5459 and the job result is done.
Feb 21 18:51:11 pve systemd[1]: pveproxy.service: Start request repeated too quickly.
Feb 21 18:51:11 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
Feb 21 18:51:11 pve systemd[1]: Failed to start pveproxy.service - PVE API Proxy Server.
░░ Subject: A start job for unit pveproxy.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 5459 and the job result is failed.
root@pve:~#
 
Last edited:
Kingneutron said:
I strongly recommend investing in a UPS. And setup NUT client.

https://www.thesmarthomebook.com/2022/09/02/setting-up-monitor-your-ups-proxmox-home-assistant/

.

If all else fails, backup your config, reinstall PVE ( NOTE the target disk for boot/root will be wiped! ) and restore LXC/VMs from backup (if you don't have it yet, setup PBS on separate hardware and take advantage of dedup)

https://github.com/kneutron/ansitest/tree/master/proxmox

Look into the bkpcrit script, point it to external disk / NAS, run it nightly in cron.
Click to expand...
Tanks,

I have an APC BACK-UPS 950 and it shutdown the server but when I connect the power the UPS was empty and the power fail again without shutdown system.

I also have a XPenology in differnet hardware but connected to the same UPS and It it broken too, DSM corrupted but data is OK I checked booting the Xpenology with live linux and the data is there.
 
You must log in or register to reply here.
Top Bottom