httpd driving me crazy.

[Aaron Konstam]

When I do a:
services httpd start

I get this error:
[root@saturn conf]# service httpd start
Starting httpd: (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
Doing a netstat -pltn gives me:

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address               Foreign Address
State       PID/Program name
tcp        0      0 127.0.0.1:2208              0.0.0.0:*
LISTEN      1900/hpiod
tcp        0      0 0.0.0.0:614                 0.0.0.0:*
LISTEN      1704/rpc.statd
tcp        0      0 0.0.0.0:5802                0.0.0.0:*
LISTEN      2096/Xvnc
tcp        0      0 0.0.0.0:5900                0.0.0.0:*
LISTEN      2598/Xorg
tcp        0      0 0.0.0.0:5902                0.0.0.0:*
LISTEN      2096/Xvnc
tcp        0      0 0.0.0.0:111                 0.0.0.0:*
LISTEN      1683/portmap
tcp        0      0 0.0.0.0:6002                0.0.0.0:*
LISTEN      2096/Xvnc
tcp        0      0 127.0.0.1:631               0.0.0.0:*
LISTEN      1917/cupsd
tcp        0      0 127.0.0.1:25                0.0.0.0:*
LISTEN      1964/sendmail: acce
tcp        0      0 127.0.0.1:6010              0.0.0.0:*
LISTEN      3923/1
tcp        0      0 127.0.0.1:2207              0.0.0.0:*
LISTEN      1905/python
tcp        0      0 :::6002                     :::*
LISTEN      2096/Xvnc
tcp        0      0 :::22                       :::*
LISTEN      1932/sshd
tcp        0      0 ::1:6010                    :::*
LISTEN      3923/1

Which shows nothing Listening on port 80. One again FC6 has done me in.
Any explanations?

[Rick Stevens]

On Tue, 2007-01-30 at 16:34 -0600, Aaron Konstam wrote:
> When I do a:
> services httpd start
>
> I get this error:
> [root@saturn conf]# service httpd start
> Starting httpd: (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
> Doing a netstat -pltn gives me:
>
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address               Foreign Address
> State       PID/Program name
> tcp        0      0 127.0.0.1:2208              0.0.0.0:*
> LISTEN      1900/hpiod
> tcp        0      0 0.0.0.0:614                 0.0.0.0:*
> LISTEN      1704/rpc.statd
> tcp        0      0 0.0.0.0:5802                0.0.0.0:*
> LISTEN      2096/Xvnc
> tcp        0      0 0.0.0.0:5900                0.0.0.0:*
> LISTEN      2598/Xorg
> tcp        0      0 0.0.0.0:5902                0.0.0.0:*
> LISTEN      2096/Xvnc
> tcp        0      0 0.0.0.0:111                 0.0.0.0:*
> LISTEN      1683/portmap
> tcp        0      0 0.0.0.0:6002                0.0.0.0:*
> LISTEN      2096/Xvnc
> tcp        0      0 127.0.0.1:631               0.0.0.0:*
> LISTEN      1917/cupsd
> tcp        0      0 127.0.0.1:25                0.0.0.0:*
> LISTEN      1964/sendmail: acce
> tcp        0      0 127.0.0.1:6010              0.0.0.0:*
> LISTEN      3923/1
> tcp        0      0 127.0.0.1:2207              0.0.0.0:*
> LISTEN      1905/python
> tcp        0      0 :::6002                     :::*
> LISTEN      2096/Xvnc
> tcp        0      0 :::22                       :::*
> LISTEN      1932/sshd
> tcp        0      0 ::1:6010                    :::*
> LISTEN      3923/1
>
> Which shows nothing Listening on port 80. One again FC6 has done me in.
> Any explanations?

Try "netstat -pan | grep :80".  You may be running something like "xmms"
which will USE port 80, but it's not a process LISTENING on port 80. 
Your check was limited to things listening on port 80.

----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     [e-mail] -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-              Never eat anything larger than your head              -
----------------------------------------------------------------------

[Andy Green]

Aaron Konstam wrote:
> Starting httpd: (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
> Which shows nothing Listening on port 80. One again FC6 has done me in.
> Any explanations?

It's not FC6's fault :-)

The behaviour is to do with a TCP connection that was made to the server 
while it was alive, that hangs around for some time, 60 seconds or 
whatever after the connection was closed on one side... that is what it 
is meant to do.

If you amend your netstat to just -n and grep on :80, you should see the 
client connection shown in TIME_WAIT.  After the timeout completes, you 
will be able to start Apache again.

-Andy

Happened to me too. There is a line in the config file that says

listen 80

Just comment this out and all will be well. It looks like its trying to 
listen on port 80 twice.

......Brian Kaye

On Tue, 30 Jan 2007, Aaron Konstam wrote:
> Date: Tue, 30 Jan 2007 16:34:55 -0600
> From: Aaron Konstam 
> Reply-To: For users of Fedora 
> To: fedora-list 
> Subject: httpd driving me crazy.
>
> When I do a:
> services httpd start
>
> I get this error:
> [root@saturn conf]# service httpd start
> Starting httpd: (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
> Doing a netstat -pltn gives me:
>
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address               Foreign Address
> State       PID/Program name
> tcp        0      0 127.0.0.1:2208              0.0.0.0:*
> LISTEN      1900/hpiod
> tcp        0      0 0.0.0.0:614                 0.0.0.0:*
> LISTEN      1704/rpc.statd
> tcp        0      0 0.0.0.0:5802                0.0.0.0:*
> LISTEN      2096/Xvnc
> tcp        0      0 0.0.0.0:5900                0.0.0.0:*
> LISTEN      2598/Xorg
> tcp        0      0 0.0.0.0:5902                0.0.0.0:*
> LISTEN      2096/Xvnc
> tcp        0      0 0.0.0.0:111                 0.0.0.0:*
> LISTEN      1683/portmap
> tcp        0      0 0.0.0.0:6002                0.0.0.0:*
> LISTEN      2096/Xvnc
> tcp        0      0 127.0.0.1:631               0.0.0.0:*
> LISTEN      1917/cupsd
> tcp        0      0 127.0.0.1:25                0.0.0.0:*
> LISTEN      1964/sendmail: acce
> tcp        0      0 127.0.0.1:6010              0.0.0.0:*
> LISTEN      3923/1
> tcp        0      0 127.0.0.1:2207              0.0.0.0:*
> LISTEN      1905/python
> tcp        0      0 :::6002                     :::*
> LISTEN      2096/Xvnc
> tcp        0      0 :::22                       :::*
> LISTEN      1932/sshd
> tcp        0      0 ::1:6010                    :::*
> LISTEN      3923/1
>
> Which shows nothing Listening on port 80. One again FC6 has done me in.
> Any explanations?

[Andy Green]

Aaron Konstam wrote:
> Anyone have any further ideas?

There was a guy last night suggesting there were two Listen: 80 lines in 
a httpd config file, that sounded like a much simpler explanation that 
would match the symptoms just as well.

-Andy

[Aaron Konstam]

On Tue, 2007-01-30 at 22:39 +0000, Andy Green wrote:
> Aaron Konstam wrote:
> > Starting httpd: (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
> > Which shows nothing Listening on port 80. One again FC6 has done me in.
> > Any explanations?
>
> It's not FC6's fault :-)
>
> The behavior is to do with a TCP connection that was made to the server 
> while it was alive, that hangs around for some time, 60 seconds or 
> whatever after the connection was closed on one side... that is what it 
> is meant to do.
>
> If you amend your netstat to just -n and grep on :80, you should see the 
> client connection shown in TIME_WAIT.  After the timeout completes, you 
> will be able to start Apache again.
>
> -Andy

That is an interesting explanation but this error occurred the first
time I tried to start Apache so the connection was never opened in the
first place. netstat -n |grep :80
returns nothing.
and:
fuser -a -n tcp 80
returns: 80/tcp:

Anyone have any further ideas?

[Rick Stevens]

On Wed, 2007-01-31 at 11:17 -0600, Aaron Konstam wrote:
> On Tue, 2007-01-30 at 22:39 +0000, Andy Green wrote:
> > Aaron Konstam wrote:
> > > Starting httpd: (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
> > > Which shows nothing Listening on port 80. One again FC6 has done me in.
> > > Any explanations?
> >
> > It's not FC6's fault :-)
> >
> > The behavior is to do with a TCP connection that was made to the server 
> > while it was alive, that hangs around for some time, 60 seconds or 
> > whatever after the connection was closed on one side... that is what it 
> > is meant to do.
> >
> > If you amend your netstat to just -n and grep on :80, you should see the 
> > client connection shown in TIME_WAIT.  After the timeout completes, you 
> > will be able to start Apache again.
> >
> > -Andy
>
> That is an interesting explanation but this error occurred the first
> time I tried to start Apache so the connection was never opened in the
> first place. netstat -n |grep :80
> returns nothing.

Try "netstat -anp".

----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     [e-mail] -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-      On a scale of 1 to 10 I'd say...  oh, somewhere in there.     -
----------------------------------------------------------------------

httpd driving me crazy.-SOLVED

[Aaron Konstam]

On Wed, 2007-01-31 at 16:17 +0000, Andy Green wrote:
> Aaron Konstam wrote:
> > Anyone have any further ideas?
>
> There was a guy last night suggesting there were two Listen: 80 lines in 
> a httpd config file, that sounded like a much simpler explanation that 
> would match the symptoms just as well.
> -Andy

Well that was not exactly right but it led to the right answer which was
that in /etc/httpd/conf.d there was a file called:
system-config-httpd.conf
Which was sourced when the httpd server started. And that file has a
Listen statement. Where that came from I don't know. 
My guess it was created when system-config-httpd was run.

But anyway the server now runs and I learned something. Thanks to
whoever made the suggestion.
--
=======================================================================
Under deadline pressure for the next week. If you want something, it can
wait. Unless it's blind screaming paroxysmally hedonistic...
=======================================================================
Aaron Konstam telephone: [phone] e-mail: [e-mail]

httpd driving me crazy.-SOLVED

[potat0]

The two listen entries (one in httpd.conf and the other in
system-config-httpd.conf) just got me too!

FYI, the entry in system-config-httpd.conf gets added when you access
the GUI located at: System-> Administration -> Server Settings -> HTTP