CLI start with multiple VCL on Varnish 6 Failed.
Guillaume Quintard
guillaume at varnish-software.com
Mon Sep 24 20:57:18 UTC 2018
test streamlined, commit bisected, issue created:
https://github.com/varnishcache/varnish-cache/issues/2782
I'll try to see what I can find once I have more time, unless someone looks
into it first
--
Guillaume Quintard
On Mon, Sep 24, 2018 at 7:37 PM BIGOT Adrien <adrien.bigot at smile.fr> wrote:
> Hi,
>
> Yesterday, I also tried manualy with varnish 6.1 and the first time I
> believed it was working. But after 1 or 2 minute (I think to a timeout) I
> had the same error : "Child not responding to CLI, killed it."
>
> Thanks Guillaume for your help !
>
> Regards,
>
> --
>
> Adrien Bigot
>
> Le 24/09/2018 à 18:58, Guillaume Quintard a écrit :
>
> Confirmed using a Dockerfile (weirdly it worked the first time when I did
> it manually), looks like we have a bug. I'll look into it
> --
> Guillaume Quintard
>
>
> On Tue, Sep 18, 2018 at 11:36 AM BIGOT Adrien <adrien.bigot at smile.fr>
> wrote:
>
>> Hello,
>>
>> Based on this blog article :
>> https://info.varnish-software.com/blog/one-vcl-per-domain I've been
>> using multiple VCL with Varnish 5.2 without any problem.
>> However, I don't manage to get it working with Varnish 6.
>>
>> I tried with the latest stable version on packagecloud.io and even with
>> the latest weekly-build.
>> Tested on Debian Strecth, Ubuntu 16.04 and Centos 7.
>>
>>
>> [root at ip-172-31-137-19 varnish]# varnishd -I start.cli -F -a :80 -f ''
>> Debug: Version: varnish-6.0.1 revision
>> 8d54bec5330c29304979ebf2c425ae14ab80493c
>> Debug: Platform:
>>
>> Linux,3.10.0-862.3.2.el7.x86_64,x86_64,-junix,-sdefault,-sdefault,-hcritbit
>> BEGIN of -I file processing
>> 200 326
>> -----------------------------
>> Varnish Cache CLI 1.0
>> -----------------------------
>>
>> Linux,3.10.0-862.3.2.el7.x86_64,x86_64,-junix,-sdefault,-sdefault,-hcritbit
>> varnish-6.0.1 revision 8d54bec5330c29304979ebf2c425ae14ab80493c
>>
>> Type 'help' for command list.
>> Type 'quit' to close CLI session.
>> Type 'start' to launch worker process.
>>
>> > vcl.load vcl-api-orig /etc/varnish/api.vcl
>> 200 14
>> VCL compiled.
>>
>> > vcl.load vcl-catz-orig /etc/varnish/catz.vcl
>> 200 14
>> VCL compiled.
>>
>> > vcl.label label-api vcl-api-orig
>> 200 0
>>
>> > vcl.label label-catz vcl-catz-orig
>> 200 0
>>
>> > vcl.load vcl-root-orig /etc/varnish/root.vcl
>> 200 14
>> VCL compiled.
>>
>> > vcl.use vcl-root-orig
>> 200 30
>> VCL 'vcl-root-orig' now active
>> END of -I file processing
>> CLI result = 400
>>
>>
>>
>> In the logs :
>>
>> On Centos
>> sept. 18 08:35:37 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx su[11820]:
>> pam_unix(su:session): session opened for user root by ec2-user(uid=0)
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> Version: varnish-6.0.1 revision 8d54bec5330c29304979ebf2c425ae14ab80493c
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> Platform:
>>
>> Linux,3.10.0-862.3.2.el7.x86_64,x86_64,-junix,-sdefault,-sdefault,-hcritbit
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> CLI -I file Rd vcl.load vcl-api-orig /etc/varnish/api.vcl
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> CLI -I file Wr 200 VCL compiled.
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> CLI -I file Rd vcl.load vcl-catz-orig /etc/varnish/catz.vcl
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> CLI -I file Wr 200 VCL compiled.
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> CLI -I file Rd vcl.label label-api vcl-api-orig
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> CLI -I file Wr 200
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> CLI -I file Rd vcl.label label-catz vcl-catz-orig
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> CLI -I file Wr 200
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> CLI -I file Rd vcl.load vcl-root-orig /etc/varnish/root.vcl
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> CLI -I file Wr 200 VCL compiled.
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> CLI -I file Rd vcl.use vcl-root-orig
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxxm varnishd[11846]:
>> CLI -I file Wr 200 VCL 'vcl-root-orig' now active
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> Child (11870) Started
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> Child (11870) not responding to CLI, killed it.
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> Child (11870) Pushing vcls failed:
>> CLI communication error
>> sept. 18 08:36:34 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> Stopping Child
>> sept. 18 08:36:35 ip-172-31-137-19.xxxxxxxxxxxxxxxxxxm varnishd[11846]:
>> Child (11870) died signal=3
>> sept. 18 08:36:35 ip-172-31-137-19.xxxxxxxxxxxxxxxxxx varnishd[11846]:
>> Child cleanup complete
>>
>> On Debian :
>> Sep 18 10:07:01 ip-172-31-137-84 varnishd[6783]: Child (6809) said Child
>> starts
>> Sep 18 10:07:01 ip-172-31-137-84 varnishd[6783]: Child cleanup complete
>> Sep 18 10:07:02 ip-172-31-137-84 varnishd[6816]: Version: varnish-6.0.1
>> revision 8d54bec5330c29304979ebf2c425ae14ab80493c
>> Sep 18 10:07:02 ip-172-31-137-84 varnishd[6816]: Platform:
>> Linux,4.9.0-8-amd64,x86_64,-junix,-sdefault,-sdefault,-hcritbit
>> Sep 18 10:07:02 ip-172-31-137-84 varnishd[6816]: CLI -I file Rd vcl.load
>> vcl-api-orig /etc/varnish/api.vcl
>> Sep 18 10:07:03 ip-172-31-137-84 varnishd[6816]: CLI -I file Wr 200 VCL
>> compiled.
>> Sep 18 10:07:03 ip-172-31-137-84 varnishd[6816]: CLI -I file Rd vcl.load
>> vcl-catz-orig /etc/varnish/catz.vcl
>> Sep 18 10:07:03 ip-172-31-137-84 varnishd[6816]: CLI -I file Wr 200 VCL
>> compiled.
>> Sep 18 10:07:03 ip-172-31-137-84 varnishd[6816]: CLI -I file Rd
>> vcl.label label-api vcl-api-orig
>> Sep 18 10:07:03 ip-172-31-137-84 varnishd[6816]: CLI -I file Wr 200
>> Sep 18 10:07:03 ip-172-31-137-84 varnishd[6816]: CLI -I file Rd
>> vcl.label label-catz vcl-catz-orig
>> Sep 18 10:07:03 ip-172-31-137-84 varnishd[6816]: CLI -I file Wr 200
>> Sep 18 10:07:03 ip-172-31-137-84 varnishd[6816]: CLI -I file Rd vcl.load
>> vcl-root-orig /etc/varnish/root.vcl
>> Sep 18 10:07:03 ip-172-31-137-84 varnishd[6816]: CLI -I file Wr 200 VCL
>> compiled.
>> Sep 18 10:07:03 ip-172-31-137-84 varnishd[6816]: CLI -I file Rd vcl.use
>> vcl-root-orig
>> Sep 18 10:07:03 ip-172-31-137-84 varnishd[6816]: CLI -I file Wr 200 VCL
>> 'vcl-root-orig' now active
>> Sep 18 10:07:03 ip-172-31-137-84 varnishd[6816]: Child (6842) Started
>> Sep 18 10:08:03 ip-172-31-137-84 varnishd[6816]: Child (6842) not
>> responding to CLI, killed it.
>> Sep 18 10:08:03 ip-172-31-137-84 varnishd[6816]: Child (6842) Pushing
>> vcls failed:
>> CLI communication
>> error (hdr)
>> Sep 18 10:08:03 ip-172-31-137-84 varnishd[6816]: Stopping Child
>> Sep 18 10:08:04 ip-172-31-137-84 varnishd[6816]: Child (6842) died
>> signal=3
>>
>>
>> Did anyone manage to get it working with varnish 6 ?
>>
>> Thank you.
>>
>> Best regards,
>>
>> --
>>
>> Bigot Adrien
>> _______________________________________________
>> varnish-misc mailing list
>> varnish-misc at varnish-cache.org
>> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20180924/35b60635/attachment-0001.html>
More information about the varnish-misc
mailing list