Lets see if perfdata is actually spooling. You should see the integer output from the following watch command change over time. It should go up and down.
If it is not changing, there is an issue spooling the perfdata and will require further troubleshooting and earlier parts of the perfdata workflow. If the number is indeed changing, then perfdata is getting reaped and we need check the rrds for newly inserted data. Choose any service that you know is returning recent properly formatted performance data and then run the following command (replacing <host> and <service> with the correct values for the service in question:
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Step 1, the integer on the watch does change. Mostly 2 or 4 or 0, but it does change.
Step 2, all NaNs for them
[root@ust-nagios1p ~]# rrdtool dump /usr/local/nagios/share/perfdata/zeus.stthomas.edu/Load.rrd | tail -25
<!-- 2015-01-21 06:00:00 CST / 1421841600 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-21 12:00:00 CST / 1421863200 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-21 18:00:00 CST / 1421884800 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-22 00:00:00 CST / 1421906400 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-22 06:00:00 CST / 1421928000 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-22 12:00:00 CST / 1421949600 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-22 18:00:00 CST / 1421971200 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-23 00:00:00 CST / 1421992800 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-23 06:00:00 CST / 1422014400 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-23 12:00:00 CST / 1422036000 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-23 18:00:00 CST / 1422057600 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-24 00:00:00 CST / 1422079200 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-24 06:00:00 CST / 1422100800 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-24 12:00:00 CST / 1422122400 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-24 18:00:00 CST / 1422144000 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-25 00:00:00 CST / 1422165600 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-25 06:00:00 CST / 1422187200 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-25 12:00:00 CST / 1422208800 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-25 18:00:00 CST / 1422230400 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-26 00:00:00 CST / 1422252000 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-26 06:00:00 CST / 1422273600 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
<!-- 2015-01-26 12:00:00 CST / 1422295200 --> <row><v> NaN </v><v> NaN </v><v> NaN </v></row>
</database>
</rra>
</rrd>
If for some reason the server cannot download this file, download it and transfer it to the XI server into the same directory as the xi-rrdcached.sh script. Comment out line 114 and then re-run the script.
NOTE: the xi-rrdcached.sh script requires internet access to complete successfully.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
awesome, it looks like that may have fixed it. I'll have to do a more thorough test/validation tomorrow but I see data again on some of the charts. THANKS!
Alirght, 75% there. Charting has started again is appears to be working in test and production for all servers/services. On our production instance of Nagios however I am not getting any charts yet for Switches and Routers (On the test environment that is working. )
So now off to troubleshooting networking charting - which I believe is a different set of troubleshooting right?