pve-manager error after apt-get upgrade

I

informant

Renowned Member
Jan 31, 2012
793
10
83
Hi, afterapt-get upgrade i have following error... what can i do here? regards

pve-manager (4.4-12) wird eingerichtet ...
Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.
dpkg: Fehler beim Bearbeiten des Paketes pve-manager (--configure):
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)

journalctl -xn
-- Logs begin at Mo 2017-02-13 15:01:51 CET, end at Mo 2017-02-20 10:13:49 CET. --
Feb 20 10:13:49 pegasus kernel: ffff8802339a0000 ffff880234aa43ac ffff8800b3ef3300 00000000ffffffff
Feb 20 10:13:49 pegasus kernel: ffff880234aa43b0 ffff88023399fe10 ffffffff81858155 ffff880234aa43a8
Feb 20 10:13:49 pegasus kernel: Call Trace:
Feb 20 10:13:49 pegasus kernel: [<ffffffff81858155>] schedule+0x35/0x80
Feb 20 10:13:49 pegasus kernel: [<ffffffff8185840e>] schedule_preempt_disabled+0xe/0x10
Feb 20 10:13:49 pegasus kernel: [<ffffffff8185a109>] __mutex_lock_slowpath+0xb9/0x130
Feb 20 10:13:49 pegasus kernel: [<ffffffff8185a19f>] mutex_lock+0x1f/0x30
Feb 20 10:13:49 pegasus kernel: [<ffffffff8121f13a>] filename_create+0x7a/0x160
Feb 20 10:13:49 pegasus kernel: [<ffffffff812200d3>] SyS_mkdir+0x53/0x100
Feb 20 10:13:49 pegasus kernel: [<ffffffff8185c276>] entry_SYSCALL_64_fastpath+0x16/0x75

systemctl status pvedaemon.service
* pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
Active: active (running) since Mo 2017-02-13 15:02:06 CET; 6 days ago
Main PID: 1333 (pvedaemon)
CGroup: /system.slice/pvedaemon.service
|- 1333 pvedaemon
|-16515 task UPID:pegasus:00004083:037F8BC9:58AAB0E6:vncproxy:5531:admin@pve:
|-16516 /bin/nc6 -l -p 5900 -w 10 -e /usr/bin/ssh -T -o BatchMode=yes 85.11.54.11 /usr/sbin/qm vncproxy 5531 2>/dev/null
|-16519 sh -c /usr/bin/ssh -T -o BatchMode=yes 85.11.54.11 /usr/sbin/qm vncproxy 5531 2>/dev/null
|-16520 /usr/bin/ssh -T -o BatchMode=yes 85.11.54.11 /usr/sbin/qm vncproxy 5531
|-23871 pvedaemon worker
|-23872 pvedaemon worker
|-23873 pvedaemon worker
`-control
|-24242 /usr/bin/perl -T /usr/bin/pvedaemon restart
|-24424 /usr/bin/perl -T /usr/bin/pvedaemon restart
`-24674 /usr/bin/perl -T /usr/bin/pvedaemon restart

Feb 20 10:07:17 pegasus pvedaemon[1333]: worker 23873 started
Feb 20 10:12:19 pegasus systemd[1]: Reloading PVE API Daemon.
Feb 20 10:13:49 pegasus systemd[1]: pvedaemon.service reload operation timed out. Stopping.
Feb 20 10:13:49 pegasus systemd[1]: Reload failed for PVE API Daemon.
Feb 20 10:14:19 pegasus systemd[1]: Reloading PVE API Daemon.
Feb 20 10:15:49 pegasus systemd[1]: pvedaemon.service reload operation timed out. Stopping.
Feb 20 10:15:49 pegasus systemd[1]: Reload failed for PVE API Daemon.
Feb 20 10:17:33 pegasus systemd[1]: Reloading PVE API Daemon.
Feb 20 10:19:03 pegasus systemd[1]: pvedaemon.service reload operation timed out. Stopping.
Feb 20 10:19:03 pegasus systemd[1]: Reload failed for PVE API Daemon.
 
please never do a apt-get upgrade always do
Code: 
apt-get dist-upgrade
 
more log output would be helpful

the complete upgrade output
journalctl -xn 100
etc.
 
does pveversion -v work?
if yes please post the output
 
