raspbian - systemd

Turbocapitalist · 02-13-2019, 02:00 AM

I've got Raspbian GNU/Linux 9.6 (stretch) and would like to debug some freequent systemd failures. Mostly it boots fine, but at intervals which I cannot predict, the machine fails to boot.

I've let it wait many tens of minutes in some cases but only power cycling helps, sometimes twice in a row is needed. I was hoping that the logs would contain something but when running journalctl I get the error:
"Specifying boot ID has no effect, no persistent journal was found"

How can I enable persistent logging in systemd so that I may check the logs from previous attempts at booting when this happens again?

syg00 · 02-13-2019, 02:08 AM

"man journald.conf"

Turbocapitalist · 02-13-2019, 02:27 AM

Thanks.

Code:

$ diff -u /etc/systemd/journald.conf.orig  /etc/systemd/journald.conf
--- /etc/systemd/journald.conf.orig     2019-02-13 10:21:31.429086408 +0200
+++ /etc/systemd/journald.conf  2019-02-13 10:17:02.580540911 +0200
@@ -12,6 +12,7 @@
 # See journald.conf(5) for details.

 [Journal]
+Storage=persistent
 #Storage=auto
 #Compress=yes
 #Seal=yes

With that it failed to boot (again) until power cycled but at least there was a partial log. I know it's not the hardware because it happens with multiple Raspberry Pis on multiple networks with multiple SD cards. I haven't seen it happen with other distros than Raspbian.

The only thing that looked off is "dhcpcd[324]: timed out" A guess is that networking or else dhcpcd itself failed somehow, but there is no warning about connectivitiy otherwise. What should I look for to see what caused that upstream?

millwood · 02-14-2019, 08:04 AM

Alternately leave it auto and sudo mkdir /var/log/journal