[Bug 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate

[Balint Reczey]

Verified with systemd/237-3ubuntu10.31:

root at x-lp1773859:~# systemctl show systemd-journald.service | grep Watch
WatchdogUSec=0
WatchdogTimestamp=Tue 2019-10-08 16:06:56 UTC
WatchdogTimestampMonotonic=176241732389
root at x-lp1773859:~# dpkg -l systemd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                   Version          Architecture     Description
+++-======================-================-================-==================================================
ii  systemd                237-3ubuntu10.31 amd64            system and service manager

The fix is applied in .31, but the crash was still be observed once:
https://errors.ubuntu.com/?release=Ubuntu%2018.04&package=systemd&period=month&version=237-3ubuntu10.31

This seem to have been misreported against the version, since the
ExecutableTimestamp is 1567655991 (date -d  @1567655991 : Thu Sep  5
03:59:51 UTC 2019) , which matches the timestamp of  /lib/systemd
/systemd-journald  in 237-3ubuntu10.29 .


** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in 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

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 Committed
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