> Ok, this actually clarifies things. Clearly, NSClient++ ignores
> everything after 'check_openmanage.exe' in your NSC.ini. There is no
> way
> that check_openmanage would complain about fans etc. when the option
> '--only storage' is specified. Since it works from command line we can
> safely as
> On Wed, Apr 27, 2011 at 5:06 AM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> ok, talked to dell, there is no hardware on the T105 that will allow
>> monitoring of the fan, voltage, etc.. basically the only thing you
>> can
>> monitor i
> On Wed, Apr 27, 2011 at 5:06 AM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> ok, talked to dell, there is no hardware on the T105 that will allow
>> monitoring of the fan, voltage, etc.. basically the only thing you
>> can
>> monitor i
> On Wed, Apr 27, 2011 at 8:28 AM, Trond Hasle Amundsen wrote:
> Trond Hasle Amundsen writes:
>
>> Are you using check_openmanage with NRPE or similar in local mode, or
>> checking via SNMP?
>
> I have an idea of what the problem might be. Can you try either of the
> development versions of check
> On Tue, Apr 26, 2011 at 12:39 PM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> the server is a PowerEdge T105. It IS running slow but I'll be
>> damned if I can figure out why, I'm beggining to suspect bad ram as
>> the performanc
> On Tue, Apr 26, 2011 at 11:10 AM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> Ok, now new and exciting changes... no matter what I do I get:
>> WARNING PLUGIN TIMEOUT: check_openmanage timed out after 30 seconds.
>>
>> I have -t 60 set on
On Tue, Apr 26, 2011 at 10:24 AM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> now my problem is this...
>>
>> Problem running 'omreport chassis fans': Error! No fan probes found
>> on this system.Problem running 'omreport chassis t
> On Tue, Apr 26, 2011 at 9:17 AM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> Thanks for the reply. I just realized from your question that I'm
>> using a pre-compiled .exe version of your check_openmanage from here:
>>
>> https://www.
> On Tue, Apr 26, 2011 at 9:17 AM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> Thanks for the reply. I just realized from your question that I'm
>> using a pre-compiled .exe version of your check_openmanage from here:
>>
>> https://www.
> On Tue, Apr 26, 2011 at 9:17 AM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> Thanks for the reply. I just realized from your question that I'm
>> using a pre-compiled .exe version of your check_openmanage from here:
>>
>> https://www.
> On Tue, Apr 26, 2011 at 4:07 AM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> on two of my dell servers check_openmanage (via nsclient++ and nrpe)
>> return the same error:
>>
>> "Use of uninitialized value in concatenation (.) or st
anyone???
On Tue, Apr 19, 2011 at 11:13 AM, Ashcor Technologies wrote:
> Hello All,
>
> on two of my dell servers check_openmanage (via nsclient++ and nrpe)
> return the same error:
>
> "Use of uninitialized value in concatenation (.) or string at
> script/che
I believe the problem is that the code being returned is not 0,1,2 for
(ok, warning, critical) and so nagios doesn't like it.
When you run the command manually from the command line, what is the
result returned?
On Tue, Apr 19, 2011 at 11:24 AM, Martin Hugo wrote:
Hello,
I am trying to m
Hello All,
on two of my dell servers check_openmanage (via nsclient++ and nrpe)
return the same error:
"Use of uninitialized value in concatenation (.) or string at
script/check_openmanage.pl line 1386."
both dell systems are running the latest OpenManage version 6.5.0.
anyone else see this o
14 matches
Mail list logo
