|
|
| Author |
Message |
SeanLee
Joined: 29 Oct 2003 Posts: 44
|
Posted: Wed Oct 29, 2003 10:44 pm Post subject: Parse Error - #00CF00:Inbound ?? |
|
|
Hello,
I'm using the latest CVS version. I just installed and added my first device - a cisco 3500 catalyst switch. I added the graphs and everything properly, however the graphs show up as broken images, and the debug info under graph management states:
ERROR: can't parse '#00CF00:Inbound'
*update*
I just noticed that it gives that same error message for every polling host I add to it, no matter what kind of data I'm trying to pull.
Any help would be appreciated.
Thank You. |
|
| Back to top |
|
 |
raX Lead Developer
Joined: 13 Oct 2001 Posts: 2234 Location: Carlisle, PA
|
Posted: Sun Nov 02, 2003 10:51 pm Post subject: |
|
|
You are getting an error because RRDTool is expecting a data source for that particular graph item. I am not exactly sure why you are seeing this error, but then again I am not entirely confident that the CVS version of Cacti is really stable right now. 0.8.4 should be out really soon, so there are lots of changes being committed right now.
-Ian |
|
| Back to top |
|
 |
Guest
|
Posted: Mon Nov 03, 2003 11:33 am Post subject: |
|
|
I can confirm this behavior with 0.8.2, so, it's not necessarily something new in CVS
I've been trying to set everything up with Apache2 instead of IIS, and have gotten this far to get stuck on this too.
ERROR: can't parse '#FF0000:CPU Usage'
is my error, on checking graph items on anything i create |
|
| Back to top |
|
 |
Guest
|
Posted: Mon Nov 03, 2003 11:33 am Post subject: |
|
|
| actually, i meant 0.8.3a not .2 |
|
| Back to top |
|
 |
SeanLee
Joined: 29 Oct 2003 Posts: 44
|
Posted: Mon Nov 03, 2003 2:59 pm Post subject: |
|
|
OK I understand now why this happens. Rax, like you suggested, it's an issue resulting from no data being collected. For example, I can't get CPU stats to work with windows 2000 server. As a result, I may get a parse error of some sort, since there is no data to parse through. This also occurs in 0.8.3a (i switched back to release version). I think it's more of an issue with setting up snmp properly and/or host template compatibility.
Thanks,
Sean |
|
| Back to top |
|
 |
|