what is the solution for "-nan" value & "unknown_datapoints" on rrd files ?
Moderators: Developers, Moderators
-
- Posts: 43
- Joined: Mon Aug 29, 2022 1:47 am
what is the solution for "-nan" value & "unknown_datapoints" on rrd files ?
what is the solution for "-nan" value & "unknown_datapoints" on rrd files ?
As Getting correct data from SNMP connection from Device, if we test it manually.
root@grwcacticpe01 # rrdtool fetch adecco01-41lge-ci2_5min_cpu_27386.rrd AVERAGE |tail
1669964700: -nan
1669965000: -nan
1669965300: -nan
1669965600: -nan
1669965900: -nan
1669966200: -nan
1669966500: -nan
1669966800: -nan
1669967100: -nan
1669967400: -nan
root@grwcacticpe01 # rrdtool info adecco01-41lge-ci2_5min_cpu_27386.rrd |grep .cdp_prep
rra[0].cdp_prep[0].value = NaN
rra[0].cdp_prep[0].unknown_datapoints = 0
rra[1].cdp_prep[0].value = 0.0000000000e+00
rra[1].cdp_prep[0].unknown_datapoints = 2
rra[2].cdp_prep[0].value = 0.0000000000e+00
rra[2].cdp_prep[0].unknown_datapoints = 14
rra[3].cdp_prep[0].value = 0.0000000000e+00
rra[3].cdp_prep[0].unknown_datapoints = 86
rra[4].cdp_prep[0].value = NaN
rra[4].cdp_prep[0].unknown_datapoints = 0
rra[5].cdp_prep[0].value = inf
rra[5].cdp_prep[0].unknown_datapoints = 2
rra[6].cdp_prep[0].value = inf
rra[6].cdp_prep[0].unknown_datapoints = 14
rra[7].cdp_prep[0].value = inf
rra[7].cdp_prep[0].unknown_datapoints = 86
rra[8].cdp_prep[0].value = NaN
rra[8].cdp_prep[0].unknown_datapoints = 0
rra[9].cdp_prep[0].value = -inf
rra[9].cdp_prep[0].unknown_datapoints = 2
rra[10].cdp_prep[0].value = -inf
rra[10].cdp_prep[0].unknown_datapoints = 14
rra[11].cdp_prep[0].value = -inf
rra[11].cdp_prep[0].unknown_datapoints = 86
rra[12].cdp_prep[0].value = NaN
rra[12].cdp_prep[0].unknown_datapoints = 0
rra[13].cdp_prep[0].value = NaN
rra[13].cdp_prep[0].unknown_datapoints = 2
rra[14].cdp_prep[0].value = NaN
rra[14].cdp_prep[0].unknown_datapoints = 14
rra[15].cdp_prep[0].value = NaN
rra[15].cdp_prep[0].unknown_datapoints = 86
root@grwcacticpe01 #
As Getting correct data from SNMP connection from Device, if we test it manually.
root@grwcacticpe01 # rrdtool fetch adecco01-41lge-ci2_5min_cpu_27386.rrd AVERAGE |tail
1669964700: -nan
1669965000: -nan
1669965300: -nan
1669965600: -nan
1669965900: -nan
1669966200: -nan
1669966500: -nan
1669966800: -nan
1669967100: -nan
1669967400: -nan
root@grwcacticpe01 # rrdtool info adecco01-41lge-ci2_5min_cpu_27386.rrd |grep .cdp_prep
rra[0].cdp_prep[0].value = NaN
rra[0].cdp_prep[0].unknown_datapoints = 0
rra[1].cdp_prep[0].value = 0.0000000000e+00
rra[1].cdp_prep[0].unknown_datapoints = 2
rra[2].cdp_prep[0].value = 0.0000000000e+00
rra[2].cdp_prep[0].unknown_datapoints = 14
rra[3].cdp_prep[0].value = 0.0000000000e+00
rra[3].cdp_prep[0].unknown_datapoints = 86
rra[4].cdp_prep[0].value = NaN
rra[4].cdp_prep[0].unknown_datapoints = 0
rra[5].cdp_prep[0].value = inf
rra[5].cdp_prep[0].unknown_datapoints = 2
rra[6].cdp_prep[0].value = inf
rra[6].cdp_prep[0].unknown_datapoints = 14
rra[7].cdp_prep[0].value = inf
rra[7].cdp_prep[0].unknown_datapoints = 86
rra[8].cdp_prep[0].value = NaN
rra[8].cdp_prep[0].unknown_datapoints = 0
rra[9].cdp_prep[0].value = -inf
rra[9].cdp_prep[0].unknown_datapoints = 2
rra[10].cdp_prep[0].value = -inf
rra[10].cdp_prep[0].unknown_datapoints = 14
rra[11].cdp_prep[0].value = -inf
rra[11].cdp_prep[0].unknown_datapoints = 86
rra[12].cdp_prep[0].value = NaN
rra[12].cdp_prep[0].unknown_datapoints = 0
rra[13].cdp_prep[0].value = NaN
rra[13].cdp_prep[0].unknown_datapoints = 2
rra[14].cdp_prep[0].value = NaN
rra[14].cdp_prep[0].unknown_datapoints = 14
rra[15].cdp_prep[0].value = NaN
rra[15].cdp_prep[0].unknown_datapoints = 86
root@grwcacticpe01 #
- TheWitness
- Developer
- Posts: 17061
- Joined: Tue May 14, 2002 5:08 pm
- Location: MI, USA
- Contact:
Re: what is the solution for "-nan" value & "unknown_datapoints" on rrd files ?
The way you ensure this is that:
- Ensure that your data collector is actually getting good data. You can do this by putting the Device in question in Debug mode by Editing the Device and Clicking the Link in the upper right hand corner and then watching your Cacti log for information
- Ensure that the data collector is working. Look for SYSTEMS STATS: in the Cacti log
- Ensure that your data collector values are not Exceeding the MAX Value set in the RRDfile which you can obtain using rrdtool info blah.rrd
- Increasing SNMP timeout's if this is what is causing the data not be be gathered
- Decreasing Max OID's if this is what is causing the data not to be gathered
True understanding begins only when we realize how little we truly understand...
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
-
- Posts: 43
- Joined: Mon Aug 29, 2022 1:47 am
Re: what is the solution for "-nan" value & "unknown_datapoints" on rrd files ?
I made two devices in Debug mode. Device1 One which is working fine, as correct values are coming in rrd file. Graph is finely plotting.
Device2, other one which has nan values in rrd file.
I can see logs in cacti for Device1 on each minute, so that values are populating.
But for Device2, only 2 -3 time polling happened in a 24 hrs. as I can see few logs for this device.
Is it polling issue for this Device2 ? or anything else ? How to make this Device to be polled on each minute, both Device has same configuration setting.
below details logged only three time in a day for Device2
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] DEBUG: In Poller, About to Start Polling of Device for Device ID 6938
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] DEBUG: Entering SNMP Ping
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] Updating Full System Information Table
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] DEBUG: Device[6938] HT[1] RECACHE: Processing 2 items in the auto reindex cache for '94.105.14.228'
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DQ[10] RECACHE OID: .1.3.6.1.2.1.1.3.0, (assert: 197382948 < output: 201042956)
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DQ[11] RECACHE OID: .1.3.6.1.2.1.1.3.0, (assert: 197382948 < output: 201042956)
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] NOTE: There are '9' Polling Items for this Device
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[27191] TT[51.71] SNMP: v2: 94.105.14.228, dsname: 5min_cpu, oid: .1.3.6.1.4.1.13191.10.3.3.1.2.1.0, value: 0
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[27197] TT[51.78] SNMP: v2: 94.105.14.228, dsname: band, oid: .1.3.6.1.4.1.13191.10.3.9.2.1.46.0, value: 4
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[27197] TT[51.82] SNMP: v2: 94.105.14.228, dsname: rssi, oid: .1.3.6.1.4.1.13191.10.3.9.2.1.41.0, value: -73
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[28737] TT[51.84] SNMP: v2: 94.105.14.228, dsname: traffic_in, oid: .1.3.6.1.2.1.2.2.1.10.589824, value: 1915713416
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[28737] TT[51.87] SNMP: v2: 94.105.14.228, dsname: traffic_out, oid: .1.3.6.1.2.1.2.2.1.16.589824, value: 682777237
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[27206] TT[51.90] SNMP: v2: 94.105.14.228, dsname: traffic_in, oid: .1.3.6.1.2.1.2.2.1.10.1912799233, value: 1914808451
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[27206] TT[51.92] SNMP: v2: 94.105.14.228, dsname: traffic_out, oid: .1.3.6.1.2.1.2.2.1.16.1912799233, value: 682762677
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[28802] TT[51.95] SNMP: v2: 94.105.14.228, dsname: traffic_in, oid: .1.3.6.1.2.1.2.2.1.10.402657280, value: 49333340
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[28802] TT[51.97] SNMP: v2: 94.105.14.228, dsname: traffic_out, oid: .1.3.6.1.2.1.2.2.1.16.402657280, value: 44969716
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] Total Time: 0.2 Seconds
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] DEBUG: Device[6938] HT[1] DEBUG: HOST COMPLETE: About to Exit Device Polling Thread Function
--------------------------------------------------------------------------------------------------
root@grwcacticpe01 # cat cacti.log|grep 'DEBUG'|grep 6938
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] DEBUG: In Poller, About to Start Polling of Device for Device ID 6938
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] DEBUG: Entering SNMP Ping
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] DEBUG: Device[6938] HT[1] RECACHE: Processing 2 items in the auto reindex cache for '94.105.14.228'
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] DEBUG: Device[6938] HT[1] DEBUG: HOST COMPLETE: About to Exit Device Polling Thread Function
2022-12-06 01:36:07 - SPINE: Poller[1] PID[29565] DEBUG: In Poller, About to Start Polling of Device for Device ID 6938
2022-12-06 01:36:07 - SPINE: Poller[1] PID[29565] Device[6938] DEBUG: Entering SNMP Ping
2022-12-06 01:36:08 - SPINE: Poller[1] PID[29565] DEBUG: Device[6938] HT[1] RECACHE: Processing 2 items in the auto reindex cache for '94.105.14.228'
2022-12-06 01:36:08 - SPINE: Poller[1] PID[29565] DEBUG: Device[6938] HT[1] DEBUG: HOST COMPLETE: About to Exit Device Polling Thread Function
2022-12-06 01:37:07 - SPINE: Poller[1] PID[16033] DEBUG: In Poller, About to Start Polling of Device for Device ID 6938
2022-12-06 01:37:07 - SPINE: Poller[1] PID[16033] Device[6938] DEBUG: Entering SNMP Ping
2022-12-06 01:37:07 - SPINE: Poller[1] PID[16033] DEBUG: Device[6938] HT[1] RECACHE: Processing 2 items in the auto reindex cache for '94.105.14.228'
2022-12-06 01:37:07 - SPINE: Poller[1] PID[16033] DEBUG: Device[6938] HT[1] DEBUG: HOST COMPLETE: About to Exit Device Polling Thread Function
Device2, other one which has nan values in rrd file.
I can see logs in cacti for Device1 on each minute, so that values are populating.
But for Device2, only 2 -3 time polling happened in a 24 hrs. as I can see few logs for this device.
Is it polling issue for this Device2 ? or anything else ? How to make this Device to be polled on each minute, both Device has same configuration setting.
below details logged only three time in a day for Device2
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] DEBUG: In Poller, About to Start Polling of Device for Device ID 6938
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] DEBUG: Entering SNMP Ping
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] Updating Full System Information Table
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] DEBUG: Device[6938] HT[1] RECACHE: Processing 2 items in the auto reindex cache for '94.105.14.228'
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DQ[10] RECACHE OID: .1.3.6.1.2.1.1.3.0, (assert: 197382948 < output: 201042956)
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DQ[11] RECACHE OID: .1.3.6.1.2.1.1.3.0, (assert: 197382948 < output: 201042956)
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] NOTE: There are '9' Polling Items for this Device
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[27191] TT[51.71] SNMP: v2: 94.105.14.228, dsname: 5min_cpu, oid: .1.3.6.1.4.1.13191.10.3.3.1.2.1.0, value: 0
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[27197] TT[51.78] SNMP: v2: 94.105.14.228, dsname: band, oid: .1.3.6.1.4.1.13191.10.3.9.2.1.46.0, value: 4
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[27197] TT[51.82] SNMP: v2: 94.105.14.228, dsname: rssi, oid: .1.3.6.1.4.1.13191.10.3.9.2.1.41.0, value: -73
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[28737] TT[51.84] SNMP: v2: 94.105.14.228, dsname: traffic_in, oid: .1.3.6.1.2.1.2.2.1.10.589824, value: 1915713416
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[28737] TT[51.87] SNMP: v2: 94.105.14.228, dsname: traffic_out, oid: .1.3.6.1.2.1.2.2.1.16.589824, value: 682777237
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[27206] TT[51.90] SNMP: v2: 94.105.14.228, dsname: traffic_in, oid: .1.3.6.1.2.1.2.2.1.10.1912799233, value: 1914808451
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[27206] TT[51.92] SNMP: v2: 94.105.14.228, dsname: traffic_out, oid: .1.3.6.1.2.1.2.2.1.16.1912799233, value: 682762677
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[28802] TT[51.95] SNMP: v2: 94.105.14.228, dsname: traffic_in, oid: .1.3.6.1.2.1.2.2.1.10.402657280, value: 49333340
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] DS[28802] TT[51.97] SNMP: v2: 94.105.14.228, dsname: traffic_out, oid: .1.3.6.1.2.1.2.2.1.16.402657280, value: 44969716
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] HT[1] Total Time: 0.2 Seconds
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] DEBUG: Device[6938] HT[1] DEBUG: HOST COMPLETE: About to Exit Device Polling Thread Function
--------------------------------------------------------------------------------------------------
root@grwcacticpe01 # cat cacti.log|grep 'DEBUG'|grep 6938
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] DEBUG: In Poller, About to Start Polling of Device for Device ID 6938
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] Device[6938] DEBUG: Entering SNMP Ping
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] DEBUG: Device[6938] HT[1] RECACHE: Processing 2 items in the auto reindex cache for '94.105.14.228'
2022-12-06 01:35:08 - SPINE: Poller[1] PID[22166] DEBUG: Device[6938] HT[1] DEBUG: HOST COMPLETE: About to Exit Device Polling Thread Function
2022-12-06 01:36:07 - SPINE: Poller[1] PID[29565] DEBUG: In Poller, About to Start Polling of Device for Device ID 6938
2022-12-06 01:36:07 - SPINE: Poller[1] PID[29565] Device[6938] DEBUG: Entering SNMP Ping
2022-12-06 01:36:08 - SPINE: Poller[1] PID[29565] DEBUG: Device[6938] HT[1] RECACHE: Processing 2 items in the auto reindex cache for '94.105.14.228'
2022-12-06 01:36:08 - SPINE: Poller[1] PID[29565] DEBUG: Device[6938] HT[1] DEBUG: HOST COMPLETE: About to Exit Device Polling Thread Function
2022-12-06 01:37:07 - SPINE: Poller[1] PID[16033] DEBUG: In Poller, About to Start Polling of Device for Device ID 6938
2022-12-06 01:37:07 - SPINE: Poller[1] PID[16033] Device[6938] DEBUG: Entering SNMP Ping
2022-12-06 01:37:07 - SPINE: Poller[1] PID[16033] DEBUG: Device[6938] HT[1] RECACHE: Processing 2 items in the auto reindex cache for '94.105.14.228'
2022-12-06 01:37:07 - SPINE: Poller[1] PID[16033] DEBUG: Device[6938] HT[1] DEBUG: HOST COMPLETE: About to Exit Device Polling Thread Function
Re: what is the solution for "-nan" value & "unknown_datapoints" on rrd files ?
You might want to consider using the 1.2.x version of spine.
Before history, there was a paradise, now dust.
-
- Posts: 43
- Joined: Mon Aug 29, 2022 1:47 am
Re: what is the solution for "-nan" value & "unknown_datapoints" on rrd files ?
what is the procedure to use 1.2.x version of spine ?
as my organization will not approve for Version upgrade. So is there any other Solution ?
Currently we are running at 1.2.18 version.
as my organization will not approve for Version upgrade. So is there any other Solution ?
Currently we are running at 1.2.18 version.
Re: what is the solution for "-nan" value & "unknown_datapoints" on rrd files ?
Download that version from GitHub, run bootstrap and follow the instructions
Code: Select all
git clone -b 1.2.x https://github.com/cacti/spine.git
cd spine
./boostrap
Before history, there was a paradise, now dust.
-
- Posts: 43
- Joined: Mon Aug 29, 2022 1:47 am
Re: what is the solution for "-nan" value & "unknown_datapoints" on rrd files ?
Will it update only Spine, other Scripts too ?
If i will update, will it depend on any Other Script ?
If i will update, will it depend on any Other Script ?
Re: what is the solution for "-nan" value & "unknown_datapoints" on rrd files ?
No
Before history, there was a paradise, now dust.
-
- Posts: 43
- Joined: Mon Aug 29, 2022 1:47 am
Re: what is the solution for "-nan" value & "unknown_datapoints" on rrd files ?
Do I need to update spine on below folder ?
/usr/local/spine/
or
/usr/local/
?
OR Direct run your command will work ?
/usr/local/spine/
or
/usr/local/
?
OR Direct run your command will work ?
-
- Posts: 43
- Joined: Mon Aug 29, 2022 1:47 am
Re: what is the solution for "-nan" value & "unknown_datapoints" on rrd files ?
Could You Please tell the full Procedure ?
Like which Path & Command ?
I checked, but bootstrap is not found in system.
Like which Path & Command ?
I checked, but bootstrap is not found in system.
Who is online
Users browsing this forum: fpiorek and 5 guests