Bug 1270616
Summary: | journald self-destructs when system hibernates, or running 'git gc' | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Hin-Tak Leung <htl10> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 27 | CC: | johannbg, jsynacek, lnykryn, msekleta, s, systemd-maint, zbyszek |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-11-30 18:35:34 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
Hin-Tak Leung
2015-10-11 22:23:08 UTC
This is known issue. If your I/O is painfully slow and journald is blocked in some system call waiting for I/O request to complete then it can miss to send watchdog ping and will be SIGABRT'ed by systemd. Recently this has changed upstream and default watchdog timeout is now set to 3min instead of 1min. I think we should backport this change to F22 and F23. In the meantime, please adjust your config locally and bump WatchdogSec to some higher value. (In reply to Michal Sekletar from comment #1) > This is known issue. If your I/O is painfully slow and journald is blocked > in some system call waiting for I/O request to complete then it can miss to > send watchdog ping and will be SIGABRT'ed by systemd. > > Recently this has changed upstream and default watchdog timeout is now set > to 3min instead of 1min. I think we should backport this change to F22 and > F23. In the meantime, please adjust your config locally and bump WatchdogSec > to some higher value. I am surprised that the 'config' is not in /etc/systemd/journald.conf but in /usr/lib/systemd/system/systemd-journald.service and not really considered 'config'. (I did a 'rpm -ql systemd | xargs grep WatchdogSec' to find out where...) $ grep -R WatchdogSec units/ units/systemd-timedated.service.in:WatchdogSec=1min units/systemd-timesyncd.service.in:WatchdogSec=1min units/systemd-journald.service.in:WatchdogSec=1min <-------------- units/systemd-udevd.service.in:WatchdogSec=1min units/systemd-importd.service.in:WatchdogSec=1min units/systemd-hostnamed.service.in:WatchdogSec=1min units/systemd-resolved.service.m4.in:WatchdogSec=1min units/systemd-machined.service.in:WatchdogSec=1min units/systemd-logind.service.in:WatchdogSec=1min units/systemd-journal-remote.service.in:WatchdogSec=10min units/systemd-journal-upload.service.in:WatchdogSec=20min units/systemd-networkd.service.m4.in:WatchdogSec=1min units/systemd-localed.service.in:WatchdogSec=1min I just clone'ed the systemd repository and did not see it - it is still 1 min? I just observed the same behavior when my system goes into suspend, under f23. # rpm -q systemd systemd-222-8.fc23.x86_64 since the units files are not officially a 'config', the work-around got overwritten after I upgraded from f22 to f23. still a prob in f23. This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Saw it recently on fedora 25 when icecat dies which causes abrt to run, which in turn causes journald to self-destruct and causes abrt to run afterwards. This effectively doubles the work load of abrt... This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Seen it in late fc26 / early fc27 . Hence bumping version. This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |