I am also still getting these error messages on my machines.
Any further information needed?
-- Package-specific info:
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU
With the upgrade to 233-9, the issue disappeared.
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
> Is the journal running properly?
Yes, I do not encounter any issues with the journal.
> Do you have any custom journal config?
I do not think so, besides 'Storage=persistent' (which I also use on
my desktop, without this issue).
> During early boot, when the journal is not yet available, log
The still show up with SELinux disabled:
$ journalctl -k -o export -n 3
__CURSOR=s=25f2ace8f7264ff68b282f9061b5272c;i=1ea9;b=514ecde25d1442d7bfe2031c7b95afbf;m=950e41f;t=551747f1c234d;x=76c61eeda7d44fb2
__REALTIME_TIMESTAMP=1496935674159949
__MONOTONIC_TIMESTAMP=156296223
_BOOT_ID=514ecde25d1442d7
> The log messages you quoted in your first mail, were those directly
> after a reboot?
No, I can reproduce them via 'systemctl daemon-reload' and they show up:
$ dmesg
...
[5.771850] random: crng init done
[ 211.548761] systemd[1]: apt-daily-upgrade.timer: Adding 49min
6.003026s random time.
Package: systemd
Version: 232-25
The logs about random time addition to systemd-timers are logged with
a kernel flag, e.g.:
$ journalctl -k -n 40
-- Logs begin at Mon 2017-04-10 14:12:30 CEST, end at Thu 2017-06-08
14:46:41 CEST. --
Jun 07 02:09:23 server02 systemd[1]: apt-daily-upgrade.timer: Ad
