[Bug 915575] New: Boot fails on systemd-journald recieving SIGTERM
http://bugzilla.suse.com/show_bug.cgi?id=915575 Bug ID: 915575 Summary: Boot fails on systemd-journald recieving SIGTERM Classification: openSUSE Product: openSUSE Factory Version: 201501* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: systemd-maintainers@suse.de Reporter: tchvatal@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 621475 --> http://bugzilla.suse.com/attachment.cgi?id=621475&action=edit Screenshot of the boot with sigterm Boot of current kernels 3.18+ fails with systemd-journald getting SIGTERM from pid 1. This happens only on SSD drive and when I migrate 1:1 to normal HDD it boots fine. I tested on 2 disks one is Kingston and other is from Intel both having this problem. Further testing revealed when you replace systemd-journald (systemd-logger) with rsyslog the machine boots just fine, so it is something with interaction sdd/systemd/systemd-journald that goes amiss. I would love to provide more debug info but really I didn't manage to get more debug stuff than this image. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=915575
Thomas Blume
http://bugzilla.suse.com/show_bug.cgi?id=915575
Martin Pluskal
http://bugzilla.suse.com/show_bug.cgi?id=915575
Tomáš Chvátal
http://bugzilla.suse.com/show_bug.cgi?id=915575
Tomáš Chvátal
http://bugzilla.suse.com/show_bug.cgi?id=915575
--- Comment #4 from Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=915575
--- Comment #5 from Tomáš Chvátal
http://bugzilla.suse.com/show_bug.cgi?id=915575
Tomáš Chvátal
http://bugzilla.suse.com/show_bug.cgi?id=915575
Thomas Blume
Created attachment 621583 [details] systemd debug logging
Hm, I don't really see a bug. There are 2 times signals sent to journald. The first time it seems to be caused by the switch from initrd to real system root: -->-- [ 5.084442] BTRFS info (device sda3): disk space caching is enabled [ 5.099132] BTRFS: detected SSD devices, enabling SSD mode [ 5.293630] systemd-journald[184]: Received SIGTERM from PID 1 (systemd). [ 5.491167] BTRFS info (device sda3): disk space caching is enabled --<-- Is sda3 your system root? If so, this SIGTERM is normal. After switch root the journal is restarted on the real root device. The other signal I can see is a trigger for a journal flush (see man systemd-journald.service > SIGNALS for reference): -->-- About to execute: /usr/bin/systemctl kill --kill-who=main --signal=SIGUSR1 systemd-journald.service Forked /usr/bin/systemctl as 474 systemd-journal-flush.service changed dead -> start --<-- This indicates that journald was correctly started before. What shows: systemctl status journald in the running system? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=915575
Tomáš Chvátal
http://bugzilla.suse.com/show_bug.cgi?id=915575
--- Comment #9 from Thomas Blume
http://bugzilla.suse.com/show_bug.cgi?id=915575
Thomas Blume
http://bugzilla.suse.com/show_bug.cgi?id=915575
Tomáš Chvátal
participants (1)
-
bugzilla_noreply@novell.com