How can I run the service check_mk-chrony on the cmd-line?

fkraus · May 25, 2023, 11:35am

CMK version: 2.1.0p25.cee
OS version: Rocky Linux 8

the problem looks like this:

Error message

root@lnzslrmma01:[~]> chronyc tracking
Reference ID : 0A65100A (salvipa01.research.silicon-austria.com)
Stratum : 4
Ref time (UTC) : Thu May 25 10:51:04 2023
System time : 0.000000207 seconds slow of NTP time
Last offset : -0.000000278 seconds
RMS offset : 0.000000278 seconds
Frequency : 10.874 ppm fast
Residual freq : +1.789 ppm
Skew : 0.037 ppm
Root delay : 0.035834674 seconds
Root dispersion : 0.001092411 seconds
Update interval : 2.0 seconds
Leap status : Normal

Except that I see message Could not open command socket on [::1]:323 when I run systemctl status chrony (the service is up and running, and sync’d) - but I’m not sure if this message is important anyway at the moment… everything looks correctly configured on the server. So I must investigate further.

Now I want to simulate the service check check_mk-chrony on the cmd-line. Where, and how can I do this? I checked this directory, but I’m wrong. How is run this on the cmd-line?

OMD[SAL]:~$ cd ~/share/check_mk/agents/special/

many thanks for your advice.

chauhan_sudhir · May 26, 2023, 9:01am

“NTP Time” is a passive check for which the data gets generated by the Checkmk agent itself.
The data is stored in a cache file under /var/lib/check_mk_agent/cache/.
You can login to the monitored host and have a look at the cache file.

fkraus · May 26, 2023, 12:42pm

ok thanks that is a file to look at. And I can’t simulate the cmd on the cmd-line?

chauhan_sudhir · May 26, 2023, 1:33pm

This is the section that is called via the agent and it includes the command:

github.com

Checkmk/checkmk/blob/master/agents/check_mk_agent.linux#LL759C1-L768C2


      
          section_chrony() {
              if inpath chronyc; then
                  # Force successful exit code. Otherwise section will be missing if daemon not running
                  #
                  # The "| cat" has been added for some kind of regression in RedHat 7.5. The
                  # SELinux rules shipped with that release were denying the chronyc call
                  # without cat.
                  run_cached "chrony" 120 30 "echo '<<<chrony>>>'; waitmax 5 chronyc -n tracking | cat || true"
              fi
          }

Also, important point is what is the normal check interval for the Chec_MK service check on this host ?