From hrhosseini at hotmail.com Sat Feb 13 10:44:26 2021 From: hrhosseini at hotmail.com (Hamidreza Hosseini) Date: Sat, 13 Feb 2021 10:44:26 +0000 Subject: varnish crush every 30 minutes in high pressure In-Reply-To: References: Message-ID: Hi guys, I want to upgrade my varnish but I didnt know what is difference between varnish 6.0.* and 6.5.* ! Are varnish 6.0.* LTS versions and varnish 6.5.* the latest? which major version should I install for production? ________________________________ From: Hamidreza Hosseini Sent: Saturday, September 26, 2020 3:39 AM To: varnish-misc at varnish-cache.org Subject: varnish crush every 30 minutes in high pressure Hi Im using varnish , before i hadn't any problem in varnish but today after crushing my dns (I fixed it now) and in high pressure , it restart whole machine almost every 30 minutes even Netdata that i'm using for monitoring and it shows in service status: Sep 26 13:49:48 varnish-1 varnishd[945]: Child (1548) not responding to CLI, killed it. Sep 26 13:49:48 varnish-1 varnishd[945]: Unexpected reply from ping: 400 CLI communication error (hdr) Sep 26 13:49:48 varnish-1 varnishd[945]: Child (1548) died signal=9 What should i do for this problem? My varnish version: varnishd (varnish-6.0.5 revision 3065ccaacc4bb537fb976a524bd808db42c5fe40) Copyright (c) 2006 Verdens Gang AS Copyright (c) 2006-2019 Varnish Software AS -------------- next part -------------- An HTML attachment was scrubbed... URL: From hrhosseini at hotmail.com Sat Feb 13 11:56:35 2021 From: hrhosseini at hotmail.com (Hamidreza Hosseini) Date: Sat, 13 Feb 2021 11:56:35 +0000 Subject: Upgrade varnish version Message-ID: Hi, I want to upgrade my varnish but I didnt know what is difference between varnish 6.0.* and 6.5.* ! Are varnish 6.0.* LTS versions and varnish 6.5.* the latest? which major version should I install for production? -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume at varnish-software.com Sat Feb 13 15:51:53 2021 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Sat, 13 Feb 2021 07:51:53 -0800 Subject: varnish crush every 30 minutes in high pressure In-Reply-To: References: Message-ID: Hi, Go with the LTS unless you need features from 6.5, it will be supported for a longer time. Cheers, On Sat, Feb 13, 2021, 02:45 Hamidreza Hosseini wrote: > Hi guys, > I want to upgrade my varnish but I didnt know what is difference between > varnish 6.0.* and 6.5.* ! > Are varnish 6.0.* LTS versions and varnish 6.5.* the latest? > which major version should I install for production? > ------------------------------ > *From:* Hamidreza Hosseini > *Sent:* Saturday, September 26, 2020 3:39 AM > *To:* varnish-misc at varnish-cache.org > *Subject:* varnish crush every 30 minutes in high pressure > > > Hi > Im using varnish , before i hadn't any problem in varnish but today after > crushing my dns (I fixed it now) and in high pressure , it > restart whole machine almost every 30 minutes even Netdata that i'm using > for monitoring and it shows in service status: > > Sep 26 13:49:48 varnish-1 varnishd[945]: Child (1548) not responding to CLI, killed it. > Sep 26 13:49:48 varnish-1 varnishd[945]: Unexpected reply from ping: 400 CLI communication error (hdr) > Sep 26 13:49:48 varnish-1 varnishd[945]: Child (1548) died signal=9 > > > What should i do for this problem? > My varnish version: > > varnishd (varnish-6.0.5 revision 3065ccaacc4bb537fb976a524bd808db42c5fe40) > Copyright (c) 2006 Verdens Gang AS > Copyright (c) 2006-2019 Varnish Software AS > > > _______________________________________________ > 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: From hrhosseini at hotmail.com Sun Feb 14 16:53:06 2021 From: hrhosseini at hotmail.com (Hamidreza Hosseini) Date: Sun, 14 Feb 2021 16:53:06 +0000 Subject: Problem in varnish-6.0.7 Message-ID: I have migrate from varnish 6.0.5 to 6.0.7 but it could not run with this errro: ``` ? varnish.service - Varnish HTTP accelerator Loaded: loaded (/etc/systemd/system/varnish.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2021-02-14 20:15:14 +0330; 4s ago Docs: https://www.varnish-cache.org/docs/4.1/ man:varnishd Process: 29630 ExecStart=/usr/sbin/varnishd -j unix,user=vcache -F -a :6081 -T localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret -s malloc,1g -i ubuntu-test (code=exited, status=2) Main PID: 29630 (code=exited, status=2) Feb 14 20:15:14 ubuntu-test varnishd[29630]: ------------############- Feb 14 20:15:14 ubuntu-test varnishd[29630]: In backend specification starting at: Feb 14 20:15:14 ubuntu-test varnishd[29630]: ('/etc/varnish/default.vcl' Line 5 Pos 1) Feb 14 20:15:14 ubuntu-test varnishd[29630]: backend default { Feb 14 20:15:14 ubuntu-test varnishd[29630]: #######---------- Feb 14 20:15:14 ubuntu-test varnishd[29630]: Running VCC-compiler failed, exited with 2 Feb 14 20:15:14 ubuntu-test varnishd[29630]: VCL compilation failed Feb 14 20:15:14 ubuntu-test systemd[1]: varnish.service: Main process exited, code=exited, status=2/INVALIDARGUMENT ``` Some part of my config: ``` vcl 4.1; import directors; backend default { .host = "test-lb"; .port = "8000"; } backend test_1 { .host = "test-1"; .port = "8000"; } backend test_2 { .host = "test-2"; .port = "8000"; } backend test_3 { .host = "test-3"; .port = "8000"; } backend test_4 { .host = "test-4"; .port = "8000"; } backend test_5 { .host = "test-5"; .port = "8000"; } backend test_6 { .host = "test-6"; .port = "8000"; } ``` -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume at varnish-software.com Sun Feb 14 17:05:24 2021 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Sun, 14 Feb 2021 09:05:24 -0800 Subject: Problem in varnish-6.0.7 In-Reply-To: References: Message-ID: Hi, That error seems truncated, can you try to run this in your terminal please: ``` varnishd -C -f /etc/varnish/default.vcl ``` This will perform only the VCL->C translation and should provide a more complete message. Cheers, -- Guillaume Quintard On Sun, Feb 14, 2021 at 8:54 AM Hamidreza Hosseini wrote: > I have migrate from varnish 6.0.5 to 6.0.7 but it could not run with this > errro: > > ``` > ? varnish.service - Varnish HTTP accelerator > Loaded: loaded (/etc/systemd/system/varnish.service; enabled; vendor > preset: enabled) > Active: failed (Result: exit-code) since Sun 2021-02-14 20:15:14 +0330; > 4s ago > Docs: https://www.varnish-cache.org/docs/4.1/ > man:varnishd > Process: 29630 ExecStart=/usr/sbin/varnishd -j unix,user=vcache -F -a > :6081 -T localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret > -s malloc,1g -i ubuntu-test (code=exited, status=2) > Main PID: 29630 (code=exited, status=2) > > Feb 14 20:15:14 ubuntu-test varnishd[29630]: ------------############- > Feb 14 20:15:14 ubuntu-test varnishd[29630]: In backend specification > starting at: > Feb 14 20:15:14 ubuntu-test varnishd[29630]: ('/etc/varnish/default.vcl' > Line 5 Pos 1) > Feb 14 20:15:14 ubuntu-test varnishd[29630]: backend default { > Feb 14 20:15:14 ubuntu-test varnishd[29630]: #######---------- > Feb 14 20:15:14 ubuntu-test varnishd[29630]: Running VCC-compiler failed, > exited with 2 > Feb 14 20:15:14 ubuntu-test varnishd[29630]: VCL compilation failed > Feb 14 20:15:14 ubuntu-test systemd[1]: varnish.service: Main process > exited, code=exited, status=2/INVALIDARGUMENT > ``` > > Some part of my config: > > ``` > vcl 4.1; > > import directors; > > backend default { > .host = "test-lb"; > .port = "8000"; > } > > backend test_1 { .host = "test-1"; .port = "8000"; } > backend test_2 { .host = "test-2"; .port = "8000"; } > backend test_3 { .host = "test-3"; .port = "8000"; } > backend test_4 { .host = "test-4"; .port = "8000"; } > backend test_5 { .host = "test-5"; .port = "8000"; } > backend test_6 { .host = "test-6"; .port = "8000"; } > ``` > > _______________________________________________ > 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: From guillaume at varnish-software.com Sun Feb 14 17:22:36 2021 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Sun, 14 Feb 2021 09:22:36 -0800 Subject: Problem in varnish-6.0.7 In-Reply-To: References: Message-ID: re-adding the mailing-list so people know it's fixed for vcl version, try using 4.1, it's the latest one, and there's no major difference with 4.0. -- Guillaume Quintard On Sun, Feb 14, 2021 at 9:16 AM Hamidreza Hosseini wrote: > Thanks for your help, > It was my problem, varnishd -C -f /etc/varnish/default.vcl shows I didn't > set my server names to dns > > And now it is working: > > ``` > Docs: https://www.varnish-cache.org/docs/4.1/ > man:varnishd > Main PID: 2765 (varnishd) > Tasks: 217 > Memory: 83.9M > CPU: 494ms > CGroup: /system.slice/varnish.service > ??2765 /usr/sbin/varnishd -j unix,user=vcache -F -a :6081 -T > localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret -s > malloc,1g -i ubuntu-test > ??2780 /usr/sbin/varnishd -j unix,user=vcache -F -a :6081 -T > localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret -s > malloc,1g -i ubuntu-test > > Feb 14 20:43:34 ubuntu-test varnishd[2765]: Warnings: > Feb 14 20:43:34 ubuntu-test varnishd[2765]: VCL compiled. > Feb 14 20:43:34 ubuntu-test varnishd[2765]: Debug: Version: varnish-6.0.7 > revision 525d371e3ea0e0c38edd7baf0f80dc226560f26e > Feb 14 20:43:34 ubuntu-test varnishd[2765]: Version: varnish-6.0.7 > revision 525d371e3ea0e0c38edd7baf0f80dc226560f26e > Feb 14 20:43:34 ubuntu-test varnishd[2765]: Debug: Platform: > Linux,4.4.0-186-generic,x86_64,-junix,-smalloc,-sdefault,-hcritbit > Feb 14 20:43:34 ubuntu-test varnishd[2765]: Platform: > Linux,4.4.0-186-generic,x86_64,-junix,-smalloc,-sdefault,-hcritbit > Feb 14 20:43:34 ubuntu-test varnishd[2765]: Debug: Child (2780) Started > Feb 14 20:43:34 ubuntu-test varnishd[2765]: Child (2780) Started > Feb 14 20:43:34 ubuntu-test varnishd[2765]: Info: Child (2780) said Child > starts > Feb 14 20:43:34 ubuntu-test varnishd[2765]: Child (2780) said Child starts > ``` > > But first I thoght it is because of VCL version > I read in doc 6.0 you wrote vcl4.0 for this version but I'm using vcl4.1 > Which one is prefered to use in 6.0.7 version? > > ------------------------------ > *From:* Guillaume Quintard > *Sent:* Sunday, February 14, 2021 9:05 AM > *To:* Hamidreza Hosseini > *Cc:* varnish-misc at varnish-cache.org > *Subject:* Re: Problem in varnish-6.0.7 > > Hi, > > That error seems truncated, can you try to run this in your terminal > please: > > ``` > varnishd -C -f /etc/varnish/default.vcl > ``` > > This will perform only the VCL->C translation and should provide a more > complete message. > > Cheers, > > -- > Guillaume Quintard > > > On Sun, Feb 14, 2021 at 8:54 AM Hamidreza Hosseini > wrote: > > I have migrate from varnish 6.0.5 to 6.0.7 but it could not run with this > errro: > > ``` > ? varnish.service - Varnish HTTP accelerator > Loaded: loaded (/etc/systemd/system/varnish.service; enabled; vendor > preset: enabled) > Active: failed (Result: exit-code) since Sun 2021-02-14 20:15:14 +0330; > 4s ago > Docs: https://www.varnish-cache.org/docs/4.1/ > man:varnishd > Process: 29630 ExecStart=/usr/sbin/varnishd -j unix,user=vcache -F -a > :6081 -T localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret > -s malloc,1g -i ubuntu-test (code=exited, status=2) > Main PID: 29630 (code=exited, status=2) > > Feb 14 20:15:14 ubuntu-test varnishd[29630]: ------------############- > Feb 14 20:15:14 ubuntu-test varnishd[29630]: In backend specification > starting at: > Feb 14 20:15:14 ubuntu-test varnishd[29630]: ('/etc/varnish/default.vcl' > Line 5 Pos 1) > Feb 14 20:15:14 ubuntu-test varnishd[29630]: backend default { > Feb 14 20:15:14 ubuntu-test varnishd[29630]: #######---------- > Feb 14 20:15:14 ubuntu-test varnishd[29630]: Running VCC-compiler failed, > exited with 2 > Feb 14 20:15:14 ubuntu-test varnishd[29630]: VCL compilation failed > Feb 14 20:15:14 ubuntu-test systemd[1]: varnish.service: Main process > exited, code=exited, status=2/INVALIDARGUMENT > ``` > > Some part of my config: > > ``` > vcl 4.1; > > import directors; > > backend default { > .host = "test-lb"; > .port = "8000"; > } > > backend test_1 { .host = "test-1"; .port = "8000"; } > backend test_2 { .host = "test-2"; .port = "8000"; } > backend test_3 { .host = "test-3"; .port = "8000"; } > backend test_4 { .host = "test-4"; .port = "8000"; } > backend test_5 { .host = "test-5"; .port = "8000"; } > backend test_6 { .host = "test-6"; .port = "8000"; } > ``` > > _______________________________________________ > 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: From hrhosseini at hotmail.com Sun Feb 14 17:30:58 2021 From: hrhosseini at hotmail.com (Hamidreza Hosseini) Date: Sun, 14 Feb 2021 17:30:58 +0000 Subject: Problem in varnish-6.0.7 In-Reply-To: References: Message-ID: Thanks for your help, It was my problem, varnishd -C -f /etc/varnish/default.vcl shows I didn't set my server names to dns And now it is working: ``` Docs: https://www.varnish-cache.org/docs/4.1/ man:varnishd Main PID: 2765 (varnishd) Tasks: 217 Memory: 83.9M CPU: 494ms CGroup: /system.slice/varnish.service ??2765 /usr/sbin/varnishd -j unix,user=vcache -F -a :6081 -T localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret -s malloc,1g -i ubuntu-test ??2780 /usr/sbin/varnishd -j unix,user=vcache -F -a :6081 -T localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret -s malloc,1g -i ubuntu-test Feb 14 20:43:34 ubuntu-test varnishd[2765]: Warnings: Feb 14 20:43:34 ubuntu-test varnishd[2765]: VCL compiled. Feb 14 20:43:34 ubuntu-test varnishd[2765]: Debug: Version: varnish-6.0.7 revision 525d371e3ea0e0c38edd7baf0f80dc226560f26e Feb 14 20:43:34 ubuntu-test varnishd[2765]: Version: varnish-6.0.7 revision 525d371e3ea0e0c38edd7baf0f80dc226560f26e Feb 14 20:43:34 ubuntu-test varnishd[2765]: Debug: Platform: Linux,4.4.0-186-generic,x86_64,-junix,-smalloc,-sdefault,-hcritbit Feb 14 20:43:34 ubuntu-test varnishd[2765]: Platform: Linux,4.4.0-186-generic,x86_64,-junix,-smalloc,-sdefault,-hcritbit Feb 14 20:43:34 ubuntu-test varnishd[2765]: Debug: Child (2780) Started Feb 14 20:43:34 ubuntu-test varnishd[2765]: Child (2780) Started Feb 14 20:43:34 ubuntu-test varnishd[2765]: Info: Child (2780) said Child starts Feb 14 20:43:34 ubuntu-test varnishd[2765]: Child (2780) said Child starts ``` ________________________________ From: Hamidreza Hosseini Sent: Sunday, February 14, 2021 8:53 AM To: varnish-misc at varnish-cache.org Subject: Problem in varnish-6.0.7 I have migrate from varnish 6.0.5 to 6.0.7 but it could not run with this errro: ``` ? varnish.service - Varnish HTTP accelerator Loaded: loaded (/etc/systemd/system/varnish.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2021-02-14 20:15:14 +0330; 4s ago Docs: https://www.varnish-cache.org/docs/4.1/ man:varnishd Process: 29630 ExecStart=/usr/sbin/varnishd -j unix,user=vcache -F -a :6081 -T localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret -s malloc,1g -i ubuntu-test (code=exited, status=2) Main PID: 29630 (code=exited, status=2) Feb 14 20:15:14 ubuntu-test varnishd[29630]: ------------############- Feb 14 20:15:14 ubuntu-test varnishd[29630]: In backend specification starting at: Feb 14 20:15:14 ubuntu-test varnishd[29630]: ('/etc/varnish/default.vcl' Line 5 Pos 1) Feb 14 20:15:14 ubuntu-test varnishd[29630]: backend default { Feb 14 20:15:14 ubuntu-test varnishd[29630]: #######---------- Feb 14 20:15:14 ubuntu-test varnishd[29630]: Running VCC-compiler failed, exited with 2 Feb 14 20:15:14 ubuntu-test varnishd[29630]: VCL compilation failed Feb 14 20:15:14 ubuntu-test systemd[1]: varnish.service: Main process exited, code=exited, status=2/INVALIDARGUMENT ``` Some part of my config: ``` vcl 4.1; import directors; backend default { .host = "test-lb"; .port = "8000"; } backend test_1 { .host = "test-1"; .port = "8000"; } backend test_2 { .host = "test-2"; .port = "8000"; } backend test_3 { .host = "test-3"; .port = "8000"; } backend test_4 { .host = "test-4"; .port = "8000"; } backend test_5 { .host = "test-5"; .port = "8000"; } backend test_6 { .host = "test-6"; .port = "8000"; } ``` -------------- next part -------------- An HTML attachment was scrubbed... URL: From mlechner at bfs.de Mon Feb 15 09:10:10 2021 From: mlechner at bfs.de (Marco Lechner) Date: Mon, 15 Feb 2021 09:10:10 +0000 Subject: Download paths of varnish.tgz include random string Message-ID: <2612346f1df24dfb9fc690b8e0288613@bfs.de> Hallo, since a while a varnish Release is not available on a clear-url basis like http://varnish-cache.org/_downloads/varnish-6.0.5.tgz with just the release verison as mutable , but has a generated random string as part o the link like https://varnish-cache.org/_downloads/41841608341add28256b374dc367af04/varnish-6.0.7.tgz Am I just missing an redirect (well https://varnish-cache.org/_downloads/varnish-6.0.7.tgz does not work anymore) Or do I have to look fort he specific URL all the time I update any build jobs in my CI environment? It was very comfortable just having to add the release number to any automatic build workflows Best regards i.A. Dr. Marco Lechner Leiter Fachgebiet RN 1 ? Head RN 1 -- Bundesamt f?r Strahlenschutz ? Federal Office for Radiation Protection Koordination Notfallschutzsysteme ? Coordination Emergency Systems ? RN 1 Rosastr. 9 D-79098 Freiburg Tel.: +49 30 18333-6724 Coronakontakt: +49 7661 9098245 E-Mail: mlechner at bfs.de www.bfs.de Abonnieren Sie den BfS-Newsletter ?StrahlenschutzAktuell? Folgen Sie uns auf Twitter Informationen zum Datenschutz gem?? Artikel 13 DSGVO finden Sie unter: www.bfs.de/datenschutz | Information concerning data protection in pursuance of section 13 GDPR can be found at: www.bfs.de/privacy-policy -- Hinweis zu Anh?ngen die auf .p7m/.p7c/.p7s oder .asc/.asc.sig enden: Die .p7?- und .asc-Dateien sind ungef?hrliche Signaturdateien (digitale Unterschriften). In E-Mail-Clients mit S/MIME Konfiguration (.p7?) oder PGP-Erweiterung (.asc) dienen sie zur: - ?berpr?fung des Absenders - ?berpr?fung einer evtl. Ver?nderung des Inhalts w?hrend der ?bermittlung ?ber das Internet Die Signaturdateien k?nnen ebenso dazu verwendet werden dem Absender dieser Signatur eine E-Mail mit verschl?sseltem Inhalt zu senden. In E-Mail-Clients ohne S/MIME Konfiguration oder PGP-Erweiterung erscheinen die Dateien als Anhang und k?nnen ignoriert werden. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dridi at varni.sh Mon Feb 15 09:18:26 2021 From: dridi at varni.sh (Dridi Boukelmoune) Date: Mon, 15 Feb 2021 09:18:26 +0000 Subject: Download paths of varnish.tgz include random string In-Reply-To: <2612346f1df24dfb9fc690b8e0288613@bfs.de> References: <2612346f1df24dfb9fc690b8e0288613@bfs.de> Message-ID: On Mon, Feb 15, 2021 at 9:12 AM Marco Lechner wrote: > > Hallo, > > since a while a varnish Release is not available on a clear-url basis like > http://varnish-cache.org/_downloads/varnish-6.0.5.tgz > with just the release verison as mutable , but has a generated random string as part o the link like > https://varnish-cache.org/_downloads/41841608341add28256b374dc367af04/varnish-6.0.7.tgz > Am I just missing an redirect (well https://varnish-cache.org/_downloads/varnish-6.0.7.tgz does not work anymore) > Or do I have to look fort he specific URL all the time I update any build jobs in my CI environment? > > It was very comfortable just having to add the release number to any automatic build workflows Hallo, This is a known issue caused by a sphinx upgrade: https://github.com/varnishcache/varnish-cache/issues/3455 It looks like it broke again, but we haven't committed to a long-term solution yet. I'll bring it up today. Thanks, Dridi From phk at phk.freebsd.dk Mon Feb 15 09:21:03 2021 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Mon, 15 Feb 2021 09:21:03 +0000 Subject: Download paths of varnish.tgz include random string In-Reply-To: <2612346f1df24dfb9fc690b8e0288613@bfs.de> References: <2612346f1df24dfb9fc690b8e0288613@bfs.de> Message-ID: <76393.1613380863@critter.freebsd.dk> -------- Hi Marco, Yes, it's known issue and I forgot to apply the workaround last time I updated our server. See: https://github.com/varnishcache/varnish-cache/issues/3455 Fix in process, it should work in a few minutes. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk at FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From hrhosseini at hotmail.com Thu Feb 18 12:49:41 2021 From: hrhosseini at hotmail.com (Hamidreza Hosseini) Date: Thu, 18 Feb 2021 12:49:41 +0000 Subject: Varnish Health check Message-ID: Hi, I want to adjust health check on my varnish backends, But I dont know how can I know they are healthy or not because the nodes are up and running and even service is up but varnish does'nt work for all requests (just third of them are responding till I restart it (It happens sometimes)). How can I check this? ``` backend server1 { .host = "server1.example.com"; .probe = { .request = "HEAD / HTTP/1.1" "Connection: close" "User-Agent: Varnish Health Probe"; .timeout = 1s; .interval = 5s; .window = 5; .threshold = 3; } } ``` -------------- next part -------------- An HTML attachment was scrubbed... URL: From hrhosseini at hotmail.com Thu Feb 18 13:31:57 2021 From: hrhosseini at hotmail.com (Hamidreza Hosseini) Date: Thu, 18 Feb 2021 13:31:57 +0000 Subject: How to adjust priority for both backend healthy Message-ID: I have two backend that both of them are healthy and I use fallback for them and I want to say all request should goes to backend1 and if backend1 become unhealthy all requests should go to backend2 but backend1 has higher priority and when backend1 become healthy, all requests should go to backend1, How can I define priority? my config: ``` vcl 4.1; import directors; probe myprobe { .request = "HEAD / HTTP/1.1" "Connection: close" "User-Agent: Varnish Health Probe"; .timeout = 1s; .interval = 5s; .window = 5; .threshold = 3; } backend backend1 { .host = "backend1"; .port = "8080"; .probe = myprobe; } backend backend2 { .host = "backend2"; .port = "8080"; .probe = myprobe; } backend backend3 { .host = "backend3"; .port = "8080"; .probe = myprobe; } sub vcl_init { new backend2_cluster = directors.round_robin(); backend2_cluster.add_backend(backend2); backend3_cluster.add_backend(backend3); new backend_cluster_fb = directors.fallback(); backend1_fb.add_backend(backend1); backend2_cluster_fb.add_backend(backend2_cluster.backend()); } sub vcl_recv { set req.backend_hint = backend_cluster_fb.backend(); } ``` -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume at varnish-software.com Thu Feb 18 15:00:23 2021 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Thu, 18 Feb 2021 07:00:23 -0800 Subject: Varnish Health check In-Reply-To: References: Message-ID: Hi, The answer will be highly dependent on your setup, usually you want to find a probe request that will truly test the backend. One option, if you have control over the backend is to write a page to test the subsystem and make sure everybody's up. This link may prove useful: https://info.varnish-software.com/blog/backends-load-balancing -- Guillaume Quintard On Thu, Feb 18, 2021 at 4:51 AM Hamidreza Hosseini wrote: > Hi, > I want to adjust health check on my varnish backends, But I dont know how > can I know they are healthy or not > because the nodes are up and running and even service is up but varnish > does'nt work for all requests (just third of them are responding till I > restart it (It happens sometimes)). > How can I check this? > ``` > backend server1 { > .host = "server1.example.com"; > .probe = { > .request = > "HEAD / HTTP/1.1" > "Connection: close" > "User-Agent: Varnish Health Probe"; > .timeout = 1s; > .interval = 5s; > .window = 5; > .threshold = 3; > } > } > ``` > _______________________________________________ > 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: From noelle at uni-wuppertal.de Thu Feb 18 15:08:10 2021 From: noelle at uni-wuppertal.de (=?UTF-8?Q?Christian_N=c3=b6lle?=) Date: Thu, 18 Feb 2021 16:08:10 +0100 Subject: Varnish Health check In-Reply-To: References:

