Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 148871 - Starting apache2 - could not bind to address [::]:443
Summary: Starting apache2 - could not bind to address [::]:443
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Server (show other bugs)
Hardware: AMD64 Linux
: High normal
Assignee: Apache Team - Bugzilla Reports
URL:
Whiteboard:
Keywords:
: 148872 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-09-23 16:12 UTC by Joseph
Modified: 2006-09-23 22:50 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph 2006-09-23 16:12:08 UTC
Latest upgrade screwup my apache on AMD64, when I try to start it I get:
* Starting apache2 ...
(98)Address already in use: make_sock: could not bind to address [::]:443
no listening sockets available, shutting down
Unable to open logs

output of "netstat -natp"
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      6483/mysqld
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN      7037/smbd
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      6845/cupsd
tcp        0      0 127.0.0.1:5432          0.0.0.0:*               LISTEN      6566/postmaster
tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN      6971/master
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN      7037/smbd
tcp        0      0 :::80                   :::*                    LISTEN      20800/apache2
tcp        0      0 :::443                  :::*                    LISTEN      20800/apache2
tcp      415      0 ::ffff:127.0.0.1:80     ::ffff:127.0.0.1:51199  CLOSE_WAIT  -

In addition when I try to start sshd I get: 
/etc/init.d/sshd start 
/etc/init.d/sshd: line 17: 7470 Segmentation fault ${SSHD_BINARY} -t ${myopts}

I re-emerged, apache, openssh did revdep-rebuild
Nothing helps.  
The upgraded worked OK on both x86 boxes but my AMD64 got screwed up.
Appreciate any help (I couldn't find anything on the forum).

#Joseph

Portage 2.1.1 (default-linux/amd64/2005.0, gcc-4.1.1, glibc-2.4-r3, 2.6.15-gentoo-r4 x86_64)
=================================================================
System uname: 2.6.15-gentoo-r4 x86_64 AMD Athlon(tm) 64 Processor 3000+
Gentoo Base System version 1.12.5
Last Sync: Sat, 23 Sep 2006 16:30:01 +0000
ccache version 2.3 [enabled]
app-admin/eselect-compiler: [Not Present]
dev-java/java-config: 1.2.11-r1
dev-lang/python:     2.3.5-r2, 2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     2.3
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.13-r3
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=athlon64 -pipe -O2"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo"
CXXFLAGS="-march=athlon64 -pipe -O2"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks metadata-transfer parallel-fetch sandbox sfperms strict"
GENTOO_MIRRORS="ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo ftp://mirror.iawnet.sandia.gov/pub/gentoo/ ftp://sunsite.ualberta.ca/pub/unix/Linux/gentoo/ rsync://linux.rz.ruhr-uni-bochum.de/gentoo/ rsync://planetmirror.com/gentoo/"
LINGUAS=""
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X acl alsa apache2 arts avi berkdb bitmap-fonts cdr cgi cli crypt cups dlloader dri dvd eds elibc_glibc emboss encode fam foomaticdb fortran gif gimp gimpprint gpm gstreamer gtk gtk2 imlib input_devices_keyboard input_devices_mouse ipv6 isdnlog java jpeg kde kernel_linux lzw lzw-tiff mp3 mpeg mysql ncurses nls nptl nptlonly ogg opengl pam pcre pdflib perl png ppds pppd python qt qt3 qt4 quicktime readline reflection scanner sdl session spell spl ssl tcpd tiff truetype-fonts type1-fonts usb userland_GNU video_cards_fbdev video_cards_nv video_cards_tdfx video_cards_vesa vorbis xorg xpm xv zlib"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-09-23 16:53:37 UTC
*** Bug 148872 has been marked as a duplicate of this bug. ***
Comment 2 Joseph 2006-09-23 18:06:08 UTC
It looks to me as if apache was trying to bind to IPv6 instead of IPv4 but I don't know why?  (I did not make any changes)
tcp 0 0 :::80 :::* LISTEN 10470/apache2
tcp 0 0 :::443 :::* LISTEN 10470/apache2

It should be:
tcp 0 0 0.0.0:80 :::* LISTEN 10470/apache2
tcp 0 0 0.0.0:443 :::* LISTEN 10470/apache

Restarting the machine doesn't help. 

#Joseph
Comment 3 Joseph 2006-09-23 22:50:35 UTC
SOLVED, it took me all day. So if somebody has the same problem here is are the solutions (options).  
The problem was caused by the fact that I had a IPv6 protocol enabled in the Kernel so after today's upgrade to apache-2.0.58-r2.  It decided that IPv6 should take precedence over IPv4 and apache binded to :::80 instead of 0.0.0.0:80

The only question I have why all of a sudden and which package cause it?

a.)
Quick way around it is to modify correctly you /etc/hosts file: 
...
# IPV6 versions of localhost and co
::1 ip6-localhost ip6-loopback syscon3.your_domain_name syscon3
...
restart apache.

Though, make sure your connection gets through your firewall to IPv6

b.)
Another solution is to tell your apache to listen to IPv4 that is in your httpd.conf
change from:
Listen 80
to
Listen 0.0.0.0:80

c.)
Disable IPv6 in your kernel

If I missed anything please add.

#Joseph