We just installed the ntpdate package, so the original NTPDATE and
NTPDATEOPTS settings work just fine. This is on a slightly older RHEL
release to you, so not sure if ntpdate is available from your repos, but
worth a try.
I don't know how the ntp test determines a good result from a bad, but it
might be looking for a string in the ntpdate output that isn't there in the
chronyc output.
Is there anything in xymond.log? The NTP probe is done by xymonnet so you
might be able to run it manually and trace it with strace, to see what it's
doing.
J
On Tue, 10 Oct 2023 at 11:01, Colin Coe <user-5b250cd7a540@xymon.invalid> wrote:
Hi all
I'm getting ready to replace our venerable RHEL6 Xymon server with one
running RHEL 9.
We use the terabithia.org RPMs.
NTP tests are all returning red. I've updated xymonserver.cfg (and
restarted the xymon service) by changing NTPDATE="/usr/bin/chronyc" and
adding NTPDATEOPTS="tracking".
When I run "/usr/bin/chronyc tracking <IP HERE>" from the shell, it works
fine however the Xymon page is red.
Service ntp on <CENSORED> is not OK : Service unavailable
Command: /usr/bin/chronyc tracking <CENSORED> 2>&1
Any ideas?