Closed jpobeda closed 6 years ago
Did you upgrade Weathermap also? From what previous version, if you did? And from which Cacti version?
Cacti 1.x now treats any php error as a reason to kill the plugin that produced it. So if you came from 0.8.8 then it's possible the error existed before but was ignored.
Looks like the immediate cause is that the host is not responding to a request. But it looks like there is some initialisation code missing there, which causes the actual error.
It was a git from last week running on 1.1.7 so it's definitely a 1.x version
I've been working around so many issues with Cacti 1.x that maybe it's been there from the very beginning.
This time this is not killing nwm, maybe because it only happened twice. I noticed Cacti does that when it happens very often.
It's not like a huge issue but maybe it points out to something. I'm pretty sure that at that time those tunnels were down so the OID didn't exist when nwm tried to poll them.
Would it be a different error for non-existent OID?
Yes - definitely something to fix :-)
I'm not sure if it would be different - it looks like it's just checking if it got a valid result, so I would guess a non-existent OID would do it too. But.. it should just complain that it got invalid data, like the rrd plugin would. The actual issue is that there should be something to set the error count to zero for each host the first time it is seen, and that's missing. Same issue in all 3 snmp ds plugins.
The idea is supposed to be that if more than a certain number of requests for a host fail, it stops trying for that run. I had a situation with a big chassis switch, where if the switch was down, 200+ SNMP requests would slowly timeout and fail, and make the poller overrun.
Oh yeah! That's definitely something to be worry about hehehe. Don't forget that import option for snmpv2 pls <3
Hi Howie,
I upgraded Cacti to 1.1.9 yesterday and Today I found this on cacti log. Only these 2 lines..
NODE CONFIGS ARE
The only clue I can give you is the attached screenshot at that time. So It may be related to non-existent OID?