Bug#734516: apache2-mpm-itk: apache restart .. could not bind to address [::]:80
Package: apache2-mpm-itk
Version: 2.2.22-13
Severity: normal
Dear Maintainer,
Context:
- running apache2-mpm-itk (with php)
- about 500 different vhosts (dynamically, different user space, hence mpm-itk version) and some generic apache vhosts
- a cron script that does some checks, and then restart the webserver every day
Log:
- not much found there
There are no other services running using port 80.
This bug only occured (and will probably occur) a few times, so i think it has to do with the user interaction with a website.
I suspect that when a user connects justs before (or while, after) restarting the webserver,
the restart fails as then the port is already taken, but this is just a guess.
Unfornately i cannot add addition information other than:
Restarting web server: apache2 ... waiting (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
Action 'start' failed.
The Apache error log may have more information.
failed!
hth,
Wim
-- Package-specific info:
List of enabled modules from 'apache2 -M':
alias auth_basic authn_file authnz_ldap authz_default
authz_groupfile authz_host authz_svn authz_user autoindex cgi dav
dav_svn deflate dir env ldap macro mime negotiation passenger perl
php5 reqtimeout rewrite setenvif ssl status
List of enabled php5 extensions:
curl gd ldap pdo pdo_pgsql pgsql pspell suhosin
-- System Information:
Debian Release: 7.3
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=nl_BE@euro, LC_CTYPE=nl_BE@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash
Versions of packages apache2-mpm-itk depends on:
ii apache2.2-bin 2.2.22-13
ii apache2.2-common 2.2.22-13
apache2-mpm-itk recommends no packages.
apache2-mpm-itk suggests no packages.
-- no debconf information
Reply to: