Steve Shipway wrote: > > 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. >
Since they're management, they actually had more choices: 3) Buy a new web-server and a loadbalancer, clone the old configuration and use the loadbalancer to keep session-id's from being eaten. 4) Buy more RAM for the old server. 5) Buy a new, beefier, server. The trouble with management is that *any* action that gives the desired result is, from their point of view, correct and side-effects are only important if they affect *this* budget-year. -- Andreas Ericsson [EMAIL PROTECTED] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 ------------------------------------------------------------------------- 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 [email protected] 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
