BL closing programs by itself!

Head_on_a_Stick · 2017-02-07 19:37:49

Kino wrote:

On reboot I had an i/o error

Have you tried a memtest and a SMART check?

You can set the systemd journal logs to persistent with:

sudo mkdir /var/log/journal

Then use this command to view the logs of the previous boot (if this happens again):

sudo journalctl -b -1

Kino · 2017-03-04 10:44:06

OK - it's just happened again!
System has been up and running for just over 13 days. Open programs were libreoffice calc, gedit, firefox and file manager - all closed down.

This is the x-sessions error log:

Xsession: X session started for kino at Sat  4 Mar 10:37:03 GMT 2017
localuser:kino being added to access control list
export DBUS_SESSION_BUS_ADDRESS='unix:abstract=/tmp/dbus-qJlCbpKu5l,guid=581a6cf06481a38429da19fe58ba98cf'
export DESKTOP_SESSION='lightdm-xsession'
export DISPLAY=':0'
export GDMSESSION='lightdm-xsession'
export HOME='/home/kino'
export LANG='en_GB.UTF-8'
export LANGUAGE='en_GB:en'
export LOGNAME='kino'
export PATH='/home/kino/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games'
export PWD='/home/kino'
export QT_STYLE_OVERRIDE='GTK+'
export SHELL='/bin/bash'
export SSH_AGENT_PID='14156'
export SSH_AUTH_SOCK='/tmp/ssh-3A6LAaD7IH16/agent.14130'
export USER='kino'
export XAUTHORITY='/home/kino/.Xauthority'
export XDG_GREETER_DATA_DIR='/var/lib/lightdm/data/kino'
export XDG_RUNTIME_DIR='/run/user/1000'
export XDG_SEAT='seat0'
export XDG_SEAT_PATH='/org/freedesktop/DisplayManager/Seat0'
export XDG_SESSION_ID='358'
export XDG_SESSION_PATH='/org/freedesktop/DisplayManager/Session0'
export XDG_VTNR='7'
Failure: Module initialization failed
/home/kino/.config/openbox/autostart: 53: /home/kino/.config/openbox/autostart: volti: not found
tint2 : nb monitor 1, nb monitor used 1, nb desktop 5
Loading Faenza-Dark-Bunsen. Icon theme : 'Faenza-Dark-Bunsen', 'Faenza-Bunsen-common', 'Faenza-Dark', 'Faenza', 'gnome', 'hicolor',
Conky: forked to background, pid is 14265
Conky: forked to background, pid is 14266
Conky: forked to background, pid is 14267
Conky: forked to background, pid is 14268
Conky: forked to background, pid is 14269


Conky: desktop window (8a) is root window
Conky: window type - normal

Conky: drawing to created window (0x2a00001)


Conky: drawing to double buffer
Conky: desktop window (8a) is root window
Conky: window type - desktop
Conky: drawing to created window (0x2e00001)
Conky: drawing to double buffer
Conky: desktop window (8a) is root window
Conky: window type - normal
Conky: desktop window (8a) is root window
Conky: drawing to created window (0x2800001)
Conky: window type - normal
Conky: desktop window (8a) is root window
Conky: drawing to double buffer
Conky: window type - normal
Conky: drawing to created window (0x1200001)
Conky: drawing to double buffer
Conky: drawing to created window (0x2c00001)
Conky: drawing to double buffer
launcher.c 215: Using icon /usr/share/icons/Faenza-Bunsen-common/categories/22/applications-internet.png
launcher.c 215: Using icon /usr/share/icons/Faenza-Bunsen-common/apps/22/system-file-manager.png
launcher.c 215: Using icon /usr/share/icons/Faenza-Bunsen-common/apps/22/accessories-text-editor.png
launcher.c 215: Using icon /usr/share/icons/Faenza-Bunsen-common/apps/22/utilities-terminal.png
tint2 : nb monitor 1, nb monitor used 1, nb desktop 5
Loading Faenza-Dark-Bunsen. Icon theme : 'Faenza-Dark-Bunsen', 'Faenza-Bunsen-common', 'Faenza-Dark', 'Faenza', 'gnome', 'hicolor',
launcher.c 215: Using icon /usr/share/icons/Faenza-Bunsen-common/categories/22/applications-internet.png
launcher.c 215: Using icon /usr/share/icons/Faenza-Bunsen-common/apps/22/system-file-manager.png
launcher.c 215: Using icon /usr/share/icons/Faenza-Bunsen-common/apps/22/accessories-text-editor.png
launcher.c 215: Using icon /usr/share/icons/Faenza-Bunsen-common/apps/22/utilities-terminal.png
** Message: x-terminal-emulator has very limited support, consider choose another terminal