yes:
pveversion -v
proxmox-ve: 4.4-80 (running kernel: 4.4.35-2-pve)
pve-manager: not correctly installed (running version: 4.4-12/e71b7a74)
pve-kernel-4.4.13-1-pve: 4.4.13-56
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.4.13-2-pve: 4.4.13-58
pve-kernel-4.4.35-2-pve: 4.4.35-79
pve-kernel-4.4.21-1-pve: 4.4.21-71
pve-kernel-4.4.16-1-pve: 4.4.16-64
pve-kernel-4.4.19-1-pve: 4.4.19-66
pve-kernel-4.4.40-1-pve: 4.4.40-80
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-109
pve-firmware: 1.1-10
libpve-common-perl: 4.0-92
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-73
pve-libspice-server1: 0.12.8-1
vncterm: 1.3-1
pve-docs: 4.4-3
pve-qemu-kvm: 2.7.1-3
pve-container: 1.0-94
pve-firewall: 2.0-33
pve-ha-manager: 1.0-40
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-3
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
 
please post the output of
Code: 
systemctl status pvedaemon pvestatd pveproxy spiceproxy
 
systemctl status pvedaemon pvestatd pveproxy spiceproxy
* pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
Active: failed (Result: timeout) since Mo 2017-02-20 10:39:55 CET; 1h 19min ago
Main PID: 1333 (code=exited, status=0/SUCCESS)

Feb 20 10:36:54 pegasus systemd[1]: pvedaemon.service start operation timed out. Terminating.
Feb 20 10:38:24 pegasus systemd[1]: pvedaemon.service stop-final-sigterm timed out. Killing.
Feb 20 10:39:55 pegasus systemd[1]: pvedaemon.service still around after final SIGKILL. Entering failed mode.
Feb 20 10:39:55 pegasus systemd[1]: Failed to start PVE API Daemon.
Feb 20 10:39:55 pegasus systemd[1]: Unit pvedaemon.service entered failed state.

* pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled)
Active: active (running) since Mo 2017-02-13 15:02:04 CET; 6 days ago
Main PID: 1321 (pvestatd)
CGroup: /system.slice/pvestatd.service
`-1321 pvestatd

Feb 20 10:06:41 pegasus pvestatd[1321]: received signal HUP
Feb 20 10:06:41 pegasus pvestatd[1321]: server shutdown (restart)
Feb 20 10:06:41 pegasus systemd[1]: Reloaded PVE Status Daemon.
Feb 20 10:06:43 pegasus pvestatd[1321]: restarting server
Feb 20 10:07:15 pegasus systemd[1]: Reloading PVE Status Daemon.
Feb 20 10:07:16 pegasus pvestatd[23861]: send HUP to 1321
Feb 20 10:07:16 pegasus pvestatd[1321]: received signal HUP
Feb 20 10:07:16 pegasus pvestatd[1321]: server shutdown (restart)
Feb 20 10:07:16 pegasus systemd[1]: Reloaded PVE Status Daemon.
Feb 20 10:07:17 pegasus pvestatd[1321]: restarting server

* pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled)
Active: active (running) since Mo 2017-02-20 06:25:07 CET; 5h 34min ago
Main PID: 4448 (pveproxy)
CGroup: /system.slice/pveproxy.service
`-4448 /usr/bin/perl -T /usr/bin/pveproxy start

Feb 20 10:07:16 pegasus systemd[1]: Reloading PVE API Proxy Server.
Feb 20 10:07:18 pegasus pveproxy[23867]: send HUP to 4448
Feb 20 10:07:18 pegasus pveproxy[4448]: received signal HUP
Feb 20 10:07:18 pegasus pveproxy[4448]: server closing
Feb 20 10:07:18 pegasus pveproxy[4448]: server shutdown (restart)
Feb 20 10:07:18 pegasus pveproxy[18391]: worker exit
Feb 20 10:07:18 pegasus pveproxy[18390]: worker exit
Feb 20 10:07:18 pegasus systemd[1]: Reloaded PVE API Proxy Server.
Feb 20 10:07:19 pegasus pveproxy[23876]: worker exit
Feb 20 10:22:01 pegasus pveproxy[16628]: worker exit

