Re: [squid-users] Re: Problem with latest squid 3.2 snapshot

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Sat, 26 Nov 2011 03:17:58 +1300

On 26/11/2011 1:53 a.m., alexatull wrote:
> Well, managed to get squid running in SMP mode
>
> Short answer was I'd copied stuff from by 3.1.16 production service and was
> explicitly specifying ip addresses and ports to listen on. So ...
>
> http_port 150.237.85.249:3128
> http_port 150.237.84.13:3128
>
> Resulted in no IP address being listened on when running in SMP mode but did
> if I fire up squid with -N arg. ( netstat -a showed squid listening on above
> IPv4 addresses)

Strange. That should not matter any more for SMP workers, they share
listening ports.

>
> setting http_port 3128 however caused squid to listen on an IPv6 address and
> everything fired up and I could run squid in SMP mode.

I suspect that had more to do with the absence of a specific address
than IPv6 specifically.

Can you verify that please?

> [
> What I actually ended up doing was
>
> 1). Remove kernel option that disabled IPv6 and rebooted machine
> 2). Rebuilt squid having removed --disable-ipv6
> 3). Changed cache effective user to locally created "squid" user instead of
> the default of nobody ( this made a big difference to things actually
> running)
> 4). Started from scratch with supplied squid sample config file ad stepped
> through things till it broke.
>

Amos
Received on Fri Nov 25 2011 - 14:18:16 MST

This archive was generated by hypermail 2.2.0 : Fri Nov 25 2011 - 12:00:02 MST