Service Check Timed Out - on some Windows servers

Troubleshooting
, ,
1

Hi there, I know, another thread about Service Check Timed out.
But:
This is only happening on 2x Windows Server 2016, one VM and one physical.
Pretty specific? Any known issues?
Weird thing, it stays on this like, forever.

cmk --debug -vvn mdt.domain.local
Checkmk version 2.0.0p15
Try license usage history update.
Trying to acquire lock on /omd/sites/services/var/check_mk/license_usage/next_run
Got lock on /omd/sites/services/var/check_mk/license_usage/next_run
Trying to acquire lock on /omd/sites/services/var/check_mk/license_usage/history.json
Got lock on /omd/sites/services/var/check_mk/license_usage/history.json
Next run time has not been reached yet. Abort.
Releasing lock on /omd/sites/services/var/check_mk/license_usage/history.json
Released lock on /omd/sites/services/var/check_mk/license_usage/history.json
Releasing lock on /omd/sites/services/var/check_mk/license_usage/next_run
Released lock on /omd/sites/services/var/check_mk/license_usage/next_run
Loading autochecks from /omd/sites/services/var/check_mk/autochecks/mdt.domain.local.mk
+ FETCHING DATA
  Source: SourceType.HOST/FetcherType.TCP
[cpu_tracking] Start [7febaa336fa0]
Connecting via TCP to 172.16.0.11:6556 (10.0s timeout)
[TCPFetcher] Fetch with cache settings: DefaultAgentFileCache(base_path=PosixPath('/omd/sites/services/tmp/check_mk/cache/mdt.domain.local'), max_age=MaxAge(checking=0, discovery=120, inventory=120), disabled=False, use_outdated=False, simulation=False)
Not using cache (Too old. Age is 1010 sec, allowed is 0 sec)
[TCPFetcher] Execute data source
Reading data from agent

All at a sudden it works, then does not anymore…

Any idea here?
I even updated checkMK to 2.0.0p15 CRE this morning. Agents are p12 if that matters.
There are more then 100 hosts (mixed Windows, Linux, appliances like switches etc) that work without issue

2

Normally the reason is a wrong configured agent on this Windows machine.
Or a firewall issue.
First → check firewall settings on the Windows host
Second → execute the agent in test mode on the Windows host
Third → check the agent configuration and take a look inside the agent log file for errors or warnings

1 Like
3

That’s the weird thing, it works on all other servers without any additional config manually made…
EDIT: Manually doing “check_mk_agent.exe test” does not do anything, even if the service is stopped before that.
I keep editing here to not spam with new messages:
Firewall settings are ok, port open, and configured as in manual
Log: 2021-11-11 08:38:56.287 [srv 5892] perf: In [54150] milliseconds process 'cscri - Pastebin.com

4

Any more ideas? I am running out of things to try…

5

Your log file shows an wrong configured “windows_updates.vbs” this should/must run asynchron and it should also be cached for a longer period of time.
The second thing you should change is that you should disable unneeded sections like “skype”, “openhardware” or “exchange” if it is not used on this machine.

1 Like
6

Thanks for the reply Andreas.
I checked and actually got the latest windows_updates.vbs from our checkMK to those clients.
Where could I change settings for asynchron and cached run?

7

Inside the check_mk.user.yml you can configure the behavior of all the plugins.

1 Like
8

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.