System logged out suddenly.

New to Debian (Or Linux in general)? Ask your questions here!

System logged out suddenly.

Postby hack3rcon » 2020-06-29 12:26

Hello,
Sometimes when I'm working with the system then it logged out suddenly and all programs closed and I should logging to the system and open the programs again. For example, I'm working with the LibreOffice and it happened. I checked the dmesg and it shows:
Code: Select all
[Jun30 16:14] kauditd_printk_skb: 2 callbacks suppressed
[  +0.000003] audit: type=1400 audit(1593517495.348:14): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/proc/11
[  +0.000093] audit: type=1400 audit(1593517495.348:15): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/proc/11
[  +0.000025] audit: type=1400 audit(1593517495.348:16): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/
[  +0.007030] audit: type=1400 audit(1593517495.356:17): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/
[  +0.000004] audit: type=1400 audit(1593517495.356:18): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/
[  +0.000002] audit: type=1400 audit(1593517495.356:19): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/
[  +0.000008] audit: type=1400 audit(1593517495.356:20): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/
[  +0.000007] audit: type=1400 audit(1593517495.356:21): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/
[  +0.000007] audit: type=1400 audit(1593517495.356:22): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/
[  +0.000008] audit: type=1400 audit(1593517495.356:23): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/sys/fs/

Which other parts of system must be examined for the troubleshooting?

Thank you.
hack3rcon
 
Posts: 445
Joined: 2015-02-16 09:54

Re: System logged out suddenly.

Postby LE_746F6D617A7A69 » 2020-06-29 18:11

Post the output of:
Code: Select all
sudo journalctl -u systemd-logind
Bill Gates: "(...) In my case, I went to the garbage cans at the Computer Science Center and I fished out listings of their operating system."
The_full_story and Nothing_have_changed
LE_746F6D617A7A69
 
Posts: 394
Joined: 2020-05-03 14:16

Re: System logged out suddenly.

Postby hack3rcon » 2020-07-02 19:03

LE_746F6D617A7A69 wrote:Post the output of:
Code: Select all
sudo journalctl -u systemd-logind

It show the current log about the logging. How can I list it by date and time?
hack3rcon
 
Posts: 445
Joined: 2015-02-16 09:54

Re: System logged out suddenly.

Postby sickpig » 2020-07-02 23:36

what does it show?
User avatar
sickpig
 
Posts: 575
Joined: 2019-01-23 10:34

Re: System logged out suddenly.

Postby cuckooflew » 2020-07-03 00:05

LE_746F6D617A7A69 wrote:
Post the output of:

Code: Select all
Code: Select all
  sudo journalctl -u systemd-logind


You were asked to post the out put of the command, please do that so they can help you.
Also, just post the output, using the command as they show it,..if they wanted you to show something else they would have shown a different syntax.

At least try make a little effort your self, how to list by date and time using journalctl
===================================
First hit: https://www.thegeekdiary.com/beginners-guide-to-journalctl-how-to-use-journalctl-to-view-and-manipulate-systemd-logs/
Code: Select all
journalctl --since "2015-02-02 20:30:00" --until "2015-03-31 12:00:00"

Also you could have just looked at the manual:
Code: Select all
$ man journalctl

Code: Select all
$ journalctl --since "2017-06-15 08:15:00"
$ journalctl --since today
$ journalctl --since yesterday
Last edited by cuckooflew on 2020-07-03 00:28, edited 1 time in total.
Please Read What we expect you have already Done
Search Engines know a lot, and
"If God had wanted computers to work all the time, He wouldn't have invented RESET buttons"
and
Just say NO to help vampires!
cuckooflew
 
Posts: 683
Joined: 2018-05-10 19:34
Location: Some where out west

Re: System logged out suddenly.

Postby sickpig » 2020-07-03 00:15

@garry thanks for comming back.
cheers!
User avatar
sickpig
 
Posts: 575
Joined: 2019-01-23 10:34

Re: System logged out suddenly.

Postby cuckooflew » 2020-07-03 00:30

Noo, Garry is gone for ever,... I took over his computer and servers though, that is why the name pops up sometimes, ...
Please Read What we expect you have already Done
Search Engines know a lot, and
"If God had wanted computers to work all the time, He wouldn't have invented RESET buttons"
and
Just say NO to help vampires!
cuckooflew
 
Posts: 683
Joined: 2018-05-10 19:34
Location: Some where out west

Re: System logged out suddenly.

Postby sickpig » 2020-07-03 00:52

no
User avatar
sickpig
 
Posts: 575
Joined: 2019-01-23 10:34

Re: System logged out suddenly.

Postby hack3rcon » 2020-07-03 14:19

