Timeout on WMI Queries
- This topic has 5 replies, 3 voices, and was last updated 4 years, 6 months ago by
trentasis.
- AuthorPosts
- 2020-01-16 at 6:27 PM #392
gennaro.piano
ParticipantHello I’ve got a problem with the implementation of the checks.
All the WMI checks get a sporadic timeout exceeded message in the Icinga2 console.
I’ve set the timeout already to 60s. But the timeout still exceeded sometimes.
Do you know how I can solve this?
Best Regards
Gennaro2020-02-19 at 10:04 AM #393admin
KeymasterThis can get tricky and time consuming to fix. First steps are usually to isolate where the problem source is.
Can you reproduce it from the command line? Write a a script to run it repeatedly from the command line. If it does not time out from the command line then the timeout problem exists in the application that is running the plugin.
Try and get a network packet capture of a timeout, ideally from a command line invocation of the plugin. See who is not responding. If the Windows box is not responding, most likely the problem exists on the Windows side.
If the problem is pinpointed to the box running the plugin, sometimes a stack trace (strace or similar) can help find the problem.
2020-12-30 at 11:59 PM #427trentasis
ParticipantHi,
I have a similar issue
UNKNOWN – Plugin Timed out (59 sec). There are multiple possible reasons for this, some of them include – The host 192.168.10.11 might just be really busy, it might not even be running Windows.Without any action after some minutes error disappears.
Have you solved?
thanks
2020-12-31 at 8:26 AM #428admin
KeymasterWhat was the result from the troubleshooting steps I posted above?
2020-12-31 at 4:51 PM #429gennaro.piano
ParticipantNeither of them. I realized after this post that I used the wrong variable for the timeout. Since I use the right one it doesn’t happen anymore.
2020-12-31 at 9:43 PM #430trentasis
ParticipantHi,
Can you give details, what you have done to solve?
Thanks - AuthorPosts
- You must be logged in to reply to this topic.