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

[Bo Berglund]

On Wed, 18 May 2022 07:50:57 +0100, Colin Law <clanlaw at gmail.com> wrote:

>Have a look at /var/log/syslog to see if it gives any clues about what is
>going on.
>
>Also check that the bios/firmware is up to date.

System f/w was updated very recently (a month or so ago).

The syslog does not give me any clues, I know when I power cycled the system via
the Shellyplug because it is set up to email me a report when it chjanges state.
So I power cycled the system on May 17 at 08:31:00.

To reiterate this is what I did leading up to the crash:
- sudo apt update
- sudo apt full-upgrade
- sudo reboot

At this point the system became inaccessible and I could no longer log on using
ssh.

Here is an excerpt from syslog around the power cycle starting about 30 min
before I power cycled the unit (I have cut down very long lines) until the
normal start log streams along.:

--------------------------------------------------------------------------
May 17 07:44:57 aspomint dbus-daemon[658]: [system] Successfully activated
service 'org.freedesktop.PackageKit'
May 17 07:44:57 aspomint systemd[1]: Started PackageKit Daemon.
May 17 07:50:02 aspomint PackageKit: daemon quit
May 17 07:50:02 aspomint systemd[1]: packagekit.service: Succeeded.
May 17 07:55:01 aspomint CRON[1197783]: (bosse) CMD (/home/bosse/bin/getm3u8url
8)
May 17 07:55:01 aspomint CRON[1197782]: (CRON) info (No MTA installed,
discarding output)
May 17 08:03:54 aspomint atd[1196928]: Exec failed for mail command: No such
file or directory
May 17 08:08:07 aspomint NetworkManager[662]: <info>  [1652767687.6318] manager:
NetworkManager state is now CONNECTED_SITE
May 17 08:08:07 aspomint dbus-daemon[658]: [system] Activating via systemd:
service name='org.freedesktop.nm_dispatcher'
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0
pid=662 comm="/usr/sbin/NetworkManager --no-daemon " label="u>
May 17 08:08:07 aspomint systemd[1]: Starting Network Manager Script Dispatcher
Service...
May 17 08:08:07 aspomint dbus-daemon[658]: [system] Successfully activated
service 'org.freedesktop.nm_dispatcher'
May 17 08:08:07 aspomint systemd[1]: Started Network Manager Script Dispatcher
Service.
May 17 08:08:07 aspomint NetworkManager[662]: <info>  [1652767687.8836] manager:
NetworkManager state is now CONNECTED_GLOBAL
May 17 08:08:18 aspomint systemd[1]: NetworkManager-dispatcher.service:
Succeeded.
May 17 08:08:27 aspomint atd[1197794]: Exec failed for mail command: No such
file or directory
May 17 08:08:34 aspomint systemd[1]: fwupd.service: Succeeded.
May 17 08:11:01 aspomint CRON[1197939]: (bosse) CMD (/home/bosse/bin/ipreport.sh
1 > /dev/null 2>&1)
May 17 08:13:05 aspomint dbus-daemon[658]: [system] Activating via systemd:
service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by
':1.4113' (uid=0 pid=1198365 comm="/usr/bin/gdbus call --system --dest
org.freedeskto" label="unconfine>
May 17 08:13:05 aspomint systemd[1]: Starting PackageKit Daemon...
May 17 08:13:05 aspomint PackageKit: daemon start
May 17 08:13:05 aspomint dbus-daemon[658]: [system] Successfully activated
service 'org.freedesktop.PackageKit'
May 17 08:13:05 aspomint systemd[1]: Started PackageKit Daemon.

----- Here the system is not responding at all -----
----- So I activated the Shellyplug switch to force a power cycle at 08:31 -----

May 17 08:31:27 aspomint systemd-modules-load[374]: Inserted module 'lp'
May 17 08:31:27 aspomint kernel: [    0.000000] Linux version 5.4.0-110-generic
(buildd at ubuntu) (gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)) #124-Ubuntu
SMP Thu Apr 14 19:46:19 UTC 2022 (Ubuntu 5.4.0-110.124-generic 5.4.181)
May 17 08:31:27 aspomint systemd-modules-load[374]: Inserted module 'ppdev'
May 17 08:31:27 aspomint systemd-modules-load[374]: Inserted module 'parport_pc'
May 17 08:31:27 aspomint kernel: [    0.000000] Command line:
BOOT_IMAGE=/boot/vmlinuz-5.4.0-110-generic
root=UUID=4b1716f6-4dce-456f-9772-7b5f2241bb1f ro quiet splash vt.handoff=7
May 17 08:31:27 aspomint systemd-modules-load[374]: Inserted module 'msr'
------------------------------------------------------------------------

>From here on out there are *lots* of normal system start log lines and in the
end I was able to log on.



-- 
Bo Berglund
Developer in Sweden