* spiceproxy.service - PVE SPICE Proxy Server
Loaded: loaded (/lib/systemd/system/spiceproxy.service; enabled)
Active: active (running) since Mo 2017-02-20 06:25:13 CET; 5h 34min ago
Main PID: 4473 (spiceproxy)
CGroup: /system.slice/spiceproxy.service
|- 4473 spiceproxy
|-18433 spiceproxy worker
`-control
`-23880 /usr/bin/perl -T /usr/bin/spiceproxy restart

Feb 20 10:06:46 pegasus spiceproxy[4473]: server shutdown (restart)
Feb 20 10:06:46 pegasus spiceproxy[4474]: worker exit
Feb 20 10:06:46 pegasus systemd[1]: Reloaded PVE SPICE Proxy Server.
Feb 20 10:06:48 pegasus spiceproxy[4473]: restarting server
Feb 20 10:06:48 pegasus spiceproxy[4473]: worker 4474 finished
Feb 20 10:06:48 pegasus spiceproxy[4473]: starting 1 worker(s)
Feb 20 10:06:48 pegasus spiceproxy[4473]: worker 18433 started
Feb 20 10:07:18 pegasus systemd[1]: Reloading PVE SPICE Proxy Server.
Feb 20 10:08:48 pegasus systemd[1]: spiceproxy.service reload operation timed out. Stopping.
Feb 20 10:08:48 pegasus systemd[1]: Reload failed for PVE SPICE Proxy Server.
 
i cannot really say what happened or what is wrong from your log files
so please post the output of

journalctl -x -b -u pvedaemon
 
Hi, do you have a next step please, well it is our cluster and it do not work at moment. regards
 
can you try to do
Code: 
apt-get -f install

and the logs while this runs?

edt:

oh and also try to restart the pvedaemon service
Code: 
systemctl restart pvedaemon
 
apt-get -f install
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
1 nicht vollständig installiert oder entfernt.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
pve-manager (4.4-12) wird eingerichtet ...
Failed to reload-or-restart pvedaemon.service: sysinit.target is queued, ignoring reload-or-start request for unit pvedaemon.service
dpkg: Fehler beim Bearbeiten des Paketes pve-manager (--configure):
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)

systemctl restart pvedaemon
Failed to restart pvedaemon.service: sysinit.target is queued, ignoring restart request for unit pvedaemon.service
 
is your root file system read only?
 
drwxr-xr-x 2 0 0 4096 Feb 5 13:26 bin
drwxr-xr-x 5 0 0 3072 Feb 20 14:21 boot
drwxr-xr-x 20 0 0 4440 Feb 20 14:41 dev
drwxr-xr-x 101 0 0 12288 Feb 20 10:14 etc
drwx------ 2 0 0 4096 Jul 31 2014 .gnupg
drwxr-xr-x 2 0 0 4096 Mär 24 2014 home
drwxr-xr-x 19 0 0 4096 Feb 20 10:06 lib
drwxr-xr-x 2 0 0 4096 Feb 5 13:26 lib64
drwx------ 2 0 0 16384 Jul 31 2014 lost+found
drwxr-xr-x 2 0 0 4096 Apr 30 2014 media
drwxr-xr-x 3 0 0 4096 Aug 1 2014 mnt
drwxr-xr-x 2 0 0 4096 Apr 30 2014 opt
dr-xr-xr-x 184 0 0 0 Feb 20 14:41 proc
drwx------ 5 0 0 4096 Feb 20 13:42 root
drwxr-xr-x 23 0 0 1160 Feb 20 14:41 run
drwxr-xr-x 2 0 0 12288 Feb 5 13:27 sbin
drwxr-xr-x 2 0 0 4096 Apr 30 2014 srv
dr-xr-xr-x 13 0 0 0 Feb 20 14:41 sys
drwxrwxrwt 8 0 0 4096 Feb 20 14:41 tmp
drwxr-xr-x 10 0 0 4096 Okt 9 2015 usr
drwxr-xr-x 11 0 0 4096 Apr 30 2014 var
 
i would check the disks for errors, maybe this is why it got mounted read only
 
hi, have done already, no errors on hdd. it comes with upgrade/dist-upgrade. after reboot it works back fine... misterie error / issue^^
thanks for help and best regards
 
You must log in or register to reply here.
Top Bottom