Page MenuHomePhabricator

Combatting sclockadj's log spam
Open, NormalPublic

Description

One of sclockadj's problems is it causes systemd's journal spam because of time changes. There are some measures that propose decreasing the log spam but it may not be enough:

https://serverfault.com/questions/815081/how-to-combat-journal-spam-unit-specific-maxlevel-settings

TODO: research if there is a way that can save us the trouble of submitting upstream systemd patches. Perhaps using an alternative logging system?

Details

Impact
Normal

Event Timeline

HulaHoop created this task.Feb 2 2017, 2:28 AM

systemd feature request:
option to disable systemd's “Time has been changed” message spam in journal log
https://github.com/systemd/systemd/issues/5207

Poettering says its already implemented?

Yes. Problem is the systemd version in Debian stretch is too old.

Ok so this should be tagged Debian Bullseye.

As a subset of T50 that ticket needs to be updated when this one here is complete.

Similar issue not yet fixed in systemd master.

systemd feature request - lower the priority of add random timer message from info to debug:
https://github.com/systemd/systemd/issues/5228


Codenames are messed up.

Tagging the ticket with a Debian codename such as Debian version 10 codename Buster results in rechecking the ticket when that phabircator component is due.


In Debian version 10 codename Buster which will be a long time, this will solve itself without further action required.

Should we do something about this in meanwhile for Whonix 14 Debian version 9 codename Stretch based release? Does this fill up the disk or are logs truncated to sane sizes?

Should we do something about this in meanwhile for Whonix 14 Debian Stretch based release? Does this fill up the disk or are logs truncated to sane sizes?

No need. Kernel logs look ok.