httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Boyle Owen" <Owen.Bo...@swx.com>
Subject RE: [users@httpd] Not able to bind to address
Date Fri, 07 Jan 2005 15:46:46 GMT


> -----Original Message-----
> From: Nick Kirby [mailto:nick.kirby@freeuk.com]
> Sent: Freitag, 7. Januar 2005 15:47
> To: users@httpd.apache.org
> Subject: RE: [users@httpd] Not able to bind to address
> 
> 
> Well, port 80 is listening on 192.168.1.2, under process ID 3976.
> 
> I'm stumped.
> 
> Localhost is fine. Router is fine, and performing port 
> forwarding, apache is
> fine, bound properly, there is no firewall on the router 

I didn't say the FW on the router. I said the FW on windows XP... Look in the security settings.

> aside from the
> blocked ports, and those are open for hhtp in and out.
> 
> It's a mystery. 

Did you read the other threads - it's a very common mystery



> 
> -----Original Message-----
> From: Boyle Owen [mailto:Owen.Boyle@swx.com] 
> Sent: 07 January 2005 14:16
> To: users@httpd.apache.org
> Subject: RE: [users@httpd] Not able to bind to address
> 
> 
> 
> > -----Original Message-----
> > From: Nick Kirby [mailto:nick.kirby@freeuk.com]
> > Sent: Freitag, 7. Januar 2005 14:59
> > To: users@httpd.apache.org
> > Subject: RE: [users@httpd] Not able to bind to address
> > 
> > 
> > Well, IP address 192.168.1.2 is bound to port 80 and is in the 
> > listening state. There are no other web servers running.
> > 
> > IIS is not on here, as far as I can see. 
> 
> Read all the entries on this thread (only some are relevant)
> http://forums.devshed.com/archive/t-122638 or here
> http://live.cgcu.net/discussion/?f=3&t=17
> 
> It looks like it's a common problem with XP. The threads are 
> pretty garbled
> with lots of cross-talk, but I get the general impression 
> that there can be
> a general problem with the Xp firewall blocking port 80 
> and/or a proxy using
> port 80. Also, it's a good idea to reboot between major system
> reconfigurations...
> 
> Without sitting down in front of your computer, it's really 
> hard to guess.
> 
> Rgds,
> Owen Boyle
> Disclaimer: Any disclaimer attached to this message may be ignored. 
> 
> > 
> > -----Original Message-----
> > From: Axel-Stéphane SMORGRAV
> > [mailto:Axel-Stephane.SMORGRAV@europe.adp.com]
> > Sent: 07 January 2005 13:50
> > To: users@httpd.apache.org
> > Subject: RE: [users@httpd] Not able to bind to address
> > 
> > Is your system Windows or *nix??
> > 
> > First of all: make sure there is no other web server 
> running on your 
> > host.
> > Although Apache is not started, there may be other web 
> servers (like 
> > IIS??) If you are running *nix, you can try "ps -ef | grep httpd".
> > Even none apache
> > web servers may contain the string httpd (e.g. ns-httpd in 
> the case of 
> > Netscape/iPlanet). On Windows, start the task manager and browse 
> > through the running processes, and look at the list of 
> services that 
> > are started.
> > 
> > Next make sure that port 80 is not bound. You can do that 
> by starting 
> > a shell (on Windows that would be a DOS command prompt - 
> cmd) on the 
> > host, run netstat and look for line like in the example below:
> > 
> > info 585$ netstat -an
> > TCP: IPv4
> >    Local Address        Remote Address    Swind Send-Q Rwind 
> > Recv-Q  State
> > -------------------- -------------------- ----- ------ -----
> > ------ -------
> > *.80                  *.*                      0       0 
> > 24576      0 LISTEN
> > or
> > 192.16.1.2.80         *.*                      0       0 
> > 24576      0 LISTEN
> > 
> > If you find such a line in the output from netstat, some 
> process has 
> > bound the port your Apache is trying to bind. In that case you will 
> > have to track down that process that binds it and kill it, 
> or you can 
> > try binding another port than 80 using the Listen 
> directive. On *nix 
> > you can use the lsof tool to find the process binding the port. On 
> > Windows I have no idea.
> > 
> > Good luck
> > 
> > -ascs
> > 
> > -----Message d'origine-----
> > De : Nick [mailto:nick.kirby@freeuk.com] Envoyé : vendredi 
> 7 janvier 
> > 2005
> > 14:28 À : Axel-Stéphane SMORGRAV Objet : RE: [users@httpd] 
> Not able to 
> > bind to address
> > 
> > I have netstat running - what am I looking for?
> > 
> > Sorry, I'm frightfully new at this.
> > 
> > Nick
> > 
> > -----Original Message-----
> > From: Axel-Stéphane SMORGRAV
> > [mailto:Axel-Stephane.SMORGRAV@europe.adp.com]
> > Sent: 07 January 2005 13:22
> > To: users@httpd.apache.org; nick.kirby@freeuk.com
> > Subject: RE: [users@httpd] Not able to bind to address
> > 
> > Run netstat to see if there is, by any chance, another process that 
> > has bound port 80 on your host.
> > 
> > -ascs
> > 
> > -----Message d'origine-----
> > De : Nick [mailto:nick.kirby@freeuk.com] Envoyé : vendredi 
> 7 janvier 
> > 2005 14:20 À : users@httpd.apache.org Objet : [users@httpd] 
> Not able 
> > to bind to address
> > 
> > Hi, I get the first bit, to stop Apache running. Looking at 
> the httpd 
> > file I see that the listen directive is simply set to
> > 
> > 
> > #
> > # Listen: Allows you to bind Apache to specific IP addresses 
> > and/or # ports,
> > instead of the default. See also the <VirtualHost> # directive.
> > #
> > # Change this to Listen on specific IP addresses as shown 
> > below to # prevent
> > Apache from glomming onto all bound IP addresses (0.0.0.0) # #Listen
> > 12.34.56.78:80 Listen 80
> > 
> > What should this be set to? The IP of the server?
> > 
> > So should it be Listen 192.16.1.2:80 ?
> > 
> > -----Original Message-----
> > From: Axel-Stéphane SMORGRAV 
> > [mailto:Axel-Stephane.SMORGRAV@europe.adp.com]
> > Sent: 07 January 2005 12:51
> > To: users@httpd.apache.org; nick.kirby@freeuk.com
> > Subject: RE: [users@httpd] I just installed Apache2 - Where's the
> > request_uri enviornment variable??
> > 
> > I believe it means that the protocol/address/port is already bound.
> > 
> > 1. Verify that the server is not already started 2. Check 
> > whether another
> > process than Apache may have bound the protocol/address/port 
> > by browsing
> > through netstat 3. Make sure that you only have one Listen 
> > directive for
> > that address/port in httpd.conf
> > 
> > -ascs
> > 
> > -----Message d'origine-----
> > De : Nick [mailto:nick.kirby@freeuk.com] Envoyé : vendredi 7 
> > janvier 2005
> > 13:35 À : users@httpd.apache.org Objet : RE: [users@httpd] I 
> > just installed
> > Apache2 - Where's the request_uri enviornment variable??
> > 
> > Could someone tell me what this means?
> > 
> > make_sock: could not bind to address 192.168.1.2:80 no 
> > listening sockets
> > available, shutting down
> > 
> > And what I have to do to fix it?
> > 
> > I am assuming the apache process cannot 'see' the IP address 
> > to serve web
> > pages. How do I go about ensuring it can always 'see' the IP?
> > 
> > -----Original Message-----
> > From: Axel-Stéphane SMORGRAV 
> > [mailto:Axel-Stephane.SMORGRAV@europe.adp.com]
> > Sent: 07 January 2005 07:37
> > To: users@httpd.apache.org
> > Subject: RE: [users@httpd] I just installed Apache2 - Where's the
> > request_uri enviornment variable??
> > 
> > There must be something else wrong because Apache 2.0.49 does 
> > supply the
> > REQUEST_URI variable to the CGI environment. Try to request
> > /cgi-bin/printenv and you will see for yourself.
> > 
> > Could your problem be due to a misconfiguration of 
> > mod_jrun20, and are you
> > sure you have the correct version of that module? Does 
> > Macromedia support
> > Apache 2.0.49? 
> > 
> > -ascs
> > 
> > -----Message d'origine-----
> > De : Jon Block [mailto:httpd@collegepublisher.com]
> > Envoyé : vendredi 7 janvier 2005 00:02
> > À : users@httpd.apache.org
> > Objet : [users@httpd] I just installed Apache2 - Where's the 
> > request_uri
> > enviornment variable??
> > 
> > I am writing a site with ColdFusion and Apache. I just 
> > upgraded from Apache
> > 1.x to Apache 2 and suddenly, Apache2 doesn't seem to be 
> > supplying me with
> > the request_uri variable that my code works with.
> > 
> > What should I do?
> > 
> > Thanks,
> > Jon
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP 
> > Server Project.
> > See <URL:http://httpd.apache.org/userslist.html> for more info.
> > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> >    "   from the digest: users-digest-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
> > 
> > 
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP 
> > Server Project.
> > See <URL:http://httpd.apache.org/userslist.html> for more info.
> > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> >    "   from the digest: users-digest-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP 
> > Server Project.
> > See <URL:http://httpd.apache.org/userslist.html> for more info.
> > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> >    "   from the digest: users-digest-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
> > 
> > 
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP 
> > Server Project.
> > See <URL:http://httpd.apache.org/userslist.html> for more info.
> > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> >    "   from the digest: users-digest-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
> > 
> >
> 
> This message is for the named person's use only. It may contain
> confidential, proprietary or legally privileged information. No
> confidentiality or privilege is waived or lost by any mistransmission.
> If you receive this message in error, please notify the 
> sender urgently
> and then immediately delete the message and any copies of it from your
> system. Please also immediately destroy any hardcopies of the message.
> You must not, directly or indirectly, use, disclose, 
> distribute, print,
> or copy any part of this message if you are not the intended 
> recipient.
> The sender's company reserves the right to monitor all e-mail
> communications through their networks. Any views expressed in this
> message are those of the individual sender, except where the message
> states otherwise and the sender is authorised to state them to be the
> views of the sender's company. 
> 
> 
> 
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP 
> Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>    "   from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
> 
> 
> 
> 
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP 
> Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>    "   from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
> 
> 

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message