A valid MODE and/or SUBMODE must be specified - F/P

[litsupport.box]

Hello,

I'm getting this warning:



When i force an immediate recheck it gives me the following OK message:



What can i do to stop getting these false positives? Or isnt it a false positive?

This is the command im using to Check OS SP:

Code: Select all

$USER1$/check_wmi_plus.pl -H $HOSTADDRESS$ -u $ARG1$ -p $ARG2$ -m $ARG3$ $ARG4$ 

(ARG3= info -s os)

Im curious to what you guys have to say.

Thank you in advance.

Kind regards,


Farid

[jolson]

Hello again litsupport.box. When are you receiving this warning? Is it only when you start a new service or does it happen periodically?

Your arguments look proper to me.

[litsupport.box]

Hello again litsupport.box. When are you receiving this warning? Is it only when you start a new service or does it happen periodically?

Your arguments look proper to me.

This message reappears frequently, and as i explained the 2nd time it tries to check it it always passes.

[brdr]

Hi, this happens in our environment too. Not often, but i did notice that it general happens when using the checks in the *.ini files from /usr/local/nagios/libexec/check_wmi_plus.d. directory, for example, the 'checkexchange.ini'. I don't remember seeing this happen using 'builtins', i.e. checkcpu. Hope this helps. I will try to track it more closely.

[brdr]

Here is snippet from nagios.log (below)... The service checks go to UNKNOWN, but then go OK.

Command and args....
$USER1$/check_wmi_plus.pl -H $HOSTADDRESS$ -u $USER23$ -p $USER24$ -m $ARG1$ -s $ARG2$ $ARG3$ -extrawmicarg --option="client ntlmv2 auth"=Yes
Arguments are (for the first line):
ARG1 = checkexchange
ARG2 = DBInstances
ARG3 = -a 'MBX70' --nodatastring="Critical: Exchange Database is unmounted"

[Tue Mar 24 10:44:20 2015] SERVICE ALERT: 300-12;Database MBX70-DB;UNKNOWN;SOFT;1;A valid MODE and/or SUBMODE must be specified
[Tue Mar 24 10:44:30 2015] SERVICE ALERT: 300-10;Database MBX50-DB;UNKNOWN;SOFT;1;A valid MODE and/or SUBMODE must be specified
[Tue Mar 24 10:45:30 2015] SERVICE ALERT: 300-10;Mount Point : MBX01-DB;UNKNOWN;SOFT;1;A valid MODE and/or SUBMODE must be specified
[Tue Mar 24 10:46:00 2015] SERVICE ALERT: 300-10;Database MBX03-DB;UNKNOWN;SOFT;1;A valid MODE and/or SUBMODE must be specified
[Tue Mar 24 10:46:30 2015] SERVICE ALERT: 300-10;Database PF01-DB;UNKNOWN;SOFT;1;A valid MODE and/or SUBMODE must be specified
[Tue Mar 24 10:47:00 2015] SERVICE ALERT: 300-13;Database MBX83-DB;UNKNOWN;SOFT;1;A valid MODE and/or SUBMODE must be specified
[Tue Mar 24 10:47:00 2015] SERVICE ALERT: 300-12;Mount Point : MBX78-DB;UNKNOWN;SOFT;1;A valid MODE and/or SUBMODE must be specified
[Tue Mar 24 10:47:39 2015] SERVICE ALERT: 300-13;Mount Point : MBX84-LOG;UNKNOWN;SOFT;1;A valid MODE and/or SUBMODE must be specified
[Tue Mar 24 10:47:50 2015] SERVICE ALERT: 300-12;Mount Point : MBX76-DB;UNKNOWN;SOFT;1;A valid MODE and/or SUBMODE must be specified
[Tue Mar 24 10:51:00 2015] SERVICE ALERT: 300-11;Mount Point : MBX65-LOG;UNKNOWN;SOFT;1;A valid MODE and/or SUBMODE must be specified
[

[brdr]

I'm happy to PM over the nagios.debug.log if that helps. Settings are at:

debug_level=-1
debug_verbosity=2
max_debug_file_size=100000000

[lmiltchev]

@litsupport.box

Have you tried increasing the timeout? It believe the default timeout is 15 seconds. You can try passing something higher than that to your command, for example:

Code: Select all

/usr/local/nagios/libexec/check_wmi_plus.pl -H <ip address> -u <username> -p <password> -m info -s os -t 30

[litsupport.box]

@litsupport.box

Have you tried increasing the timeout? It believe the default timeout is 15 seconds. You can try passing something higher than that to your command, for example:

Code: Select all

/usr/local/nagios/libexec/check_wmi_plus.pl -H <ip address> -u <username> -p <password> -m info -s os -t 30

No i havent tried that, ill do that right away. I'll update this post when i have more info.

[lmiltchev]

No i havent tried that, ill do that right away. I'll update this post when i have more info.

Sounds good. Let us know if the issue is resolved.

[litsupport.box]

I'm still getting this problem, tried -t 30,60,600 :p