> exactly the same symptoms for me. No errors, nothing... just wouldn't start. > But, here is where it gets truly mysterious. I would comment out the > mod_perl lines, and restart Apache... it would start. Then I would uncomment > the mod_perl lines, and restart, and it would restart... go figure.
Hrmmm... I'm pretty certain is was the security update that broke this for me. I checked my logs to see when mod_perl was last successfully started. It was about the same date that I updated. > actually, the AddModule and the LoadModule lines go hand-in-hand. Dunno why > this is so, but if you comment one, you have to comment the other also... > and vice versa. Afaik, that is what you are doing wrong. For me, this doesn't seem to be the case. The LoadModule line can exist without the AddModule line. Although I doubt it would work the other way around, as you can't load it if it hasn't been added. Apache will start if only the LoadModule line is commented out. > Anyway, all that said, yesterday I installed the security update, and since > then Apache with mod_perl is now working fine... Apache has been updated for > me from 1.3.22 to 1.3.23 (I think). Yes. I know that Apache was also updated. Although I didn't check it myself, several people made note of it on VersionTracker. > I know this doesn't help you much, but maybe it will give some insights. Thanks for the response. I think my next step will be to download the update and try to rerun it manually. Maybe the update had some minor, unreported failure when I ran it. Thanks again, -Alex
