FW: Can't bind to port 80
Patrick Rhodes
Patrick.Rhodes@asu.edu
Thu, 02 Mar 2000 16:13:58 -0700
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01BF849C.F9CBD334
Content-Type: text/plain;
charset="iso-8859-1"
Thanks for all the help! We had the http line not commented out in the
inetd.conf file. Works fine now!
Patrick
-----Original Message-----
From: Barney Anda [mailto:barney@freewill.tzo.com]
Sent: Wednesday, March 01, 2000 6:30 PM
To: Patrick Rhodes
Subject: RE: Can't bind to port 80
Something loaded from inetd is binding to port 80 instead. Look in
/etc/inetd.conf for ideas.
Barney Anda (barney@freewill.tzo.com)
http://freewill.tzo.com/~barney
On Wed, 1 Mar 2000, Patrick Rhodes wrote:
> Well, we have found a solution - sort of.
>
> If you start the httpd FIRST, then start the INET daemon second, then
it'll
> work correctly. Do it in reverse order, and you can't bind to port 80
with
> the httpd daemon. Any ideas why?
>
> and YES, we only have ONE "Port 80" directive. :-)
>
> Patrick
>
>
> -----Original Message-----
> From: D. Taylor [mailto:dtaylor@www.dssolutions.com]
> Sent: Wednesday, March 01, 2000 5:42 PM
> To: 'PLUG'
> Subject: Re: Can't bind to port 80
>
>
>
> netstat
> lsof
>
> Have you touched apache.conf? You do have just ONE "Port 80"
> and ONE "Listen 80" directive, right? Have you been playing
> with virtual hosts again?
>
>
> D
>
> On Wed, 1 Mar 2000, Patrick Rhodes wrote:
>
> > Date: Wed, 01 Mar 2000 16:34:16 -0700
> > From: Patrick Rhodes <Patrick.Rhodes@asu.edu>
> > Reply-To: plug-discuss@lists.PLUG.phoenix.az.us
> > To: 'PLUG' <plug-discuss@lists.PLUG.phoenix.az.us>
> > Subject: Can't bind to port 80
> >
> > Our Apache server has been running for months on a RedHat 6.0 Linux
server
> > (on port 80). Today, it seemed to have crashed (still investigating
why).
> > Now we can't get it to come back up on port 80, but it'll work just fine
> on
> > port 81. The logs say it can't bind to port 80.
> >
> > 2 things:
> > 1) Is there a way to see what ports are available and/or being used?
> >
> > 2) Any suggestions on how to fix this?
> >
> > Thanks for any and all help - we've been beating our brains trying to
fix
> > it. We also tried upgrading to RedHat 6.1, so now we are on Apache
1.3.9,
> > but the same problem is there. We have rebuilt the binary a couple of
> > times, rebooted the server, stop and started various daemons countless
> times
> > to no avail.
> >
> > If you have apache set to port 80 in it's .conf file, when you execute
> httpd
> > it'll start and stop right away - that's when you look in the logs and
see
> > that it has the binding problem.
> >
> > Patrick
> >
>
>
> _______________________________________________
> Plug-discuss mailing list - Plug-discuss@lists.PLUG.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
------_=_NextPart_001_01BF849C.F9CBD334
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2650.12">
<TITLE>FW: Can't bind to port 80</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Thanks for all the help! We had the http line not commented out in the inetd.conf file. Works fine now!</FONT>
</P>
<P><FONT SIZE=2>Patrick</FONT>
</P>
<BR>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Barney Anda [<A HREF="mailto:barney@freewill.tzo.com">mailto:barney@freewill.tzo.com</A>] </FONT>
<BR><FONT SIZE=2>Sent: Wednesday, March 01, 2000 6:30 PM</FONT>
<BR><FONT SIZE=2>To: Patrick Rhodes</FONT>
<BR><FONT SIZE=2>Subject: RE: Can't bind to port 80</FONT>
</P>
<BR>
<P><FONT SIZE=2>Something loaded from inetd is binding to port 80 instead. Look in</FONT>
<BR><FONT SIZE=2>/etc/inetd.conf for ideas. </FONT>
</P>
<P><FONT SIZE=2>Barney Anda (barney@freewill.tzo.com)</FONT>
<BR><FONT SIZE=2><A HREF="http://freewill.tzo.com/~barney" TARGET="_blank">http://freewill.tzo.com/~barney</A></FONT>
</P>
<P><FONT SIZE=2>On Wed, 1 Mar 2000, Patrick Rhodes wrote:</FONT>
</P>
<P><FONT SIZE=2>> Well, we have found a solution - sort of.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> If you start the httpd FIRST, then start the INET daemon second, then it'll</FONT>
<BR><FONT SIZE=2>> work correctly. Do it in reverse order, and you can't bind to port 80 with</FONT>
<BR><FONT SIZE=2>> the httpd daemon. Any ideas why?</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> and YES, we only have ONE "Port 80" directive. :-)</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Patrick</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> -----Original Message-----</FONT>
<BR><FONT SIZE=2>> From: D. Taylor [<A HREF="mailto:dtaylor@www.dssolutions.com">mailto:dtaylor@www.dssolutions.com</A>]</FONT>
<BR><FONT SIZE=2>> Sent: Wednesday, March 01, 2000 5:42 PM</FONT>
<BR><FONT SIZE=2>> To: 'PLUG'</FONT>
<BR><FONT SIZE=2>> Subject: Re: Can't bind to port 80</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> netstat</FONT>
<BR><FONT SIZE=2>> lsof</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Have you touched apache.conf? You do have just ONE "Port 80"</FONT>
<BR><FONT SIZE=2>> and ONE "Listen 80" directive, right? Have you been playing</FONT>
<BR><FONT SIZE=2>> with virtual hosts again?</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> D</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> On Wed, 1 Mar 2000, Patrick Rhodes wrote:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> > Date: Wed, 01 Mar 2000 16:34:16 -0700</FONT>
<BR><FONT SIZE=2>> > From: Patrick Rhodes <Patrick.Rhodes@asu.edu></FONT>
<BR><FONT SIZE=2>> > Reply-To: plug-discuss@lists.PLUG.phoenix.az.us</FONT>
<BR><FONT SIZE=2>> > To: 'PLUG' <plug-discuss@lists.PLUG.phoenix.az.us></FONT>
<BR><FONT SIZE=2>> > Subject: Can't bind to port 80</FONT>
<BR><FONT SIZE=2>> > </FONT>
<BR><FONT SIZE=2>> > Our Apache server has been running for months on a RedHat 6.0 Linux server</FONT>
<BR><FONT SIZE=2>> > (on port 80). Today, it seemed to have crashed (still investigating why).</FONT>
<BR><FONT SIZE=2>> > Now we can't get it to come back up on port 80, but it'll work just fine</FONT>
<BR><FONT SIZE=2>> on</FONT>
<BR><FONT SIZE=2>> > port 81. The logs say it can't bind to port 80.</FONT>
<BR><FONT SIZE=2>> > </FONT>
<BR><FONT SIZE=2>> > 2 things:</FONT>
<BR><FONT SIZE=2>> > 1) Is there a way to see what ports are available and/or being used?</FONT>
<BR><FONT SIZE=2>> > </FONT>
<BR><FONT SIZE=2>> > 2) Any suggestions on how to fix this?</FONT>
<BR><FONT SIZE=2>> > </FONT>
<BR><FONT SIZE=2>> > Thanks for any and all help - we've been beating our brains trying to fix</FONT>
<BR><FONT SIZE=2>> > it. We also tried upgrading to RedHat 6.1, so now we are on Apache 1.3.9,</FONT>
<BR><FONT SIZE=2>> > but the same problem is there. We have rebuilt the binary a couple of</FONT>
<BR><FONT SIZE=2>> > times, rebooted the server, stop and started various daemons countless</FONT>
<BR><FONT SIZE=2>> times</FONT>
<BR><FONT SIZE=2>> > to no avail.</FONT>
<BR><FONT SIZE=2>> > </FONT>
<BR><FONT SIZE=2>> > If you have apache set to port 80 in it's .conf file, when you execute</FONT>
<BR><FONT SIZE=2>> httpd</FONT>
<BR><FONT SIZE=2>> > it'll start and stop right away - that's when you look in the logs and see</FONT>
<BR><FONT SIZE=2>> > that it has the binding problem.</FONT>
<BR><FONT SIZE=2>> > </FONT>
<BR><FONT SIZE=2>> > Patrick</FONT>
<BR><FONT SIZE=2>> > </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> _______________________________________________</FONT>
<BR><FONT SIZE=2>> Plug-discuss mailing list - Plug-discuss@lists.PLUG.phoenix.az.us</FONT>
<BR><FONT SIZE=2>> <A HREF="http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss" TARGET="_blank">http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss</A></FONT>
<BR><FONT SIZE=2>> </FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01BF849C.F9CBD334--