RRD Data not working since update to XI 2.2, I've updated to 2.3 since but still not working
I am getting invalid performance data from "Memory Usage Physical" and _Host_ checks in Nagios since the update to 2.2 just before Xmas, log file entries below
DATATYPE::SERVICEPERFDATA TIMET::1421228304 HOSTNAME::THSDRWS21 SERVICEDESC::Memory Usage Physical SERVICEPERFDATA::'physical memory %'=76%;90;95; 'physical memory'=18.31G;21.59;22.79;0;23.9; SERVICECHECKCOMMAND::check_nrpe!CheckMEM!MaxWarn=90% MaxCrit=95% type=physical ShowAll!!!!!! HOSTSTATE::UP HOSTSTATETYPE::HARD SERVICESTATE::OK SERVICESTATETYPE::HARD SERVICEOUTPUT::OK: physical memory: 18.3G
2015-01-14 09:48:43 [21067] [1] Found Performance Data for THSDRWS21 / Memory_Usage_Physical ('physical memory %'=76%;90;95; 'physical memory'=18.29G;21.59;22.79;0;23.9;)
2015-01-14 09:48:43 [21067] [1] Invalid Perfdata detected
I've had to attach the upgrade output
Performance data broken since upgrade to 2.2
-
JulianFDRacing
- Posts: 51
- Joined: Tue Oct 16, 2012 9:45 am
Performance data broken since upgrade to 2.2
You do not have the required permissions to view the files attached to this post.
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: Performance data broken since upgrade to 2.2
Lets increase the logging verbosity and then take a deeper look into the logs. Follow the FAQ entry below to increase the log level of process_perfdata and npcd:
http://support.nagios.com/wiki/index.ph ... leshooting
Wait 15 - 20 minutes and then get a tail of the logs:
tail -250 /usr/local/nagios/var/perfdata.log > /tmp/perfdata.txt
tail -250 /usr/local/nagios/var/npcd.log > /tmp/npcd.txt
Send us a copy of /tmp/perfdata.txt and /tmp/npcd.txt
Don't forget to turn down the log level as per the FAQ when you are done!
http://support.nagios.com/wiki/index.ph ... leshooting
Wait 15 - 20 minutes and then get a tail of the logs:
tail -250 /usr/local/nagios/var/perfdata.log > /tmp/perfdata.txt
tail -250 /usr/local/nagios/var/npcd.log > /tmp/npcd.txt
Send us a copy of /tmp/perfdata.txt and /tmp/npcd.txt
Don't forget to turn down the log level as per the FAQ when you are done!
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
-
JulianFDRacing
- Posts: 51
- Joined: Tue Oct 16, 2012 9:45 am
Re: Performance data broken since upgrade to 2.2
I've increased debug to 2 but get the following on the log for a check thats failing to write to rrd/xml
2015-01-15 09:28:25 [21589] [2] Processing Line 113
2015-01-15 09:28:25 [21589] [2] Datatype set to 'SERVICEPERFDATA'
2015-01-15 09:28:25 [21589] [1] Found Performance Data for THSDRWS21 / Memory_Usage_Physical ('physical memory %'=59%;90;95; 'physical memory'=14.21G;21.59;22.79;0;23.9;)
2015-01-15 09:28:25 [21589] [2] No Custom Template found for check_ams_memory (/usr/local/nagios/etc/pnp/check_commands/check_ams_memory.cfg)
2015-01-15 09:28:25 [21589] [2] RRD Datatype is GAUGE
2015-01-15 09:28:25 [21589] [2] Template is check_ams_memory.php
2015-01-15 09:28:25 [21589] [2] No Custom Template found for check_ams_memory (/usr/local/nagios/etc/pnp/check_commands/check_ams_memory.cfg)
2015-01-15 09:28:25 [21589] [2] RRD Datatype is GAUGE
2015-01-15 09:28:25 [21589] [2] Template is check_ams_memory.php
2015-01-15 09:28:25 [21589] [2] No pattern match in function _parse(; )
2015-01-15 09:28:25 [21589] [1] Invalid Perfdata detected
2015-01-15 09:28:25 [21589] [2] Processing Line 114
2015-01-15 09:28:25 [21589] [2] No Perfdata. Skipping line 114
We use exactly the same check on another server that works fine here is a similar log snippet
2015-01-15 09:41:59 [12535] [2] Processing Line 103
2015-01-15 09:41:59 [12535] [2] Datatype set to 'SERVICEPERFDATA'
2015-01-15 09:41:59 [12535] [1] Found Performance Data for CNLASCRPSP01 / Memory_Usage_Physical ('physical memory %'=31%;90;95 'physical memory'=9.92GB;28.8;30.4;0;32)
2015-01-15 09:41:59 [12535] [2] No Custom Template found for check_ams_memory (/usr/local/nagios/etc/pnp/check_commands/check_ams_memory.cfg)
2015-01-15 09:41:59 [12535] [2] RRD Datatype is GAUGE
2015-01-15 09:41:59 [12535] [2] Template is check_ams_memory.php
2015-01-15 09:41:59 [12535] [2] No Custom Template found for check_ams_memory (/usr/local/nagios/etc/pnp/check_commands/check_ams_memory.cfg)
2015-01-15 09:41:59 [12535] [2] RRD Datatype is GAUGE
2015-01-15 09:41:59 [12535] [2] Template is check_ams_memory.php
2015-01-15 09:41:59 [12535] [2] data2rrd called
2015-01-15 09:41:59 [12535] [2] RRDs::update /usr/local/nagios/share/perfdata/CNLASCRPSP01/Memory_Usage_Physical.rrd 1421314900:31:9.92
2015-01-15 09:41:59 [12535] [2] /usr/local/nagios/share/perfdata/CNLASCRPSP01/Memory_Usage_Physical.rrd updated
2015-01-15 09:41:59 [12535] [2] Processing Line 104
So it looks like the actual error is "No pattern match in function _parse"
failed line - 2015-01-15 09:28:25 [21589] [1] Found Performance Data for THSDRWS21 / Memory_Usage_Physical ('physical memory %'=59%;90;95; 'physical memory'=14.21G;21.59;22.79;0;23.9;)
working line - 2015-01-15 09:41:59 [12535] [1] Found Performance Data for CNLASCRPSP01 / Memory_Usage_Physical ('physical memory %'=31%;90;95 'physical memory'=9.92GB;28.8;30.4;0;32)
Looking at the performance data returned the failing one uses "14.21G" whereas the working one is "9.92GB", note the "G" and "GB", also there is a semicolon on the failing string but missing on the working one
Working NSClient version - 2013-08-05 23:55:55: message:modules\FileLogger\FileLogger.cpp:86: Starting to log for: NSClient++ - 0.3.9.328 2011-08-16
Failed NSClient version - FOUND THE ISSUE - Version 3.8 of NSClient isnt compatible with NagiosXI 2.2/3, I've upgraded it to 3.9 as above and its working fine now
2015-01-15 09:28:25 [21589] [2] Processing Line 113
2015-01-15 09:28:25 [21589] [2] Datatype set to 'SERVICEPERFDATA'
2015-01-15 09:28:25 [21589] [1] Found Performance Data for THSDRWS21 / Memory_Usage_Physical ('physical memory %'=59%;90;95; 'physical memory'=14.21G;21.59;22.79;0;23.9;)
2015-01-15 09:28:25 [21589] [2] No Custom Template found for check_ams_memory (/usr/local/nagios/etc/pnp/check_commands/check_ams_memory.cfg)
2015-01-15 09:28:25 [21589] [2] RRD Datatype is GAUGE
2015-01-15 09:28:25 [21589] [2] Template is check_ams_memory.php
2015-01-15 09:28:25 [21589] [2] No Custom Template found for check_ams_memory (/usr/local/nagios/etc/pnp/check_commands/check_ams_memory.cfg)
2015-01-15 09:28:25 [21589] [2] RRD Datatype is GAUGE
2015-01-15 09:28:25 [21589] [2] Template is check_ams_memory.php
2015-01-15 09:28:25 [21589] [2] No pattern match in function _parse(; )
2015-01-15 09:28:25 [21589] [1] Invalid Perfdata detected
2015-01-15 09:28:25 [21589] [2] Processing Line 114
2015-01-15 09:28:25 [21589] [2] No Perfdata. Skipping line 114
We use exactly the same check on another server that works fine here is a similar log snippet
2015-01-15 09:41:59 [12535] [2] Processing Line 103
2015-01-15 09:41:59 [12535] [2] Datatype set to 'SERVICEPERFDATA'
2015-01-15 09:41:59 [12535] [1] Found Performance Data for CNLASCRPSP01 / Memory_Usage_Physical ('physical memory %'=31%;90;95 'physical memory'=9.92GB;28.8;30.4;0;32)
2015-01-15 09:41:59 [12535] [2] No Custom Template found for check_ams_memory (/usr/local/nagios/etc/pnp/check_commands/check_ams_memory.cfg)
2015-01-15 09:41:59 [12535] [2] RRD Datatype is GAUGE
2015-01-15 09:41:59 [12535] [2] Template is check_ams_memory.php
2015-01-15 09:41:59 [12535] [2] No Custom Template found for check_ams_memory (/usr/local/nagios/etc/pnp/check_commands/check_ams_memory.cfg)
2015-01-15 09:41:59 [12535] [2] RRD Datatype is GAUGE
2015-01-15 09:41:59 [12535] [2] Template is check_ams_memory.php
2015-01-15 09:41:59 [12535] [2] data2rrd called
2015-01-15 09:41:59 [12535] [2] RRDs::update /usr/local/nagios/share/perfdata/CNLASCRPSP01/Memory_Usage_Physical.rrd 1421314900:31:9.92
2015-01-15 09:41:59 [12535] [2] /usr/local/nagios/share/perfdata/CNLASCRPSP01/Memory_Usage_Physical.rrd updated
2015-01-15 09:41:59 [12535] [2] Processing Line 104
So it looks like the actual error is "No pattern match in function _parse"
failed line - 2015-01-15 09:28:25 [21589] [1] Found Performance Data for THSDRWS21 / Memory_Usage_Physical ('physical memory %'=59%;90;95; 'physical memory'=14.21G;21.59;22.79;0;23.9;)
working line - 2015-01-15 09:41:59 [12535] [1] Found Performance Data for CNLASCRPSP01 / Memory_Usage_Physical ('physical memory %'=31%;90;95 'physical memory'=9.92GB;28.8;30.4;0;32)
Looking at the performance data returned the failing one uses "14.21G" whereas the working one is "9.92GB", note the "G" and "GB", also there is a semicolon on the failing string but missing on the working one
Working NSClient version - 2013-08-05 23:55:55: message:modules\FileLogger\FileLogger.cpp:86: Starting to log for: NSClient++ - 0.3.9.328 2011-08-16
Failed NSClient version - FOUND THE ISSUE - Version 3.8 of NSClient isnt compatible with NagiosXI 2.2/3, I've upgraded it to 3.9 as above and its working fine now
Re: Performance data broken since upgrade to 2.2
Great! Is it safe to lock this post as "resolved"?Failed NSClient version - FOUND THE ISSUE - Version 3.8 of NSClient isnt compatible with NagiosXI 2.2/3, I've upgraded it to 3.9 as above and its working fine now
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
JulianFDRacing
- Posts: 51
- Joined: Tue Oct 16, 2012 9:45 am
Re: Performance data broken since upgrade to 2.2
Yes but worth noting that you need nsclient 3.9 as a minimum to collect "Memory Usage Physical" performance data from the NRPE CheckMEM function. its always better when you resolve your own issues 