View previous topic :: View next topic |
Author |
Message |
forceflow2 Guru
Joined: 16 Apr 2003 Posts: 464 Location: South Carolina
|
Posted: Mon Sep 12, 2005 11:33 pm Post subject: Apache and modules |
|
|
I'm trying to get Apache running with mod_perl and mod_speling. I am using the 2.1.7-beta as it supports LFS, which I need. LFS works flawlessly at the moment, the only issue is I cannot get mod_perl, nor mod_speling to function. I used the SVN mod_perl, 2.0.2-dev, which compiles and installs just fine, but segfaults whenever anybody accesses a perl script.
Code: | [Mon Sep 12 14:40:04 2005] [notice] Apache/2.1.7 (Unix) mod_perl/2.0.2-dev Perl/v5.8.7 configured -- resuming normal operations
[Mon Sep 12 14:41:10 2005] [notice] child pid 27911 exit signal Segmentation fault (11)
[Mon Sep 12 14:44:02 2005] [notice] child pid 27912 exit signal Segmentation fault (11)
[Mon Sep 12 14:44:26 2005] [notice] child pid 27913 exit signal Segmentation fault (11)
|
I read that it was an issue with LFS incompatibilities but perl, libperl, and mod_perl are all compiled with LFS support, so I don't think that's the issue. mod_speling was enabled when I setup the configure script, but adding a CheckSpelling On to my httpd.conf it refuses to start as it cannot find the module
Code: |
Syntax error on line 416 of /usr/local/apache2/conf/httpd.conf:
Invalid command 'CheckSpelling', perhaps misspelled or defined by a module not included in the server configuration |
Any help or ideas are greatly appreciated. _________________ That rank under my username doesn't mean I know everything, it just means I ask a lot of questions. |
|
Back to top |
|
|
forceflow2 Guru
Joined: 16 Apr 2003 Posts: 464 Location: South Carolina
|
Posted: Tue Sep 13, 2005 1:31 am Post subject: |
|
|
Ok, got mod_perl functioning correctly, but mod_speling still doesn't want to work. _________________ That rank under my username doesn't mean I know everything, it just means I ask a lot of questions. |
|
Back to top |
|
|
Herring42 Guru
Joined: 10 Mar 2004 Posts: 373 Location: Buckinghamshire
|
Posted: Fri Oct 21, 2005 8:54 am Post subject: |
|
|
Most apache errors of this type are the result of not recompiling extra apache modules (e.g. mod_perl, mod_php etc) after an upgrade of apache.
Have a check of the modules.d directory, and re emerge everything there.
In your case, did you recompile perl after compiling apache? _________________ "The problem with quotes on the internet is that it is difficult
to determine whether or not they are genuine." -- Abraham Lincoln |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|