From varnish-bugs at varnish-cache.org Wed May 1 12:54:47 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 01 May 2013 12:54:47 -0000 Subject: [Varnish] #1296: hash_data() behaviour deepends on argument form Message-ID: <041.3989913136de42c97a7291db910999ff@varnish-cache.org> #1296: hash_data() behaviour deepends on argument form ----------------------+------------------- Reporter: phk | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+------------------- {{{ hash_data("1" + "2" + "3") }}} does not give the same hash as: {{{ set req.http.foo = "2"; hash_data("1" + req.http.foo + "3") }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed May 1 13:14:04 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 01 May 2013 13:14:04 -0000 Subject: [Varnish] #1296: hash_data() behaviour deepends on argument form In-Reply-To: <041.3989913136de42c97a7291db910999ff@varnish-cache.org> References: <041.3989913136de42c97a7291db910999ff@varnish-cache.org> Message-ID: <056.3118e1598ad00978cc927ba3bbe36298@varnish-cache.org> #1296: hash_data() behaviour deepends on argument form ----------------------+--------------------- Reporter: phk | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+--------------------- Changes (by Poul-Henning Kamp ): * status: new => closed * resolution: => fixed Comment: In [7fd3aa3f8fdf97185af22ce9e71c338933ee1cc0]: {{{ #!CommitTicketReference repository="" revision="7fd3aa3f8fdf97185af22ce9e71c338933ee1cc0" Don't let the form of the argument to hash_data() leak into the production of the hash-key. Fixes #1296 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri May 3 12:30:57 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 03 May 2013 12:30:57 -0000 Subject: [Varnish] #1297: Negative times and nan in varnishlog tag ReqEnd Message-ID: <044.01c9f35fdc4f956b688fa5b86e2251dd@varnish-cache.org> #1297: Negative times and nan in varnishlog tag ReqEnd -----------------------------------+------------------------ Reporter: sthing | Type: defect Status: new | Priority: normal Milestone: | Component: varnishlog Version: 3.0.3 | Severity: normal Keywords: varnishlog ReqEnd nan | -----------------------------------+------------------------ Hi. We are seeing a lot of lines like this: {{{ 7 ReqEnd c 291988160 1367582527.447235107 1367582527.678284168 -0.230976820 nan nan }}} The negative time and "nan" values confuse me. According to https://www.varnish-cache.org/trac/wiki/Varnishlog the last three fields should be: The fourth number (0.017112017) is the time elapsed between the session actually being accept(2)-ed and the start of request processing for this request. Keep in mind that sessions are only accept()ed once, so this is time from the initial request was accepted until the current request begun processing (in other words: other requests from the same client/session could have been processed in the meanwhile). The fifth number (0.000022888) is the time elapsed from the start of the request processing until we start delivering the object to the client. For all practical purposes, this number is the backend response time. The sixth and last number (0.000025988) is the time from we start delivering the object until the request completes. The issue was mentioned in ticket #843, which was closed 13 months ago. However that issue was about ESI not being handled. We do use ESI on the page, and it works fine. The server is running FreeBSD 9.1. It is a development server, no noticeable load. Here is the varnishlog output for one of the requests: {{{ 8 BackendClose - default 8 BackendOpen b default 192.168.1.213 44859 192.168.1.213 80 8 TxRequest b GET 8 TxURL b /da/shop/product/01-00866 8 TxProtocol b HTTP/1.1 8 TxHeader b Host: shop-elstock.thing.varnish.netimage.dk 8 TxHeader b Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 8 TxHeader b User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.63 Safari/537.31 8 TxHeader b Referer: http://shop- elstock.thing.varnish.netimage.dk/da/ 8 TxHeader b Accept-Language: da-DK,da;q=0.8,en-US;q=0.6,en;q=0.4 8 TxHeader b Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 8 TxHeader b Cookie: PHPSESSID=ds3iu1hp9g168v43k2ufcsuu07 8 TxHeader b X-Forwarded-For: 192.168.1.1 8 TxHeader b X-DeviceGroup: pc 8 TxHeader b X-Device: pc 8 TxHeader b X-Varnish: 291988160 8 TxHeader b Accept-Encoding: gzip 8 RxProtocol b HTTP/1.1 8 RxStatus b 200 8 RxResponse b OK 8 RxHeader b Date: Fri, 03 May 2013 12:02:07 GMT 8 RxHeader b Server: Apache 8 RxHeader b X-Powered-By: PHP/5.4.11 8 RxHeader b Expires: Thu, 19 Nov 1981 08:52:00 GMT 8 RxHeader b Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 8 RxHeader b Pragma: no-cache 8 RxHeader b Vary: Accept-Encoding 8 RxHeader b Content-Encoding: gzip 8 RxHeader b Content-Length: 3502 8 RxHeader b Content-Type: text/html; charset=UTF-8 8 Fetch_Body b 4(length) cls 0 mklen 1 8 Length b 3741 8 BackendReuse b default 7 SessionOpen c 192.168.1.1 54637 192.168.1.216:80 7 ReqStart c 192.168.1.1 54637 291988160 7 RxRequest c GET 7 RxURL c /da/shop/product/01-00866 7 RxProtocol c HTTP/1.1 7 RxHeader c Host: shop-elstock.thing.varnish.netimage.dk 7 RxHeader c Connection: keep-alive 7 RxHeader c Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 7 RxHeader c User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.63 Safari/537.31 7 RxHeader c Referer: http://shop- elstock.thing.varnish.netimage.dk/da/ 7 RxHeader c Accept-Encoding: gzip,deflate,sdch 7 RxHeader c Accept-Language: da-DK,da;q=0.8,en-US;q=0.6,en;q=0.4 7 RxHeader c Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 7 RxHeader c Cookie: PHPSESSID=ds3iu1hp9g168v43k2ufcsuu07 7 VCL_call c recv 7 VCL_acl c MATCH allow_from_IP 192.168.1.0/24 7 VCL_return c lookup 7 VCL_call c hash 7 Hash c /da/shop/product/01-00866 7 Hash c shop-elstock.thing.varnish.netimage.dk 7 VCL_return c hash 7 VCL_call c miss fetch 7 Backend c 8 default default 7 TTL c 291988160 RFC 0 -1 -1 1367582528 0 1367582527 375007920 0 7 VCL_call c fetch 7 TTL c 291988160 VCL 120 -1 -1 1367582527 -0 7 VCL_return c hit_for_pass 7 ObjProtocol c HTTP/1.1 7 ObjResponse c OK 7 ObjHeader c Date: Fri, 03 May 2013 12:02:07 GMT 7 ObjHeader c Server: Apache 7 ObjHeader c X-Powered-By: PHP/5.4.11 7 ObjHeader c Expires: Thu, 19 Nov 1981 08:52:00 GMT 7 ObjHeader c Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 7 ObjHeader c Pragma: no-cache 7 ObjHeader c Vary: Accept-Encoding 7 ObjHeader c Content-Encoding: gzip 7 ObjHeader c Content-Length: 3502 7 ObjHeader c Content-Type: text/html; charset=UTF-8 7 Gzip c U F E 3502 12776 80 80 27950 7 Gzip c G F E 12776 3741 80 29848 29858 7 VCL_call c deliver deliver 7 TxProtocol c HTTP/1.1 7 TxStatus c 200 7 TxResponse c OK 7 TxHeader c Server: Apache 7 TxHeader c X-Powered-By: PHP/5.4.11 7 TxHeader c Expires: Thu, 19 Nov 1981 08:52:00 GMT 7 TxHeader c Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 7 TxHeader c Pragma: no-cache 7 TxHeader c Vary: Accept-Encoding 7 TxHeader c Content-Encoding: gzip 7 TxHeader c Content-Type: text/html; charset=UTF-8 7 TxHeader c Transfer-Encoding: chunked 7 TxHeader c Date: Fri, 03 May 2013 12:02:07 GMT 7 TxHeader c X-Varnish: 291988160 7 TxHeader c Age: 0 7 TxHeader c Via: 1.1 varnish 7 TxHeader c Connection: keep-alive 7 VCL_call c recv 7 VCL_acl c MATCH allow_from_IP 192.168.1.0/24 7 VCL_return c lookup 7 VCL_call c hash 7 Hash c ds3iu1hp9g168v43k2ufcsuu07 7 Hash c /index.php?page_label=esi_status 7 Hash c shop-elstock.thing.varnish.netimage.dk 7 VCL_return c hash 7 Hit c 291988155 7 VCL_call c hit deliver 7 VCL_call c deliver deliver 7 Length c 0 7 ReqEnd c 291988160 1367582527.447235107 1367582527.678284168 -0.230976820 nan nan 7 Debug c herding 7 Interrupted c ReqStart }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri May 3 14:17:20 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 03 May 2013 14:17:20 -0000 Subject: [Varnish] #1272: duplicate Content-Length headers with pass and stream In-Reply-To: <045.e87497923f5222571a8b67f55be7787e@varnish-cache.org> References: <045.e87497923f5222571a8b67f55be7787e@varnish-cache.org> Message-ID: <060.caf43a17c131f26e646a8efd7735ffdb@varnish-cache.org> #1272: duplicate Content-Length headers with pass and stream -----------------------------------+--------------------- Reporter: ehocdet | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Resolution: Keywords: stream Content-Length | -----------------------------------+--------------------- Comment (by ehocdet): A more generic fix in attachement (simply unset Content-Length). -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 6 06:09:44 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 06 May 2013 06:09:44 -0000 Subject: [Varnish] #1298: varnishncsa startup script, Ubuntu package Message-ID: <046.051eaaeb8137aee21d2bdd2e304e5c66@varnish-cache.org> #1298: varnishncsa startup script, Ubuntu package ----------------------+----------------------- Reporter: michaelt | Type: defect Status: new | Priority: normal Milestone: | Component: packaging Version: 3.0.3 | Severity: normal Keywords: | ----------------------+----------------------- Hi - When varnishncsa is not running, an improper exit code is returned when checking the status of varnishncsa. Eg: {{{ root at ubuntu:~# service varnishncsa status * varnishncsa is not running root at ubuntu:~# echo $? 0 }}} Compare with the varnish process: {{{ root at ubuntu:~# service varnish status * varnishd is not running root at ubuntu:~# echo $? 1 }}} The exit code for varnishncsa should be non zero similar to the check for varnish. Modifying with the following diff to '''/etc/init.d/varnishncsa''' addresses this issue. This addition brings it inline with that found in the ''status_varnishd'' function of '''/etc/init.d/varnish''' {{{ 77d76 < exit $? }}} We are using SaltStack to manage our installation and configuration of applications, Varnish included. Telling Salt to ensure varnishncsa was running did not work until the correct return code was provided when the status check was run. Although we don't use varnishlog, it appears that its init script has the same issue. Currently running * Version: 3.0.3-1~precise * Ubuntu Server 12.04 LTS * Uname: Linux ubuntu 3.2.0-40-generic #64-Ubuntu SMP Mon Mar 25 21:22:10 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux * Using the Varnish Ubuntu repository available at http://repo.varnish-cache.org/ubuntu/ -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 6 10:04:14 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 06 May 2013 10:04:14 -0000 Subject: [Varnish] #1298: varnishncsa startup script, Ubuntu package In-Reply-To: <046.051eaaeb8137aee21d2bdd2e304e5c66@varnish-cache.org> References: <046.051eaaeb8137aee21d2bdd2e304e5c66@varnish-cache.org> Message-ID: <061.3723844b5519ccfa50685198f023738f@varnish-cache.org> #1298: varnishncsa startup script, Ubuntu package -----------------------+--------------------- Reporter: michaelt | Owner: tfheen Type: defect | Status: new Priority: normal | Milestone: Component: packaging | Version: 3.0.3 Severity: normal | Resolution: Keywords: | -----------------------+--------------------- Changes (by tfheen): * owner: => tfheen -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 6 10:12:29 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 06 May 2013 10:12:29 -0000 Subject: [Varnish] #1297: Negative times and nan in varnishlog tag ReqEnd In-Reply-To: <044.01c9f35fdc4f956b688fa5b86e2251dd@varnish-cache.org> References: <044.01c9f35fdc4f956b688fa5b86e2251dd@varnish-cache.org> Message-ID: <059.3c05e728f893afab974d782607a153f8@varnish-cache.org> #1297: Negative times and nan in varnishlog tag ReqEnd -----------------------------------+--------------------- Reporter: sthing | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: varnishlog | Version: 3.0.3 Severity: normal | Resolution: Keywords: varnishlog ReqEnd nan | -----------------------------------+--------------------- Changes (by martin): * owner: => martin Comment: Hi, Thank you for reporting this. There does seem to be some discrepancies with the timing reported on ESI subrequests. This is in the process of being reworked for the next major Varnish release, and there will be fixes from that work tricking in to 3.0 as a result. I will leave this ticket open, and close once the fix is merged. Regards, Martin Blix Grydeland -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 6 14:19:55 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 06 May 2013 14:19:55 -0000 Subject: [Varnish] #1281: Documentation inconsistency wrt gzip In-Reply-To: <043.bd50c282914cee08d24ea130407d85bb@varnish-cache.org> References: <043.bd50c282914cee08d24ea130407d85bb@varnish-cache.org> Message-ID: <058.f83b1a90398b0adc5e9a26fb4c0c635b@varnish-cache.org> #1281: Documentation inconsistency wrt gzip ---------------------------+------------------------------ Reporter: perbu | Owner: perbu Type: documentation | Status: closed Priority: normal | Milestone: Varnish 3.0 dev Component: build | Version: 3.0.3 Severity: normal | Resolution: fixed Keywords: gzip docs | ---------------------------+------------------------------ Changes (by Per Buer ): * status: new => closed * resolution: => fixed Comment: In [d596b0c048cb43676667980002f9289dc95ba245]: {{{ #!CommitTicketReference repository="" revision="d596b0c048cb43676667980002f9289dc95ba245" Documentation error wrt gzip Fixes #1281 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue May 7 11:10:40 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 07 May 2013 11:10:40 -0000 Subject: [Varnish] #1299: Varnish caches redirects Message-ID: <047.a6aa0defa276dc4422419fade2754948@varnish-cache.org> #1299: Varnish caches redirects -----------------------+---------------------- Reporter: janus.ite | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: 3.0.3 | Severity: normal Keywords: | -----------------------+---------------------- When running varnishtest the following test fails: {{{ varnishtest "Do not cache redirects" server s1 { rxreq txresp -status 302 -hdr "Cache-Control: no-cache" -hdr "Location: http://example.com" rxreq txresp -status 302 -hdr "Cache-Control: no-cache" -hdr "Location: http://example.com" } -start varnish v1 -vcl+backend { } -start client c1 { txreq -url "/" rxresp expect resp.status == 302 expect resp.http.Location == "http://example.com" } varnish v1 -expect cache_hit == 0 varnish v1 -expect cache_miss == 0 client c1 -run varnish v1 -expect cache_hit == 0 varnish v1 -expect cache_miss == 1 client c1 -run varnish v1 -expect cache_hit == 0 varnish v1 -expect cache_miss == 2 }}} If I am not missing something, varnish should not cache redirects when "Cache-Control" header is set to "no-cache". Please see attached test results. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue May 7 12:00:15 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 07 May 2013 12:00:15 -0000 Subject: [Varnish] #1299: Varnish caches redirects In-Reply-To: <047.a6aa0defa276dc4422419fade2754948@varnish-cache.org> References: <047.a6aa0defa276dc4422419fade2754948@varnish-cache.org> Message-ID: <062.f1e08ef857b935ff2c579d3c1a0a1a82@varnish-cache.org> #1299: Varnish caches redirects -----------------------+-------------------- Reporter: janus.ite | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Resolution: Keywords: | -----------------------+-------------------- Comment (by janus.ite): It seems to be working when I add "max-age=0" to the Cache-Control header. However, then the last assertion "cache_miss == 2" must be changed to "cache_miss == 1". Does the miss only count once, because it the same URL? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu May 9 06:06:33 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 09 May 2013 06:06:33 -0000 Subject: [Varnish] #1300: Assert error in Tcheck(), cache.h line 1004 Message-ID: <043.f6e19b842ae15c9775aeeec0ea77eb7d@varnish-cache.org> #1300: Assert error in Tcheck(), cache.h line 1004 -----------------------------+---------------------- Reporter: amber | Type: defect Status: new | Priority: high Milestone: Varnish 3.0 dev | Component: varnishd Version: 3.0.2 | Severity: major Keywords: | -----------------------------+---------------------- Hello, In kern.log i have multiple messages like this: "Panic message: Assert error in Tcheck(), cache.h line 1004" (more info in attachment) OS: CentOS 6.x Kernel: 2.6.32-279.19.1.el6.x86_64 Varnish version: 3.0.2 When this happens, server load jumps to 30-40 (normal load average: 0.00, 0.03, 0.23) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu May 9 06:12:15 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 09 May 2013 06:12:15 -0000 Subject: [Varnish] #1300: Assert error in Tcheck(), cache.h line 1004 In-Reply-To: <043.f6e19b842ae15c9775aeeec0ea77eb7d@varnish-cache.org> References: <043.f6e19b842ae15c9775aeeec0ea77eb7d@varnish-cache.org> Message-ID: <058.37e750635cd952defa23f4b609770c1e@varnish-cache.org> #1300: Assert error in Tcheck(), cache.h line 1004 ----------------------+------------------------------ Reporter: amber | Owner: Type: defect | Status: new Priority: high | Milestone: Varnish 3.0 dev Component: varnishd | Version: 3.0.2 Severity: major | Resolution: Keywords: | ----------------------+------------------------------ Comment (by amber): Update: this bug affects only CentOS, Ubuntu works fine. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 13 10:18:44 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 13 May 2013 10:18:44 -0000 Subject: [Varnish] #1300: Assert error in Tcheck(), cache.h line 1004 In-Reply-To: <043.f6e19b842ae15c9775aeeec0ea77eb7d@varnish-cache.org> References: <043.f6e19b842ae15c9775aeeec0ea77eb7d@varnish-cache.org> Message-ID: <058.583b7e7dac0702d279d62d187d4bfee6@varnish-cache.org> #1300: Assert error in Tcheck(), cache.h line 1004 ----------------------+------------------------------ Reporter: amber | Owner: Type: defect | Status: new Priority: high | Milestone: Varnish 3.0 dev Component: varnishd | Version: 3.0.2 Severity: major | Resolution: Keywords: | ----------------------+------------------------------ Comment (by martin): Hi, Specifically which Varnish version are you using? Is this vanilla Varnish 3.0.2, or the 3.0.2s(treaming) version? The back trace looks like a bug that was specific to the 3.0.2s version and has been fixed. If this is the version you can find updated code at https://github.com/mbgrydeland /varnish-cache/tree/3.0.3-plus (the branch has been renamed -plus). If this is a regular Varnish, I suggest that you upgrade to the latest release and see if that fixes the problems for you. 3.0.2 is quite old now, and 3.0.3 (the latest) has a number of fixes that could resolve your issue. Regards, Martin Blix Grydeland -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 13 12:25:16 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 13 May 2013 12:25:16 -0000 Subject: [Varnish] #1300: Assert error in Tcheck(), cache.h line 1004 In-Reply-To: <043.f6e19b842ae15c9775aeeec0ea77eb7d@varnish-cache.org> References: <043.f6e19b842ae15c9775aeeec0ea77eb7d@varnish-cache.org> Message-ID: <058.e6aa0748330c65271f8e7c2ef362fca0@varnish-cache.org> #1300: Assert error in Tcheck(), cache.h line 1004 ----------------------+------------------------------ Reporter: amber | Owner: Type: defect | Status: new Priority: high | Milestone: Varnish 3.0 dev Component: varnishd | Version: 3.0.2 Severity: major | Resolution: Keywords: | ----------------------+------------------------------ Comment (by amber): Hi, I use Varnish 3.0.2s version. I will try 3.0.3-plus. Thank you for information. Regards, Virginijus -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 13 19:07:07 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 13 May 2013 19:07:07 -0000 Subject: [Varnish] #1301: Bug in documentation for 2.1 version, Example 1 - manipulating headers Message-ID: <045.4272b66ceca24fb94bb3120c86edfaaa@varnish-cache.org> #1301: Bug in documentation for 2.1 version, Example 1 - manipulating headers ---------------------------------+--------------------------- Reporter: bnegrao | Type: defect Status: new | Priority: normal Milestone: | Component: documentation Version: 2.1.0 | Severity: normal Keywords: documentation error | ---------------------------------+--------------------------- There's an error on Example 1, [https://www.varnish- cache.org/docs/2.1/tutorial/vcl.html#example-1-manipulating-headers this page] Where it says: "Lets say we want to remove the cookie for all objects in the '''/static''' directory" It should say: "Lets say we want to remove the cookie for all objects in the '''/images''' directory" Regards, Bruno -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 13 22:09:34 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 13 May 2013 22:09:34 -0000 Subject: [Varnish] #1302: Wrong syntax of case insensitive match at the Example on the documentation Message-ID: <045.e6fa5125318a2ff59e5daceb172ed663@varnish-cache.org> #1302: Wrong syntax of case insensitive match at the Example on the documentation ---------------------------------+--------------------------- Reporter: bnegrao | Type: defect Status: new | Priority: normal Milestone: | Component: documentation Version: 2.1.0 | Severity: normal Keywords: documentation error | ---------------------------------+--------------------------- Hello, the Example on the page [https://www.varnish- cache.org/docs/2.1/faq/general.html#why Why], on section "Why are regular expressions case-sensitive?" shows a wrong syntax in the example code snippet for case insensitive match. It forgets the () surrounding '?i' and that takes us to a compilation error on varnish start. Where it shows: {{{ if (req.http.host ~ "?iexample.com$") { ... } }}} Should be: {{{ if (req.http.host ~ "(?i)example.com$") { ... } }}} Regards, Bruno. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue May 14 05:39:14 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 14 May 2013 05:39:14 -0000 Subject: [Varnish] #1303: Crash: "Assert error in VRT_time_string(), cache_vrt.c line 346" Message-ID: <043.b75d0045623bfb658d4f91b5eac20fc8@varnish-cache.org> #1303: Crash: "Assert error in VRT_time_string(), cache_vrt.c line 346" -------------------+---------------------- Reporter: flies | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: 3.0.3 | Severity: normal Keywords: | -------------------+---------------------- Version: 3.0.3 Varnish crashes randomly with below dump. Is this workspace size related issue? {{{ May 13 16:30:14 wpf22 varnishd[15022]: Child (15023) Panic message: Assert error in VRT_time_string(), cache_vrt.c line 346: Condition((p = WS_Alloc(sp->http->ws, 30)) != 0) not true. errno = 115 (Operation now in progress) thread = (cache-worker) ident = Linux,2.6.32-5-amd64,x86_64,-smalloc,-smalloc,-hcritbit,epoll Backtrace: 0x43cca8: pan_backtrace+28 0x43cfa0: pan_ic+1bc 0x4481af: VRT_time_string+72 0x7f6a223ef896: _end+7f6a21d5123e 0x4466dd: VCL_fetch_method+7f 0x41c18e: cnt_fetch+3e8 0x41febf: CNT_Session+769 0x43e75d: wrk_thread_real+9c5 0x43ec08: wrk_thread+139 0x7f6a2bd408ca: _end+7f6a2b6a2272 sp = 0x7f6889cac008 { fd = 131, id = 131, xid = 1361532002, client = 69.164.213.164 45916, step = STP_FETCH, handling = deliver, err_code = 200, err_reason = (null), restarts = 0, esi_level = 0 flags = bodystatus = 4 ws = 0x7f6889cac080 { overflow id = "sess", {s,f,r,e} = {0x7f6889cacc78,+65536,(nil),+65536}, }, http[req] = { ws = 0x7f6889cac080[sess] "GET", "/feed/", "HTTP/1.1", "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2; Feeder.co) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.43 Safari/537.31", "Accept-Charset: utf-8;q=0.7,*;q=0.3", "Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8", "host: www.example.com", "content-type: application/x-www-form-urlencoded; charset=utf-8", "Connection: keep-alive", "X-Times: S: Mon, 13 May 2013 14:30:14 GMT", "X-Forwarded-For: XXX.XXX.XXX.XXX", "X-User-Host: www.example.com", "tmpUrl: /feed/", "tmpHost: www.example.com", "X-Database: wp200", }, worker = 0x7f69c8ff3a90 { ws = 0x7f69c8ff3cc8 { id = "wrk", {s,f,r,e} = {0x7f69c8fe19e0,+13128,(nil),+65536}, }, http[bereq] = }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue May 14 05:41:57 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 14 May 2013 05:41:57 -0000 Subject: [Varnish] #1304: Crash: "Assert error in VRY_Match(), cache_vary.c line 216" Message-ID: <043.1282bca3c6fbc7f78f4349fabdd919fd@varnish-cache.org> #1304: Crash: "Assert error in VRY_Match(), cache_vary.c line 216" -------------------+-------------------- Reporter: flies | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: 3.0.3 | Severity: normal Keywords: | -------------------+-------------------- Version: 3.0.3 Randomly crashing with following dump: {{{ Panic message: Assert error in VRY_Match(), cache_vary.c line 216: Condition(vsp + ln + 2 < sp->vary_e) not true. errno = 115 (Operation now in progress) thread = (cache-worker) ident = Linux,2.6.32-5-amd64,x86_64,-smalloc,-smalloc,-hcritbit,epoll Backtrace: 0x43cca8: pan_backtrace+28 0x43cfa0: pan_ic+1bc 0x444bfc: VRY_Match+214 0x433134: HSH_Lookup+76f 0x41de2f: cnt_lookup+27e 0x41fe14: CNT_Session+6be 0x43e75d: wrk_thread_real+9c5 0x43ec08: wrk_thread+139 0x7f6a2bd408ca: _end+7f6a2b6a2272 0x7f6a2baa7b6d: _end+7f6a2b409515 sp = 0x7f6881997008 { fd = 930, id = 930, xid = 210422274, client = XXX.XXX.XXX.XXX 33741, step = STP_LOOKUP, handling = hash, restarts = 0, esi_level = 0 flags = bodystatus = 4 ws = 0x7f6881997080 { id = "sess", {s,f,r,e} = {0x7f6881997c78,+65528,+65536,+65536}, }, http[req] = { ws = 0x7f6881997080[sess] "GET", "/feed/", "HTTP/1.1", "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2; Feeder.co) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.43 Safari/537.31", "Accept-Charset: utf-8;q=0.7,*;q=0.3", "Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8", "host: www.example.com", "content-type: application/x-www-form-urlencoded; charset=utf-8", "Connection: keep-alive", "X-Times: S: Mon, 13 May 2013 19:30:11 GMT", "X-Forwarded-For: XXX.XXX.XXX.XXX", "X-User-Host: www.example.com", "tmpUrl: /feed/", "tmpHost: www.example.com", "X-Database: wp5", }, worker = 0x7f68a2eeba90 { ws = 0x7f68a2eebcc8 { id = "wrk", {s,f,r,e} = {0x7f68a2ed99e0,0x7f68a2ed99e0,(nil),+65536}, }, }, vcl = { srcname = { "in }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue May 14 07:44:02 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 14 May 2013 07:44:02 -0000 Subject: [Varnish] #1301: Bug in documentation for 2.1 version, Example 1 - manipulating headers In-Reply-To: <045.4272b66ceca24fb94bb3120c86edfaaa@varnish-cache.org> References: <045.4272b66ceca24fb94bb3120c86edfaaa@varnish-cache.org> Message-ID: <060.2f51804eeed7850d2954757c9e322831@varnish-cache.org> #1301: Bug in documentation for 2.1 version, Example 1 - manipulating headers ---------------------------------+---------------------- Reporter: bnegrao | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: documentation | Version: 2.1.0 Severity: normal | Resolution: wontfix Keywords: documentation error | ---------------------------------+---------------------- Changes (by scoof): * status: new => closed * resolution: => wontfix Comment: Varnish 3.0 has been out for almost 2 years. There will be no more doc fixes to the 2.1 branch. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue May 14 07:47:42 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 14 May 2013 07:47:42 -0000 Subject: [Varnish] #1302: Wrong syntax of case insensitive match at the Example on the documentation In-Reply-To: <045.e6fa5125318a2ff59e5daceb172ed663@varnish-cache.org> References: <045.e6fa5125318a2ff59e5daceb172ed663@varnish-cache.org> Message-ID: <060.585ec52933a74d300d449a0f8551d06a@varnish-cache.org> #1302: Wrong syntax of case insensitive match at the Example on the documentation ---------------------------------+---------------------- Reporter: bnegrao | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: documentation | Version: 2.1.0 Severity: normal | Resolution: wontfix Keywords: documentation error | ---------------------------------+---------------------- Changes (by scoof): * status: new => closed * resolution: => wontfix Comment: Varnish 3.0 has been out for almost 2 years. There will be no more doc fixes to the 2.1 branch. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue May 14 07:59:13 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 14 May 2013 07:59:13 -0000 Subject: [Varnish] #1299: Varnish caches redirects In-Reply-To: <047.a6aa0defa276dc4422419fade2754948@varnish-cache.org> References: <047.a6aa0defa276dc4422419fade2754948@varnish-cache.org> Message-ID: <062.9274107ac2c0b2b29f182438f71da0ce@varnish-cache.org> #1299: Varnish caches redirects -----------------------+------------------------- Reporter: janus.ite | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Resolution: worksforme Keywords: | -----------------------+------------------------- Changes (by scoof): * status: new => closed * resolution: => worksforme Comment: This is not a bug. Please use the varnish-misc mailing list for these questions: https://www.varnish-cache.org/lists/mailman/listinfo/varnish- misc In general, there's no special handling of redirects. They can be cached like anything else. If you want Varnish to honor Cache-Control: no-cache, you need to add it to your VCL yourself. It will be added to a future version of the default vcl. (See commit 81006eafd6d4cd6f9481740a1d172e316a184d05, which hasn't been merged to any release yet). -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue May 14 08:20:05 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 14 May 2013 08:20:05 -0000 Subject: [Varnish] #1300: Assert error in Tcheck(), cache.h line 1004 In-Reply-To: <043.f6e19b842ae15c9775aeeec0ea77eb7d@varnish-cache.org> References: <043.f6e19b842ae15c9775aeeec0ea77eb7d@varnish-cache.org> Message-ID: <058.c73c2ab3432ddd33a22a5a9a945b7767@varnish-cache.org> #1300: Assert error in Tcheck(), cache.h line 1004 ----------------------+------------------------------ Reporter: amber | Owner: Type: defect | Status: closed Priority: high | Milestone: Varnish 3.0 dev Component: varnishd | Version: 3.0.2 Severity: major | Resolution: duplicate Keywords: | ----------------------+------------------------------ Changes (by martin): * status: new => closed * resolution: => duplicate -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue May 14 09:34:28 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 14 May 2013 09:34:28 -0000 Subject: [Varnish] #1305: Varnish:time_firstbyte and others are misleading Message-ID: <050.29f7d4db9e158b8aa89661772a4471c8@varnish-cache.org> #1305: Varnish:time_firstbyte and others are misleading --------------------------+--------------------------- Reporter: JonathanHuot | Type: documentation Status: new | Priority: normal Milestone: | Component: documentation Version: trunk | Severity: minor Keywords: | --------------------------+--------------------------- Timings in varnish are a bit misleading in documentation. Since it's important when writing a lot of consuming VCL (e.g. using VMOD) I would like to suggest this minor improvement : Reading [https://www.varnish-cache.org/trac/wiki/Varnishlog#ReqEnd], we understand pretty well that the fifth number is ''from the start of the request processing until we start delivering''. Then, if we want to print this value in varnishncsa, [https://www.varnish- cache.org/docs/trunk/reference/varnishncsa.html?highlight=Varnish:time_firstbyte] reference a "firstbyte" ''Time to the first byte from the backend arrived'' as the same value as fifth number of ReqEnd. What I suggest, is replacing '''time_firstbyte''' by '''time_lastbyte''' because we already read the full body from the backend (if streaming == no). '''time_lastbyte''' is maybe not very meaningful, feel free to propose other names, because I think this name is very important to be understood by VMOD developers (and VCL writers). -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue May 14 13:31:41 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 14 May 2013 13:31:41 -0000 Subject: [Varnish] #1302: Wrong syntax of case insensitive match at the Example on the documentation In-Reply-To: <045.e6fa5125318a2ff59e5daceb172ed663@varnish-cache.org> References: <045.e6fa5125318a2ff59e5daceb172ed663@varnish-cache.org> Message-ID: <060.ded938cf70f21792516272127fceefa0@varnish-cache.org> #1302: Wrong syntax of case insensitive match at the Example on the documentation ---------------------------------+---------------------- Reporter: bnegrao | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: documentation | Version: 2.1.0 Severity: normal | Resolution: wontfix Keywords: documentation error | ---------------------------------+---------------------- Comment (by bnegrao): The version of the documentation is actually 2.5.0. You should know that Varnish is being used in big companies (like mine) and big companies don't upgrade software without a compelling reason, what means we'll continue to use version 2.x for a long time. I don't understand why you prefer to let the error there when it's so simple to correct it. I really don't get that. Well, this is frustrating, i just feel I lost my time opening this ticket. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue May 14 14:22:51 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 14 May 2013 14:22:51 -0000 Subject: [Varnish] #1302: Wrong syntax of case insensitive match at the Example on the documentation In-Reply-To: <045.e6fa5125318a2ff59e5daceb172ed663@varnish-cache.org> References: <045.e6fa5125318a2ff59e5daceb172ed663@varnish-cache.org> Message-ID: <060.f659436bc67a53a632bdcab04974ac0b@varnish-cache.org> #1302: Wrong syntax of case insensitive match at the Example on the documentation ---------------------------------+---------------------- Reporter: bnegrao | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: documentation | Version: 2.1.5 Severity: normal | Resolution: wontfix Keywords: documentation error | ---------------------------------+---------------------- Changes (by perbu): * version: 2.1.0 => 2.1.5 Comment: bnegrao, I've pushed a fix now. Hope you're a bit happier now. You should know that any errors in the 2.1 codebase will not get fixed. There are certain semantics which one could perceive as bugs that are fixed in the 3.0 branch. These will not be addressed in the 2.1 branch. Cheers, Per. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue May 14 17:18:25 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 14 May 2013 17:18:25 -0000 Subject: [Varnish] #1302: Wrong syntax of case insensitive match at the Example on the documentation In-Reply-To: <045.e6fa5125318a2ff59e5daceb172ed663@varnish-cache.org> References: <045.e6fa5125318a2ff59e5daceb172ed663@varnish-cache.org> Message-ID: <060.28f5741700a1e4cbfec95d77d343b61e@varnish-cache.org> #1302: Wrong syntax of case insensitive match at the Example on the documentation ---------------------------------+---------------------- Reporter: bnegrao | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: documentation | Version: 2.1.5 Severity: normal | Resolution: wontfix Keywords: documentation error | ---------------------------------+---------------------- Comment (by bnegrao): Oh, thank you! I'm much happier now, totally! ;-) I think you can change the status of this ticket to 'fixed' since you acctually solved it. Regards, bruno -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri May 17 08:49:40 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 17 May 2013 08:49:40 -0000 Subject: [Varnish] #1306: reg: varnish cache hits taking longer duration Message-ID: <047.bc111348f4a102a7deb44f8cf82355a1@varnish-cache.org> #1306: reg: varnish cache hits taking longer duration -----------------------+--------------------- Reporter: sugunakar | Type: defect Status: new | Priority: highest Milestone: | Component: build Version: 2.1.4 | Severity: normal Keywords: | -----------------------+--------------------- HI, we have been using varnish for the past few years. Recently I observed that few requests are taking longer than expected. I am hitting my website say www.abc.com. OS: CentOS 5.8 Linux kernel: 2.6 Varnish version: 2.1.4-1 here is the summary of my test: 1. Send requests one by one to www.abc.com using curl 2. Measure the time using curl utility 3. Total requests sent 2000 ; time taken to send them 30-40 seconds 4. Observartions: most of requests get served within 0.3 seconds and few take more than 1 seconds and 2-3 requests take up more than 3 seconds 5. The requests taking 3 seconds are served from cache as I could see the X-varnish headers with 2 numbers. Need your help in understanding why it takes 3 seconds to serve from cache? Thanks Sugunakar -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri May 17 10:42:53 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 17 May 2013 10:42:53 -0000 Subject: [Varnish] #1306: reg: varnish cache hits taking longer duration In-Reply-To: <047.bc111348f4a102a7deb44f8cf82355a1@varnish-cache.org> References: <047.bc111348f4a102a7deb44f8cf82355a1@varnish-cache.org> Message-ID: <062.7ea27f5844edd6554483f6ddbc958a17@varnish-cache.org> #1306: reg: varnish cache hits taking longer duration -----------------------+------------------------- Reporter: sugunakar | Owner: Type: defect | Status: closed Priority: highest | Milestone: Component: build | Version: 2.1.4 Severity: normal | Resolution: worksforme Keywords: | -----------------------+------------------------- Changes (by scoof): * status: new => closed * resolution: => worksforme Comment: The bug tracker is only for bugs. Please use the varnish-misc list or the forum for questions. https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc/ https://www.varnish-cache.org/forum -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 20 05:03:48 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 20 May 2013 05:03:48 -0000 Subject: [Varnish] #1306: reg: varnish cache hits taking longer duration In-Reply-To: <047.bc111348f4a102a7deb44f8cf82355a1@varnish-cache.org> References: <047.bc111348f4a102a7deb44f8cf82355a1@varnish-cache.org> Message-ID: <062.26310a340097597dc7bb9d834d8f10b3@varnish-cache.org> #1306: reg: varnish cache hits taking longer duration -----------------------+------------------------- Reporter: sugunakar | Owner: Type: defect | Status: closed Priority: highest | Milestone: Component: build | Version: 2.1.4 Severity: normal | Resolution: worksforme Keywords: | -----------------------+------------------------- Comment (by sugunakar): Thanks scoof. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 20 05:44:08 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 20 May 2013 05:44:08 -0000 Subject: [Varnish] #1303: Crash: "Assert error in VRT_time_string(), cache_vrt.c line 346" In-Reply-To: <043.b75d0045623bfb658d4f91b5eac20fc8@varnish-cache.org> References: <043.b75d0045623bfb658d4f91b5eac20fc8@varnish-cache.org> Message-ID: <058.90d6eec1699dbaa61cf113ddb63f8e6f@varnish-cache.org> #1303: Crash: "Assert error in VRT_time_string(), cache_vrt.c line 346" ----------------------+-------------------- Reporter: flies | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Comment (by flies): {{{ (gdb) bt #0 0x00007fef098c41b5 in raise () from /lib/libc.so.6 #1 0x00007fef098c6fc0 in abort () from /lib/libc.so.6 #2 0x00000000004395cd in pan_ic (func=0x479960 "VRT_time_string", file=0x4796b5 "cache_vrt.c", line=346, cond=0x4798c8 "(p = WS_Alloc(sp->http->ws, 30)) != 0", err=115, xxx=0) at cache_panic.c:374 #3 0x0000000000443844 in VRT_time_string (sp=0x7fed69cdf008, t=1369028348.8825231) at cache_vrt.c:346 #4 0x00007fef003f068a in ?? () from ./vcl.6nDPDyFn.so #5 0x000000000044205e in VCL_fetch_method (sp=0x7fed69cdf008) at ../../include/vcl_returns.h:58 #6 0x000000000041ad8c in cnt_fetch (sp=0x7fed69cdf008) at cache_center.c:598 #7 0x000000000041e8bc in CNT_Session (sp=0x7fed69cdf008) at steps.h:41 #8 0x000000000043aaaa in wrk_thread_real (qp=0x7fef0950f2e0, shm_workspace=8192, sess_workspace=65536, nhttp=64, http_space=1128, siov=128) at cache_pool.c:186 #9 0x000000000043aef9 in wrk_thread (priv=0x7fef0950f2e0) at cache_pool.c:235 #10 0x00007fef09bfa8ca in start_thread () from /lib/libpthread.so.0 #11 0x00007fef09961b6d in clone () from /lib/libc.so.6 #12 0x0000000000000000 in ?? () }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 20 11:55:56 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 20 May 2013 11:55:56 -0000 Subject: [Varnish] #1269: varnishncsa does not show pipe'ed requests In-Reply-To: <047.74c03b61e1ee686de1e8904dfd87ef9a@varnish-cache.org> References: <047.74c03b61e1ee686de1e8904dfd87ef9a@varnish-cache.org> Message-ID: <062.680bd02cc2446290e4f0e6268ed34b04@varnish-cache.org> #1269: varnishncsa does not show pipe'ed requests -------------------------+-------------------- Reporter: prymitive | Owner: Type: defect | Status: new Priority: low | Milestone: Component: varnishncsa | Version: 3.0.3 Severity: minor | Resolution: Keywords: | -------------------------+-------------------- Comment (by prymitive): any chance to change this behavior? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed May 22 08:19:19 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 22 May 2013 08:19:19 -0000 Subject: [Varnish] #1292: Varnish restarts itself, when processing response from backend In-Reply-To: <042.4b2b91c80836415cc2d25b9977d04c7c@varnish-cache.org> References: <042.4b2b91c80836415cc2d25b9977d04c7c@varnish-cache.org> Message-ID: <057.daf53bf706d4d2a535156fb7bf3fb786@varnish-cache.org> #1292: Varnish restarts itself, when processing response from backend ----------------------+------------------------------ Reporter: ixos | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 3.0 dev Component: varnishd | Version: 3.0.3 Severity: major | Resolution: Keywords: | ----------------------+------------------------------ Comment (by ixos): Hi, I could paste vcl configuration, but i don't want it to be public. Can I get an email where can I send vcl configuration? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu May 23 10:19:27 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 23 May 2013 10:19:27 -0000 Subject: [Varnish] #1307: Multiple StatSess records in varnishlog (3.0.3plus) Message-ID: <043.e29141848057645f33a5dc1ea330536a@varnish-cache.org> #1307: Multiple StatSess records in varnishlog (3.0.3plus) ----------------------+------------------- Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Keywords: plus ----------------------+------------------- I think there's one StatSess record too many here. {{{ 13 BackendOpen b default 127.0.0.1 58234 127.0.0.1 8080 13 TxRequest b GET 13 TxURL b / 13 TxProtocol b HTTP/1.1 13 TxHeader b Host: localhost 13 TxHeader b User-Agent: lwp-request/6.03 libwww-perl/6.04 13 TxHeader b X-Forwarded-For: 127.0.0.1 13 TxHeader b X-Varnish: 1565817040 13 TxHeader b Accept-Encoding: gzip 13 RxProtocol b HTTP/1.1 13 RxStatus b 200 13 RxResponse b OK 13 RxHeader b Date: Thu, 23 May 2013 09:15:11 GMT 13 RxHeader b Accept-Ranges: bytes 13 RxHeader b Content-Type: text/html 13 RxHeader b Content-Length: 1082 13 RxHeader b Last-Modified: Wed, 25 Apr 2012 08:55:37 GMT 13 RxHeader b Server: Jetty(6.1.24) 13 Fetch_Body b 4(length) cls 0 mklen 1 13 Length b 1082 13 BackendReuse b default 0 WorkThread - 0x7f41d9efeb10 start 11 SessionOpen c 127.0.0.1 42319 :80 11 ReqStart c 127.0.0.1 42319 1565817040 11 RxRequest c GET 11 RxURL c / 11 RxProtocol c HTTP/1.1 11 RxHeader c TE: deflate,gzip;q=0.3 11 RxHeader c Connection: TE, close 11 RxHeader c Host: localhost 11 RxHeader c User-Agent: lwp-request/6.03 libwww-perl/6.04 11 VCL_call c recv lookup 11 VCL_call c hash 11 Hash c / 11 Hash c localhost 11 VCL_return c hash 11 VCL_call c miss fetch 11 Backend c 13 default default 11 TTL c 1565817040 RFC 86400 -1 -1 1369300511 0 1369300511 0 0 11 VCL_call c fetch deliver 11 ObjProtocol c HTTP/1.1 11 ObjResponse c OK 11 ObjHeader c Date: Thu, 23 May 2013 09:15:11 GMT 11 ObjHeader c Content-Type: text/html 11 ObjHeader c Last-Modified: Wed, 25 Apr 2012 08:55:37 GMT 11 ObjHeader c Server: Jetty(6.1.24) 11 VCL_call c deliver deliver 11 TxProtocol c HTTP/1.1 11 TxStatus c 200 11 TxResponse c OK 11 TxHeader c Content-Type: text/html 11 TxHeader c Last-Modified: Wed, 25 Apr 2012 08:55:37 GMT 11 TxHeader c Server: Jetty(6.1.24) 11 TxHeader c Content-Length: 1082 11 TxHeader c Accept-Ranges: bytes 11 TxHeader c Date: Thu, 23 May 2013 09:15:11 GMT 11 TxHeader c X-Varnish: 1565817040 11 TxHeader c Age: 0 11 TxHeader c Via: 1.1 varnish 11 TxHeader c Connection: close 11 TxHeader c Content-Length: 1082 11 Length c 1082 11 ReqEnd c 1565817040 1369300511.216991901 1369300511.222213268 0.000102758 0.005040407 0.000180960 11 SessionClose c Connection: close 11 StatSess c 127.0.0.1 42319 0 0 0 0 0 0 284 1082 11 StatSess c - - 0 1 1 0 0 0 0 0 }}} VCL: {{{ backend default { .host = "127.0.0.1"; .port = "8080"; } sub vcl_fetch { set beresp.do_stream=true; } }}} This was found when trying to troubleshoot an issue with thierr1, where it seems like the extra StatSess comes earlier, and cuts the log short. He's trying to create a reproducible case, and will append to this case if successful. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu May 23 13:37:06 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 23 May 2013 13:37:06 -0000 Subject: [Varnish] #1307: Multiple StatSess records in varnishlog (3.0.3plus) In-Reply-To: <043.e29141848057645f33a5dc1ea330536a@varnish-cache.org> References: <043.e29141848057645f33a5dc1ea330536a@varnish-cache.org> Message-ID: <058.c5996c217b0df77708d19c8e27d83fce@varnish-cache.org> #1307: Multiple StatSess records in varnishlog (3.0.3plus) ----------------------+-------------------- Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Resolution: Keywords: plus | ----------------------+-------------------- Comment (by tmagnien): Hi, I added a "varnishlog -c" of a full session, and we can see that every "StatSess" stops the logging for the request (no TxHeader logged, etc.). I'm available on IRC (thierr1) if needed. Thierry -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri May 24 16:02:42 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 24 May 2013 16:02:42 -0000 Subject: [Varnish] #1308: ESI 400/500 Error handling Message-ID: <045.ef50e73edb7a1b2430d34dd159791f4f@varnish-cache.org> #1308: ESI 400/500 Error handling ---------------------------------+-------------------- Reporter: mukeshk | Type: task Status: new | Priority: high Milestone: Varnish 3.0 dev | Component: build Version: 3.0.2 | Severity: normal Keywords: ESI Errors handling | ---------------------------------+-------------------- I am using ESI with varnish 3.0.2 version. In my case, ESI include URL is a sub domain page. I am trying to add some error handling in case of ESI include URL is not found or having any error in script. I tried many solutions including try, attempt, except, remove but it is showing me error page instead of my custom text. Here is my ESI code. So if there is any error in test.php, or http://abc.xyz.com domain is not accessible then i want to show a custom text message instead of a error page like 404, 503 etc. Can someone please help me. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri May 24 16:19:05 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 24 May 2013 16:19:05 -0000 Subject: [Varnish] #1309: req.url is not writable in VCL sub vcl_miss Message-ID: <049.6d981d51f737ac012fe7f6640b1bb44b@varnish-cache.org> #1309: req.url is not writable in VCL sub vcl_miss -------------------------+---------------------- Reporter: raymondjiii | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: trunk | Severity: normal Keywords: | -------------------------+---------------------- The documentation at: https://www.varnish-software.com/static/book/VCL_functions.html Shows that req.url is R/W in sub vcl_miss. If I have the simple VCL code sub vcl_miss { set req.url = std.toupper(req.url); } Now view the URL on the backend server and it has not been converted to uppercase. Move that one line to sub vcl_hash and again view the URL on the backend server and the URL is fully uppercase. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 27 10:14:17 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 27 May 2013 10:14:17 -0000 Subject: [Varnish] #1307: Multiple StatSess records in varnishlog (3.0.3plus) In-Reply-To: <043.e29141848057645f33a5dc1ea330536a@varnish-cache.org> References: <043.e29141848057645f33a5dc1ea330536a@varnish-cache.org> Message-ID: <058.9c62a215a11de641e6b5db0aa786b8eb@varnish-cache.org> #1307: Multiple StatSess records in varnishlog (3.0.3plus) ----------------------+--------------------- Reporter: scoof | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Resolution: Keywords: plus | ----------------------+--------------------- Changes (by martin): * owner: => martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 27 10:16:13 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 27 May 2013 10:16:13 -0000 Subject: [Varnish] #1308: ESI 400/500 Error handling In-Reply-To: <045.ef50e73edb7a1b2430d34dd159791f4f@varnish-cache.org> References: <045.ef50e73edb7a1b2430d34dd159791f4f@varnish-cache.org> Message-ID: <060.7c11bbfd99520f3ea2845085f152973a@varnish-cache.org> #1308: ESI 400/500 Error handling ---------------------------------+------------------------------ Reporter: mukeshk | Owner: Type: task | Status: closed Priority: high | Milestone: Varnish 3.0 dev Component: build | Version: 3.0.2 Severity: normal | Resolution: invalid Keywords: ESI Errors handling | ---------------------------------+------------------------------ Changes (by scoof): * status: new => closed * resolution: => invalid Comment: The bug tracker is only for bugs. Please use the varnish-misc mailing list (https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc) or the forum (https://www.varnish-cache.org/forum) for configuration help -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 27 10:24:25 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 27 May 2013 10:24:25 -0000 Subject: [Varnish] #1292: Varnish restarts itself, when processing response from backend In-Reply-To: <042.4b2b91c80836415cc2d25b9977d04c7c@varnish-cache.org> References: <042.4b2b91c80836415cc2d25b9977d04c7c@varnish-cache.org> Message-ID: <057.50a4d1f80e26c0d7e94b6812f0098371@varnish-cache.org> #1292: Varnish restarts itself, when processing response from backend ----------------------+------------------------------ Reporter: ixos | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 3.0 dev Component: varnishd | Version: 3.0.3 Severity: major | Resolution: Keywords: | ----------------------+------------------------------ Comment (by martin): Replying to [comment:2 ixos]: > Hi, > > I could paste vcl configuration, but i don't want it to be public. Can I get an email where can I send vcl configuration? Hi, You can mail it directly to me using martin at varnish-software.com. Regards, Martin Blix Grydeland -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 27 10:57:59 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 27 May 2013 10:57:59 -0000 Subject: [Varnish] #1309: req.url is not writable in VCL sub vcl_miss In-Reply-To: <049.6d981d51f737ac012fe7f6640b1bb44b@varnish-cache.org> References: <049.6d981d51f737ac012fe7f6640b1bb44b@varnish-cache.org> Message-ID: <064.0a0bc40714e6288bad7b42fc6e2c114f@varnish-cache.org> #1309: req.url is not writable in VCL sub vcl_miss -------------------------+------------------------- Reporter: raymondjiii | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: worksforme Keywords: | -------------------------+------------------------- Changes (by daghf): * status: new => closed * resolution: => worksforme Comment: Changes to req.* are written to bereq prior to entering vcl_miss. In order to have your changes show up in the backend request, you will then have to edit bereq.url and not req.url. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 27 11:17:45 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 27 May 2013 11:17:45 -0000 Subject: [Varnish] #1303: Crash: "Assert error in VRT_time_string(), cache_vrt.c line 346" In-Reply-To: <043.b75d0045623bfb658d4f91b5eac20fc8@varnish-cache.org> References: <043.b75d0045623bfb658d4f91b5eac20fc8@varnish-cache.org> Message-ID: <058.d8a415814afacbf4d552a150a43a2571@varnish-cache.org> #1303: Crash: "Assert error in VRT_time_string(), cache_vrt.c line 346" ----------------------+------------------------- Reporter: flies | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Resolution: worksforme Keywords: | ----------------------+------------------------- Changes (by martin): * status: new => closed * resolution: => worksforme Comment: You are running out of session workspace. When that happens, Varnish will assert. To rectify this, you should increase the session workspace available on your threads by increasing the sess_workspace runtime configuration parameter. Regards, Martin Blix Grydeland -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon May 27 11:17:56 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 27 May 2013 11:17:56 -0000 Subject: [Varnish] #1304: Crash: "Assert error in VRY_Match(), cache_vary.c line 216" In-Reply-To: <043.1282bca3c6fbc7f78f4349fabdd919fd@varnish-cache.org> References: <043.1282bca3c6fbc7f78f4349fabdd919fd@varnish-cache.org> Message-ID: <058.6a52d5ae440da1b366d5689b5f69c976@varnish-cache.org> #1304: Crash: "Assert error in VRY_Match(), cache_vary.c line 216" --------------------+------------------------- Reporter: flies | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: 3.0.3 Severity: normal | Resolution: worksforme Keywords: | --------------------+------------------------- Changes (by martin): * status: new => closed * resolution: => worksforme Comment: You are running out of session workspace. When that happens, Varnish will assert. To rectify this, you should increase the session workspace available on your threads by increasing the sess_workspace runtime configuration parameter. Regards, Martin Blix Grydeland -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu May 30 21:50:06 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 30 May 2013 21:50:06 -0000 Subject: [Varnish] #1310: varnish shouldn't allow "-" in sub names Message-ID: <043.09838e0e0f1907e3c74445d6767e8e71@varnish-cache.org> #1310: varnish shouldn't allow "-" in sub names ----------------------+------------------- Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Keywords: ----------------------+------------------- It confuses the C compiler -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri May 31 11:47:27 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 31 May 2013 11:47:27 -0000 Subject: [Varnish] #1287: Varnish 3.0.3 - segfault in libvarnish.so. In-Reply-To: <044.f166c5ec2ec8ea0bd77090495e866ce4@varnish-cache.org> References: <044.f166c5ec2ec8ea0bd77090495e866ce4@varnish-cache.org> Message-ID: <059.c338850f548d84cc21db1c60720be17e@varnish-cache.org> #1287: Varnish 3.0.3 - segfault in libvarnish.so. ------------------------------------+-------------------- Reporter: robroy | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: segfault libvarnish.so | ------------------------------------+-------------------- Comment (by lygie): Hi, is it the wrong way to use a custom error-page like this? I may have a similar issue, as i have random segfaults about every 10000 connections, too. vcl_error looks like this: {{{ sub vcl_error { set obj.http.Content-Type = "text/html; charset=utf-8"; if (obj.status == 750) { set obj.http.Location = req.http.X-Redirect; set obj.status = 302; return(deliver); } else if (obj.status == 751) { set obj.status = 200; set obj.response = "OK"; synthetic {" "}; return(deliver); } else { synthetic {" "} + obj.status + " " + obj.response + {"

Error "} + obj.status + " " + obj.response + {"

"} + obj.response + {"

Guru Meditation:

XID: "} + req.xid + {"

Varnish
"}; return(deliver); } } }}} I was never able to reproduce the error by myself. Purging has no influence, I tried to make some wired testing connections, but ll are fine. Only the live system crashes every 10000 connections. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri May 31 13:38:54 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 31 May 2013 13:38:54 -0000 Subject: [Varnish] #1311: Probe with chunked encoding results in abnormal varnishlog output Message-ID: <050.b0bdd4cc49a4d1d460793944567caa10@varnish-cache.org> #1311: Probe with chunked encoding results in abnormal varnishlog output --------------------------+-------------------- Reporter: philipseidel | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: trunk | Severity: normal Keywords: varnishlog | --------------------------+-------------------- When using a probe where the response is chunked the output in varnishlog is mangled. Example varnishlog output 0 Backend_health - sVx[2] Still healthy 4--X--- 3 3 8 0.000000 0.166129 HTTP/1.1 200 OK Transfer-Encoding: chunked 15da Test