> Has anyone seen as to where using check_http to monitor the > IIS server causes serious issues? > I figure since all it's doing is mapping port 80 for livelyihood, it > should be okay. (At this point, I don't need all the SNMP > information, just want to know that the service is open.)
We had an issue with an IIS server, where the site would allocate session ID cookies when you connected that would time out after far too long. Since we'd be connecting every 5 mins or more frequently for checks, this resulted in session IDs being eaten and the server running low on resources. I agree this is a hosed server with a stupid configuration set up by brain-dead people with no more knowledge than an MCSE, but sadly that's what you get sometimes. Management had two choices - 1) Fix the configuration of the IIS server 2) Stop monitoring it altogether Which do you think they chose? Sigh. Steve -- Steve Shipway ITSS, University of Auckland (09) 3737 599 x 86487 [EMAIL PROTECTED] ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
