Choppy graph

[LinuxGold]

I am running Ubuntu 9.04-server and Cacti 0.8.7b (no ubuntu repo for 0.8.7e),

I set up to monitor 4 servers, 3 servers was monitoring correctly but not 1 of them. It showed choppy graph as indicated on attached image. I checked that server and it appeared to be running correctly without any network problem. What is the solution to this problem?

choppy image appears in all aspects: Network status, CPU usage, etc, etc

[gandalf]

Most likely the double poller issue mentioned at 2nd link of my sig: Check your crontabs
Reinhard

[LinuxGold]

Most likely the double poller issue mentioned at 2nd link of my sig: Check your crontabs
Reinhard

vi /etc/cron.d/cacti

Code: Select all

MAILTO=root
*/5 * * * * www-data php /usr/share/cacti/site/poller.php >/dev/null 2>/var/log/cacti/poller-error.log

crontab -e -u cactiuser

Code: Select all

crontab: user `cactiuser' unknown

[gandalf]

And /etc/crontab?
Reinhard

[LinuxGold]

shamm@motubuntu01:/etc$ grep poller cron*/*

Code: Select all

cron.d/cacti:*/5 * * * * www-data php /usr/share/cacti/site/poller.php >/dev/null 2>/var/log/cacti/poller-error.log

[gandalf]

Are those choppy graphs from windows boxes? If yes, increase their SNMP timeout. SNMP is quite slow on those boxes
Reinhard

[LinuxGold]

Yes, it is a windows box, snmp timeout increased, now testing...

[LinuxGold]

Increased from 500 to 1500 in SNMP timeout -- now flatlined.

Code: Select all

08/03/2009 09:15:22 AM - SYSTEM STATS: Time:20.2517 Method:cmd.php Processes:1 Threads:N/A Hosts:13 HostsPerProcess:13 DataSources:301 RRDsProcessed:160
08/03/2009 09:20:18 AM - CMDPHP: Poller[0] Host[3] DS[32] WARNING: Result from SNMP not valid.  Partial Result: 
08/03/2009 09:20:18 AM - CMDPHP: Poller[0] Host[3] DS[32] WARNING: Result from SNMP not valid.  Partial Result: 
08/03/2009 09:20:21 AM - SYSTEM STATS: Time:20.2631 Method:cmd.php Processes:1 Threads:N/A Hosts:13 HostsPerProcess:13 DataSources:301 RRDsProcessed:174
08/03/2009 09:25:22 AM - SYSTEM STATS: Time:20.2667 Method:cmd.php Processes:1 Threads:N/A Hosts:13 HostsPerProcess:13 DataSources:301 RRDsProcessed:160
08/03/2009 09:30:19 AM - CMDPHP: Poller[0] Host[3] DS[32] WARNING: Result from SNMP not valid.  Partial Result: 
08/03/2009 09:30:19 AM - CMDPHP: Poller[0] Host[3] DS[32] WARNING: Result from SNMP not valid.  Partial Result: 
08/03/2009 09:30:22 AM - SYSTEM STATS: Time:20.2437 Method:cmd.php Processes:1 Threads:N/A Hosts:13 HostsPerProcess:13 DataSources:301 RRDsProcessed:174
08/03/2009 09:35:21 AM - SYSTEM STATS: Time:20.2592 Method:cmd.php Processes:1 Threads:N/A Hosts:13 HostsPerProcess:13 DataSources:301 RRDsProcessed:160
08/03/2009 09:40:03 AM - CMDPHP: Poller[0] Host[3] ERROR: HOST EVENT: Host is DOWN Message: UDP ping Timed out
08/03/2009 09:40:06 AM - SYSTEM STATS: Time:4.2223 Method:cmd.php Processes:1 Threads:N/A Hosts:13 HostsPerProcess:13 DataSources:301 RRDsProcessed:110
08/03/2009 09:45:22 AM - SYSTEM STATS: Time:21.2481 Method:cmd.php Processes:1 Threads:N/A Hosts:13 HostsPerProcess:13 DataSources:301 RRDsProcessed:160
08/03/2009 09:50:18 AM - CMDPHP: Poller[0] Host[3] DS[32] WARNING: Result from SNMP not valid.  Partial Result: 
08/03/2009 09:50:18 AM - CMDPHP: Poller[0] Host[3] DS[32] WARNING: Result from SNMP not valid.  Partial Result: 
08/03/2009 09:50:21 AM - SYSTEM STATS: Time:20.2616 Method:cmd.php Processes:1 Threads:N/A Hosts:13 HostsPerProcess:13 DataSources:301 RRDsProcessed:174
08/03/2009 09:55:22 AM - SYSTEM STATS: Time:20.2512 Method:cmd.php Processes:1 Threads:N/A Hosts:13 HostsPerProcess:13 DataSources:301 RRDsProcessed:160
08/03/2009 10:00:18 AM - CMDPHP: Poller[0] Host[3] DS[32] WARNING: Result from SNMP not valid.  Partial Result: 
08/03/2009 10:00:18 AM - CMDPHP: Poller[0] Host[3] DS[32] WARNING: Result from SNMP not valid.  Partial Result: 
08/03/2009 10:00:22 AM - SYSTEM STATS: Time:21.2675 Method:cmd.php Processes:1 Threads:N/A Hosts:13 HostsPerProcess:13 DataSources:301 RRDsProcessed:174

The secondary server (Host[3] is up and running),

[BSOD2600]

manual snmpwalk still working? Try restarting the windows snmp agent and/or reinstalling it. It's picky.