Re: [squid-users] Configuration error: 'Cannot bind socket...'

From: Alexandre Correa <alexandre_at_sabbath.com.br>
Date: Sun, 3 Aug 2008 17:30:40 -0300

httpd listenning at 0.0.0.0:80 ... find the line Listen ... and change it...

On Sun, Aug 3, 2008 at 5:18 PM, Gmail <breadwild_at_gmail.com> wrote:
> Background:
> Intel Core2Duo E6320 Dual-Core 1.86 GHz 4MB Cache 250GB 2048MB
> Debian Etch
>
> Without Squid I'm using in my sites-available (Debian's vhost) file:
>
> <VirtualHost *>
> ServerName mywebsite.com
> ServerAlias *.mywebsite.com ...
>
> I want to run Squid and be able to use:
>
> <VirtualHost 127.0.0.1>
> ServerName mywebsite.com
> ServerAlias *.mywebsite.com ...
>
> Here's what happens when I run /usr/sbin/squid -NCd1 :
>
> <snip>
> 2008/08/02 15:05:06| Rebuilding storage in /var/spool/squid (DIRTY)
> 2008/08/02 15:05:06| Using Least Load store dir selection
> 2008/08/02 15:05:06| Set Current Directory to /var/spool/squid
> 2008/08/02 15:05:06| Loaded Icons.
> 2008/08/02 15:05:06| commBind: Cannot bind socket FD 11 to 67.212.162.26:80:
> (98) Address already in use
> 2008/08/02 15:05:06| commBind: Cannot bind socket FD 11 to 67.212.162.27:80:
> (99) Cannot assign requested address
> 2008/08/02 15:05:06| commBind: Cannot bind socket FD 11 to 67.212.162.28:80:
> (99) Cannot assign requested address
> 2008/08/02 15:05:06| commBind: Cannot bind socket FD 11 to 67.212.162.29:80:
> (99) Cannot assign requested address
> 2008/08/02 15:05:06| commBind: Cannot bind socket FD 11 to 67.212.162.30:80:
> (99) Cannot assign requested address
> FATAL: Cannot open HTTP Port
> Aborted (core dumped)
>
> Here are the only differences from the sample squid.conf:
>
> TAG: http_port
> <snip>
> #Default:
> # Squid normally listens to port 3128
> http_port 65.123.123.26:80 defaultsite=127.0.0.1:80 vhost
> http_port 65.123.123.27:80 defaultsite=127.0.0.1:80 vhost
> http_port 65.123.123.28:80 defaultsite=127.0.0.1:80 vhost
> http_port 65.123.123.29:80 defaultsite=127.0.0.1:80 vhost
> http_port 65.123.123.30:80 defaultsite=127.0.0.1:80 vhost
>
> TAG: cache_peer
> <snip>
> #Default:
> # none
> cache_peer 127.0.0.1 parent 80 7 no-query round-robin no-digest
> originserver
>
> TAG: acl
> <snip>
> #Recommended minimum configuration:
> acl all src 0.0.0.0/0.0.0.0
> acl manager proto cache_object
> acl forwardproxy port 80 443 <-- ADDED TO DEFAULT
>
> TAG: http_access
> <snip>
> http_access allow forwardproxy <-- ADDED TO DEFAULT
>
> I ran netstat and it's not showing anything listening at 80 or 8080
>
> Any idea why I'm getting the bind error?
>
> Thanks.
>
>

-- 
Sds.
Alexandre J. Correa
Onda Internet / OPinguim.net
http://www.ondainternet.com.br
http://www.opinguim.net
Received on Sun Aug 03 2008 - 20:30:43 MDT

This archive was generated by hypermail 2.2.0 : Mon Aug 04 2008 - 12:00:03 MDT