From miguel_3_gonzalez at yahoo.es Wed Feb 1 14:31:29 2017 From: miguel_3_gonzalez at yahoo.es (=?UTF-8?Q?Miguel_Gonz=c3=a1lez?=) Date: Wed, 1 Feb 2017 15:31:29 +0100 Subject: banning in one line command Message-ID: <0bddfbd9-421f-138d-6cf7-617b6cd47936@yahoo.es> Dear all, I have Varnish 4.1 and I?m trying to run in one single line command a ban for a particular website. If I run this: root at myserver [~] # varnishadm -T :6082 -S /etc/varnish/secret varnish> ban req.http.host ~ www.myserver.com 200 I get the 200 code. However If I run it in a single line I get no 200 return code: root at myserver [~] # varnishadm -T :6082 -S /etc/varnish/secret 'ban req.http.host ~ www.myserver.com' I get nothing. If I try double quotes I get the same... I googled around and I find people asking the same but no solutions. What am I doing wrong? Thanks! Miguel From dridi at varni.sh Wed Feb 1 15:25:12 2017 From: dridi at varni.sh (Dridi Boukelmoune) Date: Wed, 1 Feb 2017 16:25:12 +0100 Subject: banning in one line command In-Reply-To: <0bddfbd9-421f-138d-6cf7-617b6cd47936@yahoo.es> References: <0bddfbd9-421f-138d-6cf7-617b6cd47936@yahoo.es> Message-ID: On Wed, Feb 1, 2017 at 3:31 PM, Miguel Gonz?lez wrote: > Dear all, > > I have Varnish 4.1 and I?m trying to run in one single line command a > ban for a particular website. If I run this: > > root at myserver [~] # varnishadm -T :6082 -S /etc/varnish/secret > > varnish> ban req.http.host ~ www.myserver.com > 200 > > I get the 200 code. However If I run it in a single line I get no 200 > return code: > > root at myserver [~] # varnishadm -T :6082 -S /etc/varnish/secret 'ban > req.http.host ~ www.myserver.com' You probably don't need the -T arg for a local access. > I get nothing. If I try double quotes I get the same... > > I googled around and I find people asking the same but no solutions. > > What am I doing wrong? Nothing wrong: what you are seeing in varnishadm's interactive shell is the response status from varnish (see man varnish-cli) but when you use varnishadm as a scripting command, only the actual output is shown. Instead of relying on the status code of the varnish-cli command, use the exit status of the varnishadm command. if ! varnishadm [...] then echo "varnishadm just failed" >&2 exit 42 fi Dridi From miguel_3_gonzalez at yahoo.es Wed Feb 1 15:29:50 2017 From: miguel_3_gonzalez at yahoo.es (=?UTF-8?Q?Miguel_Gonz=c3=a1lez?=) Date: Wed, 1 Feb 2017 16:29:50 +0100 Subject: banning in one line command In-Reply-To: References: <0bddfbd9-421f-138d-6cf7-617b6cd47936@yahoo.es> Message-ID: On 02/01/17 4:25 PM, Dridi Boukelmoune wrote: > On Wed, Feb 1, 2017 at 3:31 PM, Miguel Gonz?lez > wrote: >> Dear all, >> >> I have Varnish 4.1 and I?m trying to run in one single line command a >> ban for a particular website. If I run this: >> >> root at myserver [~] # varnishadm -T :6082 -S /etc/varnish/secret >> >> varnish> ban req.http.host ~ www.myserver.com >> 200 >> >> I get the 200 code. However If I run it in a single line I get no 200 >> return code: >> >> root at myserver [~] # varnishadm -T :6082 -S /etc/varnish/secret 'ban >> req.http.host ~ www.myserver.com' > > You probably don't need the -T arg for a local access. > >> I get nothing. If I try double quotes I get the same... >> >> I googled around and I find people asking the same but no solutions. >> >> What am I doing wrong? > > Nothing wrong: what you are seeing in varnishadm's interactive shell > is the response status from varnish (see man varnish-cli) but when you > use varnishadm as a scripting command, only the actual output is > shown. > Thanks for answering! What do you mean with the actual output? I get an empty string... Is there any manual or information about this in the wiki? Thanks From dridi at varni.sh Wed Feb 1 16:08:40 2017 From: dridi at varni.sh (Dridi Boukelmoune) Date: Wed, 1 Feb 2017 17:08:40 +0100 Subject: banning in one line command In-Reply-To: References: <0bddfbd9-421f-138d-6cf7-617b6cd47936@yahoo.es> Message-ID: > What do you mean with the actual output? I get an empty string... For commands like param.show or backend.list that give you an output. > Is there any manual or information about this in the wiki? Please double check the varnishstat manual, if it's not mentioned let me know and will push a docfix. Dridi From miguel_3_gonzalez at yahoo.es Wed Feb 1 16:29:45 2017 From: miguel_3_gonzalez at yahoo.es (=?UTF-8?Q?Miguel_Gonz=c3=a1lez?=) Date: Wed, 1 Feb 2017 17:29:45 +0100 Subject: banning in one line command In-Reply-To: <86d5defc-cf1d-a36d-83aa-1d221e359c1c@yahoo.es> References: <0bddfbd9-421f-138d-6cf7-617b6cd47936@yahoo.es> <86d5defc-cf1d-a36d-83aa-1d221e359c1c@yahoo.es> Message-ID: <57030bb5-7eb1-8ea8-e1de-54da76b91ffd@yahoo.es> On 02/01/17 5:24 PM, Miguel Gonz?lez wrote: > On 02/01/17 5:08 PM, Dridi Boukelmoune wrote: >>> What do you mean with the actual output? I get an empty string... >> >> For commands like param.show or backend.list that give you an output. >> >>> Is there any manual or information about this in the wiki? >> >> Please double check the varnishstat manual, if it's not mentioned let >> me know and will push a docfix. > > you mean varnishadm manual, this one: > > https://varnish-cache.org/docs/4.1/reference/varnishadm.html > > ? > > My experience is that using a singleliner doesn?t work, cache is not > banned. I thought It was the empty string output but considering your > answer and the manual it supposedly works but it?s not actually banning > the cache. using quotes an after the example in the manual: echo "ban req.http.host ~ myserver.com" | varnishadm -S /etc/varnish/secret 200 Before I was getting this error when not using commands for the echo command (as showed in the example in the manual): 106 expected conditional (~, !~, == or !=) got "/root" apparently this error is dued to the echo command and the use of conditionals as ~ Thanks! Miguel From Victor.Grazi at nomura.com Wed Feb 1 17:22:04 2017 From: Victor.Grazi at nomura.com (Victor.Grazi at nomura.com) Date: Wed, 1 Feb 2017 17:22:04 +0000 Subject: Varnish failing to detect valid probe page Message-ID: I am having a problem with Varnish 3.x probe page from a SpringBoot application (1.4). Varnish is failing to detect the probe page (returns 503 SERVICE NOT AVAILABLE) and consequently fails to route. When I manually ping the probe URL, it works fine, but Varnish is flagging the probe page as being down. Removing the probe page, everything works fine. Pointing to a static probe page (my.css) or any other static or dynamic URL fails. Looking at the logs, the response header looks like this: HTTP/1.1 200 Content-Type: text/plain;charset=utf-8 Content-Length: 72 Date: Wed, 01 Feb 2017 15:20:48 GMT Proxy-Connection: Keep-Alive Connection: Keep-Alive Comparing this to other working (non Spring Boot) applications, the only difference is that the working applications have an OK after the response, and the bad ones don't: HTTP/1.1 200 OK Does that mean anything? For example, here is a good one: HTTP/1.1 200 OK Date: Wed, 01 Feb 2017 14:04:18 GMT Last-Modified: Fri, 11 Nov 2016 22:00:02 GMT Content-Type: text/css Content-Length: 129 Server: Jetty(9.3.z-SNAPSHOT) Proxy-Connection: Keep-Alive Connection: Keep-Alive Not sure where else to look! Any clues? Victor Grazi Desk: +1-212-298-4445 (Internal: 74445) Mobile: +1-917-251-1247 Blackberry Phone: +1-347-726-0338 victor.grazi at nomura.com NOMURA ? GM/FID Core IT Worldwide Plaza - 8th Floor 309 West 49th Street (8th Ave) New York, NY 10019 PLEASE READ: This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please delete it and all copies from your system, destroy any hard copies and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Nomura Holding America Inc., Nomura Securities International, Inc, and their respective subsidiaries each reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state the views of such entity. Unless otherwise stated, any pricing information in this message is indicative only, is subject to change and does not constitute an offer to deal at any price quoted. Any reference to the terms of executed transactions should be treated as preliminary only and subject to our formal written confirmation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume at varnish-software.com Wed Feb 1 18:30:06 2017 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Wed, 1 Feb 2017 19:30:06 +0100 Subject: Varnish failing to detect valid probe page In-Reply-To: References: Message-ID: You found the issue: https://github.com/varnishcache/varnish-cache/issues/2069 This is "fixed" in master. But maybe you can fix your backend? -- Guillaume Quintard -- Guillaume Quintard On Wed, Feb 1, 2017 at 6:22 PM, wrote: > I am having a problem with Varnish 3.x probe page from a SpringBoot > application (1.4). Varnish is failing to detect the probe page (returns 503 > SERVICE NOT AVAILABLE) and consequently fails to route. > > When I manually ping the probe URL, it works fine, but Varnish is flagging > the probe page as being down. > > Removing the probe page, everything works fine. > > Pointing to a static probe page (my.css) or any other static or dynamic > URL fails. > > Looking at the logs, the response header looks like this: > > HTTP/1.1 200 > > Content-Type: text/plain;charset=utf-8 > > Content-Length: 72 > > Date: Wed, 01 Feb 2017 15:20:48 GMT > > Proxy-Connection: Keep-Alive > > Connection: Keep-Alive > > > > Comparing this to other working (non Spring Boot) applications, the only > difference is that the working applications have an OK after the response, > and the bad ones don't: HTTP/1.1 200 OK Does that mean anything? > > For example, here is a good one: > > HTTP/1.1 200 OK > > Date: Wed, 01 Feb 2017 14:04:18 GMT > > Last-Modified: Fri, 11 Nov 2016 22:00:02 GMT > > Content-Type: text/css > > Content-Length: 129 > > Server: Jetty(9.3.z-SNAPSHOT) > > Proxy-Connection: Keep-Alive > > Connection: Keep-Alive > > > > Not sure where else to look! Any clues? > > > > Victor Grazi > > > > Desk: +1-212-298-4445 <(212)%20298-4445> (Internal: 74445) > > Mobile: +1-917-251-1247 <(917)%20251-1247> > > Blackberry Phone: +1-347-726-0338 <(347)%20726-0338> > > victor.grazi at nomura.com > > > > *NOMURA ? GM/FID Core IT* > > Worldwide Plaza - 8th Floor > 309 West 49th Street (8th Ave) > > New York, NY 10019 > > > > > > > > PLEASE READ: This message is for the named person's use only. It may > contain confidential, proprietary or legally privileged information. No > confidentiality or privilege is waived or lost by any mistransmission. If > you receive this message in error, please delete it and all copies from > your system, destroy any hard copies and notify the sender. You must not, > directly or indirectly, use, disclose, distribute, print, or copy any part > of this message if you are not the intended recipient. Nomura Holding > America Inc., Nomura Securities International, Inc, and their respective > subsidiaries each reserve the right to monitor all e-mail communications > through its networks. Any views expressed in this message are those of the > individual sender, except where the message states otherwise and the sender > is authorized to state the views of such entity. Unless otherwise stated, > any pricing information in this message is indicative only, is subject to > change and does not constitute an offer to deal at any price quoted. Any > reference to the terms of executed transactions should be treated as > preliminary only and subject to our formal written confirmation. > > _______________________________________________ > 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 miguel_3_gonzalez at yahoo.es Thu Feb 2 12:44:18 2017 From: miguel_3_gonzalez at yahoo.es (=?UTF-8?Q?Miguel_Gonz=c3=a1lez?=) Date: Thu, 2 Feb 2017 13:44:18 +0100 Subject: banning in one line command In-Reply-To: References: <0bddfbd9-421f-138d-6cf7-617b6cd47936@yahoo.es> <86d5defc-cf1d-a36d-83aa-1d221e359c1c@yahoo.es> <5e9c8aeb-cac0-6b50-2f2f-ac3dcc088157@yahoo.es> Message-ID: On 02/02/17 1:05 PM, Dridi Boukelmoune wrote: >>> you mean varnishadm manual, this one: >>> >>> https://varnish-cache.org/docs/4.1/reference/varnishadm.html >>> >>> ? > > Yes, I was looking at something else related to varnishstat and endup > mixing things up. That's the manual I'm referring to. > >>> My experience is that using a singleliner doesn?t work, cache is not >>> banned. I thought It was the empty string output but considering your >>> answer and the manual it supposedly works but it?s not actually banning >>> the cache. > > It works for me: > > $ cat ban_test.sh > #!/bin/sh > > set -e > > if varnishadm ban "$1" > then > echo "Ban added." > varnishadm ban.list > else > echo "Failed to add ban." >&2 > exit 1 > fi > > $ ./ban_test.sh "req.url ~ /foo" > > Ban added. > Present bans: > 1486036564.163640 0 - req.url ~ /foo > 1486036505.008676 0 C > > $ ./ban_test.sh "req.url ==" > Unknown request. > Type 'help' for more info. > Too few parameters > > Command failed with error code 104 > Failed to add ban. > >> using quotes an after the example in the manual: >> >> echo "ban req.http.host ~ myserver.com" | varnishadm -S /etc/varnish/secret >> 200 > > You shouldn't need to specify -S for a local access with varnishadm. > >> Before I was getting this error when not using commands for the echo >> command (as showed in the example in the manual): >> >> 106 >> expected conditional (~, !~, == or !=) got "/root" >> >> apparently this error is dued to the echo command and the use of >> conditionals as ~ > > I suspect you were getting a shell expansion of ~ to the home > directory of the root user, hence the /root. > > Dridi Yes, i did :) Many thanks for your throughly answer! Miguel From asbjornt at gmail.com Wed Feb 8 11:09:42 2017 From: asbjornt at gmail.com (Asbjorn Taugbol) Date: Wed, 8 Feb 2017 12:09:42 +0100 Subject: Varnish 5 wont start at boot on Ubuntu 16.04 Message-ID: Varnish 5 was installed from .deb package (dpkg -i varnish_5.0.0-1_amd64.deb) and with #service varnish start it starts and does its things very well. However, upon reboot it doesnt start automatically. There may be some mixup between old /etc/init.d stuff and newer systemd in debian/ubuntu. Here is some output for debugging this after a reboot: ---------------------- root at 2:~# service varnish status ? varnish.service - Varnish Cache, a high-performance HTTP accelerator Loaded: loaded (/lib/systemd/system/varnish.service; disabled; vendor preset: Drop-In: /etc/systemd/system/varnish.service.d ??override.conf Active: inactive (dead) root at 2:~# journalctl -xe|grep varnish root at 2:~# cat /etc/systemd/system/varnish.service.d/override.conf [Service] ExecStart= ExecStart=/usr/sbin/varnishd -a :80 -a :9443 -a :9444 -T localhost:6082 -f /etc/varnish/default.vcl -S /etc/varnish/secret -s malloc,256m root at 2:~# cat /etc/default/varnish # Configuration file for Varnish Cache. # # /etc/init.d/varnish expects the variables $DAEMON_OPTS, $NFILES and $MEMLOCK # to be set from this shell script fragment. # # Note: If systemd is installed, this file is obsolete and ignored. You will # need to copy /lib/systemd/system/varnish.service to /etc/systemd/system/ and # edit that file. # Should we start varnishd at boot? Set to "no" to disable. START=yes # Maximum number of open files (for ulimit -n) NFILES=131072 # Maximum locked memory size (for ulimit -l) # Used for locking the shared memory log in memory. If you increase log size, # you need to increase this number as well MEMLOCK=82000 #DAEMON_OPTS="-a :80 \ DAEMON_OPTS="-a :80,:9443,:9444 \ -T localhost:6082 \ -f /etc/varnish/default.vcl \ -S /etc/varnish/secret \ -s malloc,256m" root at 2:/etc# locate S01varnish /etc/rc2.d/S01varnish /etc/rc3.d/S01varnish /etc/rc4.d/S01varnish /etc/rc5.d/S01varnish root at 2:/etc# ls -l rc2.d/S01varnish lrwxrwxrwx 1 root root 17 Jan 27 14:39 rc2.d/S01varnish -> ../init.d/varnish root at 2:~# /etc/init.d/varnish start [ ok ] Starting varnish (via systemctl): varnish.service. root at 2:~# ----------------------------- Any input on this is highly appreciated. Thank you. -Asbjorn -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume at varnish-software.com Wed Feb 8 11:20:12 2017 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Wed, 8 Feb 2017 12:20:12 +0100 Subject: Varnish 5 wont start at boot on Ubuntu 16.04 In-Reply-To: References: Message-ID: systemctl enable varnish ? But I thought the debian policy what to automatically start service though. -- Guillaume Quintard On Wed, Feb 8, 2017 at 12:09 PM, Asbjorn Taugbol wrote: > Varnish 5 was installed from .deb package (dpkg -i > varnish_5.0.0-1_amd64.deb) and with > > #service varnish start > > it starts and does its things very well. However, upon reboot it doesnt > start automatically. There may be some mixup between old /etc/init.d stuff > and newer systemd in debian/ubuntu. Here is some output for debugging this > after a reboot: > > ---------------------- > root at 2:~# service varnish status > ? varnish.service - Varnish Cache, a high-performance HTTP accelerator > Loaded: loaded (/lib/systemd/system/varnish.service; disabled; vendor > preset: > Drop-In: /etc/systemd/system/varnish.service.d > ??override.conf > Active: inactive (dead) > > root at 2:~# journalctl -xe|grep varnish > > root at 2:~# cat /etc/systemd/system/varnish.service.d/override.conf > [Service] > ExecStart= > ExecStart=/usr/sbin/varnishd -a :80 -a :9443 -a :9444 -T localhost:6082 -f > /etc/varnish/default.vcl -S /etc/varnish/secret -s malloc,256m > > root at 2:~# cat /etc/default/varnish > # Configuration file for Varnish Cache. > # > # /etc/init.d/varnish expects the variables $DAEMON_OPTS, $NFILES and > $MEMLOCK > # to be set from this shell script fragment. > # > # Note: If systemd is installed, this file is obsolete and ignored. You > will > # need to copy /lib/systemd/system/varnish.service to > /etc/systemd/system/ and > # edit that file. > > # Should we start varnishd at boot? Set to "no" to disable. > START=yes > > # Maximum number of open files (for ulimit -n) > NFILES=131072 > > # Maximum locked memory size (for ulimit -l) > # Used for locking the shared memory log in memory. If you increase log > size, > # you need to increase this number as well > MEMLOCK=82000 > > #DAEMON_OPTS="-a :80 \ > DAEMON_OPTS="-a :80,:9443,:9444 \ > -T localhost:6082 \ > -f /etc/varnish/default.vcl \ > -S /etc/varnish/secret \ > -s malloc,256m" > > root at 2:/etc# locate S01varnish > /etc/rc2.d/S01varnish > /etc/rc3.d/S01varnish > /etc/rc4.d/S01varnish > /etc/rc5.d/S01varnish > > root at 2:/etc# ls -l rc2.d/S01varnish > lrwxrwxrwx 1 root root 17 Jan 27 14:39 rc2.d/S01varnish -> > ../init.d/varnish > > root at 2:~# /etc/init.d/varnish start > [ ok ] Starting varnish (via systemctl): varnish.service. > root at 2:~# > > ----------------------------- > > Any input on this is highly appreciated. > > Thank you. > > -Asbjorn > > > _______________________________________________ > 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 asbjornt at gmail.com Wed Feb 8 11:30:39 2017 From: asbjornt at gmail.com (Asbjorn Taugbol) Date: Wed, 8 Feb 2017 12:30:39 +0100 Subject: Varnish 5 wont start at boot on Ubuntu 16.04 In-Reply-To: References: Message-ID: Thank you! On Wed, Feb 8, 2017 at 12:20 PM, Guillaume Quintard < guillaume at varnish-software.com> wrote: > systemctl enable varnish > > ? > > But I thought the debian policy what to automatically start service though. > > -- > Guillaume Quintard > > On Wed, Feb 8, 2017 at 12:09 PM, Asbjorn Taugbol > wrote: > >> Varnish 5 was installed from .deb package (dpkg -i >> varnish_5.0.0-1_amd64.deb) and with >> >> #service varnish start >> >> it starts and does its things very well. However, upon reboot it doesnt >> start automatically. There may be some mixup between old /etc/init.d stuff >> and newer systemd in debian/ubuntu. Here is some output for debugging this >> after a reboot: >> >> ---------------------- >> root at 2:~# service varnish status >> ? varnish.service - Varnish Cache, a high-performance HTTP accelerator >> Loaded: loaded (/lib/systemd/system/varnish.service; disabled; vendor >> preset: >> Drop-In: /etc/systemd/system/varnish.service.d >> ??override.conf >> Active: inactive (dead) >> >> root at 2:~# journalctl -xe|grep varnish >> >> root at 2:~# cat /etc/systemd/system/varnish.service.d/override.conf >> [Service] >> ExecStart= >> ExecStart=/usr/sbin/varnishd -a :80 -a :9443 -a :9444 -T localhost:6082 >> -f /etc/varnish/default.vcl -S /etc/varnish/secret -s malloc,256m >> >> root at 2:~# cat /etc/default/varnish >> # Configuration file for Varnish Cache. >> # >> # /etc/init.d/varnish expects the variables $DAEMON_OPTS, $NFILES and >> $MEMLOCK >> # to be set from this shell script fragment. >> # >> # Note: If systemd is installed, this file is obsolete and ignored. You >> will >> # need to copy /lib/systemd/system/varnish.service to >> /etc/systemd/system/ and >> # edit that file. >> >> # Should we start varnishd at boot? Set to "no" to disable. >> START=yes >> >> # Maximum number of open files (for ulimit -n) >> NFILES=131072 >> >> # Maximum locked memory size (for ulimit -l) >> # Used for locking the shared memory log in memory. If you increase log >> size, >> # you need to increase this number as well >> MEMLOCK=82000 >> >> #DAEMON_OPTS="-a :80 \ >> DAEMON_OPTS="-a :80,:9443,:9444 \ >> -T localhost:6082 \ >> -f /etc/varnish/default.vcl \ >> -S /etc/varnish/secret \ >> -s malloc,256m" >> >> root at 2:/etc# locate S01varnish >> /etc/rc2.d/S01varnish >> /etc/rc3.d/S01varnish >> /etc/rc4.d/S01varnish >> /etc/rc5.d/S01varnish >> >> root at 2:/etc# ls -l rc2.d/S01varnish >> lrwxrwxrwx 1 root root 17 Jan 27 14:39 rc2.d/S01varnish -> >> ../init.d/varnish >> >> root at 2:~# /etc/init.d/varnish start >> [ ok ] Starting varnish (via systemctl): varnish.service. >> root at 2:~# >> >> ----------------------------- >> >> Any input on this is highly appreciated. >> >> Thank you. >> >> -Asbjorn >> >> >> _______________________________________________ >> 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 lagged at gmail.com Mon Feb 13 05:22:50 2017 From: lagged at gmail.com (Andrei) Date: Sun, 12 Feb 2017 23:22:50 -0600 Subject: Odd crash Message-ID: Hello all, I woke up to numerous site timeouts, and when I went to check the backend list, this is what was returned: root at aviator [~]# varnishadm backend.list Unknown request in manager process (child not running). Type 'help' for more info. Command failed with error code 101 root at aviator [~]# I believe it was likely related to this panic: https://zerobin.net/?448b15259bc80551#Geo0NImD4HLpGWVZWk9raD7Qhl11VkNZEmh21J2S9mE= Varnish has since been upgraded to 4.1.5. Should I still be worried? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Niklas.Donath at lvdigital.de Tue Feb 14 08:20:02 2017 From: Niklas.Donath at lvdigital.de (Donath, Niklas) Date: Tue, 14 Feb 2017 08:20:02 +0000 Subject: X-Forwarded-For automatically set in varnish 4.0? Message-ID: <948AAF6D-C0AE-4E32-B20A-F100CE5216F2@lv.de> Hi there, actually, i am in a migration project from varnish 3 to varnish 4.0, and i was confused about the x-forwarded-for header settings in varnish 4.0: in the official doc, it says that x-forwarded-for is automatically set, like it is obvious in the source code: https://github.com/varnishcache/varnish-cache/blob/4.0/bin/varnishd/cache/cache_req_fsm.c#L724 But a lot of people are adding a snippet for vcl_recv like if (req.restarts == 0) { if (req.http.X-Forwarded-For) { set req.http.X-Forwarded-For = req.http.X-Forwarded-For + ", " + client.ip; } else { set req.http.X-Forwarded-For = client.ip; } } Which, from my point of view, is the same implementation as it already should exist as the docs say. I currently do not have a LB/proxy infrastructure to test it, so maybe someone can clear this up, if x-forwarded-for is automatically set by varnish before executing the vcl_recv from my custom .vcl-file, or if the given snippet is required to set the real user ip for x-forwarded-for. Thank you very much! Greetings, Niklas -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume at varnish-software.com Tue Feb 14 08:41:27 2017 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Tue, 14 Feb 2017 09:41:27 +0100 Subject: X-Forwarded-For automatically set in varnish 4.0? In-Reply-To: <948AAF6D-C0AE-4E32-B20A-F100CE5216F2@lv.de> References: <948AAF6D-C0AE-4E32-B20A-F100CE5216F2@lv.de> Message-ID: Hi, The snippet is legacy code for v3, and it's now useless/counter-productive in v4. -- Guillaume Quintard On Tue, Feb 14, 2017 at 9:20 AM, Donath, Niklas wrote: > Hi there, > > > > actually, i am in a migration project from varnish 3 to varnish 4.0, and i > was confused about the x-forwarded-for header settings in varnish 4.0: > > in the official doc, it says that x-forwarded-for is automatically set, > like it is obvious in the source code: https://github.com/ > varnishcache/varnish-cache/blob/4.0/bin/varnishd/cache/ > cache_req_fsm.c#L724 > > > > But a lot of people are adding a snippet for vcl_recv like > > > > if (req.restarts == 0) { > > if (req.http.X-Forwarded-For) { > > set req.http.X-Forwarded-For = req.http.X-Forwarded-For + ", " + > client.ip; > > } else { > > set req.http.X-Forwarded-For = client.ip; > > } > > } > > > > Which, from my point of view, is the same implementation as it already > should exist as the docs say. I currently do not have a LB/proxy > infrastructure to test it, so maybe someone can clear this up, if > x-forwarded-for is automatically set by varnish before executing the > vcl_recv from my custom .vcl-file, or if the given snippet is required to > set the real user ip for x-forwarded-for. > > > > Thank you very much! > > > > Greetings, Niklas > > > > _______________________________________________ > 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 ciapnz at gmail.com Tue Feb 14 21:37:52 2017 From: ciapnz at gmail.com (Danila Vershinin) Date: Wed, 15 Feb 2017 00:37:52 +0300 Subject: Purge specific object, not all variants Message-ID: <6C572F02-815C-4215-8078-0A0267773CAE@gmail.com> Hi, Theoretical question. Supposedly I want to introduce Vary: by device classification: mobile / desktop (via devicedetect etc.) How would I go around purging just the specific variant of an object, i.e. purge a page for mobile only? The documentation here: http://book.varnish-software.com/4.0/chapters/Cache_Invalidation.html Mentions that all methods will purge all variants. Is it wrong? Do I correctly understand that forced cache miss is the single method that allows to purge specific variant of an object? -------------- next part -------------- An HTML attachment was scrubbed... URL: From pinakee at waltzz.com Wed Feb 15 05:38:19 2017 From: pinakee at waltzz.com (Pinakee Biswas) Date: Wed, 15 Feb 2017 11:08:19 +0530 Subject: Using Varnish with PHP Message-ID: Hi, Not sure if this is the right forum but would appreciate if you could let me know how to serve PHP pages using Varnish. We have wordpress (Blog) hosted on our server. Varnish sits behind Nginx in the stack. Currently, PHP is served directly by Nginx using PhpFpm. We would like to use varnish to cache wordpress pages. We are already using Varnish to serve pages from a Python based framework. Looking forward to any help. Thanks, Pinakee Biswas http://www.jivaana.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume at varnish-software.com Wed Feb 15 08:47:44 2017 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Wed, 15 Feb 2017 09:47:44 +0100 Subject: Using Varnish with PHP In-Reply-To: References: Message-ID: Hi, I'm not sure I get the question. Varnish will serve anything as long as it's HTTP-based, so you can just point Varnish to Nging, and it will cache whatever Nginx sends its way. -- Guillaume Quintard -------------- next part -------------- An HTML attachment was scrubbed... URL: From pinakee at waltzz.com Wed Feb 15 09:21:42 2017 From: pinakee at waltzz.com (Pinakee Biswas) Date: Wed, 15 Feb 2017 14:51:42 +0530 Subject: Using Varnish with PHP In-Reply-To: References: Message-ID: Hi, Thanks for your response but in our scenario, Nginx is in front: Users/Clients----->Nginx---> Varnish---->PHP So, you mean I would need a webserver for PHP. Thanks, Pinakee On Wed, Feb 15, 2017 at 2:17 PM, Guillaume Quintard < guillaume at varnish-software.com> wrote: > Hi, I'm not sure I get the question. Varnish will serve anything as long > as it's HTTP-based, so you can just point Varnish to Nging, and it will > cache whatever Nginx sends its way. > > -- > Guillaume Quintard > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume at varnish-software.com Wed Feb 15 09:41:31 2017 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Wed, 15 Feb 2017 10:41:31 +0100 Subject: Using Varnish with PHP In-Reply-To: References: Message-ID: Yes, the usual way of doing thing is: Users/Clients----->Varnish---> Nginx---->PHP Varnish is "only" a cache, it won't generate content. -- Guillaume Quintard -------------- next part -------------- An HTML attachment was scrubbed... URL: From pinakee at waltzz.com Wed Feb 15 09:46:40 2017 From: pinakee at waltzz.com (Pinakee Biswas) Date: Wed, 15 Feb 2017 15:16:40 +0530 Subject: Using Varnish with PHP In-Reply-To: References: Message-ID: Hi, Thanks for clarifying. Doesn't it support other protocols like FastCGI to support PHP-FPM? If HTTP is the only option, then would use a web server. Thanks, Pinakee On Wed, Feb 15, 2017 at 3:11 PM, Guillaume Quintard < guillaume at varnish-software.com> wrote: > Yes, the usual way of doing thing is: > > Users/Clients----->Varnish---> Nginx---->PHP > > Varnish is "only" a cache, it won't generate content. > > -- > Guillaume Quintard > -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume at varnish-software.com Wed Feb 15 09:47:41 2017 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Wed, 15 Feb 2017 10:47:41 +0100 Subject: Using Varnish with PHP In-Reply-To: References: Message-ID: Correct, that's HTTP only. -- Guillaume Quintard -------------- next part -------------- An HTML attachment was scrubbed... URL: From bluethundr at gmail.com Wed Feb 15 14:05:48 2017 From: bluethundr at gmail.com (Tim Dunphy) Date: Wed, 15 Feb 2017 09:05:48 -0500 Subject: Using Varnish with PHP In-Reply-To: References: Message-ID: <3D9A7773-1BF9-43BD-8A1E-9DEAF28BF08F@gmail.com> NGIX is a web server. And PHP-FPM is not a protocol. HTTP is the protocol. Your question is confused. Sent from my iPhone > On Feb 15, 2017, at 4:47 AM, Guillaume Quintard wrote: > > Correct, that's HTTP only. > > -- > Guillaume Quintard > > _______________________________________________ > varnish-misc mailing list > varnish-misc at varnish-cache.org > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc From idle at pobox.com Wed Feb 15 16:01:13 2017 From: idle at pobox.com (Brad Tarver) Date: Wed, 15 Feb 2017 10:01:13 -0600 Subject: Using Varnish with PHP In-Reply-To: References: Message-ID: <1487174473.2071058.881960920.528E2D84@webmail.messagingengine.com> I have a working config file for php/wordpress/varnish/nginx if you'd like to take a look. They are plaintext on pastebin. http://pastebin.com/4MgKWWUx -- varnishd 4.0 /etc/varnish/default.vcl for WordPress caching Based on the content of the config, you would need your nginx vhost running on port 8080 and varnish would run on port 80 and/or 443. I have other PHP/nginx/varnish examples here: http://pastebin.com/u/meesteridle On Tue, Feb 14, 2017, at 11:38 PM, Pinakee Biswas wrote: > Hi, > > Not sure if this is the right forum but would appreciate if you could > let me know how to serve PHP pages using Varnish. We have wordpress > (Blog) hosted on our server. Varnish sits behind Nginx in the stack. > Currently, PHP is served directly by Nginx using PhpFpm. We would like > to use varnish to cache wordpress pages. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From idle at pobox.com Wed Feb 15 16:11:31 2017 From: idle at pobox.com (Brad Tarver) Date: Wed, 15 Feb 2017 10:11:31 -0600 Subject: Using Varnish with PHP In-Reply-To: <1487174473.2071058.881960920.528E2D84@webmail.messagingengine.com> References: <1487174473.2071058.881960920.528E2D84@webmail.messagingengine.com> Message-ID: <1487175091.2073310.881984784.0C444D70@webmail.messagingengine.com> oops. I guess varnish doesn't support 443. sorry. still, can be used for 80 On Wed, Feb 15, 2017, at 10:01 AM, Brad Tarver wrote: > I have a working config file for php/wordpress/varnish/nginx if you'd > like to take a look. > > They are plaintext on pastebin. > > http://pastebin.com/4MgKWWUx -- varnishd 4.0 /etc/varnish/default.vcl > for WordPress caching > > Based on the content of the config, you would need your nginx vhost > running on port 8080 and varnish would run on port 80 and/or 443. I > have other PHP/nginx/varnish examples here: > http://pastebin.com/u/meesteridle > > > > > On Tue, Feb 14, 2017, at 11:38 PM, Pinakee Biswas wrote: >> Hi, >> >> Not sure if this is the right forum but would appreciate if you could >> let me know how to serve PHP pages using Varnish. We have wordpress >> (Blog) hosted on our server. Varnish sits behind Nginx in the stack. >> Currently, PHP is served directly by Nginx using PhpFpm. We would >> like to use varnish to cache wordpress pages. >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pinakee at waltzz.com Thu Feb 16 05:25:54 2017 From: pinakee at waltzz.com (Pinakee Biswas) Date: Thu, 16 Feb 2017 10:55:54 +0530 Subject: Using Varnish with PHP In-Reply-To: <3D9A7773-1BF9-43BD-8A1E-9DEAF28BF08F@gmail.com> References: <3D9A7773-1BF9-43BD-8A1E-9DEAF28BF08F@gmail.com> Message-ID: Hi, Thanks for your response. FastCGI is the protocol between Nginx (web server) and PHP-FPM. The PHP pages are served by PHP-FPM. But as I understand, Varnish only supports HTTP. Thanks, Pinakee On Wed, Feb 15, 2017 at 7:35 PM, Tim Dunphy wrote: > NGIX is a web server. And PHP-FPM is not a protocol. HTTP is the protocol. > Your question is confused. > > Sent from my iPhone > > > On Feb 15, 2017, at 4:47 AM, Guillaume Quintard < > guillaume at varnish-software.com> wrote: > > > > Correct, that's HTTP only. > > > > -- > > Guillaume Quintard > > > > _______________________________________________ > > 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 pinakee at waltzz.com Thu Feb 16 05:31:49 2017 From: pinakee at waltzz.com (Pinakee Biswas) Date: Thu, 16 Feb 2017 11:01:49 +0530 Subject: Using Varnish with PHP In-Reply-To: <1487174473.2071058.881960920.528E2D84@webmail.messagingengine.com> References: <1487174473.2071058.881960920.528E2D84@webmail.messagingengine.com> Message-ID: Hi, Thanks for sharing the config - I would certainly take a look. Thanks, Pinakee On Wed, Feb 15, 2017 at 9:31 PM, Brad Tarver wrote: > I have a working config file for php/wordpress/varnish/nginx if you'd like > to take a look. > > They are plaintext on pastebin. > > http://pastebin.com/4MgKWWUx -- varnishd 4.0 /etc/varnish/default.vcl for > WordPress caching > > Based on the content of the config, you would need your nginx vhost > running on port 8080 and varnish would run on port 80 and/or 443. I have > other PHP/nginx/varnish examples here: http://pastebin.com/u/meesteridle > > > > > On Tue, Feb 14, 2017, at 11:38 PM, Pinakee Biswas wrote: > > Hi, > > Not sure if this is the right forum but would appreciate if you could let > me know how to serve PHP pages using Varnish. We have wordpress (Blog) > hosted on our server. Varnish sits behind Nginx in the stack. > Currently, PHP is served directly by Nginx using PhpFpm. We would like to > use varnish to cache wordpress pages. > > > > _______________________________________________ > 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 colas.delmas at gmail.com Thu Feb 16 21:42:15 2017 From: colas.delmas at gmail.com (Nicolas Delmas) Date: Thu, 16 Feb 2017 22:42:15 +0100 Subject: X-Forwarded-For automatically set in varnish 4.0? In-Reply-To: References: <948AAF6D-C0AE-4E32-B20A-F100CE5216F2@lv.de> Message-ID: Hello, Why is this part if code useless ? Is that because this code is in the builtin.vcl ? Thanks Le 14 f?vr. 2017 10:10 AM, "Guillaume Quintard" < guillaume at varnish-software.com> a ?crit : > Hi, > > The snippet is legacy code for v3, and it's now useless/counter-productive > in v4. > > -- > Guillaume Quintard > > On Tue, Feb 14, 2017 at 9:20 AM, Donath, Niklas < > Niklas.Donath at lvdigital.de> wrote: > >> Hi there, >> >> >> >> actually, i am in a migration project from varnish 3 to varnish 4.0, and >> i was confused about the x-forwarded-for header settings in varnish 4.0: >> >> in the official doc, it says that x-forwarded-for is automatically set, >> like it is obvious in the source code: https://github.com/varnishcach >> e/varnish-cache/blob/4.0/bin/varnishd/cache/cache_req_fsm.c#L724 >> >> >> >> But a lot of people are adding a snippet for vcl_recv like >> >> >> >> if (req.restarts == 0) { >> >> if (req.http.X-Forwarded-For) { >> >> set req.http.X-Forwarded-For = req.http.X-Forwarded-For + ", " + >> client.ip; >> >> } else { >> >> set req.http.X-Forwarded-For = client.ip; >> >> } >> >> } >> >> >> >> Which, from my point of view, is the same implementation as it already >> should exist as the docs say. I currently do not have a LB/proxy >> infrastructure to test it, so maybe someone can clear this up, if >> x-forwarded-for is automatically set by varnish before executing the >> vcl_recv from my custom .vcl-file, or if the given snippet is required to >> set the real user ip for x-forwarded-for. >> >> >> >> Thank you very much! >> >> >> >> Greetings, Niklas >> >> >> >> _______________________________________________ >> varnish-misc mailing list >> varnish-misc at varnish-cache.org >> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc >> > > > _______________________________________________ > 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 reza at varnish-software.com Thu Feb 16 22:14:44 2017 From: reza at varnish-software.com (Reza Naghibi) Date: Thu, 16 Feb 2017 17:14:44 -0500 Subject: X-Forwarded-For automatically set in varnish 4.0? In-Reply-To: References: <948AAF6D-C0AE-4E32-B20A-F100CE5216F2@lv.de> Message-ID: Hey Nicolas, This is done before vcl_recv is called in varnishd code: https://github.com/varnishcache/varnish-cache/blob/varnish-4.0.0/bin/varnishd/cache/cache_req_fsm.c#L719-L728 -- Reza Naghibi Varnish Software On Thu, Feb 16, 2017 at 4:42 PM, Nicolas Delmas wrote: > Hello, > > Why is this part if code useless ? > Is that because this code is in the builtin.vcl ? > > Thanks > > Le 14 f?vr. 2017 10:10 AM, "Guillaume Quintard" < > guillaume at varnish-software.com> a ?crit : > >> Hi, >> >> The snippet is legacy code for v3, and it's now >> useless/counter-productive in v4. >> >> -- >> Guillaume Quintard >> >> On Tue, Feb 14, 2017 at 9:20 AM, Donath, Niklas < >> Niklas.Donath at lvdigital.de> wrote: >> >>> Hi there, >>> >>> >>> >>> actually, i am in a migration project from varnish 3 to varnish 4.0, and >>> i was confused about the x-forwarded-for header settings in varnish 4.0: >>> >>> in the official doc, it says that x-forwarded-for is automatically set, >>> like it is obvious in the source code: https://github.com/varnishcach >>> e/varnish-cache/blob/4.0/bin/varnishd/cache/cache_req_fsm.c#L724 >>> >>> >>> >>> But a lot of people are adding a snippet for vcl_recv like >>> >>> >>> >>> if (req.restarts == 0) { >>> >>> if (req.http.X-Forwarded-For) { >>> >>> set req.http.X-Forwarded-For = req.http.X-Forwarded-For + ", " + >>> client.ip; >>> >>> } else { >>> >>> set req.http.X-Forwarded-For = client.ip; >>> >>> } >>> >>> } >>> >>> >>> >>> Which, from my point of view, is the same implementation as it already >>> should exist as the docs say. I currently do not have a LB/proxy >>> infrastructure to test it, so maybe someone can clear this up, if >>> x-forwarded-for is automatically set by varnish before executing the >>> vcl_recv from my custom .vcl-file, or if the given snippet is required to >>> set the real user ip for x-forwarded-for. >>> >>> >>> >>> Thank you very much! >>> >>> >>> >>> Greetings, Niklas >>> >>> >>> >>> _______________________________________________ >>> varnish-misc mailing list >>> varnish-misc at varnish-cache.org >>> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc >>> >> >> >> _______________________________________________ >> varnish-misc mailing list >> varnish-misc at varnish-cache.org >> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc >> > > _______________________________________________ > 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 colas.delmas at gmail.com Thu Feb 16 22:34:23 2017 From: colas.delmas at gmail.com (Nicolas Delmas) Date: Thu, 16 Feb 2017 23:34:23 +0100 Subject: X-Forwarded-For automatically set in varnish 4.0? In-Reply-To: References: <948AAF6D-C0AE-4E32-B20A-F100CE5216F2@lv.de> Message-ID: Thank you. I will look your link, maybe I have other useless code in my configuration files Le 16 f?vr. 2017 11:14 PM, "Reza Naghibi" a ?crit : > Hey Nicolas, > > This is done before vcl_recv is called in varnishd code: > > https://github.com/varnishcache/varnish-cache/blob/varnish-4.0.0/bin/ > varnishd/cache/cache_req_fsm.c#L719-L728 > > -- > Reza Naghibi > Varnish Software > > On Thu, Feb 16, 2017 at 4:42 PM, Nicolas Delmas > wrote: > >> Hello, >> >> Why is this part if code useless ? >> Is that because this code is in the builtin.vcl ? >> >> Thanks >> >> Le 14 f?vr. 2017 10:10 AM, "Guillaume Quintard" < >> guillaume at varnish-software.com> a ?crit : >> >>> Hi, >>> >>> The snippet is legacy code for v3, and it's now >>> useless/counter-productive in v4. >>> >>> -- >>> Guillaume Quintard >>> >>> On Tue, Feb 14, 2017 at 9:20 AM, Donath, Niklas < >>> Niklas.Donath at lvdigital.de> wrote: >>> >>>> Hi there, >>>> >>>> >>>> >>>> actually, i am in a migration project from varnish 3 to varnish 4.0, >>>> and i was confused about the x-forwarded-for header settings in varnish 4.0: >>>> >>>> in the official doc, it says that x-forwarded-for is automatically set, >>>> like it is obvious in the source code: https://github.com/varnishcach >>>> e/varnish-cache/blob/4.0/bin/varnishd/cache/cache_req_fsm.c#L724 >>>> >>>> >>>> >>>> But a lot of people are adding a snippet for vcl_recv like >>>> >>>> >>>> >>>> if (req.restarts == 0) { >>>> >>>> if (req.http.X-Forwarded-For) { >>>> >>>> set req.http.X-Forwarded-For = req.http.X-Forwarded-For + ", " >>>> + client.ip; >>>> >>>> } else { >>>> >>>> set req.http.X-Forwarded-For = client.ip; >>>> >>>> } >>>> >>>> } >>>> >>>> >>>> >>>> Which, from my point of view, is the same implementation as it already >>>> should exist as the docs say. I currently do not have a LB/proxy >>>> infrastructure to test it, so maybe someone can clear this up, if >>>> x-forwarded-for is automatically set by varnish before executing the >>>> vcl_recv from my custom .vcl-file, or if the given snippet is required to >>>> set the real user ip for x-forwarded-for. >>>> >>>> >>>> >>>> Thank you very much! >>>> >>>> >>>> >>>> Greetings, Niklas >>>> >>>> >>>> >>>> _______________________________________________ >>>> varnish-misc mailing list >>>> varnish-misc at varnish-cache.org >>>> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc >>>> >>> >>> >>> _______________________________________________ >>> varnish-misc mailing list >>> varnish-misc at varnish-cache.org >>> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc >>> >> >> _______________________________________________ >> 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 ojoa at vwd.com Fri Feb 17 06:32:29 2017 From: ojoa at vwd.com (Oliver Joa) Date: Fri, 17 Feb 2017 07:32:29 +0100 Subject: X-Forwarded-For automatically set in varnish 4.0? In-Reply-To: References: <948AAF6D-C0AE-4E32-B20A-F100CE5216F2@lv.de> Message-ID: Hi, On 14.02.2017 09:41, Guillaume Quintard wrote: > Hi, > > The snippet is legacy code for v3, and it's now > useless/counter-productive in v4. why is the x-forwarded-for-handling now in the source-code? I still use v3 and have modified it in the vcl-code. If I want to use v4 how can I modify it? Thanks and regards Olli > > -- > Guillaume Quintard > > On Tue, Feb 14, 2017 at 9:20 AM, Donath, Niklas > > wrote: > > Hi there,____ > > __ __ > > actually, i am in a migration project from varnish 3 to varnish 4.0, > and i was confused about the x-forwarded-for header settings in > varnish 4.0:____ > > in the official doc, it says that x-forwarded-for is automatically > set, like it is obvious in the source code: > https://github.com/varnishcache/varnish-cache/blob/4.0/bin/varnishd/cache/cache_req_fsm.c#L724 > ____ > > __ __ > > But a lot of people are adding a snippet for vcl_recv like____ > > __ __ > > if (req.restarts == 0) {____ > > if (req.http.X-Forwarded-For) {____ > > set req.http.X-Forwarded-For = req.http.X-Forwarded-For + ", > " + client.ip;____ > > } else {____ > > set req.http.X-Forwarded-For = client.ip;____ > > }____ > > }____ > > __ __ > > Which, from my point of view, is the same implementation as it > already should exist as the docs say. I currently do not have a > LB/proxy infrastructure to test it, so maybe someone can clear this > up, if x-forwarded-for is automatically set by varnish before > executing the vcl_recv from my custom .vcl-file, or if the given > snippet is required to set the real user ip for x-forwarded-for.____ > > __ __ > > Thank you very much!____ > > __ __ > > Greetings, Niklas____ > > __ __ > > > _______________________________________________ > varnish-misc mailing list > varnish-misc at varnish-cache.org > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc > > > > > > _______________________________________________ > varnish-misc mailing list > varnish-misc at varnish-cache.org > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc > -- Dipl. Inf. (FH) Oliver Joa Systems, Zeitbeauftragter | Web Technology Systems | vwd group vwd Vereinigte Wirtschaftsdienste GmbH Karl-G?tz-Stra?e 5 | 97424 Schweinfurt Telefon: +49 9721 499895-62 | Telefax: +49 9721 499895-77 ojoa at vwd.com | www.vwd.com __________________________________________________________________ vwd Vereinigte Wirtschaftsdienste GmbH Sitz der Gesellschaft: Tilsiter Stra?e 1 | 60487 Frankfurt am Main Handelsregister: B Frankfurt am Main HRB 100445 Gesch?ftsf?hrung: Martin Gijssel (CEO), Udo Kersting ********************************************************************************************** Der Inhalt dieser E-Mail ist ausschlie?lich f?r den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte, dass jede Form der Kenntnisnahme, Ver?ffentlichung, Vervielf?ltigung oder Weitergabe des Inhalts dieser E-Mail unzul?ssig ist. Wir bitten Sie, sich in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen. The content of this e-mail is meant exclusively for the person to whom it is addressed. If you are not the person to whom this e-mail is addressed or his/her representative, please be informed that any form of knowledge, publication, duplication or distribution of the content of this e-mail is inadmissible. In such cases we kindly ask you to contact the sender of this e-mail. ********************************************************************************************** From lagged at gmail.com Fri Feb 17 07:04:58 2017 From: lagged at gmail.com (Andrei) Date: Fri, 17 Feb 2017 01:04:58 -0600 Subject: X-Forwarded-For automatically set in varnish 4.0? In-Reply-To: References: <948AAF6D-C0AE-4E32-B20A-F100CE5216F2@lv.de> Message-ID: You can modify it as you normally would in vcl_recv, by setting req.http.X-Forwarded-For. Note the header may contain two IP addresses depending on your stack, and only one should typically be passed to the backend for proper logging. On Fri, Feb 17, 2017 at 12:32 AM, Oliver Joa wrote: > Hi, > > On 14.02.2017 09:41, Guillaume Quintard wrote: > >> Hi, >> >> The snippet is legacy code for v3, and it's now >> useless/counter-productive in v4. >> > > why is the x-forwarded-for-handling now in the source-code? I still use > v3 and have modified it in the vcl-code. If I want to use v4 how can I > modify it? > > Thanks and regards > > Olli > > >> -- >> Guillaume Quintard >> >> On Tue, Feb 14, 2017 at 9:20 AM, Donath, Niklas >> > wrote: >> >> Hi there,____ >> >> __ __ >> >> actually, i am in a migration project from varnish 3 to varnish 4.0, >> and i was confused about the x-forwarded-for header settings in >> varnish 4.0:____ >> >> in the official doc, it says that x-forwarded-for is automatically >> set, like it is obvious in the source code: >> https://github.com/varnishcache/varnish-cache/blob/4.0/bin/ >> varnishd/cache/cache_req_fsm.c#L724 >> > varnishd/cache/cache_req_fsm.c#L724>____ >> >> __ __ >> >> But a lot of people are adding a snippet for vcl_recv like____ >> >> __ __ >> >> if (req.restarts == 0) {____ >> >> if (req.http.X-Forwarded-For) {____ >> >> set req.http.X-Forwarded-For = req.http.X-Forwarded-For + ", >> " + client.ip;____ >> >> } else {____ >> >> set req.http.X-Forwarded-For = client.ip;____ >> >> }____ >> >> }____ >> >> __ __ >> >> Which, from my point of view, is the same implementation as it >> already should exist as the docs say. I currently do not have a >> LB/proxy infrastructure to test it, so maybe someone can clear this >> up, if x-forwarded-for is automatically set by varnish before >> executing the vcl_recv from my custom .vcl-file, or if the given >> snippet is required to set the real user ip for x-forwarded-for.____ >> >> __ __ >> >> Thank you very much!____ >> >> __ __ >> >> Greetings, Niklas____ >> >> __ __ >> >> >> _______________________________________________ >> varnish-misc mailing list >> varnish-misc at varnish-cache.org > > >> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc >> >> >> >> >> >> _______________________________________________ >> varnish-misc mailing list >> varnish-misc at varnish-cache.org >> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc >> >> > > -- > Dipl. Inf. (FH) Oliver Joa > Systems, Zeitbeauftragter | Web Technology Systems | vwd group > > vwd Vereinigte Wirtschaftsdienste GmbH > Karl-G?tz-Stra?e 5 | 97424 Schweinfurt > Telefon: +49 9721 499895-62 | Telefax: +49 9721 499895-77 > ojoa at vwd.com | www.vwd.com > __________________________________________________________________ > vwd Vereinigte Wirtschaftsdienste GmbH > Sitz der Gesellschaft: Tilsiter Stra?e 1 | 60487 Frankfurt am Main > Handelsregister: B Frankfurt am Main HRB 100445 > Gesch?ftsf?hrung: Martin Gijssel (CEO), Udo Kersting > > ************************************************************ > ********************************** > > Der Inhalt dieser E-Mail ist ausschlie?lich f?r den bezeichneten > Adressaten bestimmt. > Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen > Vertreter sein > sollten, so beachten Sie bitte, dass jede Form der Kenntnisnahme, > Ver?ffentlichung, > Vervielf?ltigung oder Weitergabe des Inhalts dieser E-Mail unzul?ssig ist. > Wir bitten > Sie, sich in diesem Fall mit dem Absender der E-Mail in Verbindung zu > setzen. > > The content of this e-mail is meant exclusively for the person to whom it > is addressed. > If you are not the person to whom this e-mail is addressed or his/her > representative, > please be informed that any form of knowledge, publication, duplication or > distribution > of the content of this e-mail is inadmissible. In such cases we kindly ask > you to contact > the sender of this e-mail. > > ************************************************************ > ********************************** > > > _______________________________________________ > 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 pentium100 at gmail.com Fri Feb 17 23:20:32 2017 From: pentium100 at gmail.com (Pentium100) Date: Sat, 18 Feb 2017 01:20:32 +0200 Subject: Huge system load when starting Varnish Cache Message-ID: Hello, I am using Varnish Cache to cache IPTV (hls format) segments. It usually works really well, serving 1-3gpbs of traffic. However, if, for some reason, I need to restart it, then shortly after it starts it takes up all CPU (all 24 threads) for "system" until it allocates the set memory limit (malloc,6GB). During that time (a few minutes), the requests from clients are served slow. This is expected since the cache is still not populated, however, the huge system load slows down the whole sever and makes other services slow as well. This problem happens with Varnish version 2.1.5 (the one in the default repository for CentOS6) and with version 4.0.4. If the backend is too slow for some reason, then Varnish usually just keeps using all CPU all the time. Increasing the memory limit above 6GB makes the startup process much longer (too long to wait for it in higher load conditions). Is there a way to limit the system load during this process? -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume at varnish-software.com Sat Feb 18 09:44:35 2017 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Sat, 18 Feb 2017 10:44:35 +0100 Subject: Huge system load when starting Varnish Cache In-Reply-To: References: Message-ID: On a hunch: can you post your Varnish command line please (the v4 one)? -------------- next part -------------- An HTML attachment was scrubbed... URL: From pentium100 at gmail.com Sat Feb 18 10:53:03 2017 From: pentium100 at gmail.com (Pentium100) Date: Sat, 18 Feb 2017 12:53:03 +0200 Subject: Huge system load when starting Varnish Cache In-Reply-To: References: Message-ID: /usr/sbin/varnishd -a :80 -f /etc/varnish/default.vcl -T 127.0.0.1:6082 -t 120 -p thread_pool_min=256 -p thread_pool_max=4095 -p thread_pool_timeout=120 -u varnish -g varnish -S /etc/varnish/secret -s malloc,6G -P /var/run/varnish.pid On Sat, Feb 18, 2017 at 11:44 AM, Guillaume Quintard < guillaume at varnish-software.com> wrote: > On a hunch: can you post your Varnish command line please (the v4 one)? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dridi at varni.sh Mon Feb 20 09:55:44 2017 From: dridi at varni.sh (Dridi Boukelmoune) Date: Mon, 20 Feb 2017 10:55:44 +0100 Subject: Purge specific object, not all variants In-Reply-To: <6C572F02-815C-4215-8078-0A0267773CAE@gmail.com> References: <6C572F02-815C-4215-8078-0A0267773CAE@gmail.com> Message-ID: On Tue, Feb 14, 2017 at 10:37 PM, Danila Vershinin wrote: > Hi, > > Theoretical question. Supposedly I want to introduce Vary: by device > classification: mobile / desktop (via devicedetect etc.) > How would I go around purging just the specific variant of an object, i.e. > purge a page for mobile only? > > The documentation here: > http://book.varnish-software.com/4.0/chapters/Cache_Invalidation.html > Mentions that all methods will purge all variants. > > Is it wrong? Do I correctly understand that forced cache miss is the single > method that allows to purge specific variant of an object? Hello, If you want to purge (that is to say including variants) but don't want a single purge to span both mobile and desktop classifications, I'd recommend adding the classification to the hash key and making sure to purge using the a classification. Dridi From dridi at varni.sh Mon Feb 20 10:02:07 2017 From: dridi at varni.sh (Dridi Boukelmoune) Date: Mon, 20 Feb 2017 11:02:07 +0100 Subject: X-Forwarded-For automatically set in varnish 4.0? In-Reply-To: <948AAF6D-C0AE-4E32-B20A-F100CE5216F2@lv.de> References: <948AAF6D-C0AE-4E32-B20A-F100CE5216F2@lv.de> Message-ID: Hello, Joining the discussion a bit late, but still... On Tue, Feb 14, 2017 at 9:20 AM, Donath, Niklas wrote: > Hi there, > > actually, i am in a migration project from varnish 3 to varnish 4.0, and i > was confused about the x-forwarded-for header settings in varnish 4.0: I strongly recommend moving directly to 4.1, it's the same amount of effort if you come from 3.0 anyway, with better support. > in the official doc, it says that x-forwarded-for is automatically set, like > it is obvious in the source code: > https://github.com/varnishcache/varnish-cache/blob/4.0/bin/varnishd/cache/cache_req_fsm.c#L724 > > > > But a lot of people are adding a snippet for vcl_recv like Yes, people sometimes miss changes, especially during a migration or when docs for older versions are better referenced. > Which, from my point of view, is the same implementation as it already > should exist as the docs say. I currently do not have a LB/proxy > infrastructure to test it, so maybe someone can clear this up, if > x-forwarded-for is automatically set by varnish before executing the > vcl_recv from my custom .vcl-file, or if the given snippet is required to > set the real user ip for x-forwarded-for. You nailed the core code that does it, why even doubt? If you really need to clear your doubts run varnishlog, capture a transaction, and you will see that xff is set before entering vcl_recv for 4.0+. Dridi From dridi at varni.sh Mon Feb 20 10:09:57 2017 From: dridi at varni.sh (Dridi Boukelmoune) Date: Mon, 20 Feb 2017 11:09:57 +0100 Subject: Odd crash In-Reply-To: References: Message-ID: On Mon, Feb 13, 2017 at 6:22 AM, Andrei wrote: > Hello all, > > I woke up to numerous site timeouts, and when I went to check the backend > list, this is what was returned: > > root at aviator [~]# varnishadm backend.list > Unknown request in manager process (child not running). > Type 'help' for more info. > Command failed with error code 101 > root at aviator [~]# This is because the child process is not running as indicated. This can be the case when you start varnish in debug mode, run something like `varnishadm stop` or hit a bug where the child doesn't restart after a panic. > I believe it was likely related to this panic: > https://zerobin.net/?448b15259bc80551#Geo0NImD4HLpGWVZWk9raD7Qhl11VkNZEmh21J2S9mE= It could be the panic after which the manager process failed to spawn a new child. > Varnish has since been upgraded to 4.1.5. Should I still be worried? Which version are you currently running? Dridi From lagged at gmail.com Mon Feb 20 10:22:58 2017 From: lagged at gmail.com (Andrei) Date: Mon, 20 Feb 2017 04:22:58 -0600 Subject: Odd crash In-Reply-To: References: Message-ID: I'm running 4.1.5 using the official repo (Cent6) now: Name : varnish Arch : x86_64 Version : 4.1.5 Release : 1.el6 Size : 6.3 M There haven't been any issues since the upgrade, and that was honestly the first panic I've had with Varnish in 3yrs+. I did notice the "Clock step detected" mentioned in the panic log, and have seen some reports of clock stepping causing issues, but there were no ntp/hwclock changes recorded at the time. On Mon, Feb 20, 2017 at 4:09 AM, Dridi Boukelmoune wrote: > On Mon, Feb 13, 2017 at 6:22 AM, Andrei wrote: > > Hello all, > > > > I woke up to numerous site timeouts, and when I went to check the backend > > list, this is what was returned: > > > > root at aviator [~]# varnishadm backend.list > > Unknown request in manager process (child not running). > > Type 'help' for more info. > > Command failed with error code 101 > > root at aviator [~]# > > This is because the child process is not running as indicated. This > can be the case when you start varnish in debug mode, run something > like `varnishadm stop` or hit a bug where the child doesn't restart > after a panic. > > > I believe it was likely related to this panic: > > https://zerobin.net/?448b15259bc80551#Geo0NImD4HLpGWVZWk9raD7Qhl11Vk > NZEmh21J2S9mE= > > It could be the panic after which the manager process failed to spawn > a new child. > > > Varnish has since been upgraded to 4.1.5. Should I still be worried? > > Which version are you currently running? > > Dridi > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dridi at varni.sh Mon Feb 20 11:02:17 2017 From: dridi at varni.sh (Dridi Boukelmoune) Date: Mon, 20 Feb 2017 12:02:17 +0100 Subject: Odd crash In-Reply-To: References: Message-ID: On Mon, Feb 20, 2017 at 11:22 AM, Andrei wrote: > I'm running 4.1.5 using the official repo (Cent6) now: > > Name : varnish > Arch : x86_64 > Version : 4.1.5 > Release : 1.el6 > Size : 6.3 M > > There haven't been any issues since the upgrade, and that was honestly the > first panic I've had with Varnish in 3yrs+. I did notice the "Clock step > detected" mentioned in the panic log, and have seen some reports of clock > stepping causing issues, but there were no ntp/hwclock changes recorded at > the time. Sorry, I misread your email, it clearly says that you are currently running 4.1.5... What was the version when the panic occurred? Regarding stepping clocks, I believe that we still haven't reached a consensus regarding how to deal with them. So you may still get a crash for this reason. At the very least, it now tells you the reason in the panic message. Dridi From lagged at gmail.com Mon Feb 20 12:09:48 2017 From: lagged at gmail.com (Andrei) Date: Mon, 20 Feb 2017 06:09:48 -0600 Subject: Odd crash In-Reply-To: References: Message-ID: Hi Dridi, Thanks for the input. Looking over the panic I initially linked, the exact version info was: version = varnish-4.1.4 revision 4529ff7 ident = Linux,2.6.32-642.6.2.el6.x86_64,x86_64,-junix,-smalloc,-smalloc,-hcritbit,epoll I had already upgraded to 4.1.5 before mentioning the error on the list, and it's been smooth since. It was just odd that there were no clock changes, yet it panicked due to a stepping, so I figured I'd bring it up. On Mon, Feb 20, 2017 at 5:02 AM, Dridi Boukelmoune wrote: > On Mon, Feb 20, 2017 at 11:22 AM, Andrei wrote: > > I'm running 4.1.5 using the official repo (Cent6) now: > > > > Name : varnish > > Arch : x86_64 > > Version : 4.1.5 > > Release : 1.el6 > > Size : 6.3 M > > > > There haven't been any issues since the upgrade, and that was honestly > the > > first panic I've had with Varnish in 3yrs+. I did notice the "Clock step > > detected" mentioned in the panic log, and have seen some reports of clock > > stepping causing issues, but there were no ntp/hwclock changes recorded > at > > the time. > > Sorry, I misread your email, it clearly says that you are currently > running 4.1.5... What was the version when the panic occurred? > > Regarding stepping clocks, I believe that we still haven't reached a > consensus regarding how to deal with them. So you may still get a > crash for this reason. At the very least, it now tells you the reason > in the panic message. > > Dridi > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dridi at varni.sh Mon Feb 20 13:13:12 2017 From: dridi at varni.sh (Dridi Boukelmoune) Date: Mon, 20 Feb 2017 14:13:12 +0100 Subject: Odd crash In-Reply-To: References: Message-ID: On Mon, Feb 20, 2017 at 1:09 PM, Andrei wrote: > Hi Dridi, > > Thanks for the input. Looking over the panic I initially linked, the exact > version info was: > > version = varnish-4.1.4 revision 4529ff7 ident = > Linux,2.6.32-642.6.2.el6.x86_64,x86_64,-junix,-smalloc,-smalloc,-hcritbit,epoll Yes, I definitely need to get the hang of this "reading" thing. > I had already upgraded to 4.1.5 before mentioning the error on the list, and > it's been smooth since. It was just odd that there were no clock changes, > yet it panicked due to a stepping, so I figured I'd bring it up. There's a bug I don't remember and couldn't find after a quick search. But basically it would cause the child to not restart after a panic. Something like: - panic (child crashed) - restart - CLI timeout during restart - kill the child - varnish running without a cache process The last step is similar to the one you ran into, since you couldn't list backends via the CLI. But I couldn't find this bug after a quick search and looking at the changelog I don't see anything related. So I would say you may end up in the same situation even with the latest 4.1 release. You should collect syslogs (enabled by default) and see what Varnish has to say shortly before/after a panic, it might give a clue. Dridi From lagged at gmail.com Mon Feb 20 14:17:42 2017 From: lagged at gmail.com (Andrei) Date: Mon, 20 Feb 2017 08:17:42 -0600 Subject: Odd crash In-Reply-To: References: Message-ID: On Mon, Feb 20, 2017 at 7:13 AM, Dridi Boukelmoune wrote: > On Mon, Feb 20, 2017 at 1:09 PM, Andrei wrote: > > Hi Dridi, > > > > Thanks for the input. Looking over the panic I initially linked, the > exact > > version info was: > > > > version = varnish-4.1.4 revision 4529ff7 ident = > > Linux,2.6.32-642.6.2.el6.x86_64,x86_64,-junix,-smalloc,- > smalloc,-hcritbit,epoll > > Yes, I definitely need to get the hang of this "reading" thing. > It's overrated :) > > > I had already upgraded to 4.1.5 before mentioning the error on the list, > and > > it's been smooth since. It was just odd that there were no clock changes, > > yet it panicked due to a stepping, so I figured I'd bring it up. > > There's a bug I don't remember and couldn't find after a quick search. > But basically it would cause the child to not restart after a panic. > > Something like: > > - panic (child crashed) > - restart > - CLI timeout during restart > - kill the child > - varnish running without a cache process > > The last step is similar to the one you ran into, since you couldn't > list backends via the CLI. But I couldn't find this bug after a quick > search and looking at the changelog I don't see anything related. So I > would say you may end up in the same situation even with the latest > 4.1 release. You should collect syslogs (enabled by default) and see > what Varnish has to say shortly before/after a panic, it might give a > clue. > > Dridi > Thanks for the details, I'll track it down from there and keep an eye on the issue(s). Nothing in /var/log/messages other than a ban sent ~6h prior: Feb 12 17:09:17 aviator varnishd[15791]: CLI telnet 127.0.0.1 55284 127.0.0.1 6082 Rd auth NNN Feb 12 17:09:17 aviator varnishd[15791]: CLI telnet 127.0.0.1 55284 127.0.0.1 6082 Wr 200 -----------------------------#012Varnish Cache CLI 1.0#012-----------------------------#012Linux,2.6.32-642.6.2.el6.x86_64,x86_64,-junix,-smalloc,-smalloc,-hcritbit#012varnish-4.1.4 revision 4529ff7#012#012Type 'help' for command list.#012Type 'quit' to close CLI session. Feb 12 17:09:17 aviator varnishd[15791]: CLI telnet 127.0.0.1 55284 127.0.0.1 6082 Rd ping Feb 12 17:09:17 aviator varnishd[15791]: CLI telnet 127.0.0.1 55284 127.0.0.1 6082 Wr 200 PONG 1486912157 1.0 Feb 12 17:09:17 aviator varnishd[15791]: CLI telnet 127.0.0.1 55284 127.0.0.1 6082 Rd ban req.http.Host ~ ".*" Feb 12 17:09:17 aviator varnishd[15791]: CLI telnet 127.0.0.1 55284 127.0.0.1 6082 Wr 200 -------------- next part -------------- An HTML attachment was scrubbed... URL: From lagged at gmail.com Tue Feb 21 04:59:30 2017 From: lagged at gmail.com (Andrei) Date: Mon, 20 Feb 2017 22:59:30 -0600 Subject: Odd crash In-Reply-To: References: <1CC6D7D1-743B-444E-A54A-768523C403BE@posteo.de> Message-ID: This definitely isn't an SELinux issue on my end. I've also seen Varnish work fine with SELinux (after policy updates as Dridi mentioned). On Mon, Feb 20, 2017 at 4:43 PM, Dridi Boukelmoune wrote: > On Mon, Feb 20, 2017 at 11:25 PM, Daniel Parthey wrote: > > It might be an SElinux Problem. Varnish 4.1.3 seems incompatible with the > > default SELinux Rules on CentOS. We ran into problems with child workers > > when selinux was enabled. > > I don't think it's related to SELinux. The main problem with > CentOS/Red Hat/Fedora is the SELinux policy shipped by those > distributions. They give very little margin and it becomes easy to > make a change in your configuration that ends up rejected. At the > same time conservative defaults give a smaller attack surface... > > > setenforce 0 > > service varnish restart > > > > and for permanent boot-safe change: > > > > /etc/sysconfig/selinux > > selinux=disabled > > This is _not_ how you solve SELinux problems. You switch to > permissive, collect audit logs while running offending software, > update the policy and switch back to enforcing. > > > Might make varnish more stable. > > > > Not sure why the default CentOS Policy (at least on CentOS 7) affect > varnish > > master/child communications. > > It should not, I'd like to see evidence that this is happening. Please > open a github issue on the pkg-varnish-cache project if you manage > to reproduce it and let us know how. > > Dridi > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vlad.rusu at lola.tech Tue Feb 21 07:46:11 2017 From: vlad.rusu at lola.tech (Vlad Rusu) Date: Tue, 21 Feb 2017 09:46:11 +0200 Subject: Varnish 4.1 - "Hash" in varnishlog is.. masked Message-ID: <421A95A7-57E3-45CD-9499-13CA67505C67@lola.tech> Hey there, Per https://varnish-cache.org/docs/4.1/reference/vsl.html , ?Hash? is masked by default. I am trying to use varnishlog to see the values added to the hash and I just can?t find a way to show it. Of course, I can use std to log or various other techniques, but am interested in seeing the Hash like we used to with Varnish 3. Any hints? Thanks a lot! -- Vlad Rusu skypeid: rusu.h.vlad | cell: +40758066019 Lola Tech | lola.tech -------------- next part -------------- An HTML attachment was scrubbed... URL: From geoff at uplex.de Tue Feb 21 07:57:31 2017 From: geoff at uplex.de (Geoff Simmons) Date: Tue, 21 Feb 2017 08:57:31 +0100 Subject: Varnish 4.1 - "Hash" in varnishlog is.. masked In-Reply-To: <421A95A7-57E3-45CD-9499-13CA67505C67@lola.tech> References: <421A95A7-57E3-45CD-9499-13CA67505C67@lola.tech> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 02/21/2017 08:46 AM, Vlad Rusu wrote: > > Per https://varnish-cache.org/docs/4.1/reference/vsl.html, ?Hash? > is masked by default. > > I am trying to use varnishlog to see the values added to the hash > and I just can?t find a way to show it. Start varnishd with: -p vsl_mask=+Hash The default setting for vsl_mask is: - -VCL_trace,-WorkThread,-Hash,-VfpAcct Documentation here: https://www.varnish-cache.org/docs/4.1/reference/varnishd.html#vsl-mask HTH, Geoff - -- ** * * UPLEX - Nils Goroll Systemoptimierung Scheffelstra?e 32 22301 Hamburg Tel +49 40 2880 5731 Mob +49 176 636 90917 Fax +49 40 42949753 http://uplex.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJYq/LrAAoJEOUwvh9pJNURmIkP/iVnEpxv1/h/z9Fa/h7njuOW vHapCbAeXpji7tD5uapWPb8a3h8vEAq1hxVPL2+eSAcrrSh4tsUaF0GaW83UTNms aOTecGxlF/n0HTCE/HAyKHgOD7B5dffeq1sm52UeB/mvz4GbhVg/K77tZIxNc12g HrtP0SXsKqYIHasE2QBryAdlkFBA7b36oyCGELnw5fpLsBqiJQ1AmjcmV71Oz6YE 9CkPK6e5FHRlMaKKPcbiI6upd6lGHh7SKUEOdVLI8ne4luvJQqEArvv1s6ZpHoY8 744M/yxnoDOyRBnr+pGSOo6Vv+HlN4+2vh8mXzgtD7PxjLjp3H9ooPbfyzcGmuPK i9PxuuKu6Epat+C38Y+VzPvbZeCO/S1ZvOepR7eId8Honwh/bAxfdOriqmVETfsI YPM+iEYWkDHvtjWwDHhkmfW6cAvWh564j2JZT0hAmY0INFpiZ5uMohId3nAUZ9/D FIQnEaO+67Y89nvkQZlcSB3h/D0Tu67oSuGs6JxqcND48Z1pIDsznxunl9Hly2Vw jzRg6a+jW/ZO/inQpA76SHhrlcEN6peakaGusHT/MrJPlLOkhzt2vGYxiusKvA2f ddVa6XWPjugcFLxEHgOck+QCDFBkz8Y+qVdWKEA5jHhFlc3bvmla+3zU/olEeyvk +q4oQ5Kg6zhVlY9bssZZ =22Ly -----END PGP SIGNATURE----- From vlad.rusu at lola.tech Tue Feb 21 07:58:40 2017 From: vlad.rusu at lola.tech (Vlad Rusu) Date: Tue, 21 Feb 2017 09:58:40 +0200 Subject: Varnish 4.1 - "Hash" in varnishlog is.. masked In-Reply-To: References: <421A95A7-57E3-45CD-9499-13CA67505C67@lola.tech> Message-ID: Thanks a lot! -- Vlad Rusu skypeid: rusu.h.vlad | cell: +40758066019 Lola Tech | lola.tech > On 21 Feb 2017, at 09:57, Geoff Simmons wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 02/21/2017 08:46 AM, Vlad Rusu wrote: >> >> Per https://varnish-cache.org/docs/4.1/reference/vsl.html, ?Hash? >> is masked by default. >> >> I am trying to use varnishlog to see the values added to the hash >> and I just can?t find a way to show it. > > Start varnishd with: -p vsl_mask=+Hash > > The default setting for vsl_mask is: > - -VCL_trace,-WorkThread,-Hash,-VfpAcct > > Documentation here: > https://www.varnish-cache.org/docs/4.1/reference/varnishd.html#vsl-mask > > > HTH, > Geoff > - -- > ** * * UPLEX - Nils Goroll Systemoptimierung > > Scheffelstra?e 32 > 22301 Hamburg > > Tel +49 40 2880 5731 > Mob +49 176 636 90917 > Fax +49 40 42949753 > > http://uplex.de > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQIcBAEBCAAGBQJYq/LrAAoJEOUwvh9pJNURmIkP/iVnEpxv1/h/z9Fa/h7njuOW > vHapCbAeXpji7tD5uapWPb8a3h8vEAq1hxVPL2+eSAcrrSh4tsUaF0GaW83UTNms > aOTecGxlF/n0HTCE/HAyKHgOD7B5dffeq1sm52UeB/mvz4GbhVg/K77tZIxNc12g > HrtP0SXsKqYIHasE2QBryAdlkFBA7b36oyCGELnw5fpLsBqiJQ1AmjcmV71Oz6YE > 9CkPK6e5FHRlMaKKPcbiI6upd6lGHh7SKUEOdVLI8ne4luvJQqEArvv1s6ZpHoY8 > 744M/yxnoDOyRBnr+pGSOo6Vv+HlN4+2vh8mXzgtD7PxjLjp3H9ooPbfyzcGmuPK > i9PxuuKu6Epat+C38Y+VzPvbZeCO/S1ZvOepR7eId8Honwh/bAxfdOriqmVETfsI > YPM+iEYWkDHvtjWwDHhkmfW6cAvWh564j2JZT0hAmY0INFpiZ5uMohId3nAUZ9/D > FIQnEaO+67Y89nvkQZlcSB3h/D0Tu67oSuGs6JxqcND48Z1pIDsznxunl9Hly2Vw > jzRg6a+jW/ZO/inQpA76SHhrlcEN6peakaGusHT/MrJPlLOkhzt2vGYxiusKvA2f > ddVa6XWPjugcFLxEHgOck+QCDFBkz8Y+qVdWKEA5jHhFlc3bvmla+3zU/olEeyvk > +q4oQ5Kg6zhVlY9bssZZ > =22Ly > -----END PGP SIGNATURE----- -------------- next part -------------- An HTML attachment was scrubbed... URL: From vlad.rusu at lola.tech Tue Feb 21 08:02:32 2017 From: vlad.rusu at lola.tech (Vlad Rusu) Date: Tue, 21 Feb 2017 10:02:32 +0200 Subject: Varnish 4.1 - "Hash" in varnishlog is.. masked In-Reply-To: References: <421A95A7-57E3-45CD-9499-13CA67505C67@lola.tech> Message-ID: <18142121-7E0C-435A-B4BD-100AA83FE93F@lola.tech> Are those %00 expected at the end of the Hash? ... - ReqURL /sites/all/themes/allegiant3/g4www-style/dist/styles/style.min.1.css ... - VCL_call RECV ... - VCL_call HASH - Hash "/sites/all/themes/allegiant3/g4www-style/dist/styles/style.min.1.css%00" - Hash "444%00" - Hash ?www?..com%00" Thanks! -- Vlad Rusu skypeid: rusu.h.vlad | cell: +40758066019 Lola Tech | lola.tech > On 21 Feb 2017, at 09:58, Vlad Rusu wrote: > > Thanks a lot! > > -- > Vlad Rusu > skypeid: rusu.h.vlad | cell: +40758066019 > > Lola Tech | lola.tech >> On 21 Feb 2017, at 09:57, Geoff Simmons > wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> On 02/21/2017 08:46 AM, Vlad Rusu wrote: >>> >>> Per https://varnish-cache.org/docs/4.1/reference/vsl.html , ?Hash? >>> is masked by default. >>> >>> I am trying to use varnishlog to see the values added to the hash >>> and I just can?t find a way to show it. >> >> Start varnishd with: -p vsl_mask=+Hash >> >> The default setting for vsl_mask is: >> - -VCL_trace,-WorkThread,-Hash,-VfpAcct >> >> Documentation here: >> https://www.varnish-cache.org/docs/4.1/reference/varnishd.html#vsl-mask >> >> >> HTH, >> Geoff >> - -- >> ** * * UPLEX - Nils Goroll Systemoptimierung >> >> Scheffelstra?e 32 >> 22301 Hamburg >> >> Tel +49 40 2880 5731 >> Mob +49 176 636 90917 >> Fax +49 40 42949753 >> >> http://uplex.de >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2 >> >> iQIcBAEBCAAGBQJYq/LrAAoJEOUwvh9pJNURmIkP/iVnEpxv1/h/z9Fa/h7njuOW >> vHapCbAeXpji7tD5uapWPb8a3h8vEAq1hxVPL2+eSAcrrSh4tsUaF0GaW83UTNms >> aOTecGxlF/n0HTCE/HAyKHgOD7B5dffeq1sm52UeB/mvz4GbhVg/K77tZIxNc12g >> HrtP0SXsKqYIHasE2QBryAdlkFBA7b36oyCGELnw5fpLsBqiJQ1AmjcmV71Oz6YE >> 9CkPK6e5FHRlMaKKPcbiI6upd6lGHh7SKUEOdVLI8ne4luvJQqEArvv1s6ZpHoY8 >> 744M/yxnoDOyRBnr+pGSOo6Vv+HlN4+2vh8mXzgtD7PxjLjp3H9ooPbfyzcGmuPK >> i9PxuuKu6Epat+C38Y+VzPvbZeCO/S1ZvOepR7eId8Honwh/bAxfdOriqmVETfsI >> YPM+iEYWkDHvtjWwDHhkmfW6cAvWh564j2JZT0hAmY0INFpiZ5uMohId3nAUZ9/D >> FIQnEaO+67Y89nvkQZlcSB3h/D0Tu67oSuGs6JxqcND48Z1pIDsznxunl9Hly2Vw >> jzRg6a+jW/ZO/inQpA76SHhrlcEN6peakaGusHT/MrJPlLOkhzt2vGYxiusKvA2f >> ddVa6XWPjugcFLxEHgOck+QCDFBkz8Y+qVdWKEA5jHhFlc3bvmla+3zU/olEeyvk >> +q4oQ5Kg6zhVlY9bssZZ >> =22Ly >> -----END PGP SIGNATURE----- > -------------- next part -------------- An HTML attachment was scrubbed... URL: From guillaume at varnish-software.com Tue Feb 21 08:09:29 2017 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Tue, 21 Feb 2017 09:09:29 +0100 Subject: Varnish 4.1 - "Hash" in varnishlog is.. masked In-Reply-To: <421A95A7-57E3-45CD-9499-13CA67505C67@lola.tech> References: <421A95A7-57E3-45CD-9499-13CA67505C67@lola.tech> Message-ID: Hello Vlad, Normally, varnish is configured using either the command line or using varnishadm. You can have a look at "varnishadm param.show vsl_mask" But we could probably have a pointer in the doc. Care to do it? -- Guillaume Quintard -------------- next part -------------- An HTML attachment was scrubbed... URL: From dridi at varni.sh Tue Feb 21 08:14:44 2017 From: dridi at varni.sh (Dridi Boukelmoune) Date: Tue, 21 Feb 2017 09:14:44 +0100 Subject: Varnish 4.1 - "Hash" in varnishlog is.. masked In-Reply-To: <421A95A7-57E3-45CD-9499-13CA67505C67@lola.tech> References: <421A95A7-57E3-45CD-9499-13CA67505C67@lola.tech> Message-ID: On Tue, Feb 21, 2017 at 8:46 AM, Vlad Rusu wrote: > Hey there, > > Per https://varnish-cache.org/docs/4.1/reference/vsl.html, ?Hash? is masked > by default. > > I am trying to use varnishlog to see the values added to the hash and I just > can?t find a way to show it. > > Of course, I can use std to log or various other techniques, but am > interested in seeing the Hash like we used to with Varnish 3. > > Any hints? Hello Vlad, You are looking for the VSL mask, see man varnishd. Dridi From guillaume at varnish-software.com Tue Feb 21 08:58:34 2017 From: guillaume at varnish-software.com (Guillaume Quintard) Date: Tue, 21 Feb 2017 09:58:34 +0100 Subject: Varnish 4.1 - "Hash" in varnishlog is.. masked In-Reply-To: <18142121-7E0C-435A-B4BD-100AA83FE93F@lola.tech> References: <421A95A7-57E3-45CD-9499-13CA67505C67@lola.tech> <18142121-7E0C-435A-B4BD-100AA83FE93F@lola.tech> Message-ID: yes, these are the null character. This makes sure that "hash("123");hash("456");" returns a different result than "hash("1");hash("23456");" -- Guillaume Quintard On Tue, Feb 21, 2017 at 9:02 AM, Vlad Rusu wrote: > Are those %00 expected at the end of the Hash? > > ... > - ReqURL /sites/all/themes/allegiant3/ > g4www-style/dist/styles/style.min.1.css > ... > - VCL_call RECV > ... > - VCL_call HASH > - Hash "/sites/all/themes/allegiant3/ > g4www-style/dist/styles/style.min.1.css%00" > - Hash "444%00" > - Hash ?www?..com%00" > > > Thanks! > > -- > *Vlad Rusu* > skypeid: rusu.h.vlad | cell: +40758066019 <+40%20758%20066%20019> > > Lola Tech | lola.tech > > On 21 Feb 2017, at 09:58, Vlad Rusu wrote: > > Thanks a lot! > > -- > *Vlad Rusu* > skypeid: rusu.h.vlad | cell: +40758066019 <+40%20758%20066%20019> > > Lola Tech | lola.tech > > On 21 Feb 2017, at 09:57, Geoff Simmons wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 02/21/2017 08:46 AM, Vlad Rusu wrote: > > > Per https://varnish-cache.org/docs/4.1/reference/vsl.html, ?Hash? > is masked by default. > > I am trying to use varnishlog to see the values added to the hash > and I just can?t find a way to show it. > > > Start varnishd with: -p vsl_mask=+Hash > > The default setting for vsl_mask is: > - -VCL_trace,-WorkThread,-Hash,-VfpAcct > > Documentation here: > https://www.varnish-cache.org/docs/4.1/reference/varnishd.html#vsl-mask > > > HTH, > Geoff > - -- > ** * * UPLEX - Nils Goroll Systemoptimierung > > Scheffelstra?e 32 > 22301 Hamburg > > Tel +49 40 2880 5731 <+49%2040%2028805731> > Mob +49 176 636 90917 <+49%20176%2063690917> > Fax +49 40 42949753 <+49%2040%2042949753> > > http://uplex.de > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQIcBAEBCAAGBQJYq/LrAAoJEOUwvh9pJNURmIkP/iVnEpxv1/h/z9Fa/h7njuOW > vHapCbAeXpji7tD5uapWPb8a3h8vEAq1hxVPL2+eSAcrrSh4tsUaF0GaW83UTNms > aOTecGxlF/n0HTCE/HAyKHgOD7B5dffeq1sm52UeB/mvz4GbhVg/K77tZIxNc12g > HrtP0SXsKqYIHasE2QBryAdlkFBA7b36oyCGELnw5fpLsBqiJQ1AmjcmV71Oz6YE > 9CkPK6e5FHRlMaKKPcbiI6upd6lGHh7SKUEOdVLI8ne4luvJQqEArvv1s6ZpHoY8 > 744M/yxnoDOyRBnr+pGSOo6Vv+HlN4+2vh8mXzgtD7PxjLjp3H9ooPbfyzcGmuPK > i9PxuuKu6Epat+C38Y+VzPvbZeCO/S1ZvOepR7eId8Honwh/bAxfdOriqmVETfsI > YPM+iEYWkDHvtjWwDHhkmfW6cAvWh564j2JZT0hAmY0INFpiZ5uMohId3nAUZ9/D > FIQnEaO+67Y89nvkQZlcSB3h/D0Tu67oSuGs6JxqcND48Z1pIDsznxunl9Hly2Vw > jzRg6a+jW/ZO/inQpA76SHhrlcEN6peakaGusHT/MrJPlLOkhzt2vGYxiusKvA2f > ddVa6XWPjugcFLxEHgOck+QCDFBkz8Y+qVdWKEA5jHhFlc3bvmla+3zU/olEeyvk > +q4oQ5Kg6zhVlY9bssZZ > =22Ly > -----END PGP SIGNATURE----- > > > > > _______________________________________________ > 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 dridi at varni.sh Tue Feb 21 09:14:44 2017 From: dridi at varni.sh (Dridi Boukelmoune) Date: Tue, 21 Feb 2017 10:14:44 +0100 Subject: Varnish 4.1 - "Hash" in varnishlog is.. masked In-Reply-To: <18142121-7E0C-435A-B4BD-100AA83FE93F@lola.tech> References: <421A95A7-57E3-45CD-9499-13CA67505C67@lola.tech> <18142121-7E0C-435A-B4BD-100AA83FE93F@lola.tech> Message-ID: On Tue, Feb 21, 2017 at 9:02 AM, Vlad Rusu wrote: > Are those %00 expected at the end of the Hash? > > ... > - ReqURL > /sites/all/themes/allegiant3/g4www-style/dist/styles/style.min.1.css > ... > - VCL_call RECV > ... > - VCL_call HASH > - Hash > "/sites/all/themes/allegiant3/g4www-style/dist/styles/style.min.1.css%00" > - Hash "444%00" > - Hash ?www?..com%00" Maybe null characters are part of the hash when a string is passed to hash_data, I haven't checked... Dridi From phk at phk.freebsd.dk Tue Feb 21 09:49:07 2017 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Tue, 21 Feb 2017 09:49:07 +0000 Subject: Varnish 4.1 - "Hash" in varnishlog is.. masked In-Reply-To: <18142121-7E0C-435A-B4BD-100AA83FE93F@lola.tech> References: <421A95A7-57E3-45CD-9499-13CA67505C67@lola.tech> <18142121-7E0C-435A-B4BD-100AA83FE93F@lola.tech> Message-ID: <68074.1487670547@critter.freebsd.dk> -------- In message <18142121-7E0C-435A-B4BD-100AA83FE93F at lola.tech>, Vlad Rusu writes: >Are those %00 expected at the end of the Hash? > >- Hash = >"/sites/all/themes/allegiant3/g4www-style/dist/styles/style.min.1.css%00" >- Hash "444%00" >- Hash =E2=80=9Cwww=E2=80=A6..com%00" Yes, they are necessary delimiters to avoid fields flowing into each other. Otherwise hashing ("a" and "bc") would be the same as ("ab" and "c") -- 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 phk at phk.freebsd.dk Tue Feb 21 09:49:44 2017 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Tue, 21 Feb 2017 09:49:44 +0000 Subject: Varnish 4.1 - "Hash" in varnishlog is.. masked In-Reply-To: <68074.1487670547@critter.freebsd.dk> References: <421A95A7-57E3-45CD-9499-13CA67505C67@lola.tech> <18142121-7E0C-435A-B4BD-100AA83FE93F@lola.tech> <68074.1487670547@critter.freebsd.dk> Message-ID: <68083.1487670584@critter.freebsd.dk> -------- In message <68074.1487670547 at critter.freebsd.dk>, "Poul-Henning Kamp" writes: >-------- >In message <18142121-7E0C-435A-B4BD-100AA83FE93F at lola.tech>, Vlad Rusu writes: > >>Are those %00 expected at the end of the Hash? >> >>- Hash = >>"/sites/all/themes/allegiant3/g4www-style/dist/styles/style.min.1.css%00" >>- Hash "444%00" >>- Hash =E2=80=9Cwww=E2=80=A6..com%00" > >Yes, they are necessary delimiters to avoid fields flowing into each >other. > >Otherwise hashing ("a" and "bc") would be the same as ("ab" and "c") However, it can be argued that they don't need to be in varnishlog, Martin ? -- 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 dridi at varni.sh Tue Feb 21 10:11:29 2017 From: dridi at varni.sh (Dridi Boukelmoune) Date: Tue, 21 Feb 2017 11:11:29 +0100 Subject: Varnish 4.1 - "Hash" in varnishlog is.. masked In-Reply-To: References: <421A95A7-57E3-45CD-9499-13CA67505C67@lola.tech> <18142121-7E0C-435A-B4BD-100AA83FE93F@lola.tech> Message-ID: On Tue, Feb 21, 2017 at 9:58 AM, Guillaume Quintard wrote: > yes, these are the null character. This makes sure that > "hash("123");hash("456");" returns a different result than > "hash("1");hash("23456");" There goes my need to go check it, thanks! From vlad.rusu at lola.tech Tue Feb 21 11:13:48 2017 From: vlad.rusu at lola.tech (Vlad Rusu) Date: Tue, 21 Feb 2017 13:13:48 +0200 Subject: Varnish 4.1 - "Hash" in varnishlog is.. masked In-Reply-To: References: <421A95A7-57E3-45CD-9499-13CA67505C67@lola.tech> Message-ID: Of course :) Thanks! -- Vlad Rusu skypeid: rusu.h.vlad | cell: +40758066019 Lola Tech | lola.tech > On 21 Feb 2017, at 10:09, Guillaume Quintard wrote: > > Hello Vlad, > > Normally, varnish is configured using either the command line or using varnishadm. You can have a look at "varnishadm param.show vsl_mask" > > But we could probably have a pointer in the doc. Care to do it? > > -- > Guillaume Quintard -------------- next part -------------- An HTML attachment was scrubbed... URL: From dridi at varni.sh Tue Feb 21 13:38:26 2017 From: dridi at varni.sh (Dridi Boukelmoune) Date: Tue, 21 Feb 2017 14:38:26 +0100 Subject: Varnish 4.1.4 - MAIN.n_gunzip counter increasing for every MAIN.backend_req In-Reply-To: References: <0F515569-4675-4CE0-A374-EB26F5CF4B3F@lola.tech> <48BCFFB9-AC61-41DF-8018-505F2BA3A677@lola.tech> Message-ID: > A new counter for test gunzip will be introduced in the next major release. Hello, A quick followup to let you know that it is now ready for 5.1, and I added a description to the counter. https://github.com/varnishcache/varnish-cache/commit/bad5e55 Dridi From dridi at varni.sh Wed Feb 22 10:23:56 2017 From: dridi at varni.sh (Dridi Boukelmoune) Date: Wed, 22 Feb 2017 11:23:56 +0100 Subject: Using Varnish with PHP In-Reply-To: References: <3D9A7773-1BF9-43BD-8A1E-9DEAF28BF08F@gmail.com> Message-ID: On Thu, Feb 16, 2017 at 6:25 AM, Pinakee Biswas wrote: > Hi, > > Thanks for your response. > > FastCGI is the protocol between Nginx (web server) and PHP-FPM. The PHP > pages are served by PHP-FPM. But as I understand, Varnish only supports > HTTP. Varnish only supports HTTP/1 natively on the backend side, someone could write a FastCGI-capable module. I'm just saying... in case that someone has both the time and skill and didn't know they could do it. Dridi PS. someone, if you're reading this, you know what to do From d.magnis at stoiximan.gr Wed Feb 22 11:10:35 2017 From: d.magnis at stoiximan.gr (Dimitris Magnis) Date: Wed, 22 Feb 2017 13:10:35 +0200 Subject: Updating Varnish to latest version issue Message-ID: Hello all, I've just updated my (Centos 7.3) varnish to the latest stable version from 4.1.4 to 4.1.5 which resulted in the following: Feb 22 09:15:17 varnish01 varnishd[13228]: Child (13230) not responding to CLI, killed it. Feb 22 09:15:17 varnish01 varnishd[13228]: Unexpected reply from ping: 400 CLI communication error (hdr) Feb 22 09:15:17 varnish01 varnishd[13228]: Child (13230) not responding to CLI, killed it. Feb 22 09:15:17 varnish01 varnishd[13228]: Unexpected reply from ping: 400 CLI communication error Feb 22 09:15:18 varnish01 varnishd[13228]: Child (13230) died signal=11 Feb 22 09:15:18 varnish01 varnishd[13228]: Child (13230) Last panic at: Wed, 22 Feb 2017 09:15:18 GMT#012"Wrong turn at cache/cache_session.c:551:#012Clock step detected#012thread = (cache-worker)#012version = varnish-4.1.5 revision 2c82b1c#012ident = Linux,3.10.0-514.6.1.el7.x86_64,x86_64,-junix,-smalloc,-smalloc,-hcritbit,epoll#012now = 702.656884 (mono), 1487754906.433703 (real)#012Backtrace:#012 0x434662: pan_ic+0x192#012 0x43c1e3: varnishd() [0x43c1e3]#012 0x436177: Req_Cleanup+0x1f7#012 0x450bcd: HTTP1_Session+0xbd#012 0x43accd: SES_Proto_Req+0x5d#012 0x44b209: WRK_Thread+0x4c9#012 0x44b67b: pool_thread+0x2b#012 0x7fa3501dbdc5: libpthread.so.0(+0x7dc5) [0x7fa3501dbdc5]#012 0x7fa34ff0a73d: libc.so.6(clone+0x6d) [0x7fa34ff0a73d]#012req = 0x7fa2d4d41020 {#012 MAGIC 0x00000000 (Should:REQ_MAGIC/0x2751aaa1)#012 vxid = 0, step = R_STP_RESTART,#012 req_body = R_BODY_INIT,#012 restarts = 0, esi_level = 0,#012 ws = 0x7fa2d4d41200 {#012 MAGIC 0x00000000 (Should:WS_MAGIC/0x35fac554)#012 id = \"\",#012 {s,f,r,e} = {(nil),(nil),(nil),(nil)},#012 },#012 http[req] = (nil) {#012" Feb 22 09:15:18 varnish01 varnishd[13228]: Child cleanup complete Feb 22 09:15:18 varnish01 varnishd[13228]: Child (11686) Started Feb 22 09:15:18 varnish01 varnishd[13228]: Child (11686) said Child starts Any help will be greatly appreciated! Thanks in advance PS. I've never had any similar problem with the previous version (4.1.4) [image: Stoiximan Logo] Dimitris Magnis Junior Systems Administrator Mob: +30 6980592000 <+30+6980592000> E-mail: d.magnis at stoiximan.gr -------------- next part -------------- An HTML attachment was scrubbed... URL: From dridi at varni.sh Wed Feb 22 12:07:57 2017 From: dridi at varni.sh (Dridi Boukelmoune) Date: Wed, 22 Feb 2017 13:07:57 +0100 Subject: Updating Varnish to latest version issue In-Reply-To: References: Message-ID: > PS. I've never had any similar problem with the previous version (4.1.4) Hello, The same panic can occur with 4.1.4 so this is nothing new. There's a clock_step parameter to define how much drift you want to tolerate, see man varnishd. Dridi