(cross post from www.nagios-forum.co.uk)
Hello,
I’ve inherited a Nagios 2.0b3 setup here, and I’ve ran in to a bit of a hitch. After a reboot (I believe it was due to patches) I had to restart our Windows Server 2003 machine, which hosts our Symantec Antivirus management console. There is a service set up in Nagios to check Symantec (check_tcp!38292). After the reboot Nagios reports it as CRITICAL, while all other services on that Host are OK.
This happened briefly before (a couple months ago) and a restart of the machine fixed it. I’ve restarted the machine (way) too many times, and restart Nagios as well.
I’m stumped, and help would be greatly appreciated, thanks!
-mmX