** Description changed: + [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/.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773148 Title: /lib/systemd/systemd- journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1773148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
