Partly Solved: Upgraded CPU - Can't graph 2 new cores

Post support questions that directly relate to Linux/Unix operating systems.

Moderators: Developers, Moderators

Post Reply
CeeMan
Posts: 2
Joined: Thu Apr 30, 2009 2:38 pm

Partly Solved: Upgraded CPU - Can't graph 2 new cores

Post by CeeMan »

Gday,

I've been puzzling over this for the last day or so. I upgraded my home server about 2 days ago from a Core 2 Duo to a Quad.

SNMP - Get Processor Information can see all four cores.

When I create the graphs for the new cores - the next poller run returns a value. Every subsequent poller event thereafter returns nothing.

The data sources are there for the new cores and the rra files are on the filesystem. The name on the data source for the new cores is a little odd.

See the following from poller cache:

Code: Select all

CiscoLab - CPU Utilization   	 Script Server: /usr/share/cacti/scripts/ss_host_cpu.php ss_host_cpu 10.100.5.10 1 2:161:500:public:::MD5::DES: get usage 0
	RRD: /usr/share/cacti/rra/ciscolab_cpu_140.rrd
CiscoLab - CPU Utilization 	Script Server: /usr/share/cacti/scripts/ss_host_cpu.php ss_host_cpu 10.100.5.10 1 2:161:500:public:::MD5::DES: get usage 1
	RRD: /usr/share/cacti/rra/ciscolab_cpu_141.rrd
CiscoLab - CPU Utilization - CPU2 	Script Server: /usr/share/cacti/scripts/ss_host_cpu.php ss_host_cpu 10.100.5.10 1 2:161:500:public:::MD5::DES: get usage 2
	RRD: /usr/share/cacti/rra/ciscolab_cpu_200.rrd
CiscoLab - CPU Utilization - CPU3 	Script Server: /usr/share/cacti/scripts/ss_host_cpu.php ss_host_cpu 10.100.5.10 1 2:161:500:public:::MD5::DES: get usage 3
The original 2 cores aren't referred to as CPU0 and CPU1 whereas the new ones are referred to as CPU2 and CPU3 - strange. Not sure if this anomaly has something to do with what's going on.

Currently running Fedora Core 8 with:

Code: Select all

Cacti Version  	0.8.7b
Cacti OS 	unix
SNMP Version 	net-snmp 5.4.1 
RRDTool Version 	RRDTool 1.2.x  
It might be something obvious so happy to hear any pointers on what to check/try next.

Cheers.
CeeMan
Posts: 2
Joined: Thu Apr 30, 2009 2:38 pm

Post by CeeMan »

Okay so I did a little more digging and found a discrepancy in the new rrd files.

The old working CPU rrd files have the following:

Code: Select all

ds[cpu].minimal_heartbeat = 600
Whereas the new CPU rrd file have the following:

Code: Select all

ds[cpu].minimal_heartbeat = 120
Changing the value to 600 solves my earlier graphing issue.

I'd like to understand what is causing this value to be set at 120 and how I can set it back to a default of 600 - which seems to work for a 5 minute poller?

On a side note I read that for a dual core the ds[cpu_user].max value should be 200 in each of the rrd files. Does this mean that for a Quad core it should be 400?

Cheers.
User avatar
TheWitness
Developer
Posts: 17061
Joined: Tue May 14, 2002 5:08 pm
Location: MI, USA
Contact:

Post by TheWitness »

Your Data Template has been modified for 1 Minute Polling. This can happen when you import other "3rd party" templates when you don't know what you are importing first. So, you need to change the Data Template to be accurate for your installation.

If you have questions about RRDtool, please see http://rrdtool.org

TheWitness
True understanding begins only when we realize how little we truly understand...

Life is an adventure, let yours begin with Cacti!

Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages


For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Post Reply

Who is online

Users browsing this forum: No registered users and 9 guests