Mailinglist Archive: opensuse-bugs (4258 mails)

< Previous Next >
[Bug 1021307] journald frequently crashes with coredump of the journal daemon itself
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sat, 28 Jan 2017 23:51:35 +0000
  • Message-id: <bug-1021307-21960-562ugmgcUF@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1021307
http://bugzilla.opensuse.org/show_bug.cgi?id=1021307#c8

--- Comment #8 from Siegbert Sadowski <ssadowski@xxxxxxxxxxxxxxxxxxx> ---
Hi,

many thanks for your quick response. I restarted as recommended the system with
boot option debug printk.devkmsg=on. The journal output became very verbose and
generated a huge log file (88MB) until the last crash occured. Unfortunately
the upload of the compressed file failed due to the file size limit of 10MB
while the compressed file is 12 MB. Please delete my duplicate comment 4.

However I noticed 2 things with the debug option turned on.

1. Although the log output is much larger the system was stable for at least
twice the usual crash rate.

2. A commonality, the crashes occur often around 21:30, +/- 15 minutes. I
haven't found so far a cron job in this time frame.

My thoughts: For me the analysis of Franck Bui is very logical. The short
response time of my SSD sytem disk keeps journald busy while writing the log to
'persistent storage'.

BTW: I will be out of house for the next 7 days and will be back on 06.02.2017.

Best regards,
Siegbert Sadowski

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
References