Proxmox upgrade from 6.0 to 6.1 failed

jatrn · Jan 9, 2020

Hello,

I tied upgrade proxmox 6.0 to 6.1 but it failed with two packages...

Code:

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.
2 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 (6.1-5) ...
Job for pvestatd.service failed.
See "systemctl status pvestatd.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
 installed pve-manager package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on pve-manager; however:
  Package pve-manager is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 pve-manager
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

journalctl -xe

Code:

journalctl -xe
-- Support: https://www.debian.org/support
-- 
-- The unit pvesr.service has entered the 'failed' state with result 'exit-code'.
Jan 09 15:33:01 proxmox-dc systemd[1]: Failed to start Proxmox VE replication runner.
-- Subject: A start job for unit pvesr.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit pvesr.service has finished with a failure.
-- 
-- The job identifier is 9307133 and the job result is failed.
Jan 09 15:33:01 proxmox-dc cron[19127]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Jan 09 15:33:02 proxmox-dc pve-firewall[2623]: status update error: Connection refused
Jan 09 15:33:02 proxmox-dc pveproxy[29290]: worker exit
Jan 09 15:33:02 proxmox-dc pveproxy[2771]: worker 29290 finished
Jan 09 15:33:02 proxmox-dc pveproxy[2771]: starting 1 worker(s)
Jan 09 15:33:02 proxmox-dc pveproxy[2771]: worker 29559 started
Jan 09 15:33:02 proxmox-dc pveproxy[29291]: worker exit
Jan 09 15:33:02 proxmox-dc pveproxy[29292]: worker exit
Jan 09 15:33:02 proxmox-dc pveproxy[29559]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1699.
Jan 09 15:33:02 proxmox-dc pveproxy[2771]: worker 29291 finished
Jan 09 15:33:02 proxmox-dc pveproxy[2771]: worker 29292 finished
Jan 09 15:33:02 proxmox-dc pveproxy[2771]: starting 2 worker(s)
Jan 09 15:33:02 proxmox-dc pveproxy[2771]: worker 29560 started
Jan 09 15:33:02 proxmox-dc pveproxy[2771]: worker 29561 started
Jan 09 15:33:02 proxmox-dc pveproxy[29560]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1699.
Jan 09 15:33:02 proxmox-dc pveproxy[29561]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1699.
Jan 09 15:33:04 proxmox-dc pvestatd[2624]: ipcc_send_rec[1] failed: Connection refused
Jan 09 15:33:04 proxmox-dc pvestatd[2624]: ipcc_send_rec[2] failed: Connection refused
Jan 09 15:33:04 proxmox-dc pvestatd[2624]: ipcc_send_rec[3] failed: Connection refused
Jan 09 15:33:04 proxmox-dc pvestatd[2624]: ipcc_send_rec[4] failed: Connection refused
Jan 09 15:33:04 proxmox-dc pvestatd[2624]: status update error: Connection refused
Jan 09 15:33:07 proxmox-dc pveproxy[29559]: worker exit
Jan 09 15:33:07 proxmox-dc pveproxy[2771]: worker 29559 finished
Jan 09 15:33:07 proxmox-dc pveproxy[2771]: starting 1 worker(s)
Jan 09 15:33:07 proxmox-dc pveproxy[2771]: worker 29838 started
Jan 09 15:33:07 proxmox-dc pveproxy[29560]: worker exit
Jan 09 15:33:07 proxmox-dc pveproxy[29561]: worker exit
Jan 09 15:33:07 proxmox-dc pveproxy[29838]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1699.
Jan 09 15:33:07 proxmox-dc pveproxy[2771]: worker 29560 finished
Jan 09 15:33:07 proxmox-dc pveproxy[2771]: starting 1 worker(s)
Jan 09 15:33:07 proxmox-dc pveproxy[2771]: worker 29561 finished
Jan 09 15:33:07 proxmox-dc pveproxy[2771]: worker 29839 started
Jan 09 15:33:08 proxmox-dc pveproxy[29839]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 1699.

I have empty folder /etc/pve ....

Any ideas how to repair this?

spirit · Jan 10, 2020

>>apt-get upgrade

NEVER NEVER NEVER do "upgrade".

you need to use dist-upgrade! (or use the gui)

"apt-get dist-upgrade"

(apt-get upgrade only upgraded currently installed packages, but if some new required dependencies couldn't be installed)

https://pve.proxmox.com/wiki/System_Software_Updates

jatrn · Jan 10, 2020

spirit said:
>>apt-get upgrade

NEVER NEVER NEVER do "upgrade".

you need to use dist-upgrade! (or use the gui)

"apt-get dist-upgrade"

(apt-get upgrade only upgraded currently installed packages, but if some new required dependencies couldn't be installed)

https://pve.proxmox.com/wiki/System_Software_Updates

I run upgrade form gui of course.. then I try run apt-get dist-upgrade from cli and the effect is the same....

spirit · Jan 10, 2020

If you have an empty /etc/pve , restart corosync service then pve-cluster service

jatrn · Jan 10, 2020

spirit said:
If you have an empty /etc/pve , restart corosync service then pve-cluster service

I have a standalone node..

I check on another server and I don't have this:

Code:

/dev/fuse                      30M   44K   30M   1% /etc/pve

Code:

Filesystem                Size  Used Avail Use% Mounted on
udev                       95G     0   95G   0% /dev
tmpfs                      19G  682M   19G   4% /run
/dev/mapper/pve-root       36G   19G   16G  56% /
tmpfs                      95G     0   95G   0% /dev/shm
tmpfs                     5.0M     0  5.0M   0% /run/lock
tmpfs                      95G     0   95G   0% /sys/fs/cgroup
ZFS-SR                    6.7T   14G  6.7T   1% /ZFS-SR
ZFS-SR/subvol-104-disk-0  8.0G  688M  7.4G   9% /ZFS-SR/subvol-104-disk-0
ZFS-SR/template           6.8T  187G  6.7T   3% /ZFS-SR/template
ZFS-SR/subvol-108-disk-0   20G  1.1G   19G   6% /ZFS-SR/subvol-108-disk-0
ZFS-SR/subvol-109-disk-0   20G  591M   20G   3% /ZFS-SR/subvol-109-disk-0
ZFS-SR/subvol-111-disk-0   10G  673M  9.4G   7% /ZFS-SR/subvol-111-disk-0
tmpfs                      19G     0   19G   0% /run/user/0

spirit · Jan 10, 2020

pve-cluster is the service which launch "pmxcfs" process, which is mounting /etc/pve. (even on a standalone node)

# systemctl status pve-cluster ?

jatrn · Jan 10, 2020

spirit said:
pve-cluster is the service which launch "pmxcfs" process, which is mounting /etc/pve. (even on a standalone node)

# systemctl status pve-cluster ?

I forgoten that I create a file /etc/pve/local/pve-ssl.key to simulation and now I deleted it, restart services and works all.
Thanks for help.

spirit · Jan 10, 2020

oh,ok. /etc/pve can't be mounted if files exist in not mounted /etc/pve/

jatrn · Jan 10, 2020

spirit said:
oh,ok. /etc/pve can't be mounted if files exist in not mounted /etc/pve/

Now I know that

Search

Search

Proxmox upgrade from 6.0 to 6.1 failed

jatrn

Member

spirit

Distinguished Member

jatrn

Member

spirit

Distinguished Member

jatrn

Member

spirit

Distinguished Member

jatrn

Member

spirit

Distinguished Member

jatrn

Member