Bug 990323
Summary: | systemd-journald fails after resume from hibernate | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dimitris <dimitris.on.linux> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | johannbg, lnykryn, msekleta, notting, pedrogfrancisco, plautrba, systemd-maint, ulrich.hobelmann, vpavlin, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-10-21 21:30:59 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dimitris
2013-07-30 22:37:12 UTC
FWIW, I cannot reproduce this under kernels 3.9.9-302.fc19.x86_64 or 3.11.0-0.rc3.git0.1.fc20.x86_64. It looks like sd-journald.service is started during hibernation. What is its status before hibernation? And does it start succesfully after hibernation? It was running before I initiated hibernation. Just after resume: $ systemctl status systemd-journald.service systemd-journald.service - Journal Service Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static) Active: active (running) since Tue 2013-07-30 16:00:28 PDT; 17h ago Docs: man:systemd-journald.service(8) man:journald.conf(5) Main PID: 406 (systemd-journal) Status: "Shutting down..." CGroup: name=systemd:/system/systemd-journald.service └─406 /usr/lib/systemd/systemd-journald Jul 30 16:00:28 gaspode systemd-journal[406]: Allowing runtime journal files to grow to 393.9M. Jul 30 16:00:28 gaspode systemd-journal[406]: Journal started Jul 30 16:00:30 gaspode systemd-journal[406]: Allowing system journal files to grow to 4.0G. Jul 30 16:00:42 gaspode systemd-journal[406]: Forwarding to syslog missed 60 messages. Note the Status: line. Then, wait a few seconds, and: $ systemctl status systemd-journald.service systemd-journald.service - Journal Service Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static) Active: failed (Result: start-limit) since Wed 2013-07-31 09:39:40 PDT; 34s ago Docs: man:systemd-journald.service(8) man:journald.conf(5) Process: 2895 ExecStart=/usr/lib/systemd/systemd-journald (code=exited, status=1/FAILURE) Status: "Shutting down..." Last lines in the log (before restarting), showing the repeated failures that led it to stay failed: Jul 31 09:39:40 gaspode systemd-journal[2883]: Allowing system journal files to grow to 4.0G. Jul 31 09:39:40 gaspode systemd-journal[2883]: Journal started Jul 31 09:39:39 gaspode systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE Jul 31 09:39:39 gaspode systemd[1]: systemd-journald.service: main process exited, code=killed, status=10/USR1 Jul 31 09:39:39 gaspode systemd[1]: Started Trigger Flushing of Journal to Persistent Storage. Jul 31 09:39:40 gaspode systemd-journal[2887]: Allowing system journal files to grow to 4.0G. Jul 31 09:39:40 gaspode systemd-journal[2887]: Journal started Jul 31 09:39:40 gaspode systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE Jul 31 09:39:40 gaspode systemd[1]: Started Trigger Flushing of Journal to Persistent Storage. Jul 31 09:39:40 gaspode systemd-journal[2891]: Allowing system journal files to grow to 4.0G. Jul 31 09:39:40 gaspode systemd-journal[2891]: Journal started Jul 31 09:39:40 gaspode systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE Jul 31 09:39:40 gaspode systemd[1]: Started Trigger Flushing of Journal to Persistent Storage. Jul 31 09:39:40 gaspode systemd-journal[2895]: Allowing system journal files to grow to 4.0G. Jul 31 09:39:40 gaspode systemd-journal[2895]: Journal started Jul 31 09:39:40 gaspode systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE Jul 31 09:39:40 gaspode systemd[1]: Started Trigger Flushing of Journal to Persistent Storage. This is looking more than a little kernel-triggered. As mentioned above I can't reproduce with 3.9 or 3.11 kernels, but with 3.10.4-300.fc19.x86_64 from testing after hibernate resume:
> $ systemctl status systemd-journald.service
> systemd-journald.service - Journal Service
> Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
> Active: failed (Result: start-limit) since Wed 2013-07-31 12:04:17 PDT; 4min 50s ago
> Docs: man:systemd-journald.service(8)
> man:journald.conf(5)
> Process: 5899 ExecStart=/usr/lib/systemd/systemd-journald (code=killed, signal=USR1)
> Status: "Shutting down..."
This looks like a race that was exposed bug 917081. Patching that one makes this go away too. This should be fixed by upstream commit http://cgit.freedesktop.org/systemd/systemd/commit/src/journal/journald-server.c?id=5843c5ebb4341382ae9c87e93c2c87467e573548 i.e. the kernel is generating POLLERR if kmsg runs over (i.e. when a lot of messages have been generated in a very short time), and journald exited on this. Previous update for F19 had this patch. |