Cactid doesn't work and counter reset problem.

Post general support questions here that do not specifically fall into the Linux or Windows categories.

Moderators: Developers, Moderators

Post Reply
Natti
Posts: 1
Joined: Wed Dec 15, 2004 6:38 am

Cactid doesn't work and counter reset problem.

Post by Natti »

Hi,

I'm having 2 kinds of problems.

1) Cactid doesn't work. I've downloaded the source, compiled and installed, where it ended it /usr/local/cactid/bin/cactid, and followed the install procedure.
However, the graphs stop working, and my log file says:
12/15/2004 11:40:57 AM - POLLER: Poller[0] Maximum runtime of 296 seconds exceeded. Exiting.
If I run the poller.php script from command line, it just hangs.
I'm running FreeBSD 4.8 btw.

*edit*
Nevermind problem #1, I sometimes have a small problem reading through the information I have, skipping out lines etc. I didn't copy the cactid.conf to the right location. It seems to work now after I copied to /usr/local/cactid/. So problem #2 is the only thing that's bothering me at the moment.

2) Counter reset. While polling some of my switches that have some traffic going through them, the graphs weren't showing the right load. So I generated a constant 490-510 Mbit flow through one switch and verified on the switch that the actual traffic was around 500Mbits.
The graph however only showed that I was using 60-110Mbit of traffic. Then I noticed that the counter for the total bytes in and bytes out on the switch was resetting itself after a few gigabytes of data. Which must explain why the graph was always wrong.
I've tried to lower the crontab time, so instead of polling at a 5 minute interval it polls at a 1 minute interval, the graph is closer but the counter may reset atleast 1 time. And I'm afraid that when I add all my network equipment into cacti then 1 minute polling time won't be enough for cmd.php (which leads me back to problem #1)
My question, I can't be the only one who's having this problem, is someone else here that has the same kind of problem, and solved it perhaps?

The switch I tested this on is a Cisco 3550-12G.

- Natti
duckhead
Cacti User
Posts: 59
Joined: Wed Oct 20, 2004 7:41 pm

Post by duckhead »

Let's do the obvious first. SNMP 32 bit counters can only get you to about 115Mbps, and do interesting things if there's more traffic then that.

First, are you using SNMPv2? If not, it won't work, because there's no support for 64-bit counters.

Secondly, are you using 64 bit counters in your graph definition? If not, that's the same as using SNMPv1, it won't work correctly.

I'm not having any trouble with my 3550's.
Guest

Post by Guest »

Hm, I was/am using SNMPv1, default setting on cacti, I tried to change to v2, but had some troubles, but I think that was because of misconfiguration elsewhere. I'm giving SNMPv2 a try now, and it seems to work.
The graph template I was using was "In/Out bits with total bandwith", so again, 32bit.
So to do the trick we're talking about changing the "ifInOctets" and "ifOutOctets" into "ifHCInOctets" and "ifHCOutOctets"(64Bit), and using SNMPv2 ?

The counter that I was referring to that was resetting is if you do the "show interface" command on the switch, you have two lines:
"1246606618 packets input, 1606192182 bytes, 0 no buffer"
"911625468 packets output, 1838110862 bytes, 0 underruns"

The 'bytes' counter resets between 4-5 gbytes, I thought that'd maybe have affect/effect(sp?) on the graph.
Post Reply

Who is online

Users browsing this forum: No registered users and 11 guests