Hi,

I am not sure, but I think the recent security update broke my 
mod_perl/Apache coexistance.  I am not sure because it wasn't something 
I checked right after installing it.  Also, things are fine on my other 
OS X box which also got the update.

I have not recompiled anything.  What I have is what came with original 
installed and the latest updates.

The symtom:  Apache doesn't start.  No errors in the error_log, no real 
complaints on the command line (with apachectl start); just the warning 
about resolving the "fully qualified domain name"... which I know I can 
easily fix by setting it in the conf file (but that's besides the point 
here).

I traced it down to the AddModule mod_perl.c line.  Assuming all other 
mod_perl directives are commented out (PerlRequire, etc), commenting out 
the AddModule line lets Apache start up.  The only uncommented line in 
reference to mod_perl is LoadModule line.

What I find disturbing is that I don't see any errors about Apache not 
starting anywhere.  It looks just like it would if it successfully 
started, except no processes are running.

I had this working before.  I didn't use it for a week or two, and when 
I went to play with it again a few days ago, I discovered the problem.

Does anyone know of this being a common problem?  Does anyone know of 
anything I could/should try to resolve this problem.  I can do the whole 
recompile thing, but would like to try other options first, if possible.

-Alex

Reply via email to