[PVE-User] Corosync Upgrade Issue (v2 -> v3)

[Ricardo Correa]

On Wed, Jul 17, 2019 at 8:22 AM Thomas Lamprecht <t.lamprecht at proxmox.com>
wrote:

> On 7/16/19 9:28 PM, Ricardo Correa wrote:
> > systemd[1]: Starting The Proxmox VE cluster filesystem...
> > systemd[1]: pve-cluster.service: Start operation timed out. Terminating.
> > pmxcfs[13267]: [main] crit: read error: Interrupted system call
>
> That's strange, that an error happening initially at the startup code,
> after we fork the child process which becomes the daemon doing the actual
> work we wait in the parent for it to be read, for that a simple pipe is
> used from where a byte is read, your read is getting interrupted -
> something
> which normally should not happen..
>
> Can you try to start in it the foreground:
> # systemctl stop pve-cluster
> # pmxcfs -f
>
> and see what happens their
>
> Also you probably should try to finish the upgrade:
> # apt -f install
>
> That did it! There was a message I haven't seen before though:

root at pve01:~# apt -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
8 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up pve-manager (5.4-11) ...
Setting up libqb0:amd64 (1.0.5-1~bpo9+2) ...
Setting up libvotequorum8:amd64 (3.0.2-pve2~bpo9) ...
Setting up libcpg4:amd64 (3.0.2-pve2~bpo9) ...
Setting up libcmap4:amd64 (3.0.2-pve2~bpo9) ...
Setting up libquorum5:amd64 (3.0.2-pve2~bpo9) ...
Setting up libcfg7:amd64 (3.0.2-pve2~bpo9) ...
Setting up corosync (3.0.2-pve2~bpo9) ...
Installing new version of config file /etc/default/corosync ...
Processing triggers for pve-ha-manager (2.0-9) ...
Processing triggers for pve-manager (5.4-11) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...
W: APT had planned for dpkg to do more than it reported back (18 vs 25).
   Affected packages: libqb0:amd64 pve-manager:amd64

That "APT had planned for dpkg to do more than it reported back (18 vs
25)", could
it be due to me actually trying to apt -f install many times before I had
stopped
the pve-cluster and started pmxcfs by hand?