BL closing programs by itself!

Kino · 2017-04-16 12:44:33

OK, I give up sad
Please report your issue with `journalctl` to Debian:
https://www.debian.org/Bugs/Reporting
Thanks!

Sorry, but I don't understand what the problem is!
I rebooted twice and the journal seems to reflect this.

I can't report a bug if I don't know what it is...

Head_on_a_Stick · 2017-04-16 13:10:13

Kino wrote:

I rebooted twice and the journal seems to reflect this.

No it doesn't, the output posted only shows journal contents for the current boot.

Every time you reboot with that configuration (Storage=auto, /var/log/journal present), a new entry should appear in the output of the `journalctl --list-boots` command — this is not happening in your system

The journal contents for the previous boot should now be accesible, at least according to the posted configuration details, this is the problem which I am suggesting should be reported.

Without the logs from the previous boot, it is very difficult to track down the source of the problem in the OP.

Kino · 2017-04-16 17:12:50

Sorry, but I'm still confused.

Aren't there two boots listed?:

Thu 2017-04-13 09:41:14 BST
and
Thu 2017-04-13 09:41:42 BST

Head_on_a_Stick · 2017-04-16 20:16:16

Kino wrote:

Aren't there two boots listed?:
Thu 2017-04-13 09:41:14 BST
and
Thu 2017-04-13 09:41:42 BST

From which command output are you extracting this snippet?

I was basing my statement on this output:

Kino wrote:

:~$ journalctl --list-boots
 0 f0460fc421dc46678d5cae03fe535c15 Thu 2017-04-13 09:41:14 BST—Thu 2017-04-13 09:41:42 BST

https://forums.bunsenlabs.org/viewtopic … 983#p48983

Unless the current output of the `journalctl --list-boots` command has more than one line, your system is not recording the journal contents to disk as it should.

And of course `journalctl -b -1` still does not work, no?

That is, after all, the object of our little side quest here...

Head_on_a_Stick · 2017-04-16 20:25:09

Just found this:

https://forums.bunsenlabs.org/viewtopic.php?id=2906

tl;dr: try the jessie-backports version of systemd

Horizon_Brave · 2017-04-16 20:40:43

Head_on_a_Stick wrote:

Just found this:
https://forums.bunsenlabs.org/viewtopic.php?id=2906
tl;dr: try the jessie-backports version of systemd

I was just about to post that my (non-back ported) version as well only shows 1 boot log as well with the --list-boots command:

kingcaesar@kingcaesar:~$ sudo journalctl --list-boots
 0 3f792c1b925a40038b4cefd8a34dc851 Sun 2017-04-16 16:32:44 EDT—Sun 2017-04-16 16:38:34 EDT
kingcaesar@kingcaesar:~$

My journal.conf is set properly, HoaS think this is something that was rolled natively into Stretch? Without back porting?

Head_on_a_Stick · 2017-04-16 20:56:45

Horizon_Brave wrote:

think this is something that was rolled natively into Stretch? Without back porting?

I do not understand your question, why are you asking about stretch? The systemd package *has* been backported, hence my suggestion.

The OP does not track testing/unstable (AFAIK).

Horizon_Brave · 2017-04-16 21:17:50

Head_on_a_Stick wrote:

Horizon_Brave wrote:
think this is something that was rolled natively into Stretch? Without back porting?
I do not understand your question, why are you asking about stretch? The systemd package *has* been backported, hence my suggestion.
The OP does not track testing/unstable (AFAIK).

Erm..Nevermind...

Kino · 2017-04-17 05:27:45

Ok, I tried https://forums.bunsenlabs.org/viewtopic.php?id=2906 but I'm in way over my head here...

