Upgrade doesn't work

P

pugnacity

New Member
Aug 2, 2012
8
0
1
the update from proxmox-ve-2.6.32 doesn't work

Code: 
aptitude -f installThe following partially installed packages will be configured:
  proxmox-ve-2.6.32 pve-manager 
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Setting up pve-manager (2.1-13) ...
Restarting PVE Daemon: pvedaemon.
Restarting PVE Status Daemon: pvestatd.
dpkg: error processing pve-manager (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve-2.6.32:
 proxmox-ve-2.6.32 depends on pve-manager; however:
  Package pve-manager is not configured yet.
dpkg: error processing proxmox-ve-2.6.32 (--configure):
 dependency problems - leaving unconfigured
configured to not write apport reports
                                      configured to not write apport reports
                                                                            Errors were encountered while processing:
 pve-manager
 proxmox-ve-2.6.32
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up pve-manager (2.1-13) ...
Restarting PVE Daemon: pvedaemon.
Restarting PVE Status Daemon: pvestatd.
dpkg: error processing pve-manager (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve-2.6.32:
 proxmox-ve-2.6.32 depends on pve-manager; however:
  Package pve-manager is not configured yet.
dpkg: error processing proxmox-ve-2.6.32 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 pve-manager
 proxmox-ve-2.6.32

the log says nothing
Code: 
Aug  2 07:54:59 SERVERNAME pvedaemon[28903]: received terminate requestAug  2 07:54:59 SERVERNAME pvedaemon[28903]: worker 28909 finished
Aug  2 07:54:59 SERVERNAME pvedaemon[28903]: worker 28907 finished
Aug  2 07:54:59 SERVERNAME pvedaemon[28903]: worker 28905 finished
Aug  2 07:54:59 SERVERNAME pvedaemon[28903]: server closing
Aug  2 07:55:01 SERVERNAME pvedaemon[37582]: starting server
Aug  2 07:55:01 SERVERNAME pvedaemon[37582]: starting 3 worker(s)
Aug  2 07:55:01 SERVERNAME pvedaemon[37582]: worker 37586 started
Aug  2 07:55:01 SERVERNAME pvedaemon[37582]: worker 37591 started
Aug  2 07:55:01 SERVERNAME pvedaemon[37582]: worker 37592 started
Aug  2 07:55:01 SERVERNAME pvestatd[28932]: server closing
Aug  2 07:55:02 SERVERNAME pvestatd[37697]: starting server
Aug  2 07:55:02 SERVERNAME pvedaemon[37582]: received terminate request
Aug  2 07:55:02 SERVERNAME pvedaemon[37582]: worker 37591 finished
Aug  2 07:55:02 SERVERNAME pvedaemon[37582]: worker 37586 finished
Aug  2 07:55:02 SERVERNAME pvedaemon[37582]: worker 37592 finished
Aug  2 07:55:02 SERVERNAME pvedaemon[37582]: server closing
Aug  2 07:55:05 SERVERNAME pvedaemon[37865]: starting server
Aug  2 07:55:05 SERVERNAME pvedaemon[37865]: starting 3 worker(s)
Aug  2 07:55:05 SERVERNAME pvedaemon[37865]: worker 37867 started
Aug  2 07:55:05 SERVERNAME pvedaemon[37865]: worker 37869 started
Aug  2 07:55:05 SERVERNAME pvedaemon[37865]: worker 37871 started
Aug  2 07:55:05 SERVERNAME pvestatd[37697]: server closing
Aug  2 07:55:05 SERVERNAME pvestatd[37894]: starting server

Code: 
pveversion -vpve-manager: not correctly installed (pve-manager/2.1/bdd3663d)
running kernel: 2.6.32-13-pve
pve-kernel-2.6.32-10-pve: 2.6.32-63
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-13-pve: 2.6.32-72
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-47
pve-firmware: 1.0-17
libpve-common-perl: 1.0-28
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-29
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3

how can i fix this?
 
dietmar said:
What is the output of:

# dpkg --configure pve-manager
Click to expand...

Code: 
dpkg --configure pve-manager
Setting up pve-manager (2.1-13) ...
Restarting PVE Daemon: pvedaemon.
Restarting PVE Status Daemon: pvestatd.
dpkg: error processing pve-manager (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 pve-manager
 
dietmar said:
And what do you get with

# /etc/init.d/pvestatd start
Click to expand...
Code: 
 /etc/init.d/pvestatd start
Starting PVE Status Daemon: pvestatdERROR: can't aquire lock '/var/run/pvestatd.pid.lock' - Resource temporarily unavailable
 (warning).
 
dietmar said:
Does the following work?

# /etc/init.d/pvestatd stop
# dpkg --configure pve-manager
Click to expand...
the update process still doesn't work. i've already rebooted
Code: 
/etc/init.d/pvestatd stop
Stopping PVE Status Daemon: pvestatd.
root@proxmox:~# dpkg --configure pve-manager
Setting up pve-manager (2.1-13) ...
Restarting PVE Daemon: pvedaemon.
Restarting PVE Status Daemon: pvestatd.
dpkg: error processing pve-manager (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 pve-manager
 
Sigh, I can't see whats wrong. What do you get with:

# /etc/init.d/pvestatd restart; echo $?

and

# /etc/init.d/apache2 restart; echo $?
 
dietmar said:
Sigh, I can't see whats wrong. What do you get with:

# /etc/init.d/pvestatd restart; echo $?

and

# /etc/init.d/apache2 restart; echo $?
Click to expand...
Code: 
 root@proxmox:~# /etc/init.d/pvestatd restart; echo $?Restarting PVE Status Daemon: pvestatd.
0
root@proxmox:~#  /etc/init.d/apache2 restart; echo $?
Restarting web server: apache2 ... waiting .
0
i've got the same problem on an other node.
 
Does some of the following command returns errors:

# a2enmod perl
# a2enmod ssl
# a2enmod rewrite
# a2enmod proxy
# a2ensite pve.conf
 
dietmar said:
What if you do:

/var/lib/dpkg/info/pve-manager.postinst configure; echo $?
Click to expand...

Code: 
root@proxmox10:~# /var/lib/dpkg/info/pve-manager.postinst configure; echo $?
Restarting PVE Daemon: pvedaemon.
Restarting PVE Status Daemon: pvestatd.
1
 
after reinstalling the server and only installing proxmox-ve-2.6.32 the error occurs too

we're using debian squeeze backports has this influence on the behavior of proxmox?
 
pugnacity said:
after reinstalling the server and only installing proxmox-ve-2.6.32 the error occurs too

we're using debian squeeze backports has this influence on the behavior of proxmox?
Click to expand...

I assume this depends what packages you use from backports.? we do not test this here but I assume no.
 
could ceph-common be the problem?
Code: 
# dpkg -l| grep bpo
ii  ceph-common                         0.48argonaut-1~bpo60+1       common utilities to mount and interact with a ceph storage cluster
ii  libpopt0                            1.16-1                       lib for parsing cmdline parameters
ii  librados2                           0.48argonaut-1~bpo60+1       RADOS distributed object store client library
ii  librbd1                             0.48argonaut-1~bpo60+1       RADOS block device client library
 
I installed ceph-common on running 2.1 test machines (from ceph.com), at least there are no problems.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back