what about apache -f httpd.conf? that is telling apache which conf file to use does that work?then maybe you could reinstall the service using apache -k -f httpd.conf or something
Oliver Marshall wrote:
What a day ! A clients web designer decided to make some changes to the conf file on our windows 2003 based apache box. Nothing terrible there, but when it didn't do what was wanted, and apache failed to load, they decided to start pulling files from the apache folder. When that didn't work, they decided to reinstall apache. Finally, after a few hours poking, they decided to send a tacit email to me explaining that the server isn't working. Now, having uninstalled apache, removed all the apache folders and their files, removed all the reg entries from the registry, I have installedv2.That's where things started getting really odd. Apache seemed to serve up pages from the default site, ie the one in httpd.conf which is listed at the start of the httpd.conf file, before the virtualhost entries. It seemed to totally ignore any virtualhost entries in the httpd. Any changes there were never actioned by apache, despite the APACHE -S saying the syntax was correct. So, I tried 2.2. This had exactly the same issue. Nothing in thevirtualhost section was acted on.Stranger still, if I changed the default documentroot entry of the httpd.conf file and restarted apache, it had no effect. It's like there was another httpd.conf file in use somewhere but there wasn't any on theserver outside of the apache folder.Then things got weirder still. If I stopped the apache service itself (using the service mmc snap-in in windows) it refused to start again. It produced the standard popup explaining I should check the event log or contact the manufacturer of the service. The event log didn't show any apache based errors, and I cant see anything in any of the files in the /log folder of apache. Rebooting the server failed to get the apache service working. The only way to get the service up and working is to totally reinstall apache again, which works, but I'm still left with the non-working virtualhost entries and the seemingly unread httpd.conf file. ARRGHH!!!!! Now, im no apache guru, but I have setup enough apache 1.3 and v2 boxes running windows to know how to setup an apache install to support several virtualhosts and all the gubbins that go with it. However, im at a loss to explain what the h**l is happening now. Can anyone shed any light on these weird issues? Anyone know how I can even find out more info about what apache is or isn't reading from the httpd.conf file ? Olly --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
--------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|