First troubleshooting step is the following.
On the command line do a cmk --debug -vvn hostname If it runs correctly you get a time at the end.
This you can do 2-3 times to see if there is a deviation between each run.
For the RAW edition you can only change the timeout globally. This is important to remember as you have to consider this for the check interval settings of hosts with high runtime.
Go to ~/etc/nagios/nagios.d/ open the tuning.cfg and search for this option service_check_timeout=60. This is the global check timeout for service checks.
– andreas-doehler – Checkmk Partner
As you have a timeout problem only for “Check_MK” and “Check_MK Discovery” services.
These two are the only real services executed by your monitoring core all other get the data from the “check_mk” service.
With the command cmk --debug -vvn hostname you run the Check_MK service manually.
That’s why i said you should do this more than one time to get an average and maximum time.
Result
OK – [snmp] Success, execution time 235.9 sec
Issue resolved.
This is way more than your maximum time of 180 seconds. It is possible that you get timeouts again.
You should watch at what part it takes so long and decide if you want these checks or not.
{ “@context”: “https://schema.org”, “@type”: “Organization”, “name”: “Dlightdaily”, “alternateName”: “Dlightdaily”, “url”: “https://dlightdaily.com”, “logo”: “https://dlightdaily.com/wp-content/uploads/2022/07/cropped-Dlightdaily-web-logo-500×500-1.png”, “sameAs”: [ “https://www.facebook.com/dlightdaily/”, “https://twitter.com/dlightdaily”, “https://www.youtube.com/channel/UCIqxcHVrvC3MVh6B3mNeiVw/videos”, “https://in.linkedin.com/in/dlightdaily”, “https://in.pinterest.com/dlightdaily/”, “https://dlightdaily.com” ] }