Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

On my dev environment I upgraded php with an msi, and my apache wouldn't load anymoreerror message.

Where can I find information about the reason it failed? I have the error logs for each virtual server, but no information there either, and I am not sure that I actually expect it to be found there.

share|improve this question
    
This question has been closed ass off topic on SO and SF. Let's see what happens here –  shealtiel Jan 17 '13 at 9:37

1 Answer 1

up vote 1 down vote accepted

Starting Apache says

If Apache suffers a fatal problem during startup, it will write a message describing the problem either to the console or to the ErrorLog before exiting.

I would try Running Apache as a console application expecting to see console error messages saying that it can't parse the config file (and hence doesn't know where it's errorlogs are to be written) - it should give some reasons that will be helpful

I'd also try httpd.exe -k configtest in a command prompt window (I've no idea if this will work)

You may need to tell Apache where the main config file is by using the -f option e.g. -f "c:\my server files\anotherconfig.conf"

share|improve this answer
    
I don't seem to have httpd.exe anywhere in my apache folder –  shealtiel Jan 17 '13 at 9:51
    
At the meanwhile I found the reason by trial and error. But will follow your guidence later, to learn for future. Thank you –  shealtiel Jan 17 '13 at 9:52

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.