problems upgrading mod_perl

[Robert Krueger <kr...@signal7.de>]

Hi,

I'm currently upgrading an old installation (mod_perl 1.25, perl 5.005, apache 
1.3.12 -> mod_perl 1.27, perl 5.8.0, apache 1.3.27) and encounter strange 
problems.

when starting apache I get:

Can't locate loadable object for module Apache::Log

Now this usually indicates I forgot to specify the log api to be build during 
the build process. however, I built modperl using: 

perl Makefile.PL EVERYTHING=1;make install

in addition to that tests fail with the following output:

letting apache warm up...\c
Syntax error on line 3 of /usr/local/src/apache/mod_perl-1.27/t/conf/srm.conf:
Invalid command 'PerlTransHandler', perhaps mis-spelled or defined by a module 
not included in the server configuration
done

this looks as if mod_perl was not compiled into the apache server (which I had 
mod_perl build for me).

what else can I look for?

thanks in advance for any hints.

Robert

Re: problems upgrading mod_perl

[Robert Krueger <kr...@signal7.de>]

you're right. lousy posting of mine ;-). luckily I've managed to solve the 
problem by just trying to to it step by step again with freshly unpacked 
archives to document each step to respond to your posting with a little more 
detailed info. I must have messed it up the first time somehow.

thanks for your quick response and take care,

robert

>
> I wonder if you have built a DSO Apache but haven't the right
> directives to load the mod_perl module in the configuration.
> Can you give more detail on what and how you built?
>
> - What OS.
>
> - Where you put the sources - looks like /usr/local/src/apache/ which
>   might not be such a good idea.  Where's the Apache source itself?
>
> - The current working directory when you issued the commands.
>
> - What order you did things.
>
> - What userid(s) you used at each stage.
>
> - Things they ask for in SUPPORT like `perl -V`.
>
> If your new Perl installation is OK, if you follow the instructions
> in the Guide then you should be able to start again from scratch with
> Apache and mod_perl and have it running in ten minutes.  I prefer to
> use a makepl_args.mod_perl file in the mod_perl directory for all my
> configuration options, it makes everything so easy.  I also prefer to
> build static whenever possible, leaves out a chunk of complexity that
> I don't need.
>
> 73,
> Ged.

Re: problems upgrading mod_perl

[Ged Haywood <ge...@www2.jubileegroup.co.uk>]

Hi there,

On Sun, 16 Feb 2003, Robert Krueger wrote:

> I'm currently upgrading an old installation (mod_perl 1.25, perl 5.005, apache 
> 1.3.12 -> mod_perl 1.27, perl 5.8.0, apache 1.3.27) and
[snip]
> Can't locate loadable object for module Apache::Log
[snip]
> letting apache warm up...\c
> Syntax error on line 3 of /usr/local/src/apache/mod_perl-1.27/t/conf/srm.conf:
> Invalid command 'PerlTransHandler', perhaps mis-spelled or defined by a module 
> not included in the server configuration
[snip]
> looks as if mod_perl was not compiled into the apache server (which I had 
> mod_perl build for me).

I wonder if you have built a DSO Apache but haven't the right
directives to load the mod_perl module in the configuration.
Can you give more detail on what and how you built?

- What OS.

- Where you put the sources - looks like /usr/local/src/apache/ which
  might not be such a good idea.  Where's the Apache source itself?

- The current working directory when you issued the commands.

- What order you did things.

- What userid(s) you used at each stage.

- Things they ask for in SUPPORT like `perl -V`.

If your new Perl installation is OK, if you follow the instructions
in the Guide then you should be able to start again from scratch with
Apache and mod_perl and have it running in ten minutes.  I prefer to 
use a makepl_args.mod_perl file in the mod_perl directory for all my
configuration options, it makes everything so easy.  I also prefer to
build static whenever possible, leaves out a chunk of complexity that
I don't need.

73,
Ged.