The output is:
Code: Select all
$ sudo journalctl -u systemd-logind
-- Logs begin at Thu 2020-07-02 22:33:14 +0430, end at Thu 2020-07-02 23:09:58 +0430. --
Jul 02 22:33:23 Xen systemd[1]: Starting Login Service...
Jul 02 22:33:23 Xen systemd-logind[708]: New seat seat0.
Jul 02 22:33:23 Xen systemd-logind[708]: Watching system buttons on /dev/input/event1 (Power Button)
Jul 02 22:33:23 Xen systemd-logind[708]: Watching system buttons on /dev/input/event0 (Power Button)
Jul 02 22:33:24 Xen systemd-logind[708]: Watching system buttons on /dev/input/event2 (SIGMACHIP USB Keyboar
Jul 02 22:33:24 Xen systemd-logind[708]: Watching system buttons on /dev/input/event3 (SIGMACHIP USB Keyboar
Jul 02 22:33:24 Xen systemd-logind[708]: Watching system buttons on /dev/input/event4 (SIGMACHIP USB Keyboar
Jul 02 22:33:26 Xen systemd[1]: Started Login Service.
Jul 02 22:34:31 Xen systemd-logind[708]: New session c1 of user lightdm.
Jul 02 22:34:46 Xen systemd-logind[708]: Removed session c1.
Jul 02 22:34:46 Xen systemd-logind[708]: New session 2 of user Jason.
hack3rcon
 
Posts: 445
Joined: 2015-02-16 09:54

Re: System logged out suddenly.

Postby cuckooflew » 2020-07-03 18:09

Thank you very much
Please Read What we expect you have already Done
Search Engines know a lot, and
"If God had wanted computers to work all the time, He wouldn't have invented RESET buttons"
and
Just say NO to help vampires!
cuckooflew
 
Posts: 683
Joined: 2018-05-10 19:34
Location: Some where out west

Re: System logged out suddenly.

Postby hack3rcon » 2020-07-07 09:46

It happened again:
Code: Select all
$ sudo journalctl -u systemd-logind
-- Logs begin at Mon 2020-07-06 17:39:46 +0430, end at Mon 2020-07-06 17:42:29 +
Jul 06 17:39:55 Xen systemd[1]: Starting Login Service...
Jul 06 17:39:55 Xen systemd-logind[708]: New seat seat0.
Jul 06 17:39:55 Xen systemd-logind[708]: Watching system buttons on /dev/input/e
Jul 06 17:39:55 Xen systemd-logind[708]: Watching system buttons on /dev/input/e
Jul 06 17:39:56 Xen systemd-logind[708]: Watching system buttons on /dev/input/e
Jul 06 17:39:56 Xen systemd-logind[708]: Watching system buttons on /dev/input/e
Jul 06 17:39:56 Xen systemd-logind[708]: Watching system buttons on /dev/input/e
Jul 06 17:39:58 Xen systemd[1]: Started Login Service.
Jul 06 17:41:03 Xen systemd-logind[708]: New session c1 of user lightdm.
Jul 06 17:41:30 Xen systemd-logind[708]: Removed session c1.
Jul 06 17:41:30 Xen systemd-logind[708]: New session 2 of user jason.
Jul 06 17:42:06 Xen systemd-logind[708]: Session 2 logged out. Waiting for proce
Jul 06 17:42:07 Xen systemd-logind[708]: New session c2 of user lightdm.
Jul 06 17:42:14 Xen systemd-logind[708]: Removed session c2.
Jul 06 17:42:14 Xen systemd-logind[708]: New session 5 of user jason.
hack3rcon
 
Posts: 445
Joined: 2015-02-16 09:54

Re: System logged out suddenly.

Postby LE_746F6D617A7A69 » 2020-07-07 14:18

I can see 2 problems here:
1. It looks like in Your system juornald logs are not persistent - and persistent logs have been enabled by systemd update few months ago - how is this possible? (*)
Anyway, You should enable persistent logs -> see the manual:
Code: Select all
man 5 journald.conf

2. Apparently logind logs wont tell anything useful - IMO the only chance is to enable debug mode for systemd, by adding kernel boot parameter:
Code: Select all
systemd.log_level=debug

Note: this will cause that a lot of additional information will be logged -> You should consider to set max log size limit in journald.conf

(*) EDIT: it's because stable has systemd v241-7~deb10u4, the update was available in backports ;)
Bill Gates: "(...) In my case, I went to the garbage cans at the Computer Science Center and I fished out listings of their operating system."
The_full_story and Nothing_have_changed
LE_746F6D617A7A69
 
Posts: 394
Joined: 2020-05-03 14:16


Return to Beginners Questions

Who is online

Users browsing this forum: No registered users and 12 guests

fashionable