There does seem to be an issue with the terminal emulator - any ideas??

damo · 2017-03-04 11:26:30

Kino wrote:

...
There does seem to be an issue with the terminal emulator - any ideas??

Maybe not - it seems to be a common message if you google it. Try a different one? ( Menu -> System -> Edit Debian Alternatives ).

It is possible it is a hardware issue. Have you tested the system's memory? Monitored the temperature?

Kino · 2017-03-04 13:31:16

I did a memtest and there were no problems.
I have 4G of memory and oodles of disc space... can't monitor temp.

I'll try a alternative emulator and reboot (and wait 13 days?)

Head_on_a_Stick · 2017-03-04 14:43:37

Head_on_a_Stick wrote:

Then use this command to view the logs of the previous boot (if this happens again):
sudo journalctl -b -1

That terminal emulator message is sarcastic — I also get that if rxvt-unicode is set to the default...

Kino · 2017-04-08 06:34:10

Here we are again!

Another 13 days of being logged in and now all the open programmes have been closed down but everything else (i.e conky) running as normal.

Unfortunately,

sudo journalctl -b -1
[sudo] password for kino:
Failed to look up boot -1: Cannot assign requested address

So I'm none the wiser.

Head_on_a_Stick · 2017-04-08 09:30:09

Please post the output of:

[ -d /var/log/journal ] && echo Should work but doesn\'t || echo Please read post \#41 again

EDIT: see also http://forums.debian.net/viewtopic.php?p=641172#p641172

Last edited by Head_on_a_Stick (2017-04-08 09:37:20)

Kino · 2017-04-08 09:48:20

[ -d /var/log/journal ] && echo Should work but doesn\'t || echo Please read post \#41 again
Should work but doesn't

and

sudo mkdir /var/log/journal
[sudo] password for kino: 
mkdir: cannot create directory ‘/var/log/journal’: File exists

also from your link - I do seem to have the journal logging enabled?

Last edited by Kino (2017-04-08 09:49:46)

Head_on_a_Stick · 2017-04-08 09:52:23

Kino wrote:

I do seem to have the journal logging enabled?

You should have but it doesn't seem to be working.

Try editing /etc/systemd/journald.conf instead, as per my fdn link.

You can also add your user to the systemd-journal group so that you can view the logs without `sudo`:

sudo gpasswd -a $USER systemd-journal

Kino · 2017-04-08 12:49:10

OK - have now done that.
Will reboot and see you in 13 days!

Head_on_a_Stick · 2017-04-08 19:09:44

^ Yes, sorry about that — I should have insisted that you confirm the efficacy of `journalctl -b -1` *before* suffering the next failure...

I presume that the command works now?

Kino · 2017-04-09 14:15:02

Actually no - it doesn't!

journalctl -b -1
Failed to look up boot -1: Cannot assign requested address

I think I've done everything correctly...

Head_on_a_Stick · 2017-04-09 14:21:06

Oh dear...

Can we see the output of:

find /var/log/journal
journalctl --list-boots

The second command may be a stretch-only option, which would be a shame as it's very useful...

Kino · 2017-04-09 17:05:00

OK - here goes:

find /var/log/journal
/var/log/journal
/var/log/journal/3e56a3c7a9eb4d6d9211ac1f660153db
/var/log/journal/3e56a3c7a9eb4d6d9211ac1f660153db/system.journal
/var/log/journal/3e56a3c7a9eb4d6d9211ac1f660153db/user-1000.journal
/var/log/journal/dd615b934cb54695b7041db5ef67330a
/var/log/journal/dd615b934cb54695b7041db5ef67330a/system.journal
/var/log/journal/dd615b934cb54695b7041db5ef67330a/user-1000.journal
/var/log/journal/fd40f5326f7e43cda4cf832f6fd46c71
/var/log/journal/fd40f5326f7e43cda4cf832f6fd46c71/system.journal
/var/log/journal/fd40f5326f7e43cda4cf832f6fd46c71/user-1000.journal
/var/log/journal/66469164a2564f8f873dab67e15b901c
/var/log/journal/66469164a2564f8f873dab67e15b901c/system.journal
/var/log/journal/66469164a2564f8f873dab67e15b901c/user-1000.journal
/var/log/journal/f1cebcb787554ea5ad4b9371d89e092b
/var/log/journal/f1cebcb787554ea5ad4b9371d89e092b/system.journal
/var/log/journal/f1cebcb787554ea5ad4b9371d89e092b/user-1000.journal
/var/log/journal/2c3e22391c2940a9b1a3633b31b92d04
/var/log/journal/2c3e22391c2940a9b1a3633b31b92d04/system.journal
/var/log/journal/2c3e22391c2940a9b1a3633b31b92d04/user-1000.journal
/var/log/journal/fc7de76bbd5e45ac92ef9bfb06a85de8
/var/log/journal/fc7de76bbd5e45ac92ef9bfb06a85de8/system.journal
/var/log/journal/fc7de76bbd5e45ac92ef9bfb06a85de8/user-1000.journal
journalctl --list-boots
 0 b2be3a9e84fb463ba37f07067d85c6b2 Sat 2017-04-08 13:49:27 BST—Sun 2017-04-09 17:59:46 BST

