Re: [squid-users] Squid 3.2.0.11 FATAL: kid2 registration timed out

On 16/09/11 01:12, Saleh Madi wrote:
> Thank all for your replay, why does kid1 or kid2 , ... repeatedly crash
> and when it crashes why does not it restart again aromatically? do I
> have to restart the squid main process manually when ever a kid crashes?
> Is this solution efficient? Is there any solution to over come this
> problem?
>
> workers 8
> cpu_affinity_map process_numbers=1,2,3,4,5,6,7,8
> cores=2,4,6,8,10,12,14,16
>
> redirect_program /usr/bin/squidGuard -c /etc/squid/squidGuard.conf
> redirect_children 4
> redirector_bypass on
>
> Below is the cache log for kid1 when it crash

kid1 is not crashing.

The squidGuard helper being used by kid1 is crashing when asked to
perform an action.

>
> 2011/09/15 13:51:45 kid1| helperDispatch: Helper redirector #1 has
> crashed
> 2011/09/15 13:51:45 kid1| helperDispatch: Helper redirector #1 has
> crashed
> 2011/09/15 13:51:45 kid1| WARNING: redirector #1 (FD 18) exited
> 2011/09/15 13:51:45 kid1| Too few redirector processes are running (need
> 1/4)
> 2011/09/15 13:51:45 kid1| Starting new helpers
> 2011/09/15 13:51:45 kid1| helperOpenServers: Starting 1/4 'squidGuard'
> processes

.. and being restarted.

This will cycle until >4 deaths per 30 seconds occur then kid1 will
shutdown and prevent restart to save you from infinite loops in hung
processes.

The solution is to find and fix squidGuard's problems.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.15
   Beta testers wanted for 3.2.0.11