Message-ID: <3f481b60-67ea-1c09-4d52-f34978efda4d@uni-wuppertal.de> Hi everybody, Am 18.02.2021 um 16:00 schrieb Guillaume Quintard: >> I want to adjust health check on my varnish backends, But I dont know >> how can I know they are healthy or not > The answer will be highly dependent on your setup, usually you want > to find a probe request that will truly test the backend. One option, > if you have control over the backend is to write a page to test the > subsystem and make sure everybody's up. True. It definitely is important to have a close look at the system that you are performing the health check on. We are running a php based cms and are running a health check on a small script. That script is testing if there is an active db, if the rendering engine of the cms is responding and if everthing is fine. it is returning a "1". If not, it will exit and the probe fails, rendering the backend as sick. -- -c -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5344 bytes Desc: S/MIME Cryptographic Signature URL: From hrhosseini at hotmail.com Thu Feb 18 15:10:09 2021 From: hrhosseini at hotmail.com (Hamidreza Hosseini) Date: Thu, 18 Feb 2021 15:10:09 +0000 Subject: How to adjust priority for both backend healthy In-Reply-To: References: Message-ID: How can I probe a backend varnish? for example I have 2 layer varnish disk layer and ram layer and ram layer want to check the health of layer 2, How can I do this? I've done something but I have error: sudo varnishadm backend.list -p Backend name Admin Probe Last updated boot.varnish_1 probe Sick 0/5 Current states good: 0 threshold: 3 window: 5 Average response time of good probes: 0.000000 Oldest ================================================== Newest ---------------------------------------------------------------- Happy sudo varnishlog -g raw -i Backend_health 0 Backend_health - boot.varnish_1 Still sick -------- 0 3 5 0.000000 0.000000 Open error 111 (Connection refused) my config: probe myprobe { .request = "HEAD / HTTP/1.1" "Connection: close" "User-Agent: Varnish Health Probe"; .timeout = 1s; .interval = 5s; .window = 5; .threshold = 3; } ________________________________ From: Hamidreza Hosseini Sent: Thursday, February 18, 2021 5:31 AM To: varnish-misc at varnish-cache.org Subject: How to adjust priority for both backend healthy I have two backend that both of them are healthy and I use fallback for them and I want to say all request should goes to backend1 and if backend1 become unhealthy all requests should go to backend2 but backend1 has higher priority and when backend1 become healthy, all requests should go to backend1, How can I define priority? my config: ``` vcl 4.1; import directors; probe myprobe { .request = "HEAD / HTTP/1.1" "Connection: close" "User-Agent: Varnish Health Probe"; .timeout = 1s; .interval = 5s; .window = 5; .threshold = 3; } backend backend1 { .host = "backend1"; .port = "8080"; .probe = myprobe; } backend backend2 { .host = "backend2"; .port = "8080"; .probe = myprobe; } backend backend3 { .host = "backend3"; .port = "8080"; .probe = myprobe; } sub vcl_init { new backend2_cluster = directors.round_robin(); backend2_cluster.add_backend(backend2); backend3_cluster.add_backend(backend3); new backend_cluster_fb = directors.fallback(); backend1_fb.add_backend(backend1); backend2_cluster_fb.add_backend(backend2_cluster.backend()); } sub vcl_recv { set req.backend_hint = backend_cluster_fb.backend(); } ``` -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume at varnish-software.com Thu Feb 18 15:18:21 2021 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Thu, 18 Feb 2021 07:18:21 -0800 Subject: How to adjust priority for both backend healthy In-Reply-To: References: Message-ID: Hi, No offense, I think you would get better answers on this mailing list if you started only one thread and focused on it. The current way of sending similar but slightly different questions, and then duplicating messages make it hard to focus for people willing to help you. With this being said, I believe I replied to this question in the other thread. Kind regards, -- Guillaume Quintard On Thu, Feb 18, 2021 at 7:11 AM Hamidreza Hosseini wrote: > How can I probe a backend varnish? for example I have 2 layer varnish disk > layer and ram layer and ram layer want to check the health of layer 2, How > can I do this? I've done something but I have error: > > sudo varnishadm backend.list -p > Backend name Admin Probe Last updated > boot.varnish_1 probe Sick 0/5 > Current states good: 0 threshold: 3 window: 5 > Average response time of good probes: 0.000000 > Oldest ================================================== Newest > ---------------------------------------------------------------- Happy > > sudo varnishlog -g raw -i Backend_health > 0 Backend_health - boot.varnish_1 Still sick -------- 0 3 5 0.000000 > 0.000000 Open error 111 (Connection refused) > > my config: > probe myprobe { > .request = > "HEAD / HTTP/1.1" > "Connection: close" > "User-Agent: Varnish Health Probe"; > .timeout = 1s; > .interval = 5s; > .window = 5; > .threshold = 3; > } > > ------------------------------ > *From:* Hamidreza Hosseini > *Sent:* Thursday, February 18, 2021 5:31 AM > *To:* varnish-misc at varnish-cache.org > *Subject:* How to adjust priority for both backend healthy > > I have two backend that both of them are healthy and I use fallback for > them and I want to say all request should goes to backend1 and if backend1 > become unhealthy all requests should go to backend2 but backend1 has higher > priority and when backend1 become healthy, all requests should go to > backend1, > How can I define priority? > my config: > > ``` > vcl 4.1; > > import directors; > > probe myprobe { > .request = > "HEAD / HTTP/1.1" > "Connection: close" > "User-Agent: Varnish Health Probe"; > .timeout = 1s; > .interval = 5s; > .window = 5; > .threshold = 3; > } > > backend backend1 { .host = "backend1"; .port = "8080"; .probe = myprobe; } > > backend backend2 { .host = "backend2"; .port = "8080"; .probe = myprobe; } > backend backend3 { .host = "backend3"; .port = "8080"; .probe = myprobe; } > > > sub vcl_init { > > new backend2_cluster = directors.round_robin(); > backend2_cluster.add_backend(backend2); > backend3_cluster.add_backend(backend3); > > > new backend_cluster_fb = directors.fallback(); > backend1_fb.add_backend(backend1); > backend2_cluster_fb.add_backend(backend2_cluster.backend()); > } > > sub vcl_recv { > set req.backend_hint = backend_cluster_fb.backend(); > > } > > ``` > > _______________________________________________ > 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: From hrhosseini at hotmail.com Thu Feb 18 16:19:35 2021 From: hrhosseini at hotmail.com (Hamidreza Hosseini) Date: Thu, 18 Feb 2021 16:19:35 +0000 Subject: How to adjust priority for both backend healthy In-Reply-To: References: Message-ID: I read you article and it was great but I didn't find out my answer, I said that I have 2 layer varnish: disk layer and ram layer and ram layer, I want to check the health of layer 2 for example: Varnish Ram ===> Varnish Disk ===> Webserver I adjust this probe on varnish ram: probe myprobe { .request = "HEAD / HTTP/1.1" "Connection: close" "User-Agent: Varnish Health Probe"; .timeout = 1s; .interval = 5s; .window = 5; .threshold = 3; } and varnish says: ` 0 Backend_health - boot.varnish_1 Still sick -------- 0 3 5 0.000000 0.000000 Open error 111 (Connection refused)` And I think it is right because it checks HEAD / on varnish backends and there is nothing there! So I'm asking how should I configure the probe to trigger another varnish health as a backend Best regards. ________________________________ From: Hamidreza Hosseini Sent: Thursday, February 18, 2021 5:31 AM To: varnish-misc at varnish-cache.org Subject: How to adjust priority for both backend healthy I have two backend that both of them are healthy and I use fallback for them and I want to say all request should goes to backend1 and if backend1 become unhealthy all requests should go to backend2 but backend1 has higher priority and when backend1 become healthy, all requests should go to backend1, How can I define priority? my config: ``` vcl 4.1; import directors; probe myprobe { .request = "HEAD / HTTP/1.1" "Connection: close" "User-Agent: Varnish Health Probe"; .timeout = 1s; .interval = 5s; .window = 5; .threshold = 3; } backend backend1 { .host = "backend1"; .port = "8080"; .probe = myprobe; } backend backend2 { .host = "backend2"; .port = "8080"; .probe = myprobe; } backend backend3 { .host = "backend3"; .port = "8080"; .probe = myprobe; } sub vcl_init { new backend2_cluster = directors.round_robin(); backend2_cluster.add_backend(backend2); backend3_cluster.add_backend(backend3); new backend_cluster_fb = directors.fallback(); backend1_fb.add_backend(backend1); backend2_cluster_fb.add_backend(backend2_cluster.backend()); } sub vcl_recv { set req.backend_hint = backend_cluster_fb.backend(); } ``` -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume at varnish-software.com Thu Feb 18 17:07:20 2021 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Thu, 18 Feb 2021 09:07:20 -0800 Subject: Varnish Health check In-Reply-To: References:

