Problem update proxmox 4

Melanxolik

Well-Known Member
Dec 18, 2013
86
0
46
Hello, I have big problem with update proxmox4

root@pdebug:~# uname -a
Linux pdebug 4.2.0-1-pve #1 SMP Mon Sep 21 10:49:08 CEST 2015 x86_64 GNU/Linux
root@pdebug:~#


root@pdebug:~# apt-get update
Ign http://ftp.debian.org jessie InRelease
Hit http://ftp.debian.org jessie Release.gpg
Hit http://ftp.debian.org jessie Release
Hit http://security.debian.org jessie/updates InRelease
Hit http://ftp.debian.org jessie/main amd64 Packages
Hit http://security.debian.org jessie/updates/main amd64 Packages
Hit http://ftp.debian.org jessie/contrib amd64 Packages
Hit http://security.debian.org jessie/updates/contrib amd64 Packages
Hit http://ftp.debian.org jessie/contrib Translation-en
Hit http://security.debian.org jessie/updates/contrib Translation-en
Hit http://ftp.debian.org jessie/main Translation-en
Hit http://security.debian.org jessie/updates/main Translation-en
Reading package lists... Done
root@pdebug:~#

root@pdebug:~# 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
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@pdebug:~#

Please, could you help me fix this problem?
 
Hi
Maybe you should have a look there = ;)
See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.

Could it be that dbus is not running ?
What is the output of "pgrep -lf dbus" ?
 
I read journal and saw next:

root@pdebug:~# journalctl -xn
-- Logs begin at Wed 2015-10-14 11:06:53 EEST, end at Wed 2015-10-14 11:34:17 EEST. --
Oct 14 11:21:42 pdebug systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
Oct 14 11:21:42 pdebug pvedaemon[4155]: no such method 'PVE::Service::pvedaemon::run_cli_handler'
Oct 14 11:21:42 pdebug systemd[1]: pvedaemon.service: control process exited, code=exited status=255
Oct 14 11:21:42 pdebug systemd[1]: Failed to start PVE API Daemon.
-- Subject: Unit pvedaemon.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit pvedaemon.service has failed.
--
-- The result is failed.
Oct 14 11:21:42 pdebug systemd[1]: Unit pvedaemon.service entered failed state.
Oct 14 11:22:01 pdebug cron[1336]: (*system*pveupdate) RELOAD (/etc/cron.d/pveupdate)

root@pdebug:~# pgrep -lf dbus
1358 dbus-daemon
root@pdebug:~#
 
I installed the proxmox4 beta for two weeks ago and in this time I want to only update my proxmox installation.
When use update, I get error message
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)

thats all, i never upgrade from 3 to 4 version, i first install clear proxmox4 to fresh server.
 
I installed the proxmox4 beta for two weeks ago and in this time I want to only update my proxmox installation.
When use update, I get error message


thats all, i never upgrade from 3 to 4 version, i first install clear proxmox4 to fresh server.


I have the same problem. Yesterday I did "apt-get upgrade" and now I am stuck in the same point :(
 
Hum, I already upgraded four nodes of Proxmox VE nodes from Beta2 to release and I haven't met that problem yet.

Which Package repositories are you using ?

You should use either pve-enterprise, or pve-no-subscribtion if you don't have a subscribtion.