I have a number of CentOS 5.4 servers running Apache 2.2.3. Nothing has changed on them recently except that I installed some latest updates some time last week with "yum update", but now I think that might have caused some problems on the servers.
Now, for some reason the webserver will get into a state where httpd is no longer running (or there are only two instances of httpd running) and the server refuses all connections on port 80 or port 443, but, when I try to restart the server, I get this error:
[rootatsls-ec5p18 ~]# service httpd restart
Stopping httpd: [FAILED]
Starting httpd: [Tue Nov 24 09:55:20 2009] [warn] Useless use of AllowOverride i
n line 998.
(98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
How do I fix this so Apache stops getting stuck into this non-restartable state?
I cannot give out root access to the server but I'll try any suggestions.
If I reboot the server, then it will usually come up again. But I don't know how apache is getting into this "stuck state".
If I do a tail on the error log, it looks like:
[Tue Nov 24 09:39:12 2009] [emerg] (22)Invalid argument: couldn't grab the accep
[Tue Nov 24 09:39:36 2009] [emerg] (22)Invalid argument: couldn't grab the accep
[Tue Nov 24 09:40:36 2009] [emerg] (22)Invalid argument: couldn't grab the accep
[Tue Nov 24 09:41:24 2009] [emerg] (22)Invalid argument: couldn't grab the accep
(where the timestamp "Tue Nov 24 09:41:24 2009" is a few minutes ago).
Preferably, I need a way to fix this problem.
Otherwise, at least an explanation for what's going on.
Even if you just have a suggestion for what log files to look at, or what command to run, in order to help narrow down the problem, that is helpful.
If you post a comment that turns out to help solve the problem or even just helps to gather more information, I'll send you a tip. I've sent $10 and $20 tips to people who have sent helpful comments before when I posted a troubleshooting job.
My machines where I'm seeing this problem are CentOS 5.4 and Apache 2.2.3.