[Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

[Balint Reczey]

The journal restart can be observed on zesty as well.

However, the journal is not corrupted, the renaming and replacing took place as a safety measure due to unclean shutdown.
$ sudo journalctl --verify --file=/run/log/journal/*/*
PASS: /run/log/journal//6ff4e09ca827435bbe1b6efc2236a105/system.journal                                                     
PASS: /run/log/journal//6ff4e09ca827435bbe1b6efc2236a105/system at 00055289b166aebb-17bfde05076f84d2.journal~                  
PASS: /run/log/journal//6ff4e09ca827435bbe1b6efc2236a105/system at b7f19f66c640442d854033592fdedbb6-0000000000013de4-0005528690181932.journal
PASS: /run/log/journal//6ff4e09ca827435bbe1b6efc2236a105/system at b7f19f66c640442d854033592fdedbb6-0000000000013569-000552843559e7e6.journal
PASS: /run/log/journal//6ff4e09ca827435bbe1b6efc2236a105/system at b7f19f66c640442d854033592fdedbb6-0000000000012d03-00055282a0e0b31b.journal
PASS: /run/log/journal//6ff4e09ca827435bbe1b6efc2236a105/system at b7f19f66c640442d854033592fdedbb6-00000000000124a8-000552806e21938c.journal
PASS: /run/log/journal//6ff4e09ca827435bbe1b6efc2236a105/system at b7f19f66c640442d854033592fdedbb6-0000000000011ca8-0005527efc9ec6de.journal
PASS: /run/log/journal//6ff4e09ca827435bbe1b6efc2236a105/system at b7f19f66c640442d854033592fdedbb6-00000000000114a4-0005527d2438261c.journal

Was the journal corrupted in your case?


** Changed in: systemd (Ubuntu Artful)
       Status: New => Incomplete

-- 
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/1696970

Title:
  softlockup DoS causes systemd-journald.service to abort with SIGABORT

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Artful:
  Incomplete

Bug description:
  I was running the new stress-ng softlockup stressor and observed that
  systemd-journald gets killed with an abort and this corrupts the
  systemd journal.

  How to reproduce:

  git clone git://kernel.ubuntu.com/cking/stress-ng
  cd stress-ng
  make clean; make

  sudo ./stress-ng --softlockup 0 -t 360 -v

  ..and wait for 360 seconds.  dmesg shows the following, 100%
  reproduceable:

  
  [  875.310331] systemd[1]: systemd-timesyncd.service: Watchdog timeout (limit 3min)!
  [  875.310740] systemd[1]: systemd-timesyncd.service: Killing process 574 (systemd-timesyn) with signal SIGABRT.
  [  875.327289] systemd[1]: systemd-timesyncd.service: Main process exited, code=killed, status=6/ABRT
  [  875.327666] systemd[1]: systemd-timesyncd.service: Unit entered failed state.
  [  875.327686] systemd[1]: systemd-timesyncd.service: Failed with result 'watchdog'.
  [  875.327917] systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
  [  875.327954] systemd[1]: Stopped Network Time Synchronization.
  [  875.328845] systemd[1]: Starting Network Time Synchronization...
  [  875.525071] systemd[1]: Started Network Time Synchronization.
  [  875.539619] systemd[1]: systemd-journald.service: Main process exited, code=dumped, status=6/ABRT
  [  875.544257] systemd-journald[5214]: File /run/log/journal/440e485e550040e3b93b66b2faae8525/system.journal corrupted or uncleanly shut down, renaming and replacing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1696970/+subscriptions