James Quacinella wrote:
> I use monit for monitoring programs. Here is a snippet I had used when
> monitoring a varnish install (too bad it never went into production;
> change values to you liking / environment):
>
A Billion thanks to you :)
I have been looking for a tool that could do this
Gaute Amundsen wrote:
> On Tuesday 03 July 2007 11:27, Dag-Erling Smørgrav wrote:
>
>>
>> I would recommend retrieving a page (or a set of pages). Simply
>> checking the pid won't help you if Varnish has gone off into la-la land,
>> or been SIGSTOPped or something.
>>
>> DES
>>
> Not what
On Tuesday 03 July 2007 11:27, Dag-Erling Smørgrav wrote:
> Gaute Amundsen <[EMAIL PROTECTED]> writes:
> > Now the question is, how do I best detect if varnsih should have a
> > problem? Would it be reasonably reliable to just chek if the pid from
> > /var/run/varnish.pid is running, do I need to
Gaute Amundsen <[EMAIL PROTECTED]> writes:
> Now the question is, how do I best detect if varnsih should have a
> problem? Would it be reasonably reliable to just chek if the pid from
> /var/run/varnish.pid is running, do I need to fetch a page, or is
> there some better way?
I would recommend re
- Gaute Amundsen <[EMAIL PROTECTED]> wrote:
> I have come to understand that in some builds under some conditions
> varnish
> may hang or a crash. (we run 1.0.4-3el4.i386.rpm)
Hi Gaute,
I'll just say that in my experience Varnish has proven itself to be extremely
stable. We actually run 1.0
I have come to understand that in some builds under some conditions varnish
may hang or a crash. (we run 1.0.4-3el4.i386.rpm)
I have now routed all our ~180 sites troug varnish, pipe by default, cached
for selected hostnames. Talk a bout all ones eggs in one basket :)
The way it is all set up,
