You are not logged in.
Hi everybody,
I've got the following SSH issue bugging me when rebooting my Devuan 5 machine.
devuan@DevuanRpi:~$ sudo reboot
Broadcast message from root@DevuanRpi (pts/1) (Mon Aug 12 07:02:06 2024):
The system is going down for reboot NOW!
Broadcast message from root@DevuanRpi (pts/1) (Mon Aug 12 07:02:06 2024):
The system is going down for reboot NOW!
devuan@DevuanRpi:~$ █
It seems as if the reboot proceeds faster than the SSH service is able to logout - thus my terminal becomes unresponsive for 15+ minutes.
Now it is not that big of a disturbance but quite an annoyance. Besides I would like to understand the reason for this.
Could somebody help me please?
Offline
Couldn't you just type ~. to forcefully disconnect the ssh client? (That's tilde followed by period.)
Offline
Unfortunately I can't type anything because the console becomes unresponsive. So the only options I have are:
a. close that terminal and start a new one or
b. wait for that session to time-out (which gives me a client_loop: send disconnect: Broken pipe error afterwards.
Although I'm not very familiar with init.d my guess is that I need to change something in the way the services are shutdown (maybe the order) but I don't know where to start.
Offline
how about using
sudo reboot ; exit
Offline
@ralph.ronnquist That did the trick! Thanks a lot! I will make an alias with this one...
Offline
Actually it's Enter ~ ., although Enter is usually the last key pressed.
If the network gets deconfigured for some reason (for example dhcpcd killed) before sshd is terminated, then the system has no chance to properly close the connection.
AIX has a nice feature that redirects console output to the ssh session that initiated shutdown, so you can see rc messages when the system is shutting down.
Last edited by Matlib (2024-08-14 22:16:24)
Offline