Hi,
New to varnish so forgive me if this has been answered before. I tried
searching but mainly got instructions on how to maintain a boat :-)
I have defined a vcl_error stanza in my vcl that puts a "sorry, we're
currently maintaining the site" sign up, when all backends are sick.
I had a ch
I'm experimenting with a large varnish cache as a central master to
multiple front-end caches. The master having a long object grace and
a slower LRU interval. How long can I cache objects and keep them
available as graced objects? If a front end varnish cache receives an
object from a d
On Apr 29, 2009, at 9:30 AM, Nick Loman wrote:
> Michael S. Fischer wrote:
>> On Apr 29, 2009, at 9:22 AM, Poul-Henning Kamp wrote:
>>> In message <49f87de4.3040...@loman.net>, Nick Loman writes:
>>>
Has Varnish got a solution to this problem which does not involve
time-wait recycling? O
Michael S. Fischer wrote:
> On Apr 29, 2009, at 9:22 AM, Poul-Henning Kamp wrote:
>
>> In message <49f87de4.3040...@loman.net>, Nick Loman writes:
>>
>>> Has Varnish got a solution to this problem which does not involve
>>> time-wait recycling? One thing I've thought of is perhaps SO_REUSEADDR
>>>
Hi all,
I have a varnish config looking roughly like this:
backend be1 {
.host = "10.10.10.10";
.port = "80";
}
sub vcl_recv {
elseif (req.http.host ~ "^x.example.com") {
set req.http.Host = "host.example.com";
set req.backend = be1;
}
elseif (req.http.host ~ "^xi
On Apr 29, 2009, at 9:22 AM, Poul-Henning Kamp wrote:
> In message <49f87de4.3040...@loman.net>, Nick Loman writes:
>
>> Has Varnish got a solution to this problem which does not involve
>> time-wait recycling? One thing I've thought of is perhaps
>> SO_REUSEADDR
>> is used or could be used when
In message <49f87de4.3040...@loman.net>, Nick Loman writes:
>Has Varnish got a solution to this problem which does not involve
>time-wait recycling? One thing I've thought of is perhaps SO_REUSEADDR
>is used or could be used when Varnish makes connections to the backend?
Varnish tries as hard a
Hi there,
Has anyone come to a satisfactory solution to the issue of running out
of local port numbers when Varnish makes a connection to the backend server?
Under Linux, my understanding is the number of available port numbers
can be increased to a maximum of 64511 by setting
/proc/sys/net/ip
>> First of all, varnishtop -i TxURL hangs on my system, it shows 3-5
>> Entries,
>> then freez and uses nearly 100%cpu on one of 8. Have to kill the pid.
>> varnishtop with no args works.
>
> Ok, that's not good... I've seen varnishtop hang like that before,
> but not
> with CPU usage. I've ye
