This bug was fixed in the package systemd - 237-3ubuntu10.31
---------------
systemd (237-3ubuntu10.31) bionic; urgency=medium
[ Dimitri John Ledkov ]
* Add conflicts with upstart and systemd-shim. (LP: #1773859)
* d/p/debian/UBUNTU-units-disable-journald-watchdog.patch
- units: Disable journald Watchdog (LP: #1773148)
* d/p/cryptsetup-add-support-for-sector-size-option-8881.patch
- cryptsetup: add support for sector-size= option (LP: #1776626)
* d/p/systemctl-correctly-proceed-to-immediate-shutdown-if-sche.patch
- systemctl: correctly proceed to immediate shutdown if scheduling fails
(LP: #1670291)
* d/p/networkd-add-support-to-configure-IPv6-MTU-8664.patch
- networkd: add support to set IPv6MTUBytes (LP: #1671951)
-- Balint Reczey <rbal...@ubuntu.com> Mon, 30 Sep 2019 17:23:17 +0200
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1773148
Title:
/lib/systemd/systemd-
journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate
Status in systemd:
New
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Cosmic:
Fix Released
Bug description:
[Impact]
* systemd aborts journald, upon watchdog expiry and generates lots of crash
reports
* it appears that journald is simply stuck in fsync
* it has been agreed to disable watchdog timer on journald
[Test Case]
* watch drop-off of errors w.r.t. watchdog timer
[Regression Potential]
* Potentially journald does get stuck, and thus is no longer
automatically restarted with a sigabrt crash. However, so far, it is
not known to do that.
[Other Info]
* Original bug report
The Ubuntu Error Tracker has been receiving reports about a problem regarding
systemd. This problem was most recently seen with package version
237-3ubuntu10, the problem page at
https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1773148/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
