starting chronyd -q unreliable

chronyd -q should perform requested operation then exit. 
It should never stay running. 

I start chrony daily via cron from another machine.
15 00 * * * ssh [email protected] "chronyd -q 'pool pool.ntp.org
iburst'"

This works for a while...

2023-06-07T05:15:01Z chronyd version 4.2 starting (+CMDMON +NTP
+REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6
+DEBUG)
2023-06-07T05:15:01Z Initial frequency -12.651 ppm
2023-06-07T05:15:06Z System clock wrong by -0.001617 seconds (step)
2023-06-07T05:15:06Z chronyd exiting

Then for seemingly no reason:

2023-07-06T05:15:01Z chronyd version 4.2 starting (+CMDMON +NTP
+REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6
+DEBUG)
2023-07-06T05:15:01Z Fatal error : Another chronyd may already be
running (pid=1141), check /run/chrony/chronyd.pid

So I start killing it an hour before via cron.
14 00 * * * ssh [email protected] "kill `pidof chronyd`|&grep -v
'usage:'"

This works fine for a month or so and then wala its back again.
This should never happen.

Affected machine is a centos clone distro. 
-- 
 Calvin Arndt
(217) 377-2979
[email protected]