[smokeping-users] Smokeping 500 Internal Server Error or a Blank page (fwd)

[G.W. Haywood]

Hi there,

On Fri, 22 Aug 2008, Joyce Gutierrez wrote:

> thanks again for replying,

Don't forget to CC the Smokeping list.  That's what it's for. :)

> In my case I have the path, /usr/local/smokeping/lib, I checked
> Smokeping.pm and it was there, I also checked if the other paths
> like for the RRD tool are right and I found out that they were all
> pointing at the right paths/folders. Now when i check the apache
> error log, I do not see any errors related to Smokeping

So you changed something?

> could there be any other reason for the error 500 Internal Server
> Error/Blank Page ?

There can be an infinite number of reasons.  But they will always be
mentioned in the Apache error log, so as I said in my first message to
you that's where you need to look because that's where the answer is.

--

73,
Ged.

> ----- Original Message ----
> From: G.W. Haywood <ged at jubileegroup.co.uk>
> To: Joyce Gutierrez <joycee729 at yahoo.com>
> Sent: Friday, August 22, 2008 10:44:43 PM
> Subject: Re: [smokeping-users] Smokeping 500 Internal Server Error or a Blank page
>
> Hi there,
>
> On Fri, 22 Aug 2008, Joyce Gutierrez wrote:
>
> > smokeping.cgi: Can't locate Smokeping.pm in @INC (@INC contains: ...
>
> There is a Perl array called @INC which contains a list of paths.
>
> The paths are where Perl searches for any needed Perl modules like
> Smokeping.pm.   Smokeping.pm is not on one of those paths.  A while
> ago you probably edited /usr/sbin/smokeping (or wherever you keep
> your smokeping), early in the file, to add a statement like this:
>
> use lib qw(/usr/share/perl5/smokeping);
>
> (This was taken from a copy of /usr/sbin/smokeping on one of my
> machines, but the path you used may have been different.)  This
> adds to @INC the path to your Smokeping.pm, without which Perl
> will not be able to find it.  It's in the documentation.
>
> Something has changed.  Perhaps you upgraded something.  Whatever
> changed doesn't really matter, you just need to make sure that the
> place where Smokeping.pm lives is mentioned in that statement.