Re: Squid-SMP problems in current trunk

On 16/07/11 07:43, Tsantilas Christos wrote:
> Hi all,
> currently the squid-smp is broken in squid-trunk.
> The squid kids crashing immediately after started. The first probelm is
> the "assertion failed: mem.cc:516: "MemPools[t]" " assertion which is
> fixed by Amos patch "[PATCH] Allow MemPool late initialization". This
> patch looks that solves this problem and should applied.

Okay. Thanks for the verify. Applied.

>
> After applying this patch someone will hit the bug 3264:
> http://bugs.squid-cache.org/show_bug.cgi?id=3264
> This bug too does not allow kids process to start processing requests.
> There is a patch attached here which (I believe) solves the problem.

Thank you.
>
> But now I am hitting the following assertion:
> assertion failed: Connection.cc:29: "fd < 0"
> The later problem looks that it has to do with file descriptors of the
> listening sockets.

"fd < 0" indicates something is failing to call conn->close() when
abandoning an open socket.

NP: close() is reentrant. So components can and should always close()
when they are sure the FD/socket must no longer be used.

I'm not very certain about SMP listening sockets, which process(es) are
safe to close() on reconfigure/shutdown? the unsafe ones must do fd=-1
to abandon the FD information explicitly before the conn object destructs.

What situations are you hitting "fd < 0" Christos?

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.14
   Beta testers wanted for 3.2.0.9