I have a journal-forwarder application running on an embedded Linux system managed by systemd. We’re encountering an issue where the application is immediately killed after a log rotation (log rotation seems to be triggered by an NTP time update). GDB indicates that the crash occurs within the systemd library. Our application uses a handle to the journal, and we suspect that this handle is invalidated due to the log rotation but our application does not know about it.

Description:
I am experiencing an issue where journal files written by systemd 237 are not readable by systemd 244.5 & 245. When attempting to use journalctl to view the journls produced on the v237 system, I get error messages indicating “incompatible flags 0x1c” and “Protocol not supported”. The flags correspond to archived, sealed, and read-only states configured in /etc/system/journald.conf and have not been modified from the defaults on the v237 system. Here is output showing the errors:

Closed 2 mins ago.