[SOLVED] pvedaemon broken after upgrade from 4.0beta2 to 4.0

prisoner

Renowned Member
Oct 8, 2015
5
0
66
Hi,

i've a problem with pve daemon after an upgrade from 4beta2 to 4.0 release:

Code:
Setting up pve-manager (4.0-48) ...Job for pvedaemon service failed. See 'systemctl status pvedaemon service' and 'journalctl -xn' for details.
dpkg: error processing package pve-manager (--configure):
subprocess installed post-installation script returned error exit status 1
E: Sub-process usr bin dpkg returned an error code (1)


after some troubleshooting i've found this error:


Code:
Node0:~# usr bin pvedaemon start
no such method 'PVE::Service:vedaemon::run_cli_handler'
pveversion -v
proxmox-ve: 4.0-14 (running kernel: 4.2.1-1-pve)
pve-manager: not correctly installed (running version: 4.0-48/0d8559d0)


can someone help me to find a solution? i can't find anything in the forum.

Thank You

Andrea
 
Last edited:
post the output of:

> pveversion -v

and:

> apt-get update && apt-get dist-upgrade

> apt-get install proxmox-ve
 
post the output of:

> pveversion -v

> apt-get update && apt-get dist-upgrade

> apt-get install proxmox-ve

Code:
root[at]node0:~# pveversion -v
proxmox-ve: 4.0-14 (running kernel: 4.2.1-1-pve)
pve-manager: not correctly installed (running version: 4.0-48/0d8559d0)
pve-kernel-3.19.8-1-pve: 3.19.8-3
pve-kernel-4.1.3-1-pve: 4.1.3-7
pve-kernel-4.2.0-1-pve: 4.2.0-13
pve-kernel-4.2.1-1-pve: 4.2.1-14
lvm2: 2.02.116-pve1
corosync-pve: 2.3.5-1
libqb0: 0.17.2-1
pve-cluster: 4.0-22
qemu-server: 4.0-30
pve-firmware: 1.1-7
libpve-common-perl: 4.0-25
libpve-access-control: 4.0-9
libpve-storage-perl: 4.0-26
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.4-9
pve-container: 1.0-7
pve-firewall: 2.0-12
pve-ha-manager: 1.0-9
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.3-1
lxcfs: 0.9-pve2
cgmanager: 0.37-pve2
criu: 1.6.0-1
zfsutils: 0.6.5-pve4~jessie

root[at]node0:/etc/apt/sources.list.d# apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 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 (4.0-48) ...
Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.
dpkg: error processing package pve-manager (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)
root[at]node0:/etc/apt/sources.list.d# apt-get install proxmox-ve
Reading package lists... Done
Building dependency tree       
Reading state information... Done
proxmox-ve is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 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 (4.0-48) ...
Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.
dpkg: error processing package pve-manager (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)

Thank you
 
is this a dedicated server from OVH?
 
Found the problem, i've missed to switch from enterprise to no-subscription repository.
I mark this as "solved", thank you.

Andrea
 
I have the same problem.

root@mon:/~# apt-get -fy install
Чтение списков пакетов… Готово
Построение дерева зависимостей
Чтение информации о состоянии… Готово
Следующий пакет устанавливался автоматически и больше не требуется:
ifenslave-2.6
Для его удаления используйте «apt-get autoremove».
обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 0 пакетов не обновлено.
не установлено до конца или удалено 1 пакетов.
После данной операции, объём занятого дискового пространства возрастёт на 0 B.
Настраивается пакет pve-manager (4.1-5) …
Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.
dpkg: ошибка при обработке пакета pve-manager (--configure):
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
При обработке следующих пакетов произошли ошибки:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)



root@mon:~# systemctl status pvedaemon.service
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
Active: failed (Result: exit-code) since Пт 2016-01-15 16:19:02 YEKT; 12s ago
Process: 2978 ExecStart=/usr/bin/pvedaemon start (code=exited, status=255)

янв 15 16:19:02 mon pvedaemon[2978]: no such method 'PVE::Service::pvedaemon::run_cli_handler'
янв 15 16:19:02 mon systemd[1]: pvedaemon.service: control process exited, code=exited status=255
янв 15 16:19:02 mon systemd[1]: Failed to start PVE API Daemon.
янв 15 16:19:02 mon systemd[1]: Unit pvedaemon.service entered failed state.


root@mon:~# journalctl -xn
-- Logs begin at Пт 2016-01-15 15:50:09 YEKT, end at Пт 2016-01-15 16:19:02 YEKT. --
янв 15 16:17:01 mon CRON[2834]: pam_unix(cron:session): session closed for user root
янв 15 16:19:00 mon systemd-sysv-generator[2955]: Ignoring creation of an alias umountiscsi.service for itself
янв 15 16:19:00 mon systemd[1]: Cannot add dependency job for unit watchdog-mux.socket, ignoring: Unit watchdog-mux.socket failed to load: No such file or directory.
янв 15 16:19:01 mon systemd[1]: Cannot add dependency job for unit watchdog-mux.socket, ignoring: Unit watchdog-mux.socket failed to load: No such file or directory.
янв 15 16:19:01 mon systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
янв 15 16:19:01 mon cron[1329]: (*system*pveupdate) RELOAD (/etc/cron.d/pveupdate)
янв 15 16:19:02 mon pvedaemon[2978]: no such method 'PVE::Service::pvedaemon::run_cli_handler'
янв 15 16:19:02 mon systemd[1]: pvedaemon.service: control process exited, code=exited status=255
янв 15 16:19:02 mon systemd[1]: Failed to start PVE API Daemon.
-- Subject: Ошибка юнита pvedaemon.service
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Произошел сбой юнита pvedaemon.service.
--
-- Результат: failed.
янв 15 16:19:02 mon systemd[1]: Unit pvedaemon.service entered failed state.


root@mon:~# pveversion -v
proxmox-ve: 4.0-14 (running kernel: 4.2.1-1-pve)
pve-manager: not correctly installed (running version: 4.1-5/f910ef5c)
pve-kernel-4.1.3-1-pve: 4.1.3-7
pve-kernel-4.2.1-1-pve: 4.2.1-14
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 0.17.2-1
pve-cluster: 4.0-30
qemu-server: 4.0-46
pve-firmware: 1.1-7
libpve-common-perl: 4.0-25
libpve-access-control: 4.0-11
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.4-21
pve-container: 1.0-37
pve-firewall: 2.0-15
pve-ha-manager: 1.0-18
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-5
lxcfs: 0.13-pve3
cgmanager: 0.39-pve1
criu: 1.6.0-1
 
Oh yes. It's my mistake.
But now I corrected it and all the same pve-manager package gives an error while installation and PVE API Daemon is not starting.


# apt-get -fy install
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
ifenslave-2.6
Use 'apt-get autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up pve-manager (4.1-5) ...
Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.
dpkg: error processing package pve-manager (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)




# systemctl status pvedaemon.service
* pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
Active: failed (Result: exit-code) since Fri 2016-01-15 18:19:41 YEKT; 42s ago
Process: 8265 ExecStart=/usr/bin/pvedaemon start (code=exited, status=255)

Jan 15 18:19:41 mon pvedaemon[8265]: no such method 'PVE::Service::pvedaemon::run_cli_handler'
Jan 15 18:19:41 mon systemd[1]: pvedaemon.service: control process exited, code=exited status=255
Jan 15 18:19:41 mon systemd[1]: Failed to start PVE API Daemon.
Jan 15 18:19:41 mon systemd[1]: Unit pvedaemon.service entered failed state.​
 
apt-get dist-upgrade?