Re: [squid-users] tproxy cache.log flooded

On 11/03/11 04:30, jeffrey j donovan wrote:
>
> On Mar 10, 2011, at 10:08 AM, jiluspo wrote:
>
>> whats going on witht this bind thingi
>>
>> 2011/03/10 19:59:26| commBind: Cannot bind socket FD 1160 family 2 to 0.0.0.0 port 0: (98) Address already in use
>> 2011/03/10 19:59:26| comm_fdopen6: FD 1160: TPROXY comm_ips_bind_rem() failed: errno 98 ((98) Address already in use)
>> 2011/03/10 19:59:26| commBind: Cannot bind socket FD 1160 family 2 to 0.0.0.0 port 0: (98) Address already in use
>> 2011/03/10 19:59:26| comm_fdopen6: FD 1160: TPROXY comm_ips_bind_rem() failed: errno 98 ((98) Address already in use)
>> 2011/03/10 19:59:26| commBind: Cannot bind socket FD 1160 family 2 to 0.0.0.0 port 0: (98) Address already in use
>
> sounds like you have stray process.
>
> scan for the running PID
> ps -ax | grep tprox
> shutdown squid and look whos still running, and or send a kill or shutdown to tprox

Maybe, but I would not expect anything to show up.

This is not one of the official Squid releases. There is no such
function or text output as "comm_fdopen6" or "comm_ips_bind_rem" in any
Squid.

Although there is an comm_fdopen and commBind in Squid-2.x. Which
neither supports IPv6 nor TPROXYv4.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.11
   Beta testers wanted for 3.2.0.5