Fehler nach Upgrade von 6 auf 7

O

oketech

New Member
Apr 5, 2021
2
0
1
30
Schönen guten Abend.

Ich erhalte die folgende Fehlermeldung nach einem Update von 6 auf 7 und dem ausführen von "apt upgrade":
Diff: 
Setting up pve-manager (6.4-13) ...
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)

journal -xe sagt mir das folgendes:

Code: 
-- Subject: A start job for unit user@0.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit user@0.service has begun execution.
--
-- The job identifier is 7983.
Jan 09 21:55:19 solarsystem systemd[287411]: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file: No such file or directory
Jan 09 21:55:19 solarsystem systemd[287411]: PAM adding faulty module: pam_unix.so
Jan 09 21:55:19 solarsystem systemd[287411]: PAM failed: Authentication failure
Jan 09 21:55:19 solarsystem systemd[287411]: user@0.service: Failed to set up PAM session: Operation not permitted
Jan 09 21:55:19 solarsystem systemd[287411]: user@0.service: Failed at step PAM spawning /lib/systemd/systemd: Operation not permitted
-- Subject: Process /lib/systemd/systemd could not be executed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The process /lib/systemd/systemd could not be executed and failed.
--
-- The error number returned by this process is ERRNO.
Jan 09 21:55:19 solarsystem systemd[1]: user@0.service: Failed with result 'protocol'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit user@0.service has entered the 'failed' state with result 'protocol'.
Jan 09 21:55:19 solarsystem systemd[1]: Failed to start User Manager for UID 0.
-- Subject: A start job for unit user@0.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit user@0.service has finished with a failure.
--
-- The job identifier is 7983 and the job result is failed.
Jan 09 21:55:19 solarsystem systemd[1]: Started Session 12 of user root.
-- Subject: A start job for unit session-12.scope has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit session-12.scope has finished successfully.
--
-- The job identifier is 7976.
Jan 09 21:55:21 solarsystem systemd[1]: Reloading.
Jan 09 21:55:21 solarsystem systemd[1]: /lib/systemd/system/logrotate.service:16: Unknown lvalue 'ProtectClock' in section 'Service', ignoring
Jan 09 21:55:21 solarsystem systemd[1]: /lib/systemd/system/logrotate.service:18: Unknown lvalue 'ProtectHostname' in section 'Service', ignoring
Jan 09 21:55:21 solarsystem systemd[1]: /lib/systemd/system/logrotate.service:19: Unknown lvalue 'ProtectKernelLogs' in section 'Service', ignoring
Jan 09 21:55:22 solarsystem systemd[1]: Reloading PVE API Daemon.
-- Subject: A reload job for unit pvedaemon.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A reload job for unit pvedaemon.service has begun execution.
--
-- The job identifier is 8062.
Jan 09 21:55:22 solarsystem pvedaemon[287513]: Undefined subroutine &PVE::Syscall::SYS_open_tree called at /usr/share/perl5/PVE/Syscall.pm line 8.
Jan 09 21:55:22 solarsystem pvedaemon[287513]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Syscall.pm line 77.
Jan 09 21:55:22 solarsystem pvedaemon[287513]: Compilation failed in require at /usr/share/perl5/PVE/Tools.pm line 31.
Jan 09 21:55:22 solarsystem pvedaemon[287513]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Tools.pm line 31.
Jan 09 21:55:22 solarsystem pvedaemon[287513]: Compilation failed in require at /usr/share/perl5/PVE/JSONSchema.pm line 10.
Jan 09 21:55:22 solarsystem pvedaemon[287513]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/JSONSchema.pm line 10.
Jan 09 21:55:22 solarsystem pvedaemon[287513]: Compilation failed in require at /usr/share/perl5/PVE/INotify.pm line 20.
Jan 09 21:55:22 solarsystem pvedaemon[287513]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/INotify.pm line 20.
Jan 09 21:55:22 solarsystem pvedaemon[287513]: Compilation failed in require at /usr/share/perl5/PVE/Daemon.pm line 22.
Jan 09 21:55:22 solarsystem pvedaemon[287513]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Daemon.pm line 22.
Jan 09 21:55:22 solarsystem pvedaemon[287513]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvedaemon.pm line 7.
Jan 09 21:55:22 solarsystem pvedaemon[287513]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvedaemon.pm line 7.
Jan 09 21:55:22 solarsystem pvedaemon[287513]: Compilation failed in require at /usr/bin/pvedaemon line 11.
Jan 09 21:55:22 solarsystem pvedaemon[287513]: BEGIN failed--compilation aborted at /usr/bin/pvedaemon line 11.
Jan 09 21:55:22 solarsystem systemd[1]: pvedaemon.service: Control process exited, code=exited, status=255/EXCEPTION
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecReload= process belonging to unit pvedaemon.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 255.
Jan 09 21:55:22 solarsystem systemd[1]: Reload failed for PVE API Daemon.
-- Subject: A reload job for unit pvedaemon.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A reload job for unit pvedaemon.service has finished.
--
-- The job identifier is 8062 and the job result is failed.

Ein "dist-update" möchte mir proxmox-ve runterschmeißen:

Code: 
W: (pve-apt-hook) !! WARNING !!
W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'!
W: (pve-apt-hook)
W: (pve-apt-hook) If you really want to permanently remove 'proxmox-ve' from your system, run the following command
W: (pve-apt-hook)       touch '/please-remove-proxmox-ve'
W: (pve-apt-hook) run apt purge proxmox-ve to remove the meta-package
W: (pve-apt-hook) and repeat your apt invocation.
W: (pve-apt-hook)
W: (pve-apt-hook) If you are unsure why 'proxmox-ve' would be removed, please verify
W: (pve-apt-hook)       - your APT repository settings
W: (pve-apt-hook)       - that you are using 'apt full-upgrade' to upgrade your system
E: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (1)
E: Failure running script /usr/share/proxmox-ve/pve-apt-hook

Hat jemand von euch eine Idee, wo es klemmen könnte?

Meine "/etc/apt/sources.list" sieht wie folgt aus:

Code: 
deb http://ftp.debian.org/debian bullseye main contrib

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


# PVE pve-no-subscription repository provided by proxmox.com,

# NOT recommended for production use

deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription


# security updates

deb http://security.debian.org/debian-security bullseye-security main contrib

Ich freue mich über jeden Input von euch!

Danke und noch einen schönen Abend
 
Last edited:
bitte vollen output von 'pveversion -v', 'apt update' und 'apt full-upgrade' posten (bei letzterem wenn proxmox-ve entfernt werden soll abbrechen)
 
Hi Fabian,

danke für deine schnelle Antwort.

Als ich gerade meinen Output posten wollte, habe ich festgestellt, dass sich noch in meiner apt-list ein buster release versteckt hat. Nun hat alles wunderbar funktioniert!

Danke dir für deinen Input!

Viele Grüße
Oke
 
You must log in or register to reply here.
Top Bottom