Reboot on ssh command locks up device, how to solve?

[Bo Berglund]

On Wed, 18 May 2022 21:17:58 +0200, Bo Berglund <bo.berglund at gmail.com> wrote:

>On Wed, 18 May 2022 19:33:39 +0100, Colin Law <clanlaw at gmail.com> wrote:
>
>>On Wed, 18 May 2022 at 18:28, Bo Berglund <bo.berglund at gmail.com> wrote:
>>> ...
>>> But I guess that finding this needle in the haystack is bwyond my capabilities,
>>> so I will rely on the shelly plug for future mishaps too.
>>
>>Possibly there is a process that refuses to stop and hangs the reboot.
>>Try it with -f and see if that does it.
>>
>>Colin
>
>I will have to wait until tomorrow morning (Sweden) to do that because the
>system is busy until 07:00 CET
>
>But then I could presumably test by running a sudo reboot -f and if that works
>then also test sudo reboot.
>

UPDATE:

Now I stopped all running at jobs and then tried 'sudo reboot -f' from the PuTTY
session.

It worked as follows:

- Cursor moved one line down and stayed there, no output
- No keboard action worked anymore (expected)
- A delay of some 10-15 seconds
- Printed "rebooting" on screen (never seen that before)
- Then the network disappeared and PuTTY showed the alert message
- When I next connected with PuTTY after some 30 s it worked fine.

In all other devices I have used the reboot command the PuTTY message about lost
connection is instant, but here it takes a while for it to come.

But unlike with only 'sudo reboot', adding -f seems to have the wanted effect of
making a "clean" reboot.

Thanks!


-- 
Bo Berglund
Developer in Sweden