varnish saint-mode

[Simon Males]

Back to your original problem, it's sounds like the VCL is failing to compile.

Using varnishadm, you get see the compiler error's on screen.

vcl.list
        List all loaded configuration.

In your case, you will only one, likely called 'boot', as your restart
varnish to load a vcl.

vcl.load <configname> <filename>
        Compile and load the VCL file under the name provided.

Here is an example of trying to compile a bogus VCL.

# varnishadm -S /etc/varnish/secret -T localhost:6082 vcl.load fail
/etc/varnish/default.vcl
Message from VCC-compiler:
Expected '.' got 'crap'
(program line 101), at
(input Line 3 Pos 9)
        crap code compiler fail
--------####-------------------



On Tue, Aug 23, 2011 at 11:52 PM, alexus <alexus at gmail.com> wrote:
> I'm not sure what am I suppose to do with that and how would that help me...
>
> [root at 6prx01 ~]# varnishadm help
> CLI connected to 127.0.0.1 6082
> help [command]
> ping [timestamp]
> auth response
> quit
> banner
> status
> start
> stop
> vcl.load <configname> <filename>
> vcl.inline <configname> <quoted_VCLstring>
> vcl.use <configname>
> vcl.discard <configname>
> vcl.list
> vcl.show <configname>
> param.show [-l] [<param>]
> param.set <param> <value>
> panic.show
> panic.clear
> storage.list
> ban.url <regexp>
> ban <field> <operator> <arg> [&& <field> <oper> <arg>]...
> ban.list
>
> [root at 6prx01 ~]#
>
>
> On Mon, Aug 22, 2011 at 9:15 PM, Simon Males <sime at sime.net.au> wrote:
>> On Tue, Aug 23, 2011 at 1:28 AM, alexus <alexus at gmail.com> wrote:
>>> I'm trying to implement "saint mode" into my default.vcl, I copy and
>>> paste that little snippet that came with that documentation but now my
>>> varnish wont even start.
>>>
>>> Misbehaving servers — Varnish version 3.0.0 documentation
>>> https://www.varnish-cache.org/docs/3.0/tutorial/handling_misbehaving_servers.html#saint-mode
>>>
>>> either I'm putting that into a wrong place or something else I dont
>>> know, all I know as soon as I comment it out, varnish starts Ok.
>>> any ideas how to troubleshoot it?
>>
>> You may have some compiler output in /tmp/*.varnish.
>>
>> Otherwise you can compile it on demand with a running varnishd:
>>
>> $ varnishadm -S /etc/varnish/secrect -T localhost:6082 vcl.load
>> name_the_vcl /etc/varnish/default.vcl
>>
>> (I'm using 2.1, so varnishadm in 3.0 may be different).
>>
>> Failure to compile will produce 'classic' compiler type output.
>>
>> Moons ago I had a problem when compiler would fail when I copied and
>> pasted something some the web, it felt like it was a funny line ending
>> character.


-- 
Simon Males