NSClient++ Help (#1) - (Return code of x is out of bounds) change to Unknown instead of Critical (#63) - Message List
Is there a way to change the (Return code of x is out of bounds) to report an Unknown status to Nagios instead of a Critical status to Nagios? This way I could choose not to get noticed on Unknown errors, but still get noticed on Critical and Warning errors.
Thanks in advance for your help!
JohnK
-
Message #144
in what context?
sounds like an external NRPE script?
MickeM
mickem12/01/07 00:19:31 (5 years ago)-
Message #146
One of the commands I use in Nagios is: check_command check_nt!MEMUSE!-w 80 -c 90
and it often returns: Return code of 139 is out of bounds). Instead of reporting to Nagios this as a Critical status, is there a way to change this to an Unknown status?
Thank you for your help.
JohnK
anonymous12/03/07 15:57:54 (5 years ago)-
Message #147
check_nt does its "own" handling so the short answer is "no", but most likely there is something wrong that causes check_nt to report 139 so my guess is: yes.
To find out what, run the command from the CLI and also check the NSCP logs (and perhaps enable debug logging or even run tiwh the /test option)
MickeM
anonymous12/03/07 20:03:41 (5 years ago)
-
-
