Re: locking SHMFILE in core failed: Cannot allocate memory

In message 3e3a0c981002231659h2181697bpd8b1ebf97707a...@mail.gmail.com, Tami Lee writes: When I start Varnishd, I got the error below. Varnish still seems to work, but what does the error message mean? More importantly, what may not be working? Notice: locking SHMFILE in core failed: Cannot

Varnish CLI user feedback, please.

I'm looking at the CLI/varnishadm stuff right now, and would like some feedback from you guys... Right now (in -trunk) we have these possible CLI configurations: A) no CLI at all. B) CLI on stdin (-d) C) CLI on TELNET (-T) D) CLI on call-back (-M) If the

RE: health check path doesn't change after VCL reload (2.0.6)

I remember seeing a post recently that mentioned that the old health checks are still performed as long as the old VCL is loaded. This is done to allow a quick switch back to the previous VCL. This seems likely from behavior I have seen. Jim -Original Message- From:

Re: health check path doesn't change after VCL reload (2.0.6)

That's great. Still, the VCL indicated as active had a different path for the health check. On Wed, Feb 24, 2010 at 3:24 PM, Poul-Henning Kamp p...@phk.freebsd.dkwrote: In message b6b8b6b71002241137j71ae210r35487c328e8f6...@mail.gmail.com, John N orman writes: We notice that after VCL is

Re: health check path doesn't change after VCL reload (2.0.6)

In message b6b8b6b71002241315w1c62022t1bf941d6f2cac...@mail.gmail.com, John N orman writes: Still, the VCL indicated as active had a different path for the health check. Hopefully both got probed ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since

host header altered by Varnish?

Sorry about all the questions . . . On my backend I want to redirect domain.com to www.domain.com I see Host: domain.com in both the RX and TX sections of the log . . . but the redirect isn't getting triggered. The backend is Apache, and the redirect directives are routine. RewriteCond

Re: health check path doesn't change after VCL reload (2.0.6)

No, only the former / old path. I'm not super-troubled right now because a Varnish restart did pick up the new path (but at the cost of my cache) -- but I'm a bit worried about the next time I have to change it. I will be changing the probe interval soon, so that will give me a chance to

Re: Varnish CLI user feedback, please.

On Wed, Feb 24, 2010 at 7:37 PM, Poul-Henning Kamp p...@phk.freebsd.dkwrote: I'm looking at the CLI/varnishadm stuff right now, and would like some feedback from you guys... Right now (in -trunk) we have these possible CLI configurations: A) no CLI at all. Probably useful for a

Re: host header altered by Varnish?

I have the same stuff on my backends and what you have here should work. The only thing I can think of from your example is a missing 'RewriteEngine on' on top. If I don't have that the rewriting is silently ignored by apache. On 24-Feb-2010 22:21, John Norman wrote: Sorry about all the

Varnish 2.0.6 nuking all my objects?

Howdy, We are finally getting around to upgrading to the latest version of varnish and are running into quite a weird problem. Everything works fine for a bit (1+day) , then all of a sudden Varnish starts nuking all of the objects from the cache: About 4 hours ago there were 1 million