Hi there,
I don't know if this really is a problem with Proxmox Backup Server or with Debian or with my hardware. I couldn't find the source of my problems.
I had this problem about 4 times and I think this will not fix itself. The problem happened often after updating/rebooting but I couldn't link that to my situation.
The first symptom are login problems via ssh. It takes a long time to connect and if I leave the system running I cannot connect anymore.
Kernel Info: Linux pbs 7.0.14-11-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.14-11 (2026-08-06T23:36Z) x86_64 GNU/Linux
Here the relevant log for that:
I found some other errors in the log that my be linked to the problem above.
This was a one (I haven't counted) time event: [see attached file kernel one time.txt]
This was many times in the logs: [see attached file kernel multiple times.txt]
I don't know if those log snippets point the right way. So if you have other ideas...
And the end I have some funny error messages..
I don't know if this really is a problem with Proxmox Backup Server or with Debian or with my hardware. I couldn't find the source of my problems.
I had this problem about 4 times and I think this will not fix itself. The problem happened often after updating/rebooting but I couldn't link that to my situation.
The first symptom are login problems via ssh. It takes a long time to connect and if I leave the system running I cannot connect anymore.
Kernel Info: Linux pbs 7.0.14-11-pve #1 SMP PREEMPT_DYNAMIC PMX 7.0.14-11 (2026-08-06T23:36Z) x86_64 GNU/Linux
Here the relevant log for that:
Code:
Aug 08 19:22:33 pbs sshd-session[152196]: Accepted publickey for monitoring from ... port 59148 ssh2: ED25519 SHA256:...
Aug 08 19:22:33 pbs sshd-session[152196]: pam_unix(sshd:session): session opened for user monitoring(uid=1002) by monitoring(uid=0)
Aug 08 19:22:33 pbs systemd-logind[1006]: New session 324 of user monitoring.
Aug 08 19:24:04 pbs systemd[1]: user@1002.service: State 'final-sigterm' timed out. Killing.
Aug 08 19:24:04 pbs systemd[1]: user@1002.service: Killing process 151566 (systemd) with signal SIGKILL.
Aug 08 19:24:04 pbs systemd[1]: user@1002.service: Killing process 150321 (systemd) with signal SIGKILL.
Aug 08 19:24:33 pbs sshd-session[152196]: pam_systemd(sshd:session): Failed to create session: Connection timed out
Aug 08 19:24:33 pbs sshd-session[152394]: Connection closed by ... port 59148
Aug 08 19:24:33 pbs sshd-session[152196]: pam_unix(sshd:session): session closed for user monitoring
Aug 08 19:24:33 pbs systemd-logind[1006]: Session 324 logged out. Waiting for processes to exit.
Aug 08 19:24:33 pbs systemd-logind[1006]: Removed session 324.
Aug 08 19:26:04 pbs systemd[1]: user@1002.service: Processes still around after final SIGKILL. Entering failed mode.
Aug 08 19:26:04 pbs systemd[1]: user@1002.service: Failed with result 'timeout'.
Aug 08 19:26:04 pbs systemd[1]: user@1002.service: Unit process 150321 (systemd) remains running after unit stopped.
Aug 08 19:26:04 pbs systemd[1]: user@1002.service: Unit process 151566 (systemd) remains running after unit stopped.
Aug 08 19:26:04 pbs systemd[1]: Failed to start user@1002.service - User Manager for UID 1002.
Aug 08 19:26:04 pbs systemd[1]: session-321.scope: PID 151561 vanished before we could move it to target cgroup '/user.slice/user-1002.slice/session-321.scope', skipping: No such process
Aug 08 19:26:04 pbs systemd[1]: session-321.scope: No PIDs left to attach to the scope's control group, refusing.
Aug 08 19:26:04 pbs systemd[1]: session-321.scope: Failed with result 'resources'.
Aug 08 19:26:04 pbs systemd[1]: Failed to start session-321.scope - Session 321 of User monitoring.
Aug 08 19:26:04 pbs systemd[1]: session-324.scope: PID 152196 vanished before we could move it to target cgroup '/user.slice/user-1002.slice/session-324.scope', skipping: No such process
Aug 08 19:26:04 pbs systemd[1]: session-324.scope: No PIDs left to attach to the scope's control group, refusing.
Aug 08 19:26:04 pbs systemd[1]: session-324.scope: Failed with result 'resources'.
Aug 08 19:26:04 pbs systemd[1]: Failed to start session-324.scope - Session 324 of User monitoring.
Aug 08 19:26:04 pbs systemd[1]: Stopping user-runtime-dir@1002.service - User Runtime Directory /run/user/1002...
Aug 08 19:26:04 pbs systemd[1]: run-user-1002.mount: Deactivated successfully.
Aug 08 19:26:04 pbs systemd[1]: user-runtime-dir@1002.service: Deactivated successfully.
Aug 08 19:26:04 pbs systemd[1]: Stopped user-runtime-dir@1002.service - User Runtime Directory /run/user/1002.
Aug 08 19:26:04 pbs systemd[1]: Removed slice user-1002.slice - User Slice of UID 1002.
Aug 08 19:26:04 pbs systemd-logind[1006]: Removed session 322.
Aug 08 19:26:34 pbs sshd-session[152609]: Connection closed by ... port 34106 [preauth]I found some other errors in the log that my be linked to the problem above.
This was a one (I haven't counted) time event: [see attached file kernel one time.txt]
This was many times in the logs: [see attached file kernel multiple times.txt]
I don't know if those log snippets point the right way. So if you have other ideas...
And the end I have some funny error messages..
Code:
# sudo reboot
Failed to set wall message, ignoring: Transport endpoint is not connected
Call to Reboot failed: Transport endpoint is not connected
# sudo halt
Call to Halt failed: Connection timed out
Last edited:
