> 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. [ 211.549338] systemd[1]: apt-daily.timer: Adding 8h 21min 56.235615s random time. [ 240.582494] systemd[1]: apt-daily-upgrade.timer: Adding 59min 27.836513s random time. [ 240.583213] systemd[1]: apt-daily.timer: Adding 1h 35min 20.497281s random time. [ 400.847746] systemd[1]: apt-daily-upgrade.timer: Adding 9min 48.986980s random time. [ 400.848365] systemd[1]: apt-daily.timer: Adding 8h 8min 53.943346s random time. > If you disable SELinux, does the problem go away? They still are generated in permissive mode. I tried to boot in SELinux disabled mode, but dbus did not start up, I'll investigate further... Jun 08 16:23:43 server02 systemd[1]: Started D-Bus System Message Bus. Jun 08 16:23:43 server02 dbus-daemon[703]: Failed to set up security class mapping (selinux_set_mapping():Invalid argument). Jun 08 16:24:08 server02 systemd[1]: dbus.service: Main process exited, code=exited, status=1/FAILURE Jun 08 16:24:08 server02 systemd[1]: dbus.service: Unit entered failed state. Jun 08 16:24:08 server02 systemd[1]: dbus.service: Failed with result 'exit-code'. _______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers