I tried using the blacklisting syntax and that never seemed to work....your command fits my needs perfectly,
We have 82 2650's and are trying to phase them out, but 10 of the 18 I installed had problems -makes me wonder if there is something wrong with openamange 5.5 on that version. Since we have those servers under 3rd party warranty so we will pursue with them that open manage is having problems Just another feature request.....I would like to make the host name an html clickable link to the https://servername:1311 Open Manage web interface. I thought about wrapping the open manage check to do it, but seemed kind of kludgy. Thanks Jack > From: [email protected] > To: [email protected] > CC: [email protected] > Subject: Re: Check_openmanage > Date: Mon, 4 Jan 2010 16:43:01 +0100 > > Jack Lyons <[email protected]> writes: > > > I have some older 2650 that through some message with State=UKNOWN when I > > use > > check_openmanage > > > > See below for output of check_openmanage -d > > > > Is this a hardware issue that we need to address or is this a system > > configuration issue - no fan probes, no temp probes, no volt probs that > > could > > be handled via configuration / change of check_openmanage > > > > I have added this to the perl code and it works, but I am having problems > > compiling check_openmanage.pl on windows. (problems installings and using > > PAR::Packer) > > > > in the $ok_errors section > > | No\sfan\sprobes\sfound\son\sthis\ssystem # No battery > > probes > > | No\stemperature\sprobes\sfound\son\sthis\ssystem # No > > battery probes > > | No\svoltage\sprobes\sfound\son\sthis\ssystem # No > > battery probes > > > > > A) Could someone give me a compiled version of the check_openmanage.pl > > that has the $ok_errors section in it. > > Yes, I could do that for you. But see below first... > > > B) Can we modify the --only option to include warning+ to include warning > > messages and above AND ignore Unknown states? > > Not sure that I understand what you mean. If used, the --only option > specifies exactly one component to check. For example, '--only cpu' > would make the plugin only check the CPUs. All other components are > ignored. No warnings about e.g. fan probes should then appear. > > > C) is there another way to prevent to configure the plugin for nagios from > > alerting on this output. > > Yes. You can use the '--check' option to specify that you don't want to > check these things. Example: > > check_openmanage --check fans=0,temp=0,voltage=0 > > Using the '--check' option as above will prevent check_openmanage to > ever running the commands that are failing. > > [...] > > UNKNOWN | Problem running 'omreport chassis fans': Error! No fan probes > > found > > on this system. > > UNKNOWN | Problem running 'omreport chassis temps': Error! No temperature > > probes found on this system. > > UNKNOWN | Problem running 'omreport chassis volts': Error! No voltage probes > > found on this system. > > These are errors from running omreport. They indicate that something is > wrong, either with the hardware or with Openmanage. I would try > reinstalling Openmanage first, which may help. The 2650 is an old model, > but if you still have a valid warranty you should contact Dell support > about this problem. These commands should not fail like this. If all > else fails, use the '--check' option as described above. > > Cheers, > -- > Trond H. Amundsen <[email protected]> > Center for Information Technology Services, University of Oslo
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ 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
