On 17/10/10 19:40, Arthur Titeica wrote:
On Wednesday 04 August 2010 16:55:46 Amos Jeffries wrote:
Zeller, Jan (ID) wrote:
It looks like that message only occurs on a reconfigure. Does "-k
restart"
after the config change work?
Amos
hmm the change applies once squid is restarted but now I am getting :
010/08/04 08:21:20 kid3| commBind: Cannot bind socket FD 12 to [::]: (13)
Permission denied .
.
squid is running as
cache_effective_user proxy
cache_effective_group proxy
squid processes are running but no listening port. Any clue why this
happens ?
Nothing I know about should lead to a kidN using bind on [::] or 0.0.0.0.
Maybe Alex has a clue.
cc'ing to squid-dev where beta release problems really need to be
discussed. Please followup there.
Amos
Sorry for bumping this thread but I see the same with 3.2.0.2-20101016.
Something is trying to bind to [::] and the proxy is refuzing conections.
The thread title suggests that the 'workers' setting is ignored but I guess
it's not as I see the 4 squid processes with ps.
Since that earlier response I've learned a thing or two about how the
kidN work. With "workers 2" the "kid3" is the coordinator process which
opens shared ports and passes them to the other kids for sharing.
The lack of port number in the address being opened and bound seems to
be the problem.
Do you have all http_port configured inside if..endif for specific
workers, or some shared ones?
Are you running Squid as root or a less-privileged user?
Is IPv6 disabled on the box?
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.9
Beta testers wanted for 3.2.0.3
