Hello,
Could somebody give me a hand on this issue??
WEATHERMAP: Poller[0] WARNING: [Map 7] 2.conf: ReadData: LINK node03892-node03934a, target: /var/www/html/cacti/rra/firewall_in_126.rrd on config line 576 of /var/www/html/cacti/plugins/weathermap/configs/2.conf had no valid data, according to WeatherMapDataSource_rrd
I have a map with a bunch of devices and some of them are showing correct info and color on their graphs and others no.
Regards!!!
Config File had no Valid Data
Moderators: Developers, Moderators
Config File had no Valid Data
- Attachments
-
- Picture.png (88.38 KiB) Viewed 2440 times
Re: Config File had no Valid Data
Hi,
I'm facing today the same issue on my system.
08/31/2016 06:06:22 PM - WEATHERMAP: Poller[0] WARNING: [Map 126] xxx.conf: ReadData: LINK xxx-node04438, target: /var/www/html/cacti/rra/xxx_bytecount_8244.rrd:ByteCount:ByteCount on config line 371 of /var/www/html/cacti/plugins/weathermap/configs/xxx.conf had no valid data, according to WeatherMapDataSource_rrd
i see it when I run the poller manually.
I'm facing today the same issue on my system.
08/31/2016 06:06:22 PM - WEATHERMAP: Poller[0] WARNING: [Map 126] xxx.conf: ReadData: LINK xxx-node04438, target: /var/www/html/cacti/rra/xxx_bytecount_8244.rrd:ByteCount:ByteCount on config line 371 of /var/www/html/cacti/plugins/weathermap/configs/xxx.conf had no valid data, according to WeatherMapDataSource_rrd
i see it when I run the poller manually.
Re: Config File had no Valid Data
It might be helpful know if those graphs exists and are showing data correctly.
Sometimes you can do:
[root@myserver1 cacti]# rrdtool info rra/mydevice_traffic_in_523.rrd
filename = "rra/mydevice_traffic_in_523.rrd"
rrd_version = "0003"
step = 300
last_update = 1472676934
header_size = 2912
ds[traffic_in].index = 0
ds[traffic_in].type = "COUNTER"
ds[traffic_in].minimal_heartbeat = 600
ds[traffic_in].min = 0.0000000000e+00
ds[traffic_in].max = 1.0000000000e+09
ds[traffic_in].last_ds = "1820875728"
ds[traffic_in].value = 6.9907626667e+04
ds[traffic_in].unknown_sec = 0
ds[traffic_out].index = 1
ds[traffic_out].type = "COUNTER"
ds[traffic_out].minimal_heartbeat = 600
ds[traffic_out].min = 0.0000000000e+00
ds[traffic_out].max = 1.0000000000e+09
ds[traffic_out].last_ds = "565866015"
ds[traffic_out].value = 7.6400040000e+04
ds[traffic_out].unknown_sec = 0
rra[0].cf = "AVERAGE"
rra[0].rows = 600
rra[0].cur_row = 383
rra[0].pdp_per_row = 1
rra[0].xff = 5.0000000000e-01
rra[0].cdp_prep[0].value = NaN
rra[0].cdp_prep[0].unknown_datapoints = 0
rra[0].cdp_prep[1].value = NaN
rra[0].cdp_prep[1].unknown_datapoints = 0
rra[1].cf = "AVERAGE"
rra[1].rows = 700
rra[1].cur_row = 20
rra[1].pdp_per_row = 6
rra[1].xff = 5.0000000000e-01
rra[1].cdp_prep[0].value = 6.9953805778e+03
rra[1].cdp_prep[0].unknown_datapoints = 0
rra[1].cdp_prep[1].value = 8.4651470222e+03
rra[1].cdp_prep[1].unknown_datapoints = 0
rra[2].cf = "AVERAGE"
rra[2].rows = 775
rra[2].cur_row = 141
rra[2].pdp_per_row = 24
rra[2].xff = 5.0000000000e-01
rra[2].cdp_prep[0].value = 1.4862882489e+04
rra[2].cdp_prep[0].unknown_datapoints = 0
rra[2].cdp_prep[1].value = 1.8375155622e+04
rra[2].cdp_prep[1].unknown_datapoints = 0
rra[3].cf = "AVERAGE"
rra[3].rows = 797
rra[3].cur_row = 600
rra[3].pdp_per_row = 288
rra[3].xff = 5.0000000000e-01
rra[3].cdp_prep[0].value = 3.8060360706e+06
rra[3].cdp_prep[0].unknown_datapoints = 0
rra[3].cdp_prep[1].value = 9.4974872005e+05
rra[3].cdp_prep[1].unknown_datapoints = 0
rra[4].cf = "MAX"
rra[4].rows = 600
rra[4].cur_row = 462
rra[4].pdp_per_row = 1
rra[4].xff = 5.0000000000e-01
rra[4].cdp_prep[0].value = NaN
rra[4].cdp_prep[0].unknown_datapoints = 0
rra[4].cdp_prep[1].value = NaN
rra[4].cdp_prep[1].unknown_datapoints = 0
rra[5].cf = "MAX"
rra[5].rows = 700
rra[5].cur_row = 409
rra[5].pdp_per_row = 6
rra[5].xff = 5.0000000000e-01
rra[5].cdp_prep[0].value = 1.9602308222e+03
rra[5].cdp_prep[0].unknown_datapoints = 0
rra[5].cdp_prep[1].value = 2.1725981111e+03
rra[5].cdp_prep[1].unknown_datapoints = 0
rra[6].cf = "MAX"
rra[6].rows = 775
rra[6].cur_row = 159
rra[6].pdp_per_row = 24
rra[6].xff = 5.0000000000e-01
rra[6].cdp_prep[0].value = 1.9602308222e+03
rra[6].cdp_prep[0].unknown_datapoints = 0
rra[6].cdp_prep[1].value = 2.1725981111e+03
rra[6].cdp_prep[1].unknown_datapoints = 0
rra[7].cf = "MAX"
rra[7].rows = 797
rra[7].cur_row = 454
rra[7].pdp_per_row = 288
rra[7].xff = 5.0000000000e-01
rra[7].cdp_prep[0].value = 3.5679259636e+05
rra[7].cdp_prep[0].unknown_datapoints = 0
rra[7].cdp_prep[1].value = 2.0524881671e+04
rra[7].cdp_prep[1].unknown_datapoints = 0
and then, once you know the DS names:
rrdtool fetch rra/mydevice_traffic_in_523.rrd MAX or AVERAGE
I've seen that message before on WM when the data in the rrd file is old and has not been udpated for a few days.
Howie can bring more light here.
Cheers,
Sometimes you can do:
[root@myserver1 cacti]# rrdtool info rra/mydevice_traffic_in_523.rrd
filename = "rra/mydevice_traffic_in_523.rrd"
rrd_version = "0003"
step = 300
last_update = 1472676934
header_size = 2912
ds[traffic_in].index = 0
ds[traffic_in].type = "COUNTER"
ds[traffic_in].minimal_heartbeat = 600
ds[traffic_in].min = 0.0000000000e+00
ds[traffic_in].max = 1.0000000000e+09
ds[traffic_in].last_ds = "1820875728"
ds[traffic_in].value = 6.9907626667e+04
ds[traffic_in].unknown_sec = 0
ds[traffic_out].index = 1
ds[traffic_out].type = "COUNTER"
ds[traffic_out].minimal_heartbeat = 600
ds[traffic_out].min = 0.0000000000e+00
ds[traffic_out].max = 1.0000000000e+09
ds[traffic_out].last_ds = "565866015"
ds[traffic_out].value = 7.6400040000e+04
ds[traffic_out].unknown_sec = 0
rra[0].cf = "AVERAGE"
rra[0].rows = 600
rra[0].cur_row = 383
rra[0].pdp_per_row = 1
rra[0].xff = 5.0000000000e-01
rra[0].cdp_prep[0].value = NaN
rra[0].cdp_prep[0].unknown_datapoints = 0
rra[0].cdp_prep[1].value = NaN
rra[0].cdp_prep[1].unknown_datapoints = 0
rra[1].cf = "AVERAGE"
rra[1].rows = 700
rra[1].cur_row = 20
rra[1].pdp_per_row = 6
rra[1].xff = 5.0000000000e-01
rra[1].cdp_prep[0].value = 6.9953805778e+03
rra[1].cdp_prep[0].unknown_datapoints = 0
rra[1].cdp_prep[1].value = 8.4651470222e+03
rra[1].cdp_prep[1].unknown_datapoints = 0
rra[2].cf = "AVERAGE"
rra[2].rows = 775
rra[2].cur_row = 141
rra[2].pdp_per_row = 24
rra[2].xff = 5.0000000000e-01
rra[2].cdp_prep[0].value = 1.4862882489e+04
rra[2].cdp_prep[0].unknown_datapoints = 0
rra[2].cdp_prep[1].value = 1.8375155622e+04
rra[2].cdp_prep[1].unknown_datapoints = 0
rra[3].cf = "AVERAGE"
rra[3].rows = 797
rra[3].cur_row = 600
rra[3].pdp_per_row = 288
rra[3].xff = 5.0000000000e-01
rra[3].cdp_prep[0].value = 3.8060360706e+06
rra[3].cdp_prep[0].unknown_datapoints = 0
rra[3].cdp_prep[1].value = 9.4974872005e+05
rra[3].cdp_prep[1].unknown_datapoints = 0
rra[4].cf = "MAX"
rra[4].rows = 600
rra[4].cur_row = 462
rra[4].pdp_per_row = 1
rra[4].xff = 5.0000000000e-01
rra[4].cdp_prep[0].value = NaN
rra[4].cdp_prep[0].unknown_datapoints = 0
rra[4].cdp_prep[1].value = NaN
rra[4].cdp_prep[1].unknown_datapoints = 0
rra[5].cf = "MAX"
rra[5].rows = 700
rra[5].cur_row = 409
rra[5].pdp_per_row = 6
rra[5].xff = 5.0000000000e-01
rra[5].cdp_prep[0].value = 1.9602308222e+03
rra[5].cdp_prep[0].unknown_datapoints = 0
rra[5].cdp_prep[1].value = 2.1725981111e+03
rra[5].cdp_prep[1].unknown_datapoints = 0
rra[6].cf = "MAX"
rra[6].rows = 775
rra[6].cur_row = 159
rra[6].pdp_per_row = 24
rra[6].xff = 5.0000000000e-01
rra[6].cdp_prep[0].value = 1.9602308222e+03
rra[6].cdp_prep[0].unknown_datapoints = 0
rra[6].cdp_prep[1].value = 2.1725981111e+03
rra[6].cdp_prep[1].unknown_datapoints = 0
rra[7].cf = "MAX"
rra[7].rows = 797
rra[7].cur_row = 454
rra[7].pdp_per_row = 288
rra[7].xff = 5.0000000000e-01
rra[7].cdp_prep[0].value = 3.5679259636e+05
rra[7].cdp_prep[0].unknown_datapoints = 0
rra[7].cdp_prep[1].value = 2.0524881671e+04
rra[7].cdp_prep[1].unknown_datapoints = 0
and then, once you know the DS names:
rrdtool fetch rra/mydevice_traffic_in_523.rrd MAX or AVERAGE
I've seen that message before on WM when the data in the rrd file is old and has not been udpated for a few days.
Howie can bring more light here.
Cheers,
Cacti - 1.2.15
Poller Type - Spine
Weathermap 0.98a
Server Info - Linux 3.10.0 - Centos 7
Web Server - Apache/2.4.6 PHP 5.4.16
MySQL - 5.5 ;RRDTool - 1.4.8 ;SNMP - 5.7.2
Religion - Anti forum pets
Poller Type - Spine
Weathermap 0.98a
Server Info - Linux 3.10.0 - Centos 7
Web Server - Apache/2.4.6 PHP 5.4.16
MySQL - 5.5 ;RRDTool - 1.4.8 ;SNMP - 5.7.2
Religion - Anti forum pets
- Howie
- Cacti Guru User
- Posts: 5508
- Joined: Thu Sep 16, 2004 5:53 am
- Location: United Kingdom
- Contact:
Re: Config File had no Valid Data
If Weathermap doesn't see any data from the last few minutes (I think it is 15 minutes by default), then it will tell you there is no valid data. This is to stop you sitting in your NOC thinking everything is fine when actually the monitoring system stopped working 3 days ago
You can change the limit, if you have rrd files that are only updated every 30 minutes. Look in the TARGET reference section of the manual. But usually, if you get this, it's because data isn't being put into the rrd files - possibly because you are running out of time during a poll. In that case you should be looking at the cacti.log and addressing the Cacti polling performance issues: check for bad SNMP details, maybe increase the number of requests per query, maybe look at spine (or Boost).
Either that, or someone re-created the device with a new device ID and rrd files and didn't tell you, so you are still looking at the old file.
Finally, if you only get this when you are running the poller manually: Consider permissions problems. Make sure you run it as the same user that the cron job does.
You can change the limit, if you have rrd files that are only updated every 30 minutes. Look in the TARGET reference section of the manual. But usually, if you get this, it's because data isn't being put into the rrd files - possibly because you are running out of time during a poll. In that case you should be looking at the cacti.log and addressing the Cacti polling performance issues: check for bad SNMP details, maybe increase the number of requests per query, maybe look at spine (or Boost).
Either that, or someone re-created the device with a new device ID and rrd files and didn't tell you, so you are still looking at the old file.
Finally, if you only get this when you are running the poller manually: Consider permissions problems. Make sure you run it as the same user that the cron job does.
Weathermap 0.98a is out! & QuickTree 1.0. Superlinks is over there now (and built-in to Cacti 1.x).
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
Some Other Cacti tweaks, including strip-graphs, icons and snmp/netflow stuff.
(Let me know if you have UK DevOps or Network Ops opportunities, too!)
Re: Config File had no Valid Data
thanks for your reply.
after using your suggestions, the issue was that someone delete the graph and created a new one with new RRD.
I've changed that map, and everything is back to be cool.
thanks again.
can you please take a look on my new post, hope you can
http://forums.cacti.net/viewtopic.php?f=21&t=56335
after using your suggestions, the issue was that someone delete the graph and created a new one with new RRD.
I've changed that map, and everything is back to be cool.
thanks again.
can you please take a look on my new post, hope you can
http://forums.cacti.net/viewtopic.php?f=21&t=56335
Who is online
Users browsing this forum: No registered users and 1 guest