Ad blocker detected: Our website is made possible by displaying online advertisements to our visitors. Please consider supporting us by disabling your ad blocker on our website.
Hi, i'm having a few problems with Cacti. I've installed RRDTool, mysql server, and cacti all via yum on a fedora core 2 box.
First, I'm having broken graphs, and I've applied all of the listed patches. The attached images should be more descriptive. BS1 is the host that cacti is running on. I have a dell powerconnect 3024 (Premier Switch2) that similarily seems to be leaving only slight broken lines on the graph.
Also, I'm having problems with the poller reaching its maximum runtime. Here's a quote from the logfile:
It seems that the runtime is exceeded only by my switches (Dell PowerConnect 3024/3324. Is this possibly a setting I should be changing on the switch (if possible), or changing the timeout listed in the device profile in cacti? I'm using cmd.php and I noticed the timeout within the file is set to 296 seconds, but I'm hesitant to altering that. Any suggestions?
Very high load, what going on on your box? You might want to run "top".
TheWitness
At that time it was running a backup. You can tell when the backup starts, but I'm still seeing quite a few gaps in the graphs for not only the local machine but also other hosts after applying the necessary patches.
I've attached 2 images, the first graph is a cacti graph of the traffic the interfaces are seeing on a different host. The 2nd is the cacti graph of the local host, there seems to be a gap in the processes listed.
Attachments
broken load graphs from the localhost
cacti3.jpg (115.15 KiB) Viewed 6978 times
alternate snmp enabled host with massive gaps in the interface reporting
[size=117][i][b]Tony Roman[/b][/i][/size]
[size=84][i]Experience is what causes a person to make new mistakes instead of old ones.[/i][/size]
[size=84][i]There are only 3 way to complete a project: Good, Fast or Cheap, pick two.[/i][/size]
[size=84][i]With age comes wisdom, what you choose to do with it determines whether or not you are wise.[/i][/size]
11/02/2005 10:50:02 AM - CMDPHP: Poller[0] ASSERT: '1921375800<1921375800' failed. Recaching host 'sw2.hq.premtech.com', data query #1
11/02/2005 10:50:16 AM - SYSTEM STATS: Time:15.5908 Method:cmd.php Processes:1 Threads:N/A Hosts:23 HostsPerProcess:23 DataSources:475 RRDsProcessed:492
11/02/2005 10:50:16 AM - SYSTEM STATS: Time:15.5409 Method:cmd.php Processes:1 Threads:N/A Hosts:23 HostsPerProcess:23 DataSources:475 RRDsProcessed:426
11/02/2005 10:50:17 AM - POLLER: Poller[0] Host[3] WARNING: Recache Event Detected for Host
11/02/2005 10:50:17 AM - POLLER: Poller[0] Host[3] WARNING: Recache Event Detected for Host
11/02/2005 10:50:37 AM - RECACHE STATS: RecacheTime:20.3294 HostsRecached:1
11/02/2005 10:50:37 AM - RECACHE STATS: RecacheTime:20.6919 HostsRecached:1
11/02/2005 10:55:07 AM - CMDPHP: Poller[0] Host[3] DS[34] WARNING: Result from SNMP not valid. Partial Result:
11/02/2005 10:55:07 AM - CMDPHP: Poller[0] ASSERT: '1921405600<' failed. Recaching host 'sw2.hq.premtech.com', data query #1
11/02/2005 10:59:58 AM - POLLER: Poller[0] Maximum runtime of 296 seconds exceeded. Exiting.
11/02/2005 10:59:58 AM - POLLER: Poller[0] Maximum runtime of 296 seconds exceeded. Exiting.
11/02/2005 11:00:27 AM - SYSTEM STATS: Time:25.9552 Method:cmd.php Processes:1 Threads:N/A Hosts:23 HostsPerProcess:23 DataSources:475 RRDsProcessed:308
11/02/2005 11:00:27 AM - SYSTEM STATS: Time:26.1311 Method:cmd.php Processes:1 Threads:N/A Hosts:23 HostsPerProcess:23 DataSources:475 RRDsProcessed:432
11/02/2005 11:00:28 AM - POLLER: Poller[0] Host[3] WARNING: Recache Event Detected for Host
11/02/2005 11:00:28 AM - POLLER: Poller[0] Host[3] WARNING: Recache Event Detected for Host
11/02/2005 11:00:58 AM - RECACHE STATS: RecacheTime:30.2733 HostsRecached:1
11/02/2005 11:00:59 AM - RECACHE STATS: RecacheTime:30.6249 HostsRecached:1
11/02/2005 11:05:02 AM - CMDPHP: Poller[0] ASSERT: '1921464800<1921464800' failed. Recaching host 'sw2.hq.premtech.com', data query #1
11/02/2005 11:09:58 AM - POLLER: Poller[0] Maximum runtime of 296 seconds exceeded. Exiting.
11/02/2005 11:09:58 AM - POLLER: Poller[0] Maximum runtime of 296 seconds exceeded. Exiting.
Is there possibly a setting I should change in the poller.php file to increase the runtime timeout setting, and would it help if I did? Are there any other suggestions on what I should be trying to fix this problem?
I'm seeing the same behaviour on a new cacti system I just installed here. The cricket graphs are fine, the cacti graphs for the same resources have gaps in them. I'm seeing this both on my WAN router and my air handlers.
Looking in the log, I see similar erorrs to other users:
11/09/2005 02:39:58 PM - POLLER: Poller[0] Maximum runtime of 296 seconds exceeded. Exiting.
Is there any way to either run multiple concurrent pollers or to thread it? With cricket I ended up splitting my data sets, as it couldn't complete a pool of all the devices in one 5 minute cycle.
- Dan
[i] "Step up to red alert!" "Are you sure, sir?[/i]
[i] It means changing the bulb in the sign..." - Red Dwarf[/i]
For that low amount of data sources that Pizop reported, there's no obviuos reason that polling should take 300 secs. I'm wondering about the logs entries appearing as twins. This looks like two polers runninmg concurrently. This is knows as a reason for being slow and having gaps in graphs. To check this out, please look at your crontab in more detail, e.g.
/etc/crontab
/etc/cron.d/cacti
crontab -e (for user root)
crontab -e -u cactiuser (for user cactiuser)
This is likely to appear when installing from rpm (puts cronjob /etc/cron.d/cacti) and manually inserting poller cmd at a crontab of your choice.
Reinhard