[SOLVED] apt upgrade failure

RobFantini

Famous Member
May 24, 2012
2,009
102
133
Boston,Mass
on a non cluster system using pve-test :

Code:
apt-get  dist-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.
5 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up pve-cluster (4.0-42) ...
Job for pve-cluster.service failed. See 'systemctl status pve-cluster.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript pve-cluster, action "restart" failed.
dpkg: error processing package pve-cluster (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of qemu-server:
 qemu-server depends on pve-cluster; however:
  Package pve-cluster is not configured yet.

* systemctl status pve-cluster.service :
Code:
● pve-cluster.service - The Proxmox VE cluster filesystem
  Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
  Active: failed (Result: exit-code) since Tue 2016-06-14 21:35:24 EDT; 1min 37s ago
  Process: 19602 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=255)
 Main PID: 8267 (code=killed, signal=KILL)

Jun 14 21:35:14 s022 pmxcfs[19602]: [main] notice: unable to aquire pmxcfs lock - trying again
Jun 14 21:35:14 s022 pmxcfs[19602]: [main] notice: unable to aquire pmxcfs lock - trying again
Jun 14 21:35:24 s022 pmxcfs[19602]: [main] crit: unable to aquire pmxcfs lock: Resource temporarily unavailable
Jun 14 21:35:24 s022 pmxcfs[19602]: [main] notice: exit proxmox configuration filesystem (-1)
Jun 14 21:35:24 s022 systemd[1]: pve-cluster.service: control process exited, code=exited status=255
Jun 14 21:35:24 s022 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 14 21:35:24 s022 systemd[1]: Unit pve-cluster.service entered failed state.
Probably I screwed something up in a config file or installing software.
Or there is a bug.

any clues on getting this fixed?

I'll try rebooting.
 
after reboot upgrade worked.

I had installed napp-it a couple of days ago. the install added a line to /etc/hosts . I am not sure if it had something to do with the issue .

Code:
127.0.0.1 localhost.localdomain localhost
172.30.24.4 s022.fantinibakery.com s022 pvelocalhost
# The following lines are desirable for IPv6 capable hosts
::1  ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
# next entry is done by napp-it agent-bootinit to avoid root console spamming, comment it optionally with a #
#127.0.0.1  s022
I commented the last line prior to reboot , but doing so was not able to complete the upgrade.

the 1ST 'systemctl status pve-cluster.service' complained about an IP address...
Code:
# systemctl status pve-cluster.service
● pve-cluster.service - The Proxmox VE cluster filesystem
  Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
  Active: failed (Result: exit-code) since Tue 2016-06-14 21:11:19 EDT; 9min ago
  Process: 16023 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=255)
 Main PID: 8267 (code=killed, signal=KILL)

Jun 14 21:11:19 s022 pmxcfs[16023]: [main] crit: Unable to get local IP address
Jun 14 21:11:19 s022 systemd[1]: pve-cluster.service: control process exited, code=exited status=255
Jun 14 21:11:19 s022 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jun 14 21:11:19 s022 systemd[1]: Unit pve-cluster.service entered failed state.

So I assume the /etc/hosts line or some other dns issue caused the problem.
 
notice: unable to aquire pmxcfs lock - trying again

The lock file under /var/lib/pve-cluster/.pmxcfs.lockfile was probably not deleted, you could delete it manually the next time after you ensured with ps aux | grep pmxcfs that no instance of pmxcfs runs.

172.30.24.4 s022.fantinibakery.com s022 pvelocalhost
[..]
#127.0.0.1 s022
the 1ST 'systemctl status pve-cluster.service' complained about an IP address...

The filesystem execs an getadrrinfo on the nodename, so this should resolve to the Node IP through /etc/hosts which then the napp-it entry conflicts in your case.
 

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!

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!