Message-ID: please keep the mailing-list in CC for future communications. > Open error 111 (Connection refused) This is a TCP issue, the backend is just not accepting the connection, are you sure the IP:PORT is right? -- Guillaume Quintard On Thu, Feb 18, 2021 at 8:16 AM Hamidreza Hosseini wrote: > I read you article and it was great but I didn't find out my answer, I > said that I have 2 layer varnish: disk layer and ram layer and ram layer, > I want to check the health of layer 2 for example: > > Varnish Ram ===> Varnish Disk ===> Webserver > I adjust this probe on varnish ram: > > probe myprobe { > .request = > "HEAD / HTTP/1.1" > "Connection: close" > "User-Agent: Varnish Health Probe"; > .timeout = 1s; > .interval = 5s; > .window = 5; > .threshold = 3; > } > and varnish says: ` 0 Backend_health - boot.varnish_1 Still sick -------- > 0 3 5 0.000000 0.000000 Open error 111 (Connection refused)` > And I think it is right because it checks HEAD / on varnish backends and > there is nothing there! > So I'm asking how should I configure the probe to trigger another varnish > health as a backend > > Best regards. > > ------------------------------ > *From:* Guillaume Quintard > *Sent:* Thursday, February 18, 2021 7:14 AM > *To:* Hamidreza Hosseini > *Subject:* Re: Varnish Health check > > Ah, I missed the multilayer setup. In that case, you can have a look at > this one: https://info.varnish-software.com/blog/howto-respond-to-probes > -- > Guillaume Quintard > > > On Thu, Feb 18, 2021 at 7:08 AM Hamidreza Hosseini > wrote: > > How can I probe a backend varnish? for example I have 2 layer varnish disk > layer and ram layer and ram layer want to check the health of layer 2, How > can I do this? I've done something but I have error: > > sudo varnishadm backend.list -p > Backend name Admin Probe Last updated > boot.varnish_1 probe Sick 0/5 > Current states good: 0 threshold: 3 window: 5 > Average response time of good probes: 0.000000 > Oldest ================================================== Newest > ---------------------------------------------------------------- Happy > > sudo varnishlog -g raw -i Backend_health > 0 Backend_health - boot.varnish_1 Still sick -------- 0 3 5 0.000000 > 0.000000 Open error 111 (Connection refused) > > my config: > probe myprobe { > .request = > "HEAD / HTTP/1.1" > "Connection: close" > "User-Agent: Varnish Health Probe"; > .timeout = 1s; > .interval = 5s; > .window = 5; > .threshold = 3; > } > ------------------------------ > *From:* Guillaume Quintard > *Sent:* Thursday, February 18, 2021 7:00 AM > *To:* Hamidreza Hosseini > *Cc:* varnish-misc at varnish-cache.org > *Subject:* Re: Varnish Health check > > Hi, > > The answer will be highly dependent on your setup, usually you want to > find a probe request that will truly test the backend. One option, if you > have control over the backend is to write a page to test the subsystem and > make sure everybody's up. > > This link may prove useful: > https://info.varnish-software.com/blog/backends-load-balancing > > -- > Guillaume Quintard > > > On Thu, Feb 18, 2021 at 4:51 AM Hamidreza Hosseini > wrote: > > Hi, > I want to adjust health check on my varnish backends, But I dont know how > can I know they are healthy or not > because the nodes are up and running and even service is up but varnish > does'nt work for all requests (just third of them are responding till I > restart it (It happens sometimes)). > How can I check this? > ``` > backend server1 { > .host = "server1.example.com"; > .probe = { > .request = > "HEAD / HTTP/1.1" > "Connection: close" > "User-Agent: Varnish Health Probe"; > .timeout = 1s; > .interval = 5s; > .window = 5; > .threshold = 3; > } > } > ``` > _______________________________________________ > 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: From guillaume at varnish-software.com Thu Feb 18 17:07:58 2021 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Thu, 18 Feb 2021 09:07:58 -0800 Subject: How to adjust priority for both backend healthy In-Reply-To: References: Message-ID: I'm formally abandoning this thread and will only focus on the other one -- Guillaume Quintard On Thu, Feb 18, 2021 at 8:21 AM Hamidreza Hosseini wrote: > I read you article and it was great but I didn't find out my answer, I > said that I have 2 layer varnish: disk layer and ram layer and ram layer, > I want to check the health of layer 2 for example: > > Varnish Ram ===> Varnish Disk ===> Webserver > I adjust this probe on varnish ram: > > probe myprobe { > .request = > "HEAD / HTTP/1.1" > "Connection: close" > "User-Agent: Varnish Health Probe"; > .timeout = 1s; > .interval = 5s; > .window = 5; > .threshold = 3; > } > and varnish says: ` 0 Backend_health - boot.varnish_1 Still sick -------- > 0 3 5 0.000000 0.000000 Open error 111 (Connection refused)` > And I think it is right because it checks HEAD / on varnish backends and > there is nothing there! > So I'm asking how should I configure the probe to trigger another varnish > health as a backend > > Best regards. > > ------------------------------ > *From:* Hamidreza Hosseini > *Sent:* Thursday, February 18, 2021 5:31 AM > *To:* varnish-misc at varnish-cache.org > *Subject:* How to adjust priority for both backend healthy > > I have two backend that both of them are healthy and I use fallback for > them and I want to say all request should goes to backend1 and if backend1 > become unhealthy all requests should go to backend2 but backend1 has higher > priority and when backend1 become healthy, all requests should go to > backend1, > How can I define priority? > my config: > > ``` > vcl 4.1; > > import directors; > > probe myprobe { > .request = > "HEAD / HTTP/1.1" > "Connection: close" > "User-Agent: Varnish Health Probe"; > .timeout = 1s; > .interval = 5s; > .window = 5; > .threshold = 3; > } > > backend backend1 { .host = "backend1"; .port = "8080"; .probe = myprobe; } > > backend backend2 { .host = "backend2"; .port = "8080"; .probe = myprobe; } > backend backend3 { .host = "backend3"; .port = "8080"; .probe = myprobe; } > > > sub vcl_init { > > new backend2_cluster = directors.round_robin(); > backend2_cluster.add_backend(backend2); > backend3_cluster.add_backend(backend3); > > > new backend_cluster_fb = directors.fallback(); > backend1_fb.add_backend(backend1); > backend2_cluster_fb.add_backend(backend2_cluster.backend()); > } > > sub vcl_recv { > set req.backend_hint = backend_cluster_fb.backend(); > > } > > ``` > > _______________________________________________ > 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: From hrhosseini at hotmail.com Sat Feb 20 04:52:02 2021 From: hrhosseini at hotmail.com (Hamidreza Hosseini) Date: Sat, 20 Feb 2021 04:52:02 +0000 Subject: Varnish Health check In-Reply-To: References: Message-ID: I correct the wrong name (It couldn't resolve from dns server), But now I have this error: 0 Backend_health - boot.varnish_1 Still sick 4---X-R- 0 3 5 0.007800 0.000000 HTTP/1.1 400 Bad Request My probe: probe myprobe { .request = "HEAD / HTTP/1.1" "Connection: close" "User-Agent: Varnish Health Probe"; .timeout = 3s; .interval = 5s; .window = 5; .threshold = 3; } Should I change the probe request "HEAD /" to something else? Is there any way to define special port and whenever it is accessable even with authentication erro (error 400) it consider backend healthy? ________________________________ From: Hamidreza Hosseini Sent: Thursday, February 18, 2021 4:49 AM To: varnish-misc at varnish-cache.org Subject: Varnish Health check Hi, I want to adjust health check on my varnish backends, But I dont know how can I know they are healthy or not because the nodes are up and running and even service is up but varnish does'nt work for all requests (just third of them are responding till I restart it (It happens sometimes)). How can I check this? ``` backend server1 { .host = "server1.example.com"; .probe = { .request = "HEAD / HTTP/1.1" "Connection: close" "User-Agent: Varnish Health Probe"; .timeout = 1s; .interval = 5s; .window = 5; .threshold = 3; } } ``` -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume at varnish-software.com Sat Feb 20 06:06:27 2021 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Fri, 19 Feb 2021 22:06:27 -0800 Subject: Varnish Health check In-Reply-To: References: Message-ID: Your backend is returning a 400, most probably because there's no host header in your probe. -- Guillaume Quintard On Fri, Feb 19, 2021 at 8:53 PM Hamidreza Hosseini wrote: > I correct the wrong name (It couldn't resolve from dns server), But now I > have this error: > > 0 Backend_health - boot.varnish_1 Still sick 4---X-R- 0 3 5 0.007800 > 0.000000 HTTP/1.1 400 Bad Request > > My probe: > > probe myprobe { > .request = > "HEAD / HTTP/1.1" > "Connection: close" > "User-Agent: Varnish Health Probe"; > .timeout = 3s; > .interval = 5s; > .window = 5; > .threshold = 3; > } > Should I change the probe request "HEAD /" to something else? > Is there any way to define special port and whenever it is accessable even > with authentication erro (error 400) it consider backend healthy? > ------------------------------ > *From:* Hamidreza Hosseini > *Sent:* Thursday, February 18, 2021 4:49 AM > *To:* varnish-misc at varnish-cache.org > *Subject:* Varnish Health check > > Hi, > I want to adjust health check on my varnish backends, But I dont know how > can I know they are healthy or not > because the nodes are up and running and even service is up but varnish > does'nt work for all requests (just third of them are responding till I > restart it (It happens sometimes)). > How can I check this? > ``` > backend server1 { > .host = "server1.example.com"; > .probe = { > .request = > "HEAD / HTTP/1.1" > "Connection: close" > "User-Agent: Varnish Health Probe"; > .timeout = 1s; > .interval = 5s; > .window = 5; > .threshold = 3; > } > } > ``` > _______________________________________________ > 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: