Restart function in the apache service monitor

doesn't work

[deep9]

Hello!

I'm running Apache v2.2.6 SSL. When I hit the restart in the apache service monitor gui it successfully restarts. But my webpage gets inaccessible. So instead I have to stop the server first then start it, in the service monitor gui. How come my webpage becomes inaccessible with the restart function?

//deep9

[coopster]

Hello deep9 and welcome to WebmasterWorld.

Assuming you are referring to a Windows installation here ... it sounds like a funky binary/executable or something. Try a fresh uninstall/reinstall to see if your issue clears.

[deep9]

Already tried. No difference.

[gergoe]

See if your Apache is still running after the restart (in the Services panel within the Control Panel). If it is not running, probably the service stopped because of an error condition. If that's the case, you should find some log entries in the error log (/log folder in the Apache installation directory).

I don't know how the Apache Monitor works, but try issuing the bin/apache2.exe -k restart command from the command line while the server is running, this command tells the Apache to restart the child processes without actually restarting the server, might give you better results.

And at last, take a look in the Eventlog (same place as the Services in the Control Panel), in the Application category you might find some entries related to the Apache service.

[deep9]

After restart from the gui the service is active, but page is inaccessible. With the cmd httpd.exe -k restart its the same thing. And there is no error(s) in the event log, nor the logfile.

[gergoe]

Well, without any trace of error it is hardly possible to find out what goes wrong... You would need to find out why it is down, or how it is down. The second one is relatively easy, make a telnet connection to the pc with the Apache running on it through port 80, and send the

GET / HTTP/1.0

line to it, terminated by two linefeed characters (twice enter).

If you can't make the connection at all, it means the child process can not be altered by the main process (the first one is stopped, but the new one can not be started), in that case it is related to the operating system, more likely the security settings (try running the service under different credentials). Although you would need to see some warnings/errors in your Apache log in this case - if that's enabled after all [httpd.apache.org].

If you could make the connection, but you get no reply, it probably means an another software (firewall, PWS, skype, ...) has taken the http port, and the Apache can not bind itself to that ip address and port anymore. In this case you can use the

netstat -a -b -n

command to find out which process is listening on port 80.

And at last, if you get something back, that should give a clue on what's going on, post it back this forum, and let's hope someone can tell what's wrong.