alex at bengler
Jul 3, 2010, 2:16 PM
Post #5 of 14
On Sat, Jul 3, 2010 at 11:04 PM, Per Buer <perbu [at] varnish-software> wrote:
> On Sat, Jul 3, 2010 at 7:59 PM, Alexander Staubo <alex [at] bengler> wrote:
>> On Sat, Jul 3, 2010 at 7:01 PM, Flavio Torres <fla_torres [at] yahoo> wrote:
>>> Hi Alexander,
>>> Have you seen this thread
>> Yes. That threads seems to be about a different problem.
> I don't think so. Try it.
I do think so:
(1) The child isn't segfaulting -- it's dying with signal 3 (SIGQUIT),
and only after the parent sends SIGKILL.
(2) I have already increased cli_timeout and decreased the maximum
number of threads, and it's not helping.
(3) The number of threads at the time that the child dies is not high.
After switching to malloc and increasing the cli_timeout, Varnish does
stay up for longer periods of time, but it's still dying at least once
>> In my case I don't have any panic messages in the log.
> You're sure you're looking in the right log?
>> Curiously, though, the child is dying with SIGQUIT.
> Are you setting diag_bitmap? That would make the master send QUIT.
varnish-misc mailing list
varnish-misc [at] varnish-cache