Your message dated Sun, 28 Nov 2010 19:41:01 -0600
with message-id <20101128194101.5812c...@panther>
and subject line Something on 80
has caused the Debian Bug report #578029,
regarding nginx: [emerg]: bind() to [::]:80 failed (98: Address already in use)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
578029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578029
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nginx
Version: 0.7.65-5
Severity: normal
The message in subject appear in error.log while upgrade or reconfigure
(more certainly while running postinst script) fresh installed and don't
touched package. As result the running server drop down and should be
started manually. There are something wrong with "listen" directive in
default config or it is in some way related to bug #577456, that is
reported as fixed, but may be not complete or right.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Shell: /bin/sh linked to /bin/bash
Versions of packages nginx depends on:
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libgeoip1 1.4.6.dfsg-19 A non-DNS IP-to-country resolver l
ii libpcre3 7.8-3 Perl 5 Compatible Regular Expressi
ii libssl0.9.8 0.9.8n-1 SSL shared libraries
ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
nginx recommends no packages.
nginx suggests no packages.
-- no debconf information
--
*********************************
**** Vladimir Stavrinov ******
******* [email protected] *********
*********************************
--- End Message ---
--- Begin Message ---
I looked into this further and it definitely only happens when you try to
listen on a port (in this case 80) that already has a listening application
bound to it.
Make sure nothing is already listening on that port (apache, lighty, nginx,
etcetera). You can find the application with 'lsof -i :80'.
--- End Message ---
