[systemd-bugs] [Bug 85871] New: boot hangs due to non-starting systemd-journal-flush.service

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=85871

            Bug ID: 85871
           Summary: boot hangs due to non-starting
                    systemd-journal-flush.service
           Product: systemd
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: evangelos at foutrelis.com
        QA Contact: systemd-bugs at lists.freedesktop.org

systemd 217 patched with 919699e (units: don't order journal flushing afte
remote-fs.target) will usually fail to boot and get stuck showing:

"A start job is running for Trigger Flushing of Journal to Persistent Storage"

I haven't been able to reproduce this with systemd.log_level=debug, so I'm not
sure what's going on exactly.

Relevant log entries are:

====================
Nov 04 20:32:04 notbad systemd[1]: Starting Journal Service...
Nov 04 20:32:04 notbad systemd[1]: Started Journal Service.
Nov 04 20:32:04 notbad systemd[1]: Unit systemd-journald.service entered failed
state.
Nov 04 20:32:04 notbad systemd[1]: systemd-journald.service failed.
Nov 04 20:32:04 notbad systemd[1]: systemd-journald.service has no holdoff
time, scheduling restart.
Nov 04 20:32:04 notbad systemd[1]: Stopping Journal Service...
Nov 04 20:32:04 notbad systemd[1]: Starting Journal Service...
Nov 04 20:32:04 notbad systemd[1]: Started Journal Service.
Nov 04 20:32:04 notbad systemd-journal[131]: Journal started
Nov 04 20:32:04 notbad systemd[1]: Starting Trigger Flushing of Journal to
Persistent Storage...
====================

systemd-journald.service didn't fail like that before commit 919699e.

I've also tried adding "After=systemd-remount-fs.service" to the flush service
similar to commit 1f1926a (units: order sd-journal-flush after sd-remount-fs)
but the issue remains.

I'm using Arch Linux although the same issue has been reported on Fedora.
[1][2]

[1] https://plus.google.com/104174679492403594632/posts/GJ566nR6eUq
[2] https://bugs.archlinux.org/task/42678

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20141104/4e9a1ee3/attachment-0001.html>