Hi all,
apt-get update && apt-get dist-upgrade this morning : bad luck!
Here is my pveversion -v :
[root@SV-VR-HB-KVM6-ENC1-ZS:~]# pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.18-11-pve)
pve-manager: 5.4-4 (running version: 5.4-4/97a96833)
pve-kernel-4.15: 5.4-1
pve-kernel-4.13: 5.2-2
pve-kernel-4.15.18-13-pve: 4.15.18-37
pve-kernel-4.15.18-12-pve: 4.15.18-36
pve-kernel-4.15.18-11-pve: 4.15.18-34
pve-kernel-4.15.18-10-pve: 4.15.18-32
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.18-8-pve: 4.15.18-28
pve-kernel-4.15.18-7-pve: 4.15.18-27
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.18-2-pve: 4.15.18-21
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.13.16-4-pve: 4.13.16-51
pve-kernel-4.10.15-1-pve: 4.10.15-15
pve-kernel-4.10.11-1-pve: 4.10.11-9
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-51
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-41
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-26
pve-cluster: 5.0-36
pve-container: 2.0-37
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-20
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-3
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-50
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
I use Ayufan diff backup patches, so I usually do immediately after any update :
apt-get install --reinstall libpve-storage-perl pve-manager qemu-server lxc-pve pve-container
Then apply patch. Nothing special here.
I also tried without applying patch, same problem :
- nothing listens on port 8006,
- pve-manager active (exited)
- can't restart pve-manager
I noticed that pveproxy failed with compilation problems :
[root@SV-VR-HB-KVM6-ENC1-ZS:/var/log]# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-04-25 09:12:12 CEST; 13min ago
Main PID: 19852 (code=exited, status=0/SUCCESS)
CPU: 1.298s
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS pveproxy[8763]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS pveproxy[8763]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS pveproxy[8763]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS pveproxy[8763]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS pveproxy[8763]: Compilation failed in require at /usr/bin/pveproxy line 11.
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS pveproxy[8763]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS systemd[1]: pveproxy.service: Control process exited, code=exited status=255
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS systemd[1]: Failed to start PVE API Proxy Server.
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS systemd[1]: pveproxy.service: Unit entered failed state.
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Any idea?
Thx,
Christophe.
apt-get update && apt-get dist-upgrade this morning : bad luck!
Here is my pveversion -v :
[root@SV-VR-HB-KVM6-ENC1-ZS:~]# pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.18-11-pve)
pve-manager: 5.4-4 (running version: 5.4-4/97a96833)
pve-kernel-4.15: 5.4-1
pve-kernel-4.13: 5.2-2
pve-kernel-4.15.18-13-pve: 4.15.18-37
pve-kernel-4.15.18-12-pve: 4.15.18-36
pve-kernel-4.15.18-11-pve: 4.15.18-34
pve-kernel-4.15.18-10-pve: 4.15.18-32
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.18-8-pve: 4.15.18-28
pve-kernel-4.15.18-7-pve: 4.15.18-27
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.18-2-pve: 4.15.18-21
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.13.16-4-pve: 4.13.16-51
pve-kernel-4.10.15-1-pve: 4.10.15-15
pve-kernel-4.10.11-1-pve: 4.10.11-9
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-51
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-41
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-26
pve-cluster: 5.0-36
pve-container: 2.0-37
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-20
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-3
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-50
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
I use Ayufan diff backup patches, so I usually do immediately after any update :
apt-get install --reinstall libpve-storage-perl pve-manager qemu-server lxc-pve pve-container
Then apply patch. Nothing special here.
I also tried without applying patch, same problem :
- nothing listens on port 8006,
- pve-manager active (exited)
- can't restart pve-manager
I noticed that pveproxy failed with compilation problems :
[root@SV-VR-HB-KVM6-ENC1-ZS:/var/log]# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-04-25 09:12:12 CEST; 13min ago
Main PID: 19852 (code=exited, status=0/SUCCESS)
CPU: 1.298s
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS pveproxy[8763]: Compilation failed in require at /usr/share/perl5/PVE/API2.pm line 13.
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS pveproxy[8763]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2.pm line 13.
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS pveproxy[8763]: Compilation failed in require at /usr/share/perl5/PVE/Service/pveproxy.pm line
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS pveproxy[8763]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pveproxy.pm
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS pveproxy[8763]: Compilation failed in require at /usr/bin/pveproxy line 11.
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS pveproxy[8763]: BEGIN failed--compilation aborted at /usr/bin/pveproxy line 11.
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS systemd[1]: pveproxy.service: Control process exited, code=exited status=255
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS systemd[1]: Failed to start PVE API Proxy Server.
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS systemd[1]: pveproxy.service: Unit entered failed state.
Apr 25 09:12:12 SV-VR-HB-KVM6-ENC1-ZS systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Any idea?
Thx,
Christophe.