At 10:15 -0500 02/12/2005, Geoffrey Young wrote:
>I suspect that the perl compiled with mod_perl was a different perl than the
>one you expected.
I did upgrade to Perl 5.8.5 sometime back and didn't rebuild mod_perl at the
time (although I also left 5.6.1 in place and swear I've restarted the Apac
> I suspect that the perl compiled with mod_perl was a different perl than the
> one you expected. I'll take a look and see if I can't make that error
> message a bit better (like spitting out @INC as well or something).
ok, this patch seems to be a bit better. if I remove Apache.pm from perl's
Vicki Brown wrote:
> At 15:38 -0500 02/11/2005, Perrin Harkins wrote:
>
>>Do you have a backup of your application code? I'd suggest building a
>>fresh apache/perl/mod_perl, verifying that it works, and then putting
>>your code in place. There are plenty of docs on perl.apache.org to help
>>yo
At 15:38 -0500 02/11/2005, Perrin Harkins wrote:
>Do you have a backup of your application code? I'd suggest building a
>fresh apache/perl/mod_perl, verifying that it works, and then putting
>your code in place. There are plenty of docs on perl.apache.org to help
>you with the install.
That's wh
On Thu, 2005-02-10 at 22:42 -0800, Vicki Brown wrote:
> Everything has been running just fine until today when we accidentally
> powered down the server (the hardware as well as the web server).
>
> Now all we get in the httpd error log is
> Apache.pm failed to load!
Ouch. Someone must have
