Blew away .../var/varnish/HOSTNAME/ -- broke varnishstat, how to recover?

2008-06-02 Thread Chris Shenton
We're using varnish for a public site, works beautifully and handled  
getting slashdotted gracefully -- many thanks!

We built it with zc.buildout which creates .../parts/varnish/install/ 
var/varnish/FQDN/... and others.  In a recent update, I accidentally  
blew away the .../var/varnish/FQDN directory which contained a few  
files that seem necessary for varnishstat and perhaps others to work.

  bin.XXkP5ZYv
  _.c
  _.vsl

$ varnishstat
Cannot open /usr/local/mastersite_buildout/parts/varnish/install/var/ 
varnish/FQDN/_.vsl: No such file or directory

Varnish continues to serve well, so I haven't restarted.

What's the recommended way to re-create this directory?  I'm assuming  
restarting Varnish will re-create it but want to be sure.

We have to fill out pounds of paperwork in order to take any outage on  
a public server, no matter how small.  Is there a way to restart  
Varnish without any downtime -- to continue accepting but holding  
connections until restarted, rather like Apache's apachectl graceful  
does?  Other ideas?

Thanks.

___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc


Re: Blew away .../var/varnish/HOSTNAME/ -- broke varnishstat, how to recover?

2008-06-02 Thread Chris Shenton

On Jun 2, 2008, at 11:19 AM, Poul-Henning Kamp wrote:

 Yes, restarting varnish (completely: ie both manager and child  
 process)
 should recreate it with no side effects.

 Varnish doesn't spend long time on startup, so I would just get it
 done and over with.

Just tried it on a QA server and it restarts in about 0.25 seconds,  
and re-creates the directory with the _.vsl file.  Have to see if my  
overlords are OK with that.  Thanks.


 (In the meantime, if you have enabled the telnet option, you can still
 see the stats through the CLI interface.)

I do have that and can ask it for stats. Thanks for the reminder. 
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc


Re: Blew away .../var/varnish/HOSTNAME/ -- broke varnishstat, how to recover?

2008-06-02 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Chris Shenton write
s:

What's the recommended way to re-create this directory?  I'm assuming  
restarting Varnish will re-create it but want to be sure.

Yes, restarting varnish (completely: ie both manager and child process)
should recreate it with no side effects.

We have to fill out pounds of paperwork in order to take any outage on  
a public server, no matter how small.  Is there a way to restart  
Varnish without any downtime -- to continue accepting but holding  
connections until restarted, rather like Apache's apachectl graceful  
does?  Other ideas?

Varnish doesn't spend long time on startup, so I would just get it
done and over with.

You are in no rush however, so you can schedule it for whenever
you want.

(In the meantime, if you have enabled the telnet option, you can still
see the stats through the CLI interface.)

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc


Re: Blew away .../var/varnish/HOSTNAME/ -- broke varnishstat, how to recover?

2008-06-02 Thread Michael S. Fischer
On Mon, Jun 2, 2008 at 7:57 AM, Chris Shenton [EMAIL PROTECTED]
wrote:

 We have to fill out pounds of paperwork in order to take any outage on
 a public server, no matter how small.  Is there a way to restart
 Varnish without any downtime -- to continue accepting but holding
 connections until restarted, rather like Apache's apachectl graceful
 does?  Other ideas?


Can you avoid the problem by putting your Varnish servers behind a load
balancer?  That way, you can preemptively disable the server from taking
traffic on the LB side prior to restarting Varnish, thereby eliminating any
perceivable customer effect.

Also, be careful about using apachectl graceful (especially combined with
log rotation), as connections that are currently idle but which may never
receive traffic again will not be terminated.  I consider it too leaky to
use.

Best regards,

--Michael
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc