<p dir="ltr">Hi Farzad,</p> <p dir="ltr">It seems that you missed Lennart's comments? It's here: <a href="https://lists.freedesktop.org/archives/systemd-devel/2018-January/040162.html">https://lists.freedesktop.org/archives/systemd-devel/2018-January/040162.html</a></p> <p dir="ltr">John</p> <br><div class="gmail_quote"><div dir="ltr">Farzad Panahi <<a href="mailto:farzad.panahi@gmail.com">farzad.panahi@gmail.com</a>> 於 2018年1月20日週六 05:52 寫道：<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hey guys. I really appreciate any comment on this issue. Please let me know if this question does not belong to this mailing list.</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 12, 2018 at 4:13 PM, Farzad Panahi <span dir="ltr"><<a href="mailto:farzad.panahi@gmail.com" target="_blank">farzad.panahi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>I am running Arch-ARM on RPi3. I have noticed when system crashes I cannot find any related crash log in journal logs.</div><div><br></div><div>Arch Linux ARM on RPi3: `Linux 4.4.37-1-ARCH #1 SMP armv7l GNU/Linux`</div><div><br></div><div>Systemd: `systemd 232`</div><div><br></div><div>`/etc/systemd/journald.conf`:</div><div><br></div><div><br></div><div> [Journal]</div><div> Storage=<span style="color:rgb(0,0,0);font-family:monospace;font-size:medium">persistent</span></div><div> Compress=yes</div><div> #Seal=yes</div><div> #SplitMode=uid</div><div> SyncIntervalSec=1</div><div> #RateLimitIntervalSec=30s</div><div> #RateLimitBurst=1000</div><div> SystemMaxUse=1.5G</div><div> #SystemKeepFree=</div><div> #SystemMaxFileSize=</div><div> #SystemMaxFiles=100</div><div> #RuntimeMaxUse=</div><div> #RuntimeKeepFree=</div><div> #RuntimeMaxFileSize=</div><div> #RuntimeMaxFiles=100</div><div> MaxRetentionSec=1month</div><div> MaxFileSec=3hour</div><div> #ForwardToSyslog=no</div><div> #ForwardToKMsg=no</div><div> #ForwardToConsole=no</div><div> #ForwardToWall=yes</div><div> #TTYPath=/dev/console</div><div> #MaxLevelStore=debug</div><div> #MaxLevelSyslog=debug</div><div> #MaxLevelKMsg=notice</div><div> #MaxLevelConsole=info</div><div> #MaxLevelWall=emerg</div><div><br></div><div>Recent crash log:</div><div><br></div><div> Dec 29 03:43:48 sudo[21861]: my_user : TTY=unknown ; PWD=/opt/my_app/repo/src ; USER=root ; COMMAND=/usr/sbin/hciconfig hci0 reset</div><div> Dec 29 03:43:48 sudo[21861]: pam_unix(sudo:session): session opened for user root by (uid=0)</div><div> Dec 29 03:43:48 sudo[21861]: pam_unix(sudo:session): session closed for user root</div><div> Dec 29 03:43:48 my_app.py[17773]: trying to connect to XX:XX:XX:XX:XX:XX</div><div> Dec 29 03:43:48 systemd-udevd[21865]: Process '/bin/hciconfig hci0:64 up' failed with exit code 1.</div><div> Dec 29 03:43:51 my_app.py[17773]: connection successful :)</div><div> -- Reboot --</div><div> Jan 03 16:31:25 systemd[1]: Time has been changed</div><div> Jan 03 16:31:26 dhcpcd[470]: forked to background, child pid 587</div><div> Jan 03 16:31:25 systemd-timesyncd[360]: Synchronized to time server <a href="http://206.108.0.133:123" target="_blank">206.108.0.133:123</a> (<a href="http://2.arch.pool.ntp.org" target="_blank">2.arch.pool.ntp.org</a>).</div><div> Jan 03 16:31:25 systemd[1]: Starting Update man-db cache...</div><div> Jan 03 16:31:25 systemd[1]: Starting Rotate log files...</div><div> Jan 03 16:31:25 systemd[1]: Started Verify integrity of password and group files.</div><div> Jan 03 16:31:25 systemd[1]: ssh-tunnel.service: Service hold-off time over, scheduling restart.</div><div><br></div><div><br></div><div>**Looks like that somehow `journald` is failing to `sync` logs when a crash happens.** </div><div><br></div><div> - Is this a known behaviour? </div><div> - Is there a workaround for this?</div><div><br></div><div><br></div><div>----------</div><div>Also I am curious to know if the following claim from [Arch Linux wiki][1] is still valid:</div><div><br></div><div>> Since the syslog component of systemd, journald, does not flush its</div><div>> logs to disk during normal operation, these logs will be gone when the</div><div>> machine is shut down abnormally (power loss, kernel lock-ups, ...). In</div><div>> the case of kernel lock-ups, it is pretty important to have some</div><div>> kernel logs for debugging. Until journald gains a configuration option</div><div>> for flushing kernel logs, rsyslog can be used in conjunction with</div><div>> journald.</div><div><br></div><div><br></div><div>----------</div><div>related bug report (old): [Bug 61411 - All logs since last boot gone after crash/hard reboot][2]</div><div><br></div><div>similar issue (old): <a href="https://unix.stackexchange.com/questions/67394/debugging-lock-up-systemd-loses-my-logs" target="_blank">https://unix.stackexchange.com/questions/67394/debugging-lock-up-systemd-loses-my-logs</a></div><div><br></div><div> [1]: <a href="https://wiki.archlinux.org/index.php/Rsyslog#journald_with_rsyslog_for_kernel_messages" target="_blank">https://wiki.archlinux.org/index.php/Rsyslog#journald_with_rsyslog_for_kernel_messages</a></div><div> [2]:</div><div><a href="https://bugs.freedesktop.org/show_bug.cgi?id=61411" target="_blank">https://bugs.freedesktop.org/show_bug.cgi?id=61411</a></div><div><br></div></div> </blockquote></div><br></div> _______________________________________________<br> systemd-devel mailing list<br> <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank">systemd-devel@lists.freedesktop.org</a><br> <a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a><br> </blockquote></div>