Agent Problems - Timeout

Troubleshooting
1

Hello everybody. I recently started managing a Check_MK server. The problem is that I have not configured it and have no previous experience with it, so sorry in advance.

The problem is that my agent on a server keeps failing after a short while. -> “Service Check Timed Out”

When I restart the service on the server, it usually works for a short time. Agent has also been reinstalled.

I saw in the agent output file that a WMI query times out. WMI service on the server is enabled.

Perf-O-Meter currently says that the query time is ~ 30sec

2

That’s very long for a normal Windows machine.
The reason can be very different from machine to machine. Are there any plugins running inside the agent? What agent version do you use? Is there any modification inside the ini/yml config file?

On a healthy Windows server the agent without plugins should have a runtime not longer than 1-3 seconds. Shorter is better :slight_smile:

3

Hey andreas :slight_smile:
ya, thats a long time :slight_smile:

Those Plugins are running:
mcafee_av_client.bat
megaraid.bat
mk_inventory.vbs
win_printers.ps1
windows_multipath.vbs
windows_os_bonding.ps1
windows_tasks.ps1
windows_updates.vbs

There are 3 identical servers with same config, same plugins. Just this server is making trouble.

Agent Version 1.5.0.p9

config files are not changed.

BTW: Without Plugins the Time is ~1 sec

EDIT:
I tried it without plugins and then with every single plugin to find out the time.
Result:
Without Plugins = 0,5 sec

mcafee_av_client.bat = 0,7 sec
megaraid.bat = 0,8 sec
mk_inventory.vbs = 0,8 sec
win_printers.ps1 = 3,1 sec
windows_multipath.vbs = 8,1 sec
windows_os_bonding.ps1 = 4,8 sec
windows_tasks.ps1 = 5,6 sec
windows_updates.vbs = 15 sec

1 Like
4

Hi @ZigBee,

Windows is evil - are you using the Enterprise version? If so, apply a rule: [Service check timeout (Microcore)] - it might help.

You can also play around with freshness in the agent configuration but i would go for the Rule option first.

5

That has nothing to do with windows or the check timeout.
The problem is that this Windows agent has no real configuration. --> no good check_mk.ini file

All the plugins should be configured as async execution and for some like windows_updates.vbs you need to configure cache time and maximum execution time.

With a good agent configuration this host will also respond with a time of 1.5-2 seconds maximum.

1 Like
6

Hi @andreas-doehler,
i stand corrected. You’re right - as you have already updates the documentation on https://checkmk.de/cms_agent_windows.html, is there any way for @zigbee to lookup the old examples for the agent configuration? In case he/she can’t use the new agent?

7

For the old configuration the examples are inside the “check_mk.example.ini” file.
You can find the example ini inside your WATO agent files or inside the github after selecting the old branch for 1.5.

8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.