Howdy,
I’m running the community edition on Ubuntu. All the graphs work except the traffic graphs (bits). I get the standard “Draw error”.
I don’t get any errors polling (other than a MIB not being supported for engineID).
The devices are all Mikrotik routers.
I put an &debug=1 on the traffic graph URL and discovered an error all the way at the bottom:
“command returned 1 (ERROR: Unused Arguments “” in command : AREA:inbits0#B6D14B:ether1-wan Rx: )"
The full text is here: http://pastebin.ubuntu.com/14490188/
It’s unclear to me if this is actually causing this one graph (on all my systems) to fail but so far there is a trend from spot checking.
Any thoughts on how to debug this further?
Thanks,
Joey
Hi,
This is caused by a bug/feature introduced in later rrdtool revisions which change the behaviour if the rrdtool parser.
A workaround has been in subscription edition for quite a while and will be in the next CE which should be released shortly.
A quick fix is to use an older rrdtool package. IIRC you need 1.4.7 or older.
Adam.
Sent from BlueMail
On 15 Jan 2016, 02:05, at 02:05, Joey Stanford joey@stan4d.net wrote:
Howdy,
I’m running the community edition on Ubuntu. All the graphs work except the traffic graphs (bits). I get the standard “Draw error”.
I don’t get any errors polling (other than a MIB not being supported for engineID).
The devices are all Mikrotik routers.
I put an &debug=1 on the traffic graph URL and discovered an error all the way at the bottom:
“command returned 1 (ERROR: Unused Arguments “” in command : AREA:inbits0#B6D14B:ether1-wan Rx: )"
The full text is here: http://pastebin.ubuntu.com/14490188/
It’s unclear to me if this is actually causing this one graph (on all my systems) to fail but so far there is a trend from spot checking.
Any thoughts on how to debug this further?
Thanks,
Joey
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
On Jan 14, 2016, at 20:09 , Adam Armstrong adama@memetic.org wrote:
Hi,
This is caused by a bug/feature introduced in later rrdtool revisions which change the behaviour if the rrdtool parser.
A workaround has been in subscription edition for quite a while and will be in the next CE which should be released shortly.
A quick fix is to use an older rrdtool package. IIRC you need 1.4.7 or older.
Adam.
Groovy thanks! I can wait until the next release.
Out of interest… I have this setup along side smokeping, cacti, and network weathermap to monitor our (all volunteer, non-profit) emergency communications network that spans mountain tops from Cheyenne, Wyoming, all through Colorado, and down into Sandia Crest, New Mexico. I’ve been looking for an easy way to process the core network SNMP traps. We used to use The Dude since we’re 100% Mikrotik but since that software died (and is in the process of being resurrected) I’ve been trying a bunch of different things. Aside from this graphing error, the only other three issues I had were a) geolocation didn’t work until I change the API to Google (very weird…wouldn’t take full addresses or post codes), b) there is no documentation about smokeping integration on the main site (minus a small page with two tips) but I found a great blog post how to get it setup, and c) apache keeps throwing zombies and I can’t seem to pinpoint it yet.
Anyway, thanks for coding the system up! It’s already telling us that it’s gets to -7C in one of our installations.
participants (2)
-
Adam Armstrong -
Joey Stanford