Hallo,
wir wollten heute eigentlich neuen Speicher in unsere Proxmox-Server einbauen und ich wollte die Gelegenheit nutzen noch einmal apt-get upgrade zu fahren, in der Erwartung, daß es sicherlich einen neuen angepassten Proxmox-Kernel geben würde. Ich bekomme folgende Fehlermeldung. Gibt es eigentlich eine zentrale Komponente von Proxmox, deren Versionsnummer als Indikator für den Stand der anderen installierten Komponenten von PVE dienen kann?
root@zeus:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
libintl-perl libintl-xs-perl libmodule-find-perl libmodule-scandeps-perl
libproc-processtable-perl libsort-naturally-perl libterm-readkey-perl
Use 'apt autoremove' to remove them.
The following packages have been kept back:
libpve-common-perl libpve-storage-perl proxmox-ve pve-manager pve-qemu-kvm qemu-server
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up pve-manager (6.1-11) ...
Job for pvedaemon.service failed.
See "systemctl status pvedaemon.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@zeus:~# systemctl status pvedaemon
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2020-04-09 14:45:13 CEST; 7 months 9 days ago
Process: 3426 ExecReload=/usr/bin/pvedaemon restart (code=exited, status=255/EXCEPTION)
Main PID: 1915 (pvedaemon)
Tasks: 4 (limit: 4915)
Memory: 174.1M
CGroup: /system.slice/pvedaemon.service
├─ 1915 pvedaemon
├─ 7520 pvedaemon worker
├─ 9238 pvedaemon worker
└─26993 pvedaemon worker
Nov 18 14:55:10 zeus pvedaemon[3426]: Compilation failed in require at /usr/share/perl5/PVE/API2
Nov 18 14:55:10 zeus pvedaemon[3426]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/
Nov 18 14:55:10 zeus pvedaemon[3426]: Compilation failed in require at /usr/share/perl5/PVE/API2
Nov 18 14:55:10 zeus pvedaemon[3426]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/
Nov 18 14:55:10 zeus pvedaemon[3426]: Compilation failed in require at /usr/share/perl5/PVE/Serv
Nov 18 14:55:10 zeus pvedaemon[3426]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/
Nov 18 14:55:10 zeus pvedaemon[3426]: Compilation failed in require at /usr/bin/pvedaemon line 1
Nov 18 14:55:10 zeus pvedaemon[3426]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon li
Nov 18 14:55:10 zeus systemd[1]: pvedaemon.service: Control process exited, code=exited, status=
Nov 18 14:55:10 zeus systemd[1]: Reload failed for PVE API Daemon.
wir wollten heute eigentlich neuen Speicher in unsere Proxmox-Server einbauen und ich wollte die Gelegenheit nutzen noch einmal apt-get upgrade zu fahren, in der Erwartung, daß es sicherlich einen neuen angepassten Proxmox-Kernel geben würde. Ich bekomme folgende Fehlermeldung. Gibt es eigentlich eine zentrale Komponente von Proxmox, deren Versionsnummer als Indikator für den Stand der anderen installierten Komponenten von PVE dienen kann?
root@zeus:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
libintl-perl libintl-xs-perl libmodule-find-perl libmodule-scandeps-perl
libproc-processtable-perl libsort-naturally-perl libterm-readkey-perl
Use 'apt autoremove' to remove them.
The following packages have been kept back:
libpve-common-perl libpve-storage-perl proxmox-ve pve-manager pve-qemu-kvm qemu-server
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up pve-manager (6.1-11) ...
Job for pvedaemon.service failed.
See "systemctl status pvedaemon.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@zeus:~# systemctl status pvedaemon
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2020-04-09 14:45:13 CEST; 7 months 9 days ago
Process: 3426 ExecReload=/usr/bin/pvedaemon restart (code=exited, status=255/EXCEPTION)
Main PID: 1915 (pvedaemon)
Tasks: 4 (limit: 4915)
Memory: 174.1M
CGroup: /system.slice/pvedaemon.service
├─ 1915 pvedaemon
├─ 7520 pvedaemon worker
├─ 9238 pvedaemon worker
└─26993 pvedaemon worker
Nov 18 14:55:10 zeus pvedaemon[3426]: Compilation failed in require at /usr/share/perl5/PVE/API2
Nov 18 14:55:10 zeus pvedaemon[3426]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/
Nov 18 14:55:10 zeus pvedaemon[3426]: Compilation failed in require at /usr/share/perl5/PVE/API2
Nov 18 14:55:10 zeus pvedaemon[3426]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/
Nov 18 14:55:10 zeus pvedaemon[3426]: Compilation failed in require at /usr/share/perl5/PVE/Serv
Nov 18 14:55:10 zeus pvedaemon[3426]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/
Nov 18 14:55:10 zeus pvedaemon[3426]: Compilation failed in require at /usr/bin/pvedaemon line 1
Nov 18 14:55:10 zeus pvedaemon[3426]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon li
Nov 18 14:55:10 zeus systemd[1]: pvedaemon.service: Control process exited, code=exited, status=
Nov 18 14:55:10 zeus systemd[1]: Reload failed for PVE API Daemon.
