View previous topic :: View next topic |
Author |
Message |
Joseph_sys Advocate
Joined: 08 Jun 2004 Posts: 2712 Location: Edmonton, AB
|
Posted: Sat Sep 23, 2006 7:14 pm Post subject: [SOLVED] CAN NOT start apache2 - Address already in use |
|
|
After upgrade when I try to start apache I get:
Code: | 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 |
netstat -natp gives me:
Code: | 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 20302/apache2
tcp 0 0 :::443 :::* LISTEN 20302/apache2
tcp 521 0 ::ffff:127.0.0.1:80 ::ffff:127.0.0.1:51936 CLOSE_WAIT -
tcp 671 0 ::ffff:127.0.0.1:80 ::ffff:127.0.0.1:51937 CLOSE_WAIT -
tcp 495 0 ::ffff:127.0.0.1:80 ::ffff:127.0.0.1:51938 CLOSE_WAIT - |
Where is that strange address :::80 and :::443 coming from, I was expecting 0 0.0.0.0:80
Appreciate any help
Last edited by Joseph_sys on Sun Sep 24, 2006 5:41 am; edited 1 time in total |
|
Back to top |
|
|
Darknight Guru
Joined: 26 Jan 2004 Posts: 483 Location: Italy
|
Posted: Sat Sep 23, 2006 11:36 pm Post subject: |
|
|
Chances are you merged the config files without noticing that you were overwriting your own configs with the new one, and deleting the previously set listening ip directive. In your apache configuration files (/etc/apache2/httpd.conf) you will find the line you have to change. |
|
Back to top |
|
|
Joseph_sys Advocate
Joined: 08 Jun 2004 Posts: 2712 Location: Edmonton, AB
|
Posted: Sat Sep 23, 2006 11:53 pm Post subject: |
|
|
Darknight wrote: | Chances are you merged the config files without noticing that you were overwriting your own configs with the new one, and deleting the previously set listening ip directive. In your apache configuration files (/etc/apache2/httpd.conf) you will find the line you have to change. |
No, that would be to easy to spot:
Listen 80 is still in new http.conf
I've "config-archive" and have compared the new http.conf to archie one and the only section that was added was:
Code: | < # itk MPM [THIS MPM IS NOT SUPPORTED]
< # StartServers: number of server processes to start
< # MinSpareServers: minimum number of server processes which are kept spare
< # MaxSpareServers: maximum number of server processes which are kept spare
< # MaxClients: maximum number of server processes allowed to start
< # MaxRequestsPerChild: maximum number of requests a server process serves
< <IfModule itk.c>
< StartServers 5
< MinSpareServers 2
< MaxSpareServers 10
< MaxClients 150
< MaxRequestsPerChild 1000
< </IfModule> |
So something else must have screwed up my apache.
During upgrade 23packages were emerged/updated and one of them is the culprit:
emerged unmerged
openssl-0.9.8c-r2 openssl-0.9.8c
libsdl-1.2.11 libsdl-1.2.8-r1
libutempter-1.1.4.1 libutempter-1.1.2.1
mplayer-1.0_pre8
sdl-image-1.2.5-r1 sdl-image-1.2.3-r1
apache-2.0.58-r2
nano-1.3.12-r1 nano-1.3.11-r2
graphviz-2.8-r1 graphviz-2.8
eject-2.1.5 eject-2.1.0-r1
lzo-2.02-r1
libtasn1-0.3.5 libtasn1-0.2.18
gnutls-1.4.4-r1 gnutls-1.2.10
nspr-4.6.3 nspr-4.6.1-r2
zip-2.31-r1 zip-2.31
nss-3.11.3 nss-3.11-r1
openssh-4.3_p2-r4 openssh-4.3_p2-r1
gnome-doc-utils-0.6.1
seamonkey-1.0.3
startup-notification-0.8
yelp-2.14.2-r2 yelp-2.6.5
gzip-1.3.5-r9 gzip-1.3.5-r8
fribidi-0.10.7 fribidi-0.10.4
mozilla-firefox-1.5.0.7 mozilla-firefox-1.5.0.5
|
|
Back to top |
|
|
Joseph_sys Advocate
Joined: 08 Jun 2004 Posts: 2712 Location: Edmonton, AB
|
|
Back to top |
|
|
pjp Administrator
Joined: 16 Apr 2002 Posts: 20054
|
Posted: Sun Sep 24, 2006 5:45 am Post subject: |
|
|
Moved from Networking & Security _________________ Quis separabit? Quo animo? |
|
Back to top |
|
|
|