Bug 1438229
Summary: | /usr/lib/systemd/systemd-journald crashes | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tomasz Kłoczko <kloczko.tomasz> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 27 | CC: | johannbg, lnykryn, msekleta, muadda, ssahani, s, systemd-maint, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-29 17:54:37 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
Tomasz Kłoczko
2017-04-02 07:36:38 UTC
SIGABRT is probably because of a watchdog timeout. Was the machine under heavy load when this happened? Yes it was. It was just after login into Gnome session in which autostart I have chrome opening about 40 tabs, evolution, about 8 terminal session + skype + empathy. Seems that this crash caused that whole GUI session failed and gdm was no longer even able to display login screen. From last two or three kernel versions seems some kernel debug options enabled in kernel are slowing my laptop now. Only kernel on which I still can work is 4.10.0-1. Nevertheless as long as still everything is running I don't see why something should receive SIGABRT (?). A bit odd. There's a watchdog set with a limit of 3 min for systemd-journald. systemd-journald being aborted does (or at least should not) cause an issue for other programs, because systemd will immediately restart journald and hand it the previous set of descriptors. So this should only result in a loss of some messages. You can disable the watchdog, or make it significantly higher: systemctl edit systemd-journald, add [Service] WatchdogSec=30min I'm sure that in this exact case GUI session crashed after about 1in when in meantime I was able to interact with some applications. OK, will try to change WatchdogSec, PS. can we chat on IRC? I have some issue with tracing some systemd core service on aarm64 HW which seems so far not able to use under Fedora and I'm looking for some help. I'm on freenode.net IRC on #fedora-devel. This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'. Closing |