Hi list,
i'm having an odd problem with the development machine I installed =20
Nagios Core 3.4.0 to.
It took me some time to make sure what the problem acutally is, but =20
there must have some change in the performance data handling.
For my setup:
It's two machines running CentOS 5.8 x64, the production-machine is =20
Nagios Core 3.3.1 and the development machine is Nagios Core 3.4.0, =20
both have the same versions of other packages both have PNP-0.6.17 and =20
both have nagios-plugins-1.4.15 - and both have the exact same config =20
(except the dev-machine doesn't send email to everyone).
So far about the basics.
I'm having the problem with the check_snmp and check_nt scripts, if =20
there is a label (on check_snmp) or a counter (on check_nt) with =20
blanks and it's therefor in apostrophes.
So that means, that Nagios is still checking the state of the checks, =20
but there is no performance data handled by PNP, as the input is =20
invalid.
Let me explain that with an example:
This checks the environment temperature sensor of APC UPS.
______
command_line=09$USER1$/check_snmp -H $HOSTADDRESS$ -C $ARG1$ -o =20
.1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.1 -w 29 -c 40 -l 'environment =20
Temperature' -u =B0C
______
as you can see the label "-l 'environment Temperature'" is set in apostroph=
es.
If that check is run by Nagios 3.3.1 it looks like follows in Service =20
State Information window:
_____
Status Information:SNMP OK - environment Temperature 24 =B0C
Performance Data:environment Temperature=3D24
_____
If that exact same check is run by Nagios 3.4.0 it looks like:
_____
Status Information:SNMP OK - 24 =B0C
Performance Data:=3D24
_____
So Nagios is still recognizing the value and handling the =20
notifications and escalations as it should, but "=3D24" is sent to PNP =20
as performance data, what clearly is invalid.
In production system (Nagios Core 3.3.1 - PNP-0.6.17) perfdata.log tells:
_____
Found Performance Data for APC_5000XL / Environment-Temperature =20
(environment Temperature=3D24)
_____
and is put into the graph just fine.
In development system (Nagios Core 3.4.0 - same PNP-version!) it is:
_____
Found Performance Data for APC_5000XL / Environment-Temperature (=3D24)
Invalid Perfdata detected
_____
So Nagios 3.4.0 is doing something to the performance data.
The only possibility to change that behavior back to normal is to =20
change the check-command to anything valid without apostrophes, like:
______
command_line=09$USER1$/check_snmp -H $HOSTADDRESS$ -C $ARG1$ -o =20
.1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.1 -w 29 -c 40 -l Temperature -u =B0C
______
but that's not what I'd call "solution".
I downgraded the development system to 3.3.1 and instantly that checks =20
were reported correctly and graphs are drawn.
Back to 3.4.0 that stops immediately.
Does anyone else have registered such behaviour or can this be =20
confirmed as a bug?
Maybe I'm having blinders for changes that were clearly =20
communicated... or am missing some major point, so please tell me.
I would appreciate any help or confirmation that this is a bug and =20
will be fixed in further releases.
If you have any further queries, please do not hesitate to contact me.
cheers
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: hells@wannabepunk.d