[systemd-bugs] [Bug 71721] New: systemd-journald - 60 second pause in dracut, then hangs systemd at Init Default Target

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 71721
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: systemd-journald - 60 second pause in dracut, then
                    hangs systemd at Init Default Target
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: james at nurealm.net
          Hardware: x86 (IA32)
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

Arch Linux
kernel 3.12.0-1-ARCH
dracut 034-1
systemd 208-2

Symptom: on boot with "systemd.log_level=debug", after log message"Started
Journal Service", the booting-process pauses for exactly 60 seconds.  Then, at
Init Default Target, after pivot, where systemd proper should start, after the
log message "systemd-journald[43]: Received SIGTERM", the system hangs
permanantly.

Circumstances: The pause and hang can be influenced by the "debug" and
"systemd.log_target=<blah>" kernel command-line boot parameters.

With no "debug" and no "systemd.log_target=<blah>" parameter, the boot pauses
and then hangs.

With "debug" and no "systemd.log_target=<blah>" parameter, the boot never
pauses or hangs and seems to start normally.

With no "debug" and with any of
"systemd.log_target=[journal|syslog|journal-or-kmsg|syslog-or-kmsg]", the boot
will pause and then hang.

With no "debug" and with any of "systemd.log_target=[console|kmsg|null]", the
boot does not pause or hang and seems to start normally.

The pause and hang seem to be related to systemd-journald.  Setting "debug" or
setting "systemd.log_target=[console|kmsg|null]" acts as a work-around to the
pause and hang.

With no "debug" and no "systemd.log_target=<blah>" parameter, where the boot
would otherwise pause and then hang, using the kernel command-line boot
parameter "init=/usr/bin/bash", the shell starts normally, and then running
"/usr/lib/systemd/systemd --system" from the shell, all systemd-managed
processes seem to start-up normally.

Hopefully, that's enough information to narrow-down the source of the problem. 
Let me know if there is any easy way to expose more useful error messages
during the pause or at the hang.

-- 
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/20131118/cc38bab4/attachment.html>