Cluster broken after node restart; libqb error: couldn't open file

[alpiua]

Hello!
I've just started with a proxmox on home lab with 3 nodes.
I've shutdown one node for maintainance, and after turned of It can't join a cluster.

Failed to find a solution in the google so decided to ask here

Getting this errors:

# pvecm status
Cluster information
-------------------
Name: ClusterName
Config Version: 3
Transport: knet
Secure auth: on

Cannot initialize CMAP service

pve-cluster

# systemctl restart pve-cluster
# systemctl status pve-cluster
pmxcfs[758248]: [libqb] error: couldn't open file /dev/shm/qb-758253-758248-28-OR5BrH/qb-request-cpg-header: No such file or directory (2)
pmxcfs[758248]: [libqb] error: couldn't create file for mmap
pmxcfs[758248]: [libqb] error: qb_rb_open:REQUEST: No such file or directory (2)
pmxcfs[758248]: [libqb] error: connection failed: No such file or directory (2)
pmxcfs[758248]: [status] crit: cpg_initialize failed: 12

the folder really do not exist

ls: cannot access '/dev/shm/qb-758253-758248-28-OR5BrH/qb-request-cpg-header': No such file or directory

corosync

# systemct status corosync
systemd[1]: Starting Corosync Cluster Engine...
systemd[1]: corosync.service: start operation timed out. Terminating.
systemd[1]: corosync.service: Failed with result 'timeout'.
systemd[1]: Failed to start Corosync Cluster Engine.

How I could bring the cluster up ?

Also ssh access become remarkable slow after last boot, with following messages in the journal:

systemd-logind[6482]: Failed to connect to system bus: No such file or directory
systemd-logind[6482]: Failed to fully start up daemon: No such file or directory
systemd[1]: Failed to start User Login Management.
...
dbus-daemon[2783]: [system] Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
sshd[828522]: pam_systemd(sshd:session): Failed to create session: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)

 

[alpiua]

Happily, I was able to resolve the issues after finding this answer:
https://forum.proxmox.com/threads/systemd-logind-fail-to-connect-to-dbus.106174/#post-457226