Ubuntu 20.04.3 desktop (Cinnamon) - SSH disconnects when user logs off the desktop!

[Bo Berglund]

On Sun, 23 Jan 2022 10:35:46 +0000, Colin Law <clanlaw at gmail.com> wrote:

>On Sat, 22 Jan 2022 at 23:01, Bo Berglund <bo.berglund at gmail.com> wrote:
>>
>> On Sat, 22 Jan 2022 21:42:27 +0000, Colin Law <clanlaw at gmail.com> wrote:
>>
>> >On Sat, 22 Jan 2022 at 21:15, Bo Berglund <bo.berglund at gmail.com> wrote:
>> >>
>> >> Every time it reboots I get about 1360-1400 lines of logging into syslog, which
>> >> cannot be filtered by grep eithar. :(
>> >>
>> >
>> >Can you put syslog on a sharing site so we can have a look?
>> >
>> Here you go:
>> https://blog.boberglund.com/files/syslog.bosse.gz
>
>The file isn't a gz file, it is the original syslog text.

Except the gz file is 3.6 MB whereeas the syslog itself is more than 20 MB...

>The reason grep has problems is that there are non-printable
>characters in the file.  The start of each reboot is marked by a jump
>of a few minutes in the timestamp and at that point there are often
>unprintable characters (probably nulls, but I haven't checked that
>far).  This usually means that there was a power failure or hard
>reset.

But it only ever happens if the system is waiting for a local system login...
When either desktop is active (not counting VNC because that is not stopping
this), then the system is stable "forever"...

>So either there is a hardware problem or problem with the
>power supply or something very odd is going on. I don't know of any
>way that software can trigger a hard reset.
>

I just made a test as follows:
1) The system has been on the Cinnamon desktop on the hardware since 12 hours at
least
2) I have had a PuTTY session open since then too
3) This morning 11:39:00 I logged out of the desktop and stay on the login
screen
4) At 11:45:23 the on-boot script was called after a reboot happened

So it took 384 seconds after I logged off the GUI session until the system was
done rebooted and called the crontab on-boot entry for reporting.

The interval between calls thereafter is very accurate as 384 +/- 1 second or
so.

I opened PuTTY again and ran journalctl -b -1 -e and got this at the time of
logout and forward:

jan 23 11:39:03 asposerver gnome-session-binary[14694]: Entering running state
jan 23 11:39:03 asposerver xbrlapi.desktop[15015]: openConnection: connect: No
such file or directory
jan 23 11:39:03 asposerver xbrlapi.desktop[15015]: cannot connect to braille
devices daemon brltty at :0
jan 23 11:39:04 asposerver gnome-shell[14745]: Registering session with GDM
jan 23 11:39:09 asposerver gnome-shell[14745]: Warning: Failed to start
gsd-xsettings
jan 23 11:39:09 asposerver gnome-shell[14745]: JS WARNING:
[resource:///org/gnome/shell/ui/layout.js 24]: reference to undefined property
"MetaWindowXwayland"
jan 23 11:39:12 asposerver systemd[14673]: tracker-extract.service: Succeeded.
jan 23 11:39:32 asposerver tracker-store[14789]: OK
jan 23 11:39:32 asposerver systemd[14673]: tracker-store.service: Succeeded.
jan 23 11:39:33 asposerver systemd[1]: fprintd.service: Succeeded.
jan 23 11:39:33 asposerver systemd[1]: systemd-localed.service: Succeeded.
jan 23 11:39:33 asposerver systemd[1]: systemd-hostnamed.service: Succeeded.
jan 23 11:40:03 asposerver geoclue[14842]: Service not used for 60 seconds.
Shutting down..
jan 23 11:40:03 asposerver systemd[1]: geoclue.service: Succeeded.

That ends the output...


-- 
Bo Berglund
Developer in Sweden