Originally posted by unSpawn
Seems there is already something listening on the HTTPS port when it tries to restart. Find out what it is.
Next to that check if there's any app that tries to restart httpd if it fails.
I am about 99% sure that it is Apache that has port 443 bound up. What is was doing last time I SSH'ed into it when it was crashed, there were apache processes still running (many of them, no childs, only parent processes). They would not die in the regular way however. Lets say that one of the processes had a process ID of 873 just for example. If you do "kill -HUP 873", it has no effect, if you do "kill 873", that has no effect either. If you do "killall httpd" or "killall apache", that also has no effect as it comes back saying it can't find any. However, if I do "kill -KILL 873", that finally kills it. I am not sure what the -KILL does, I just found it on the internet somewhere. After all apache processes were finally killed, then apache came back up within 1 minute.
Now, to the question about what apps try to restart apache if it is down, there are 2 of them on the server. The first one is the DirectAdmin Web Hosting Control Panel Software, and the other is a system monitoring program (I can't remember the name). Both of these monitor services on the machine and attempt to restart them when they find one down. But, since apache is still running in a semi-crashed state, it can not be restarted because the crashed form of apache is still bound to the ports.
I had not thought of some other machine sending some kind of requests to crash it, I will check the logs.