Håvard Futsæter <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > We know what causes it, but it isn't trivial to fix without degrading
> > performance too much.
> Does this mean it is difficult to figure out a satisfactory solution
> at all? Or that you have a solu
Hi. I was wondering if there has been any change of status for this
issue ( that is, conflict between purging and timeout)?
Dag-Erling Smørgrav wrote:
> Håvard Futsæter <[EMAIL PROTECTED]> writes:
>> Hi. There have not been any replies to my previous mail (seen below),
>> and I was wondering if t
Håvard Futsæter <[EMAIL PROTECTED]> writes:
> Hi. There have not been any replies to my previous mail (seen below),
> and I was wondering if this was because my description of the problem
> was unclear? Or perhaps I did not supply enough data to find the
> source of the problem?
We know what cause
Hi. There have not been any replies to my previous mail (seen below),
and I was wondering if this was because my description of the problem
was unclear? Or perhaps I did not supply enough data to find the source
of the problem?
I would gladly have attached more log-data here, but I am afraid t
Dag-Erling Smørgrav wrote:
> Håvard Futsæter <[EMAIL PROTECTED]> writes:
>> Might this perhaps be an indication that Varnish gets into trouble
>> when it receives a request for a resource while the cached object for
>> this resource is beeing recycled?
>
> Sounds like it. Poul-Henning, could you
Håvard Futsæter <[EMAIL PROTECTED]> writes:
> Might this perhaps be an indication that Varnish gets into trouble
> when it receives a request for a resource while the cached object for
> this resource is beeing recycled?
Sounds like it. Poul-Henning, could you take a closer look at the
locking in
Thanks for the quick reply!
Dag-Erling Smørgrav wrote:
> Håvard Futsæter <[EMAIL PROTECTED]> writes:
>> This object is then requested and delivered from cache several times.
>> Then we see the following in the log, at a time immediately after
>> 14:59:27:
>>
>> 0 ExpPick138012248
>> 0 VCL_
Håvard Futsæter <[EMAIL PROTECTED]> writes:
> This object is then requested and delivered from cache several times.
> Then we see the following in the log, at a time immediately after
> 14:59:27:
>
> 0 ExpPick138012248
> 0 VCL_call timeout
> 0 VCL_return discard
vcl_timeout() is
We have a problem with the child process regularly dying and restarting.
We use Varnish in front of three backends, each serving different types
of content. One of these backends is quite slow, and initially we
thought the problem with the child process was related to this slow
backend. We hope
