Node unreachable until reboot

Jan 31, 2021
21
1
8
59
Last night, a Proxmox node left a cluster and was also no longer accessible via ssh. The following was kept in the log. Unfortunately, the quorum for the cluster was deemed ok and thus ha did not work.

Only a hard reboot could fix the problem. Is there a solution to this and do I have to worry?

Jan 03 07:55:21 HA-PVE-01 dbus-daemon[1283]: [system] The maximum number of pending replies for ":1.2" (uid=0 pid=1302 comm="/lib/systemd/systemd-logind " label="unconfined") has been reached (max_replies_per_connection=128) Jan 03 07:55:21 HA-PVE-01 systemd-logind[1302]: Failed to stop user service 'user@0.service', ignoring: The maximum number of pending replies per connection has been reached Jan 03 07:56:11 HA-PVE-01 sshd[1581009]: Accepted password for root from 192.168.178.80 port 53632 ssh2 Jan 03 07:56:11 HA-PVE-01 sshd[1581009]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0) Jan 03 07:57:25 HA-PVE-01 pveproxy[1537079]: proxy detected vanished client connection Jan 03 07:57:36 HA-PVE-01 pmxcfs[1543447]: [status] notice: received log Jan 03 07:57:41 HA-PVE-01 dbus-daemon[1283]: [system] The maximum number of pending replies for ":1.2" (uid=0 pid=1302 comm="/lib/systemd/systemd-logind " label="unconfined") has been reached (max_replies_per_connection=128) Jan 03 07:57:41 HA-PVE-01 dbus-daemon[1283]: [system] The maximum number of pending replies for ":1.2" (uid=0 pid=1302 comm="/lib/systemd/systemd-logind " label="unconfined") has been reached (max_replies_per_connection=128) Jan 03 07:57:41 HA-PVE-01 systemd-logind[1302]: Failed to start user service 'user@0.service', ignoring: The maximum number of pending replies per connection has been reached Jan 03 07:57:41 HA-PVE-01 systemd-logind[1302]: Failed to start session scope session-266771.scope: The maximum number of pending replies per connection has been reached Jan 03 07:57:41 HA-PVE-01 sshd[1581009]: pam_systemd(sshd:session): Failed to create session: The maximum number of pending replies per connection has been reached Jan 03 07:57:42 HA-PVE-01 sshd[1581009]: Received disconnect from 192.168.178.80 port 53632:11: Jan 03 07:57:42 HA-PVE-01 sshd[1581009]: Disconnected from user root 192.168.178.80 port 53632 Jan 03 07:57:42 HA-PVE-01 sshd[1581009]: pam_unix(sshd:session): session closed for user root Jan 03 07:57:51 HA-PVE-01 dbus-daemon[1283]: [system] The maximum number of pending replies for ":1.2" (uid=0 pid=1302 comm="/lib/systemd/systemd-logind " label="unconfined") has been reached (max_replies_per_connection=128) Jan 03 07:57:51 HA-PVE-01 systemd-logind[1302]: Failed to stop user service 'user@0.service', ignoring: The maximum number of pending replies per connection has been reached Jan 03 07:57:55 HA-PVE-01 pmxcfs[1543447]: [status] notice: received log Jan 03 07:58:41 HA-PVE-01 pveproxy[1537079]: proxy detected vanished client connection Jan 03 07:58:42 HA-PVE-01 sshd[1581445]: Accepted password for root from 192.168.178.80 port 53676 ssh2 Jan 03 07:58:42 HA-PVE-01 sshd[1581445]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0) -- Reboot --

Best regards

Thomas
 
Last edited:

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!