Yeah, the only two I'm testing with are check_nrpe and check_tcp, and it's all of them on every server that start failing. Any idea what kind of shared resources it might be starving?
Dan -----Original Message----- From: Andreas Ericsson [mailto:a...@op5.se] Sent: Tuesday, December 14, 2010 10:12 AM To: Nagios Users List Cc: Daniel Wittenberg Subject: Re: [Nagios-users] Return code of 127 is out of bounds - only on high cpu load though On 12/14/2010 05:08 PM, Daniel Wittenberg wrote: > I noticed something odd the other day while stressing my servers. I > noticed that when I overload it with too many hosts/checks, that I > start getting active check failures with the standard 127 code. But, > if I slowly reduce the number of hosts/checks, I’ll get to a point > where it starts working again. Anyone else seen this, where the > “plugin may be missing” really isn’t the problem and only on high > load? > Does it happpen for all checks or just checks of a certain type? Some checks share resources in a way that cause them to bomb out when too many of them are run simultaneously. One possible error in such cases is the infamous 127 error. If it happens with compiled plugins from the standard plugins package, that's not it though as they're all fairly well behaved. -- Andreas Ericsson andreas.erics...@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ 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
