httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Leavitt <tho...@thomasleavitt.org>
Subject [users@httpd] Apache restart problem: Address already in use: make_sock: could not bind to address [::]:443
Date Mon, 02 Oct 2006 20:37:45 GMT
Here's the deal - I can't restart apache

service httpd restart
or
service httpd stop
service httpd start

without manually first terminating a bunch of hung processes... 

# service httpd stop
Shutting down httpd:                                            [  OK  ]
#
# service httpd start
Starting httpd: (98)Address already in use: make_sock: could not bind to address [::]:443
no listening sockets available, shutting down
Unable to open logs


I then have to manually grep and kill -KILL (a regular SIGTERM won't
work) each and every instance of httpd still running (which can be a
considerable number, up to 100)...

since I started the server this morning, there's only 2:
apache   21670  0.9  3.8 122440 29912 ?        S    10:48   1:36 /usr/sbin/httpd -f /etc/httpd/conf/httpd.conf
-DAPACHE2 -DHAVE_AUTH_EXTERNAL -DHAVE_AUTH_MYSQL -DHAVE_DOSEVASIVE -DHAVE_PERL -DHAVE_PHP5
-DHAVE_SSL -DHAVE_SUEXEC -DHAVE_ACCESS -DHAVE_ACTIONS -DHAVE_ALIAS -DHAVE_ASIS -DHAVE_AUTH
-DHAVE_AUTH_ANON -DHAVE_AUTH_DBM -DHAVE_AUTH_DIGEST -DHAVE_AUTOINDEX -DHAVE_CACHE -DHAVE_CASE_FILTER
-DHAVE_CASE_FILTER_IN -DHAVE_CERN_META -DHAVE_CGI -DHAVE_CGID -DHAVE_CHARSET_LITE -DHAVE_DEFLATE
-DHAVE_DIR -DHAVE_DISK_CACHE -DHAVE_DUMPIO -DHAVE_ENV -DHAVE_EXPIRES -DHAVE_EXT_FILTER -DHAVE_HEADERS
-DHAVE_IMAP -DHAVE_INCLUDE -DHAVE_INFO -DHAVE_LOG_CONFIG -DHAVE_LOG_FORENSIC -DHAVE_LOGIO
-DHAVE_MIME -DHAVE_MIME_MAGIC -DHAVE_NEGOTIATION -DHAVE_REWRITE -DHAVE_SETENVIF -DHAVE_SPELING
-DHAVE_STATUS -DHAVE_UNIQUE_ID -DHAVE_USERTRACK -DHAVE_VHOST_ALIAS
apache   21676  1.1  4.0 123928 31392 ?        S    10:48   1:54 /usr/sbin/httpd -f /etc/httpd/conf/httpd.conf
-DAPACHE2 -DHAVE_AUTH_EXTERNAL -DHAVE_AUTH_MYSQL -DHAVE_DOSEVASIVE -DHAVE_PERL -DHAVE_PHP5
-DHAVE_SSL -DHAVE_SUEXEC -DHAVE_ACCESS -DHAVE_ACTIONS -DHAVE_ALIAS -DHAVE_ASIS -DHAVE_AUTH
-DHAVE_AUTH_ANON -DHAVE_AUTH_DBM -DHAVE_AUTH_DIGEST -DHAVE_AUTOINDEX -DHAVE_CACHE -DHAVE_CASE_FILTER
-DHAVE_CASE_FILTER_IN -DHAVE_CERN_META -DHAVE_CGI -DHAVE_CGID -DHAVE_CHARSET_LITE -DHAVE_DEFLATE
-DHAVE_DIR -DHAVE_DISK_CACHE -DHAVE_DUMPIO -DHAVE_ENV -DHAVE_EXPIRES -DHAVE_EXT_FILTER -DHAVE_HEADERS
-DHAVE_IMAP -DHAVE_INCLUDE -DHAVE_INFO -DHAVE_LOG_CONFIG -DHAVE_LOG_FORENSIC -DHAVE_LOGIO
-DHAVE_MIME -DHAVE_MIME_MAGIC -DHAVE_NEGOTIATION -DHAVE_REWRITE -DHAVE_SETENVIF -DHAVE_SPELING
-DHAVE_STATUS -DHAVE_UNIQUE_ID -DHAVE_USERTRACK -DHAVE_VHOST_ALIAS

this is on mandriva 2006

i can supply more detailed sysconfig / os info if desired

Normally, this is just an annoyance, because the server itself is rarely
if ever restarted, and for some reason, I don't encounter the problem
immediately, so once I've stopped and started the server once, I can
redo it several times while I'm tinkering, if I need to, without this
problem.

However, this morning, the server died at 3:06 a.m., and did not restart
(some cron process, I'm sure)...

[Mon Oct 02 03:06:50 2006] [error] [client 127.0.0.1] File does not
exist: /var/www/html/ap2_snmp
[Mon Oct 02 03:07:03 2006] [warn] child process 7923 still did not exit,
sending a SIGTERM
[Mon Oct 02 03:07:03 2006] [warn] child process 7919 still did not exit,
sending a SIGTERM
[Mon Oct 02 03:07:03 2006] [warn] child process 7921 still did not exit,
sending a SIGTERM
[Mon Oct 02 03:07:03 2006] [warn] child process 31079 still did not
exit, sending a SIGTERM
[Mon Oct 02 03:07:03 2006] [warn] child process 25984 still did not
exit, sending a SIGTERM
[Mon Oct 02 03:07:03 2006] [warn] child process 31896 still did not
exit, sending a SIGTERM
[Mon Oct 02 03:07:03 2006] [warn] child process 25510 still did not
exit, sending a SIGTERM
[Mon Oct 02 03:07:03 2006] [warn] child process 20737 still did not
exit, sending a SIGTERM
[Mon Oct 02 03:07:03 2006] [warn] child process 19403 still did not
exit, sending a SIGTERM
[Mon Oct 02 03:07:03 2006] [warn] child process 9412 still did not exit,
sending a SIGTERM
[Mon Oct 02 03:07:03 2006] [warn] child process 9414 still did not exit,
sending a SIGTERM
[Mon Oct 02 03:07:03 2006] [warn] child process 20741 still did not
exit, sending a SIGTERM
[Mon Oct 02 03:07:03 2006] [warn] child process 12175 still did not
exit, sending a SIGTERM
[Mon Oct 02 03:07:03 2006] [warn] child process 12176 still did not
exit, sending a SIGTERM
[Mon Oct 02 03:07:03 2006] [warn] child process 13142 still did not
exit, sending a SIGTERM

... and the error log terminated right there...

httpd was not running when a customer woke me up to tell me the web
server wasn't responding...

I've periodically dug through Google and other sites to determine if
this is a known problem, and I've been unable to find anything that
clearly points to the same problem, along with a resolution... any ideas
on how to address this?

Thomas



---------------------------------------------------------------------
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@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message