#### demo-hp 2026-11-14T10:58:06Z kernel 7.0.14-28-pve
## before: chrony active; loaded 83417e83b538; cache(cur) 83417e83b538; cache(old folder) dbf67f16ac25; fresh 83417e83b538
## source mtime 2026-07-01 22:28:16; old copy mtime 2026-08-21 17:42:38
saved the good cache file to /root/spike-profile-usr.sbin.chronyd.good (83417e83b538)
PLANTED: the old compiled copy is now in the running kernel's folder; its time 2026-08-21 17:42:38 is newer than the source
## reload the way the system does at a start (systemctl reload apparmor = apparmor_parser --write-cache --replace)
reload rc=0
## after the reload: loaded dbf67f16ac25  (dbf67f16 = the profile of chrony 4.6.1; 83417e83 = of 4.8)
## chrony still runs under the replaced profile? active; its confinement: /usr/sbin/chronyd (enforce)
Job for chrony.service failed because the control process exited with error code.
See "systemctl status chrony.service" and "journalctl -xeu chrony.service" for details.
restart rc=1
## after a restart: chrony failed; result=exit-code
2026-11-14T11:58:07+01:00 demo-hp chronyd[1853258]: Loaded seccomp filter (level 1)
2026-11-14T11:58:07+01:00 demo-hp chronyd[1853258]: Fatal error : Could not send notification to $NOTIFY_SOCKET
2026-11-14T11:58:07+01:00 demo-hp chronyd[1853258]: Fatal error : Could not send notification to $NOTIFY_SOCKET
2026-11-14T11:58:07+01:00 demo-hp systemd[1]: chrony.service: Main process exited, code=exited, status=1/FAILURE
2026-11-14T11:58:07+01:00 demo-hp systemd[1]: chrony.service: Failed with result 'exit-code'.
2026-11-14T11:58:07+01:00 demo-hp systemd[1]: Failed to start chrony.service - chrony, an NTP client/server.
