Since I got the pleasure of watching some Windows boxen with Nagios, I took the Windows Update plugin from Michal Jankowski and implemented it. It took me some time, to initially set up the nsclient++ correctly so it just works, but up till now the check plugin sometimes reported the usual “Service Check Timed Out”.
Usually I ended up increasing the cscript timeout, or the nsclient++ socket timeout, but it still kept showing up. Since I rely heavily on my surveillance tools, I have the demand, that as few as possible false positives show up. So I ended up chasing down this error today, and after that I have to say it was quite simple.
In my case, it wasn’t cscript (that timeout is set to 300 seconds), neither nsclient++ (socket timeout is set to 300 seconds too), nor the nrpe plugin itself (that has 300 seconds as well).
As it turns out, Nagios got an additional setting controlling these things, called service_check_timeout which defaults to 60 seconds. Sadly the plugin, or rather Windows needs longer than those 60 seconds to figure out whether or not it needs updating, thus Nagios is killing the plugin and returning a CRITICAL message.
After increasing the value of service_check_timeout that’ll be fixed hopefully.
Cool blog, dude. Lots of good info on here.
Jesus Monkey Balls!
I love you, I couldn’t find this anywhere, you saved me hours of torment.
I think I love you! … Thank you so much.. my headache is finally gone!
Great tip, I knew this setting but nagios is such a maze, it makes you lost when you get to fix other things. Thanks for pointing me in right direction.
Same fix for Linux boxes?
Yeah, same fix for Linux boxes.