pnp4nagios 0.6.25 BULK Mode with NPCD

[rkennedy]

I was able to replicate what you said about the warning / critical not firing. I'll talk to the devs and get back to you shortly.

[Pikmin]

Thank you kindly

[tmcdonald]

I think this is a bug, or at the very least something we need to clarify in terms of output. Please run the check_mrtg check again just as you did a few posts ago, the one that should return WARNING/CRITICAL. After you run it, run echo $? and post the output. Regarding the output, we probably should print out "OK", "WARNING", or "CRITICAL" before the other information, so it's obvious what the state is just looking at the output.

[Pikmin]

This one should return OK

Code: Select all

./check_mrtg -F /var/www/mrtg/192.168.199.1_5.log -a MAX -v 1 -w 11250000 -c 11875000 -l Incoming
Max. Incoming = 186122 |Incoming=186122;11250000;11875000;
[root@ndnagios libexec]# echo $?
0

This one should return critical

Code: Select all

./check_mrtg -F /var/www/mrtg/192.168.199.1_5.log -a MAX -v 1 -w 22 -c 33
Max. value = 186122 |value=186122;22;33;
[root@ndnagios libexec]# echo $?
2

[tmcdonald]

From a status perspective it appears to be fine, it's just not displaying the OK/CRITICAL text. Being a binary file I don't have a great way to patch that for you, but the file that needs to be edited was pretty small:

https://github.com/nagios-plugins/nagio ... rtg.c#L151

Shouldn't be too hard to add in. I'll put in a feature request on the Github page for this.

[Pikmin]

Thank you very much

[rkennedy]

As it looks like a feature request was put in here, https://github.com/nagios-plugins/nagio ... issues/125 -

I'm going to close this thread out now as it's resolved, and a feature request has been started. It's now in the developers hands!

Feel free to open another thread in the future if you ever need assistance.