Apache configuration

RT Users
#1

Hi there,

we are currently running RT on several maschines, all with SuSE Linux 7.0. We
use the standard apache, adding only the lines in the httpd.conf that are
needed for RT.

Now for the great mistery :

We tried to start the webserver (with rcapache start) and … syntax error
…
After several tries we can start the webserver without problems.

Guess what has changed in the config file : Nothing

Can somebody explain this ?

#2

frederic.gobin@mindmatics.de wrote:

Hi there,

we are currently running RT on several maschines, all with SuSE Linux 7.0. We
use the standard apache, adding only the lines in the httpd.conf that are
needed for RT.

Now for the great mistery :

We tried to start the webserver (with rcapache start) and … syntax error
…
After several tries we can start the webserver without problems.

Guess what has changed in the config file : Nothing

Can somebody explain this ?

Unfortunately, You did not provide us with enough data. Normally, more
information is found in the apache error log. Maybe You can post the changed
part of Your configuration, and any error messages You can find.

By the way: It would be best if You updated Your MySQL and apache
installations to more current versions SuSE 7.0 is a bit old nowadays.

Regards,
Harald

Harald WagenerAn der Alster 4220099 Hamburg*http://www.fcb-wilkens.com

#3

Mysql was updated to the current version, apache not.
And there is nothing about the error in the error log …

I can give another information :

(I had to use “httpd -t” directly, because the apachectl-script is not there)
“httpd -t” gives an error
"Invalid command ‘PerlRequire’, perhaps mis-spelled or defined by a module not included in the server configuration"

I think it is because SuSE uses some conditionals in their config file.
(Something like

LoadModule perl_module /usr/lib/apache/libperl.so )On Fri, 10 May 2002 16:39:41 +0200, Harald Wagener wrote: > > frederic.gobin@mindmatics.de wrote: >> >> Hi there, >> >> we are currently running RT on several maschines, all with SuSE Linux 7.0. We >> use the standard apache, adding only the lines in the httpd.conf that are >> needed for RT. >> >> Now for the great mistery : >> >> We tried to start the webserver (with rcapache start) and ... syntax error >> ... >> After several tries we can start the webserver without problems. >> >> Guess what has changed in the config file : Nothing >> >> Can somebody explain this ? > > Unfortunately, You did not provide us with enough data. Normally, more > information is found in the apache error log. Maybe You can post the changed > part of Your configuration, and any error messages You can find. > > By the way: It would be best if You updated Your MySQL and apache > installations to more current versions SuSE 7.0 is a bit old nowadays. > > Regards, > Harald > > -- > Harald Wagener*An der Alster 42*20099 Hamburg*http://www.fcb-wilkens.com >
#4

I think it is because SuSE uses some conditionals in their config
file. (Something like

LoadModule perl_module /usr/lib/apache/libperl.so )

If this is the case, and you have libperl.so, start apache with -DPERL
to define it (so that the IfDefine PERL is true).

(darren)

What is truth, on the experiential level, but truthfulness?
– Raimundo Panikkar, “The Silence Of God”

#5

frederic.gobin@mindmatics.de wrote:

Mysql was updated to the current version, apache not.
And there is nothing about the error in the error log …

I can give another information :

(I had to use “httpd -t” directly, because the apachectl-script is not there)
“httpd -t” gives an error
"Invalid command ‘PerlRequire’, perhaps mis-spelled or defined by a module not included in the server configuration"

I think it is because SuSE uses some conditionals in their config file.
(Something like

LoadModule perl_module /usr/lib/apache/libperl.so )

IIRC, the SuSE 7.0 configuration for mod_perl is faulty. I don’t remember
anymore what it was or how to fix it, but at that time it was fairly difficult
to understand the chain of includes and defines in SuSE’s setup. We switched
to another distribution shortly afterwards (for reasons completely unrelated).

And, returning to RT from this topic, it’s always better to compile apache
with mod_perl built in to avoid these errors.

Regards,
Harald

Harald WagenerAn der Alster 4220099 Hamburg*http://www.fcb-wilkens.com