On Fr, 13.10.17 12:00, Michael Littlejohn ([email protected]) wrote:

> Hi,
> 
> TL;DR: Server is receiving log message via systemd-journal-remote
> from 14s in the future (sender clock is 14s fast). Causes journal
> files to close, rotate and start anew on every message/batch. Check
> at journal-file.c:621 is checking for messages "from the future"
> from perspective of local system, rather than checking if messages
> are in or out of order within context of that message
> stream. Discuss.

Sounds like a bug. Rotate-on-time-jumps is a feature journald should
enforce, but not journal-remote. Please file a bug about this in the
github issue tracker, or even better prep a PR fixing this!

Thanks,

Lennart

-- 
Lennart Poettering, Red Hat
_______________________________________________
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to