dist-upgrade issue

[okieunix1957]

Hi,

I got the following error after doing dist-upgrade on my node.

rrors were encountered while processing:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)

I rebooted the node and re-run this again:
Do you want to continue? [Y/n] y
Setting up pve-manager (6.1-7) ...
pveproxy.service is not active, cannot reload.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)

The proxy service did not load and this is a fresh install.
Any ideas here?

 

[okieunix1957]

Hi,

I got the following error after doing dist-upgrade on my node.

rrors were encountered while processing:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)

I rebooted the node and re-run this again:
Do you want to continue? [Y/n] y
Setting up pve-manager (6.1-7) ...
pveproxy.service is not active, cannot reload.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)

The proxy service did not load and this is a fresh install.
Any ideas here?

host21:~# systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: activating (start-pre) since Wed 2020-03-04 20:49:31 PST; 111ms ago
Cntrl PID: 7057 (pvecm)
Tasks: 1 (limit: 4915)
Memory: 8.4M
CGroup: /system.slice/pveproxy.service
└─7057 /usr/bin/perl /usr/bin/pvecm updatecerts --silent

Mar 04 20:49:31 host21 systemd[1]: Starting PVE API Proxy Server...
root@host21:~# journalctl -xe
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pve-cluster.service has finished with a failure.
--
-- The job identifier is 47711 and the job result is failed.
Mar 04 20:49:54 host21 systemd[1]: Condition check resulted in Corosync Cluster Engine being sk
-- Subject: A start job for unit corosync.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit corosync.service has finished successfully.
--
-- The job identifier is 47712.
Mar 04 20:49:54 host21 systemd[1]: Starting PVE API Proxy Server...
-- Subject: A start job for unit pveproxy.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pveproxy.service has begun execution.
--
-- The job identifier is 47645.
Mar 04 20:49:55 host21 pvecm[7276]: ipcc_send_rec[1] failed: Connection refused
Mar 04 20:49:55 host21 pvecm[7276]: ipcc_send_rec[2] failed: Connection refused
Mar 04 20:49:55 host21 pvecm[7276]: ipcc_send_rec[3] failed: Connection refused
Mar 04 20:49:55 host21 pvecm[7276]: Unable to load access control list: Connection refused

seems the pvecm is having issues here.

 

[oguz]

hi,

what does running hostname --ip-address return? it should be returning the IP of the host. if it doesn't then please check your /etc/hosts file and add an entry for the correct IP (found in /etc/network/interfaces or in the output of ip a for the correct interface). check afterwards again if it returns the correct IP, then retry apt update && apt full-upgrade

 

[okieunix1957]

hi,

what does running hostname --ip-address return? it should be returning the IP of the host. if it doesn't then please check your /etc/hosts file and add an entry for the correct IP (found in /etc/network/interfaces or in the output of ip a for the correct interface). check afterwards again if it returns the correct IP, then retry apt update && apt full-upgrade

Out of Frustration, I rebuild all 3 node, You instructions is further confusing. Because I ran update then dist-upgrade which is covered in many documentation. Why full-upgrade?