http://bugzilla.opensuse.org/show_bug.cgi?id=1021307 Bug ID: 1021307 Summary: journald frequently crashes with coredump of the journal daemon itself Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: ssadowski@electronic-space.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0 Build Identifier: Hello community, I installed Leap 42.2 fresh on a new SSD. After configuration (with Yast) the system hangs 1-2 times per day. The journal log file shows always the same pattern: Jan 19 22:02:35 serv2 systemd-journald[15033]: System journal (/var/log/journal/) is currently using 784.0M. Maximum allowed usage is set to 4.0G. Leaving at least 4.0G free (of currently available 44.7G of space). Enforced usage limit is thus 4.0G, of which 3.2G are still available. Jan 19 22:02:35 serv2 systemd-journald[15033]: Journal started Jan 19 22:00:01 serv2 cron[15019]: pam_unix(crond:session): session opened for user root by (uid=0) Jan 19 22:00:01 serv2 systemd[1]: Started Session 17 of user root. Jan 19 22:02:35 serv2 CRON[15019]: pam_unix(crond:session): session closed for user root Jan 19 22:02:17 serv2 systemd[1]: systemd-journald.service: Watchdog timeout (limit 3min)! Jan 19 22:02:35 serv2 systemd[1]: Starting Flush Journal to Persistent Storage... Jan 19 22:02:35 serv2 systemd[1]: Started Flush Journal to Persistent Storage. Jan 19 22:02:35 serv2 systemd-coredump[15025]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.0c14f Then when I try to reboot it takes 30-45 minutes(!) for the system to shut down. There are no other error messages in the log. Can you help me? Many Thanks in advance. Reproducible: Couldn't Reproduce Steps to Reproduce: 1.monitored the system with journalctl -ef 2.after a couple of hours the above described log entry occurs 3. -- You are receiving this mail because: You are on the CC list for the bug.