NagiosGrapher and XML::Simple

[Hugo van der Kooij]

On Thu, 2 Feb 2006, Christopher Gill wrote:

> I'm having some very frustrating trouble getting NagiosGrapher working.
> Since it doesn't have it sown mialing lists, figured I'd ask here. I've
> followed the install instructions provided, but when running the
> collection script, collect2.pl, I get a perl error back claiming it
> can't find the 'new' constructor on XML::Simple.
>
> Specific error:
> Can't locate object method "new" via package "XML::Simple" (perhaps you
> forgot to load "XML::Simple"?) at NagiosGrapher.pm line 367.
>
> This is on Redhat WS 4 with Perl 5.8.5-24. I installed XML::Simple from
> CPAN since Redhat doesn't have a package for it. It shows up correctly
> in the POD index, so I'm fairly sure I installed it correctly. Could
> this be a NagiosGrapher bug, or is my perl install just mucked up? Any
> thoughts would be greatly appreciated.

I got it working. WHile not on RHEL4 but FC4 there are packages out there
to do the job. Like atrpms (http://atrpms.net/dist/el4/) and other
archives.

If you insist on getting them fro CPAN I suggest you at least repackage
them to solve dependencies issue with the CPAN2RPM tool.

But that is in fact al besides Nagios.

Hugo.

-- 
	I hate duplicates. Just reply to the relevant mailinglist.
	hvdkooij at vanderkooij.org		http://hvdkooij.xs4all.nl/
		Don't meddle in the affairs of magicians,
		for they are subtle and quick to anger.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
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