On Thu, Aug 20, 2009 at 11:54 AM, Terry<td3...@gmail.com> wrote: > On Thu, Aug 20, 2009 at 11:33 AM, > cr...@hooters-uk.com<cr...@hooters-uk.com> wrote: >> Hi Group, I hope you can give me a better >> understanding of the check_load command as I'm unsure >> what my settings should be aligned to, if you take a >> look at the below command line I get Warning and >> Critical alerts all the time and I'm not sure what to >> alter the figure to as I do not understand them at >> the minute. >> >> command[check_load]=/usr/local/nagios/libexec/check_load >> -w 15,10,5 -c 30,25,20 >> >> The above line give: WARNING - load average: 3.99, >> 4.56, 7.60 >> >> Looking at the warning and given the fact that the >> server guys says that his server is running OK, what >> would be the ideal -w and -c be to use. >> >> I will try and read up on the above but just looking >> for help now on this one server. >> >> Many thanks >> >> Craig >> > > Run cat /proc/cpuinfo and put that in here. >
Sorry, missed a number. I think it is generating a warning because your 15 minute average is above the level you wish to be warned at. 7.60 > 5. Which you are already guessing. My original thought was you should consider using the -r option which may offer a more realistic number by which you can compare the user experience to. Check out /usr/local/nagios/libexec/check_load --help for a detailed description of that option. A load average of 15 is pretty insane by my experience. Use the -r option and then go from there. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ 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