Head_on_a_Stick · 2017-04-09 21:08:53

How about

grep Storage /etc/systemd/journald.conf

Kino · 2017-04-10 06:33:34

That would be

grep Storage /etc/systemd/journald.conf
Storage=persistent

Head_on_a_Stick · 2017-04-10 07:00:52

Weird

I must have messed something up.

Try removing /var/log/journal and recreating the directory afresh then set Storage to auto:

sudo rm -rf /var/log/journal # careful here, you could wipe your system with a typo
sudo mkdir -p /var/log/journal
sudo sed -i 's/persistent/auto/' /etc/systemd/journald.conf # or use an editor

Then reboot twice and check for two boot logs in `journalctl --list-boots`

Sector11 · 2017-04-10 19:33:50

MOD EDIT:

S11's question split as; off topic & steals thread, continues here.
Sorry for any inconvenience.

Kino · 2017-04-13 08:45:47

OK - in response to post #57

:~$ find /var/log/journal
/var/log/journal
/var/log/journal/6702930f2b8d41e6ad01a6ba197493c9
/var/log/journal/6702930f2b8d41e6ad01a6ba197493c9/system.journal
/var/log/journal/6702930f2b8d41e6ad01a6ba197493c9/user-1000.journal
/var/log/journal/0c51bd665150458da2df13a952aa0990
/var/log/journal/0c51bd665150458da2df13a952aa0990/system.journal
/var/log/journal/0c51bd665150458da2df13a952aa0990/user-1000.journal
:~$ journalctl --list-boots
 0 f0460fc421dc46678d5cae03fe535c15 Thu 2017-04-13 09:41:14 BST—Thu 2017-04-13 09:41:42 BST
:~$ grep Storage /etc/systemd/journald.conf
Storage=auto

Head_on_a_Stick · 2017-04-16 10:41:48

OK, I give up

Please report your issue with `journalctl` to Debian:

https://www.debian.org/Bugs/Reporting

Thanks!

#41 2017-02-07 19:37:49

Re: BL closing programs by itself!

#42 2017-03-04 10:44:06

Re: BL closing programs by itself!

#43 2017-03-04 11:26:30

Re: BL closing programs by itself!

#44 2017-03-04 13:31:16

Re: BL closing programs by itself!

#45 2017-03-04 14:43:37

Re: BL closing programs by itself!

#46 2017-04-08 06:34:10

Re: BL closing programs by itself!

#47 2017-04-08 09:30:09

Re: BL closing programs by itself!

#48 2017-04-08 09:48:20

Re: BL closing programs by itself!

#49 2017-04-08 09:52:23

Re: BL closing programs by itself!

#50 2017-04-08 12:49:10

Re: BL closing programs by itself!

#51 2017-04-08 19:09:44

Re: BL closing programs by itself!

#52 2017-04-09 14:15:02

Re: BL closing programs by itself!

#53 2017-04-09 14:21:06

Re: BL closing programs by itself!

#54 2017-04-09 17:05:00

Re: BL closing programs by itself!

#55 2017-04-09 21:08:53

Re: BL closing programs by itself!

#56 2017-04-10 06:33:34

Re: BL closing programs by itself!

#57 2017-04-10 07:00:52

Re: BL closing programs by itself!

#58 2017-04-10 19:33:50

Re: BL closing programs by itself!

#59 2017-04-13 08:45:47

Re: BL closing programs by itself!

#60 2017-04-16 10:41:48

Re: BL closing programs by itself!

Board footer