perfparse draws graphs, but no data plotted?

[John Christian]

Hi gurus,

On a new perfparse setup, it seems to be ALMOST working, but no data lines are
plotted on the performance graphs. The perfparse summary table lists the hosts,
services, last reading, and values. Click on a graph and perfparse generates a
graph image (.png) which includes the hostname, service name, and metric. BUT,
no data lines are drawn on the graph.

I've waited a couple of days for data to be collected.
Same behavior with different hosts and services.
Same behavior when adjusting the scale, size, and time periods.

Nagios 2.0b4  (./configure  --with-command-group=nobody --enable-embedded-perl
--with-perlcache --with-default-perfdata)
Perfparse v0.105.6
Solaris 9
mysql-max-4.1.14-sun-solaris2.9-sparc-64bit.pkg (from Sunfreeware)

I have confirmed the Nagios "Process Info" link shows "Performance Data Being
Processed? Yes"
I have confirmed performance data is being provided by the plugins.
I have confirmed performance data is being stored in the database. (I don't
know if it's all the right data in the right places, but the db is being
populated with values that look reasonable to me.)

My Nagios Status Map is drawn correctly so I assume(?) my gd-2.0.33, Freetype
2, zlib, jpeg, and libpng graphic libraries are installed properly.

TIA for any direct solutions or hints on where to looks next!
-John



	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null