Bug#975561: journal: do not trigger assertion when journal_file_close() get NULL

[Michael Biebl]

Control: fixed -1 243-1


Hello Boris

Am Montag, den 23.11.2020, 17:14 +0100 schrieb Boris Granwehr:
> 
> Sometimes the systemd-journald process crashes on startup with the
> error message:
> Failed to create new runtime journal: No such file or directory
> Assertion 'f' failed at ../src/journal/journal-file.c:332, function
> journal_file_close().
> Aborting.
> 
> This is caused by changing the "storage" parameter in
> "/etc/systemd/journald.conf"
> from the default value "volatile" to "auto" (if "/var/log/journal"
> exists)
> or to changing it to "persistent".
> 
> The following systemd 243 upstream commit fixes this bug:
> https://github.com/systemd/systemd/pull/12679/files
> 
> The bug is fixed for debian releases since bullseye (systemd 246).
> Is it possible to fix the bug also for older debian releases like
> stretch

The change looks ok for a stable upload (i.e. buster) and I can include
that in the next stable point release after 10.7 (for 10.7 it is too
late).
For old-stable I don't plan to make any further uploads.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20201124/7b621c10/attachment.sig>