:~$ systemd --version
systemd 215
+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR
:~$ ls -l /var/log/journal/*/system* | head
-rw-r----- 1 root root             8388608 Apr 13 09:40 /var/log/journal/0c51bd665150458da2df13a952aa0990/system.journal
-rw-r----- 1 root systemd-journal 16777216 Apr 17 06:11 /var/log/journal/6702930f2b8d41e6ad01a6ba197493c9/system.journal
:~$ journalctl --file /var/log/journal/6702930f2b8d41e6ad01a6ba197493c9/system.journal
-- Logs begin at Thu 2017-04-13 09:41:14 BST, end at Mon 2017-04-17 06:17:01 BST. --
Apr 13 09:41:14 dell-pc systemd-journal[229]: Runtime journal is using 8.0M (max allowed 77.6M, trying to leave 116.4M free of 767.9M available → current
Apr 13 09:41:14 dell-pc systemd-journal[229]: Runtime journal is using 8.0M (max allowed 77.6M, trying to leave 116.4M free of 767.9M available → current
Apr 13 09:41:14 dell-pc kernel: microcode: microcode updated early to revision 0xd0, date = 2010-09-30
Apr 13 09:41:14 dell-pc kernel: Linux version 4.7.0-0.bpo.1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4
Apr 13 09:41:14 dell-pc kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.7.0-0.bpo.1-amd64 root=UUID=748c34ea-42a8-4355-866e-f0dc6dde2a28 ro initrd=/inst
Apr 13 09:41:14 dell-pc kernel: Disabled fast string operations
Apr 13 09:41:14 dell-pc kernel: x86/fpu: Legacy x87 FPU detected.
Apr 13 09:41:14 dell-pc kernel: x86/fpu: Using 'eager' FPU context switches.
Apr 13 09:41:14 dell-pc kernel: e820: BIOS-provided physical RAM map:
Apr 13 09:41:14 dell-pc kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
Apr 13 09:41:14 dell-pc kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
Apr 13 09:41:14 dell-pc kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000bf5ffbff] usable
Apr 13 09:41:14 dell-pc kernel: BIOS-e820: [mem 0x00000000bf5ffc00-0x00000000bf601bff] ACPI NVS
Apr 13 09:41:14 dell-pc kernel: BIOS-e820: [mem 0x00000000bf603c00-0x00000000bfffffff] reserved
Apr 13 09:41:14 dell-pc kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Apr 13 09:41:14 dell-pc kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fed003ff] reserved
Apr 13 09:41:14 dell-pc kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed9ffff] reserved
Apr 13 09:41:14 dell-pc kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000feefffff] reserved
Apr 13 09:41:14 dell-pc kernel: BIOS-e820: [mem 0x00000000ffb00000-0x00000000ffffffff] reserved
Apr 13 09:41:14 dell-pc kernel: BIOS-e820: [mem 0x0000000100000000-0x000000013bffffff] usable
Apr 13 09:41:14 dell-pc kernel: NX (Execute Disable) protection: active
Apr 13 09:41:14 dell-pc kernel: SMBIOS 2.3 present.
Apr 13 09:41:14 dell-pc kernel: DMI: Dell Inc.                 OptiPlex 745                 /0MM599, BIOS 2.3.1  05/21/2007
Apr 13 09:41:14 dell-pc kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Apr 13 09:41:14 dell-pc kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Apr 13 09:41:14 dell-pc kernel: e820: last_pfn = 0x13c000 max_arch_pfn = 0x400000000

Horizon_Brave · 2017-04-17 19:18:20

Actually, screw it, bashful nature be damned, I've given up on saving face..

HoaS what I was asking is that because the fix for this issue is in systemd version 230 is in Jessie-backports ...software that'd been fit to work on earlier kernels, that would imply that the 230 (or higher version) is already in the Stretch release? (most of Jessie-backports are "backported" from Stretch...)

@Kino,

So it looks like you're still running version 215, you can update it, but you'll have to enable backporting modules in your /etc/apt/sourches/

sudo tee -a /etc/apt/sources.list <<< "deb http://httpredir.debian.org/debianjessie-backports main contrib non-free"

Then update the APT package database:

sudo apt-get update

Then you should be able to install from the backport repos...careful where you play though, I hear it's rough around the edges!

Head_on_a_Stick · 2017-04-17 22:18:11

Horizon_Brave wrote:

the 230 (or higher version) is already in the Stretch release?

Yes.

https://packages.debian.org/stretch/systemd

You could also have used the madison option for apt-cache(8) to list all available versions of a package:

apt-cache madison systemd

EDIT: also:

H_B wrote:

the Stretch release

Debian stretch is still a development branch, I will let you know when it is actually released as Debian 9

Last edited by Head_on_a_Stick (2017-04-17 22:27:06)

Horizon_Brave · 2017-04-18 02:39:29

Whoops I provided the command for the older httpredir.... hmm I assume that

"deb http://cdn-fastly.deb.debian.org/debianjessie-backports main contrib non-free"

Is the proper new cdn fqdn for backports..

And yea I know Debby Stretch is still in dev technically... but it's so close to being officially Debian 9 Stable, I'm just blurring the two...

damo · 2017-04-18 03:19:38

Horizon_Brave wrote:

Whoops I provided the command for the older httpredir.... hmm I assume that
"deb http://cdn-fastly.deb.debian.org/debianjessie-backports main contrib non-free"
Is the proper new cdn fqdn for backports..
And yea I know Debby Stretch is still in dev technically... but it's so close to being officially Debian 9 Stable, I'm just blurring the two...

There is a typo in your deb line

# Debian backports
deb http://cdn-fastly.deb.debian.org/debian jessie-backports main contrib non-free

I've just updated the sources.list details: Sources - sources.list and backports details

httpredir still works though.

Last edited by damo (2017-04-18 03:22:13)

Kino · 2017-04-18 06:42:04

I can actually live with this for now...

As far as the issue with systemd goes, can I wait and do a

sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

at an appropriate time?

Last edited by Kino (2017-04-18 06:42:21)

damo · 2017-04-18 06:57:37

^ You are running Stable AFAIK, so a dist-upgrade is a rare event. Or you can upgrade to the backports version of systemd.

Horizon_Brave · 2017-04-18 17:05:34

Head_on_a_Stick wrote:

You could also have used the madison option for apt-cache(8) to list all available versions of a package:
apt-cache madison systemd

Ooo that's a new one on me... Same sort of output as apt-cache policy, but less verbose...

Kino, you should try out the backported 'newer' systemd 230 you may find the other newer features helpful as well

Kino · 2017-04-25 07:51:08

OK, I have just got round to trying to install a newer version of systemd - but without success.
Not sure what I'm doing wrong.

First I updated my sources as per

sudo tee -a /etc/apt/sources.list <<< "deb http://httpredir.debian.org/debian jessie-backports main contrib non-free"

then

sudo apt-get update

followed by

sudo apt-get upgrade

After reboot I still have

systemd --version
systemd 215
+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR

Do I need to install systemd via the command line?

damo · 2017-04-25 07:58:28

You need to specifically install a package from backports, otherwise the stable one is the only one in use.....

sudo apt-get install -t jessie-backports $packagename

Sources - sources.list and backports details

Kino · 2017-04-25 08:54:14

OK - thanks.

:~$ systemd --version
systemd 230
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
:~$ grep Storage /etc/systemd/journald.conf
#Storage=auto
:~$ sudo journalctl -b -1
[sudo] password for kino: 
-- Logs begin at Tue 2017-04-25 09:42:46 BST, end at Tue 2017-04-25 09:46:02 BST. --
Apr 25 09:42:46 dell-pc systemd-journald[735]: Runtime journal (/run/log/journal/) is 8.0M, max 77.6M, 69.6M free.

the command

sudo journalctl -b -1

shows lines 1-18 and hitting the return key keeps showing even more lines (>100) so I stopped.

And now

:~$ journalctl --list-boots
-1 7e54abebaa15440081c823449664bfcb Tue 2017-04-25 09:42:46 BST—Tue 2017-04-25 09:4
 0 f4bfe67632e34d2792190bbe519b1629 Tue 2017-04-25 09:43:57 BST—Tue 2017-04-25 09:5
lines 1-2/2 (END)

seems to be working ok.

So again, see you in 13 days!

damo · 2017-04-25 09:08:15

Kino wrote:

....
the command
sudo journalctl -b -1
shows lines 1-18 and hitting the return key keeps showing even more lines (>100) so I stopped.

Use Page-Down, or scroll. My journal has 1800+ lines! Read up on the other options for filtering etc...

man journalctl

#61 2017-04-16 12:44:33

Re: BL closing programs by itself!

#62 2017-04-16 13:10:13

Re: BL closing programs by itself!

#63 2017-04-16 17:12:50

Re: BL closing programs by itself!

#64 2017-04-16 20:16:16

Re: BL closing programs by itself!

#65 2017-04-16 20:25:09

Re: BL closing programs by itself!

#66 2017-04-16 20:40:43

Re: BL closing programs by itself!

#67 2017-04-16 20:56:45

Re: BL closing programs by itself!

#68 2017-04-16 21:17:50

Re: BL closing programs by itself!

#69 2017-04-17 05:27:45

Re: BL closing programs by itself!

#70 2017-04-17 19:18:20

Re: BL closing programs by itself!

#71 2017-04-17 22:18:11

Re: BL closing programs by itself!

#72 2017-04-18 02:39:29

Re: BL closing programs by itself!

#73 2017-04-18 03:19:38

Re: BL closing programs by itself!

#74 2017-04-18 06:42:04

Re: BL closing programs by itself!

#75 2017-04-18 06:57:37

Re: BL closing programs by itself!

#76 2017-04-18 17:05:34

Re: BL closing programs by itself!

#77 2017-04-25 07:51:08

Re: BL closing programs by itself!

#78 2017-04-25 07:58:28

Re: BL closing programs by itself!

#79 2017-04-25 08:54:14

Re: BL closing programs by itself!

#80 2017-04-25 09:08:15

Re: BL closing programs by itself!

Board footer