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

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

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

Best Regards,
Saleh Madi

On Thu, 2011-09-15 at 23:34 +1200, Amos Jeffries wrote:
> On 15/09/11 20:03, fredbmail wrote:
> > You should change this value
> >
> > Line 49
> >
> > Old:
> > src/ipc/Strand.cc: setTimeout(6, "Ipc::Strand::timeoutHandler"); // TODO:
> > make 6 configurable?
> > New:
> > src/ipc/Strand.cc: setTimeout(120, "Ipc::Strand::timeoutHandler"); // TODO:
> > make 6 configurable?
> >
> > For cache disk with 130G setTimeout(120) is a good value for me
> >
> > Amos i saw the messages from Alex Rousskov (CVS mailling list) about SMP/IPC there will be a change about this problem in next CVS ?
>
> Currently no, it is not yet fixed. However his SMP work being merged
> means the release countdown is started and we have a focus on fixing
> everything. So a fairly good chance of being resolved soon.
>
> Amos
> --
> Please be using
> Current Stable Squid 2.7.STABLE9 or 3.1.15
> Beta testers wanted for 3.2.0.11
>
Received on Thu Sep 15 2011 - 13:12:57 MDT