From varnish-bugs at varnish-cache.org Mon Mar 4 11:03:31 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Mar 2013 11:03:31 -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.995c826625eef00916edf5e72cbcde3d@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 | -----------------------------------+--------------------- Changes (by martin): * owner: => martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 5 12:53:52 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 05 Mar 2013 12:53:52 -0000 Subject: [Varnish] #1273: varnishncsa Extended variables. doesn't return Varnish:handling Message-ID: <042.85b4e36647f1fdf9a653f6a2a6f3cac6@varnish-cache.org> #1273: varnishncsa Extended variables. doesn't return Varnish:handling -------------------------------------------------+------------------------- Reporter: hugo | Type: defect Status: new | Priority: low Milestone: | Component: varnishncsa Version: 3.0.3 | Severity: minor Keywords: varnishncsa, Extended variables, | handling | -------------------------------------------------+------------------------- When using varnishncsa %{X}x option with handling variable. it only returns a '-' character. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 5 14:48:35 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 05 Mar 2013 14:48:35 -0000 Subject: [Varnish] #1273: varnishncsa Extended variables. doesn't return Varnish:handling In-Reply-To: <042.85b4e36647f1fdf9a653f6a2a6f3cac6@varnish-cache.org> References: <042.85b4e36647f1fdf9a653f6a2a6f3cac6@varnish-cache.org> Message-ID: <057.5b006231fa5a4570958caad02f860498@varnish-cache.org> #1273: varnishncsa Extended variables. doesn't return Varnish:handling -------------------------------------------------+------------------------- Reporter: hugo | Owner: Type: defect | Status: new Priority: low | Milestone: Component: varnishncsa | Version: 3.0.3 Severity: minor | Resolution: Keywords: varnishncsa, Extended variables, | handling | -------------------------------------------------+------------------------- Comment (by hugo): When using %{Varnish:handling}x it works fine for hit/miss/pass. This bug only applies when it's handled like an error. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 6 14:50:12 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 06 Mar 2013 14:50:12 -0000 Subject: [Varnish] #1274: Panic when field-name in Vary header is too long (>127 chars) Message-ID: <043.a64356674baeac7cb37102ae1901d42d@varnish-cache.org> #1274: Panic when field-name in Vary header is too long (>127 chars) --------------------+------------------- Reporter: daghf | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------- See: http://seclists.org/fulldisclosure/2013/Mar/61 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 6 14:53:29 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 06 Mar 2013 14:53:29 -0000 Subject: [Varnish] #1275: Panic with malformed Vary header Message-ID: <043.5457d0fc1a6c89f8914b8ab213dda1bc@varnish-cache.org> #1275: Panic with malformed Vary header --------------------+------------------- Reporter: daghf | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------- See: http://seclists.org/fulldisclosure/2013/Mar/55 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 6 18:48:49 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 06 Mar 2013 18:48:49 -0000 Subject: [Varnish] #1276: varnishncsa does not use the modified URL from within varnish VCL Message-ID: <049.1f0c439f596f10dfe15d1e745241e613@varnish-cache.org> #1276: varnishncsa does not use the modified URL from within varnish VCL -------------------------+------------------------- Reporter: raymondjiii | Type: defect Status: new | Priority: normal Milestone: | Component: varnishncsa Version: trunk | Severity: normal Keywords: varnishncsa | -------------------------+------------------------- I modify the URL within my VCL using inline C code with something like: C{ if (strlen(VRT_r_req_url(sp)) < 1000) { syslog(LOG_ERR, "%s", VRT_r_req_url(sp)); char url[1024] = ""; strcpy(url, VRT_r_req_url(sp)); (*URLRemoveTime_fn)(url); syslog(LOG_ERR, "%s", "Modified URL:"); syslog(LOG_ERR, "%s", url); VRT_l_req_url(sp, url, vrt_magic_string_end); } else { syslog(LOG_ERR, "%s", "VARNISH URL TOO LONG"); syslog(LOG_ERR, "%s", VRT_r_req_url(sp)); } }C The above is within the "sub vcl receive" subroutine. I have done a number of tests showing that the modified URL does get cached within Varnish and is hashed against the modified URL. I add X-Cache (Hit/Miss) and X-Cache-Hits HTTP headers to show that my modified URL is in fact being returned from Varnish and not the backend Apache server. Varnishncsa always shows the original URL and not my modified version of the URL. My backend apache server log DOES show the modified URL. I would like varnishncsa to show the data with the modified URL and not the original URL request. I can provide any additional information needed. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 6 18:51:29 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 06 Mar 2013 18:51:29 -0000 Subject: [Varnish] #1276: varnishncsa does not use the modified URL from within varnish VCL In-Reply-To: <049.1f0c439f596f10dfe15d1e745241e613@varnish-cache.org> References: <049.1f0c439f596f10dfe15d1e745241e613@varnish-cache.org> Message-ID: <064.b7981bdba1784651a4eecea608405e8b@varnish-cache.org> #1276: varnishncsa does not use the modified URL from within varnish VCL -------------------------+-------------------- Reporter: raymondjiii | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishncsa | Version: trunk Severity: normal | Resolution: Keywords: varnishncsa | -------------------------+-------------------- Comment (by raymondjiii): This is within Varnish 3.0.3 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 7 09:37:44 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 07 Mar 2013 09:37:44 -0000 Subject: [Varnish] #1277: missing build dep Message-ID: <043.0bd479023ce9bc9b2ced403ad88f9c70@varnish-cache.org> #1277: missing build dep --------------------+------------------- Reporter: perbu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: major | Keywords: --------------------+------------------- The current master branch wont build without libedit. The failure happens in varnishadm and it's quite hard to defer what actually is going on. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 7 09:38:32 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 07 Mar 2013 09:38:32 -0000 Subject: [Varnish] #1278: missing counter - s_error Message-ID: <043.97e9443c31428c68989de969a620ae43@varnish-cache.org> #1278: missing counter - s_error -------------------------+------------------- Reporter: perbu | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: -------------------------+------------------- varnishstat needs a counter for s_error, much like s_pass, s_pipe, etc. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 11 01:50:36 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Mar 2013 01:50:36 -0000 Subject: [Varnish] #1279: Buy replica rolex for sale Message-ID: <045.e16f2b2062bd27e2da0403a3e6423fff@varnish-cache.org> #1279: Buy replica rolex for sale ---------------------------+-------------------- Reporter: maoxian | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: trunk | Severity: normal Keywords: rolex replica | ---------------------------+-------------------- They are [http://www.buymereplicarolex.com Rolex replica] the mock-school [http://www.buymereplicarolex.com/sea-dweller sea dweller replica] in the poetry [http://www.buymereplicarolex.com/yachtmaster yachtmaster replica] and prose [http://www.buymereplicarolex.com/milgauss milgauss replica]. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 11 02:50:35 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Mar 2013 02:50:35 -0000 Subject: [Varnish] #1280: replica wtches rolex for sale Message-ID: <045.cbb822a2f2d67800f5648460f02faa81@varnish-cache.org> #1280: replica wtches rolex for sale ---------------------------+-------------------- Reporter: maoxian | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: trunk | Severity: normal Keywords: replica rolex | ---------------------------+-------------------- They are [http://www.buymereplicarolex.com Rolex replica] the mock-school [http://www.buymereplicarolex.com/sea-dweller sea dweller replica] in the poetry [http://www.buymereplicarolex.com/yachtmaster yachtmaster replica] and prose [http://www.buymereplicarolex.com/milgauss milgauss replica]. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 11 07:06:48 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Mar 2013 07:06:48 -0000 Subject: [Varnish] #1280: (spam) (was: replica wtches rolex for sale) In-Reply-To: <045.cbb822a2f2d67800f5648460f02faa81@varnish-cache.org> References: <045.cbb822a2f2d67800f5648460f02faa81@varnish-cache.org> Message-ID: <060.809041422c63a4917b7e5c35862f71a9@varnish-cache.org> #1280: (spam) ---------------------+---------------------- Reporter: maoxian | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: invalid Keywords: | ---------------------+---------------------- Changes (by phk): * keywords: replica rolex => * status: new => closed * resolution: => invalid Old description: > They are [http://www.buymereplicarolex.com Rolex replica] the mock-school > [http://www.buymereplicarolex.com/sea-dweller sea dweller replica] in the > poetry [http://www.buymereplicarolex.com/yachtmaster yachtmaster replica] > and prose [http://www.buymereplicarolex.com/milgauss milgauss replica]. New description: -- -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 11 07:07:42 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Mar 2013 07:07:42 -0000 Subject: [Varnish] #1279: (spam) (was: Buy replica rolex for sale) In-Reply-To: <045.e16f2b2062bd27e2da0403a3e6423fff@varnish-cache.org> References: <045.e16f2b2062bd27e2da0403a3e6423fff@varnish-cache.org> Message-ID: <060.5e0b8b71d9bf9da9ec1522325a6f741d@varnish-cache.org> #1279: (spam) ---------------------+---------------------- Reporter: maoxian | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: invalid Keywords: | ---------------------+---------------------- Changes (by phk): * keywords: rolex replica => * status: new => closed * resolution: => invalid Old description: > They are [http://www.buymereplicarolex.com Rolex replica] the mock-school > [http://www.buymereplicarolex.com/sea-dweller sea dweller replica] in the > poetry [http://www.buymereplicarolex.com/yachtmaster yachtmaster replica] > and prose [http://www.buymereplicarolex.com/milgauss milgauss replica]. New description: -- -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 11 09:03:18 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Mar 2013 09:03:18 -0000 Subject: [Varnish] #1276: varnishncsa does not use the modified URL from within varnish VCL In-Reply-To: <049.1f0c439f596f10dfe15d1e745241e613@varnish-cache.org> References: <049.1f0c439f596f10dfe15d1e745241e613@varnish-cache.org> Message-ID: <064.ca7052ce9560bdea9fa8fd991361d1c6@varnish-cache.org> #1276: varnishncsa does not use the modified URL from within varnish VCL -------------------------+---------------------- Reporter: raymondjiii | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishncsa | Version: trunk Severity: normal | Resolution: wontfix Keywords: varnishncsa | -------------------------+---------------------- Changes (by tfheen): * status: new => closed * resolution: => wontfix Comment: This is intentional. If you want to log something else, use std.log("foo:" + req.url) and the %{VCL_Log:foo}x format. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 11 11:03:33 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Mar 2013 11:03:33 -0000 Subject: [Varnish] #1278: missing counter - s_error In-Reply-To: <043.97e9443c31428c68989de969a620ae43@varnish-cache.org> References: <043.97e9443c31428c68989de969a620ae43@varnish-cache.org> Message-ID: <058.cbe118a348a65e8022b7f95c06a7764c@varnish-cache.org> #1278: missing counter - s_error -------------------------+--------------------- Reporter: perbu | Owner: martin Type: enhancement | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | -------------------------+--------------------- Changes (by martin): * owner: => martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 11 11:14:47 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Mar 2013 11:14:47 -0000 Subject: [Varnish] #1273: varnishncsa Extended variables. doesn't return Varnish:handling In-Reply-To: <042.85b4e36647f1fdf9a653f6a2a6f3cac6@varnish-cache.org> References: <042.85b4e36647f1fdf9a653f6a2a6f3cac6@varnish-cache.org> Message-ID: <057.2732dd764690308c3e722db1dbf6f8c3@varnish-cache.org> #1273: varnishncsa Extended variables. doesn't return Varnish:handling -------------------------------------------------+------------------------- Reporter: hugo | Owner: Type: defect | Status: new Priority: low | Milestone: Component: varnishncsa | Version: 3.0.3 Severity: minor | Resolution: Keywords: varnishncsa, Extended variables, | handling | -------------------------------------------------+------------------------- Comment (by Tollef Fog Heen ): In [cb3e952b4346e34dbf425b67ca667928d927c59b]: {{{ #!CommitTicketReference repository="" revision="cb3e952b4346e34dbf425b67ca667928d927c59b" Treat error as miss + error in %{Varnish:handling}x format Fixes #1273 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 11 11:14:49 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Mar 2013 11:14:49 -0000 Subject: [Varnish] #1273: varnishncsa Extended variables. doesn't return Varnish:handling In-Reply-To: <042.85b4e36647f1fdf9a653f6a2a6f3cac6@varnish-cache.org> References: <042.85b4e36647f1fdf9a653f6a2a6f3cac6@varnish-cache.org> Message-ID: <057.297e3f6d93155b8f82578fbe9a6636b6@varnish-cache.org> #1273: varnishncsa Extended variables. doesn't return Varnish:handling -------------------------------------------------+------------------------- Reporter: hugo | Owner: Type: defect | Status: closed Priority: low | Milestone: Component: varnishncsa | Version: 3.0.3 Severity: minor | Resolution: fixed Keywords: varnishncsa, Extended variables, | handling | -------------------------------------------------+------------------------- Changes (by Tollef Fog Heen ): * status: new => closed * resolution: => fixed Comment: (In [cb3e952b4346e34dbf425b67ca667928d927c59b]) Treat error as miss + error in %{Varnish:handling}x format Fixes #1273 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 11 11:17:18 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Mar 2013 11:17:18 -0000 Subject: [Varnish] #1275: Panic with malformed Vary header In-Reply-To: <043.5457d0fc1a6c89f8914b8ab213dda1bc@varnish-cache.org> References: <043.5457d0fc1a6c89f8914b8ab213dda1bc@varnish-cache.org> Message-ID: <058.d8e7e0222a9438217f4cbc7cb16fe2b8@varnish-cache.org> #1275: Panic with malformed Vary header --------------------+--------------------- Reporter: daghf | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+--------------------- Changes (by martin): * owner: => martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 11 11:17:25 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Mar 2013 11:17:25 -0000 Subject: [Varnish] #1274: Panic when field-name in Vary header is too long (>127 chars) In-Reply-To: <043.a64356674baeac7cb37102ae1901d42d@varnish-cache.org> References: <043.a64356674baeac7cb37102ae1901d42d@varnish-cache.org> Message-ID: <058.eb5eff0c16281ec7ee41c01d562c58db@varnish-cache.org> #1274: Panic when field-name in Vary header is too long (>127 chars) --------------------+--------------------- Reporter: daghf | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+--------------------- Changes (by martin): * owner: => martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 11 11:20:44 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Mar 2013 11:20:44 -0000 Subject: [Varnish] #1270: Any way to detect/distinguish ESI requests? In-Reply-To: <046.c9b37f3467e6d6c2b4aa0b0321021a52@varnish-cache.org> References: <046.c9b37f3467e6d6c2b4aa0b0321021a52@varnish-cache.org> Message-ID: <061.8ba4c1cd5bb1bb504a4eb1858b112463@varnish-cache.org> #1270: Any way to detect/distinguish ESI requests? -------------------------+---------------------- Reporter: whocares | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Resolution: invalid Keywords: | -------------------------+---------------------- Changes (by tfheen): * status: new => closed * resolution: => invalid Comment: You can use if (req.esi_level > 0) { set req.http.X-Esi = ""; } -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 11 11:26:40 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Mar 2013 11:26:40 -0000 Subject: [Varnish] #1257: Varnish restarting it self, large cache. In-Reply-To: <051.4eb1f47d3c10c74deb792ffa3ee19c81@varnish-cache.org> References: <051.4eb1f47d3c10c74deb792ffa3ee19c81@varnish-cache.org> Message-ID: <066.515d9abd34380298eba4a564869705f5@varnish-cache.org> #1257: Varnish restarting it self, large cache. ---------------------------+-------------------- Reporter: anders-bazoom | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: 3.0.3 Severity: major | Resolution: Keywords: | ---------------------------+-------------------- Changes (by phk): * owner: => phk Comment: I'm not certain that there is much we can do in the short term, until we find a way to reproduce this where we can add debugging. I'm keeping the ticket open, on the off-chance that they hypervisors scheduling have exposed a race-condition in the varnish code. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 11 11:39:10 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Mar 2013 11:39:10 -0000 Subject: [Varnish] #1268: 'shortlived' does not consider grace/keep In-Reply-To: <043.b6f261f0eca41d964db078b4b18d6e88@varnish-cache.org> References: <043.b6f261f0eca41d964db078b4b18d6e88@varnish-cache.org> Message-ID: <058.89c132e4a50d5b7230477873cab84aaf@varnish-cache.org> #1268: 'shortlived' does not consider grace/keep --------------------+-------------------- Reporter: daghf | Owner: daghf Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+-------------------- Changes (by daghf): * owner: => daghf -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 11 11:42:01 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Mar 2013 11:42:01 -0000 Subject: [Varnish] #1265: Randomly getting 503 errors while using Varnish with Apache In-Reply-To: <053.ec20d9f905bc8ee3198ace78366822af@varnish-cache.org> References: <053.ec20d9f905bc8ee3198ace78366822af@varnish-cache.org> Message-ID: <068.ea766ffed984395a9538a5146f18e13b@varnish-cache.org> #1265: Randomly getting 503 errors while using Varnish with Apache -----------------------------+-------------------- Reporter: abhishekjain203 | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Resolution: Keywords: | -----------------------------+-------------------- Description changed by martin: Old description: > Hi, > > We are using Pound, Varnish with Apache on our server and we occasionally > get 503 errors on some of the pages. Below is the Varnish log: > > 201 SessionOpen c 66.87.117.80 39422 208.113.240.79:80 > 201 ReqStart c 66.87.117.80 39422 1459793886 > 201 RxRequest c GET > 201 RxURL c /templates/ja_elastica/css/typo.css > 201 RxProtocol c HTTP/1.1 > 201 RxHeader c Accept: > text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8, > text/css, image/*, application/javascript, application/vbscript, */* > 201 RxHeader c x-wap-profile: > http://device.sprintpcs.com/Samsung/SPH-L710/LJ7.rdf > 201 RxHeader c User-Agent: Mozilla/5.0 (Linux; U; Android 4.1.1; > en-us; SPH-L710 Build/JRO03L) AppleWebKit/534.30 (KHTML, like Gecko) > Version/4.0 Mobile Safari/534.30 > 201 RxHeader c Accept-Encoding: gzip,deflate > 201 RxHeader c Accept-Language: en-US > 201 RxHeader c Accept-Charset: utf-8, iso-8859-1, utf-16, *;q=0.7 > 201 RxHeader c Cookie: > 2fda71d172c9d46b6d4c8e631064f5e0=xom9uHeaplOMwN3EF5N7Z3; > ja_elastica_tpl=ja_elastica; > __utma=112986586.416097245.1360781530.1360781530.1360826480.2; > __utmc=112986586; > __utmz=112986586.1360781530.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); > _ > 201 RxHeader c Host: www.organicfacts.net > 201 RxHeader c Cache-Control: max-age=43200 > 201 RxHeader c Connection: keep-alive > 201 VCL_call c recv pass > 201 VCL_call c hash > 201 Hash c /templates/ja_elastica/css/typo.css > 201 Hash c www.organicfacts.net > 201 VCL_return c hash > 201 VCL_call c pass pass > 201 Backend c 203 default default > 201 TTL c 1459793886 RFC -1 -1 -1 1360926637 0 1360926637 0 0 > 201 VCL_call c fetch > 201 TTL c 1459793886 VCL 120 -1 -1 1360926637 -0 > 201 VCL_return c hit_for_pass > 201 ObjProtocol c HTTP/1.1 > 201 ObjResponse c Service Temporarily Unavailable > 201 ObjHeader c Date: Fri, 15 Feb 2013 11:10:37 GMT > 201 ObjHeader c Server: Apache > 201 ObjHeader c Vary: Accept-Encoding > 201 ObjHeader c Content-Encoding: gzip > 201 ObjHeader c Content-Length: 236 > 201 ObjHeader c Content-Type: text/html; charset=iso-8859-1 > 201 Gzip c u F - 236 323 80 80 1823 > 201 VCL_call c deliver deliver > 201 TxProtocol c HTTP/1.1 > 201 TxStatus c 503 > 201 TxResponse c Service Temporarily Unavailable > 201 TxHeader c Server: Apache > 201 TxHeader c Vary: Accept-Encoding > 201 TxHeader c Content-Encoding: gzip > 201 TxHeader c Content-Type: text/html; charset=iso-8859-1 > 201 TxHeader c Content-Length: 236 > 201 TxHeader c Accept-Ranges: bytes > 201 TxHeader c Date: Fri, 15 Feb 2013 11:10:37 GMT > 201 TxHeader c X-Varnish: 1459793886 > 201 TxHeader c Age: 0 > 201 TxHeader c Via: 1.1 varnish > 201 TxHeader c Connection: keep-alive > 201 Length c 236 > 201 ReqEnd c 1459793886 1360926637.034808159 1360926637.036862135 > 0.000040293 0.002015114 0.000038862 > > Below are the parameters that we are passing while running varnish: > > varnishd -f /etc/varnish/default.vcl -s malloc,2.5G -T 127.0.0.1:2000 -a > 208.113.241.84:80,208.113.240.79:80,127.0.0.3:80 -p thread_pool_max=1500 > -p thread_pools=4 -p listen_depth=2048 -p lru_interval=1800 -h > classic,169313 -p first_byte_timeout=600 -p sess_timeout=600 -p > sess_workspace=131072 -p connect_timeout=600 -p max_restarts=6 -p > vcl_trace=on > > And this is our vcl config: > > backend default { > .host = "127.0.0.2"; > .port = "80"; > .connect_timeout = 600s; > .first_byte_timeout = 600s; > .between_bytes_timeout = 600s; > } > > backend mydomain{ > .host = "127.0.0.4"; > .port = "80"; > .connect_timeout = 600s; > .first_byte_timeout = 600s; > .between_bytes_timeout = 600s; > } > > sub vcl_recv { > # choose a backend depending on domain > if (req.http.host ~ "www.villcart.com") { > set req.backend = mydomain; > }else{ > set req.backend = default; > } > } > > As there is no error in both the varnish log and apache log, we are not > able to figure out where the problem is. Could you please help us out? > > Regards, > Abhishek New description: Hi, We are using Pound, Varnish with Apache on our server and we occasionally get 503 errors on some of the pages. Below is the Varnish log: {{{ 201 SessionOpen c 66.87.117.80 39422 208.113.240.79:80 201 ReqStart c 66.87.117.80 39422 1459793886 201 RxRequest c GET 201 RxURL c /templates/ja_elastica/css/typo.css 201 RxProtocol c HTTP/1.1 201 RxHeader c Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8, text/css, image/*, application/javascript, application/vbscript, */* 201 RxHeader c x-wap-profile: http://device.sprintpcs.com/Samsung/SPH-L710/LJ7.rdf 201 RxHeader c User-Agent: Mozilla/5.0 (Linux; U; Android 4.1.1; en- us; SPH-L710 Build/JRO03L) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30 201 RxHeader c Accept-Encoding: gzip,deflate 201 RxHeader c Accept-Language: en-US 201 RxHeader c Accept-Charset: utf-8, iso-8859-1, utf-16, *;q=0.7 201 RxHeader c Cookie: 2fda71d172c9d46b6d4c8e631064f5e0=xom9uHeaplOMwN3EF5N7Z3; ja_elastica_tpl=ja_elastica; __utma=112986586.416097245.1360781530.1360781530.1360826480.2; __utmc=112986586; __utmz=112986586.1360781530.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); _ 201 RxHeader c Host: www.organicfacts.net 201 RxHeader c Cache-Control: max-age=43200 201 RxHeader c Connection: keep-alive 201 VCL_call c recv pass 201 VCL_call c hash 201 Hash c /templates/ja_elastica/css/typo.css 201 Hash c www.organicfacts.net 201 VCL_return c hash 201 VCL_call c pass pass 201 Backend c 203 default default 201 TTL c 1459793886 RFC -1 -1 -1 1360926637 0 1360926637 0 0 201 VCL_call c fetch 201 TTL c 1459793886 VCL 120 -1 -1 1360926637 -0 201 VCL_return c hit_for_pass 201 ObjProtocol c HTTP/1.1 201 ObjResponse c Service Temporarily Unavailable 201 ObjHeader c Date: Fri, 15 Feb 2013 11:10:37 GMT 201 ObjHeader c Server: Apache 201 ObjHeader c Vary: Accept-Encoding 201 ObjHeader c Content-Encoding: gzip 201 ObjHeader c Content-Length: 236 201 ObjHeader c Content-Type: text/html; charset=iso-8859-1 201 Gzip c u F - 236 323 80 80 1823 201 VCL_call c deliver deliver 201 TxProtocol c HTTP/1.1 201 TxStatus c 503 201 TxResponse c Service Temporarily Unavailable 201 TxHeader c Server: Apache 201 TxHeader c Vary: Accept-Encoding 201 TxHeader c Content-Encoding: gzip 201 TxHeader c Content-Type: text/html; charset=iso-8859-1 201 TxHeader c Content-Length: 236 201 TxHeader c Accept-Ranges: bytes 201 TxHeader c Date: Fri, 15 Feb 2013 11:10:37 GMT 201 TxHeader c X-Varnish: 1459793886 201 TxHeader c Age: 0 201 TxHeader c Via: 1.1 varnish 201 TxHeader c Connection: keep-alive 201 Length c 236 201 ReqEnd c 1459793886 1360926637.034808159 1360926637.036862135 0.000040293 0.002015114 0.000038862 }}} Below are the parameters that we are passing while running varnish: varnishd -f /etc/varnish/default.vcl -s malloc,2.5G -T 127.0.0.1:2000 -a 208.113.241.84:80,208.113.240.79:80,127.0.0.3:80 -p thread_pool_max=1500 -p thread_pools=4 -p listen_depth=2048 -p lru_interval=1800 -h classic,169313 -p first_byte_timeout=600 -p sess_timeout=600 -p sess_workspace=131072 -p connect_timeout=600 -p max_restarts=6 -p vcl_trace=on And this is our vcl config: backend default { .host = "127.0.0.2"; .port = "80"; .connect_timeout = 600s; .first_byte_timeout = 600s; .between_bytes_timeout = 600s; } backend mydomain{ .host = "127.0.0.4"; .port = "80"; .connect_timeout = 600s; .first_byte_timeout = 600s; .between_bytes_timeout = 600s; } sub vcl_recv { # choose a backend depending on domain if (req.http.host ~ "www.villcart.com") { set req.backend = mydomain; }else{ set req.backend = default; } } As there is no error in both the varnish log and apache log, we are not able to figure out where the problem is. Could you please help us out? Regards, Abhishek -- -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 11 11:50:43 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Mar 2013 11:50:43 -0000 Subject: [Varnish] #1265: Randomly getting 503 errors while using Varnish with Apache In-Reply-To: <053.ec20d9f905bc8ee3198ace78366822af@varnish-cache.org> References: <053.ec20d9f905bc8ee3198ace78366822af@varnish-cache.org> Message-ID: <068.2c586d0ee71556d222027ed5be7601ab@varnish-cache.org> #1265: Randomly getting 503 errors while using Varnish with Apache -----------------------------+------------------------- Reporter: abhishekjain203 | 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: {{{ 201 ObjProtocol c HTTP/1.1 201 ObjResponse c Service Temporarily Unavailable 201 ObjHeader c Date: Fri, 15 Feb 2013 11:10:37 GMT 201 ObjHeader c Server: Apache }}} This shows that the 503 page is produced by the Apache, not Varnish. So you will need to have a look at your Apache instance to find the problem. Regards, Martin Blix Grydeland -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 11 11:57:00 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Mar 2013 11:57:00 -0000 Subject: [Varnish] #1263: Varnish Crash In-Reply-To: <043.4fecdbacf5db6c2385e7c0167e5aff67@varnish-cache.org> References: <043.4fecdbacf5db6c2385e7c0167e5aff67@varnish-cache.org> Message-ID: <058.e31d7568565387d7ef89d8bef9ea8004@varnish-cache.org> #1263: Varnish Crash ----------------------+-------------------- Reporter: comur | Owner: daghf Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 3.0.2 Severity: major | Resolution: Keywords: crash | ----------------------+-------------------- Changes (by daghf): * owner: => daghf -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 12 10:17:27 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 12 Mar 2013 10:17:27 -0000 Subject: [Varnish] #1277: missing build dep In-Reply-To: <043.0bd479023ce9bc9b2ced403ad88f9c70@varnish-cache.org> References: <043.0bd479023ce9bc9b2ced403ad88f9c70@varnish-cache.org> Message-ID: <058.94aa3df3cb6551adf37ee75457ff01f2@varnish-cache.org> #1277: missing build dep --------------------+-------------------- Reporter: perbu | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: major | Resolution: Keywords: | --------------------+-------------------- Comment (by Tollef Fog Heen ): In [a5d5ecdea86ba6d9dcb036a78f7606c693f42190]: {{{ #!CommitTicketReference repository="" revision="a5d5ecdea86ba6d9dcb036a78f7606c693f42190" Require libedit/readline Remove a bunch of ifdef code and fix up proper configure check for libedit. Fixes #1277 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 12 10:17:29 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 12 Mar 2013 10:17:29 -0000 Subject: [Varnish] #1277: missing build dep In-Reply-To: <043.0bd479023ce9bc9b2ced403ad88f9c70@varnish-cache.org> References: <043.0bd479023ce9bc9b2ced403ad88f9c70@varnish-cache.org> Message-ID: <058.ca5bf8d0802c8ffe513e5be684783904@varnish-cache.org> #1277: missing build dep --------------------+--------------------- Reporter: perbu | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: major | Resolution: fixed Keywords: | --------------------+--------------------- Changes (by Tollef Fog Heen ): * status: new => closed * resolution: => fixed Comment: (In [a5d5ecdea86ba6d9dcb036a78f7606c693f42190]) Require libedit/readline Remove a bunch of ifdef code and fix up proper configure check for libedit. Fixes #1277 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 12 22:00:57 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 12 Mar 2013 22:00:57 -0000 Subject: [Varnish] #1270: Any way to detect/distinguish ESI requests? In-Reply-To: <046.c9b37f3467e6d6c2b4aa0b0321021a52@varnish-cache.org> References: <046.c9b37f3467e6d6c2b4aa0b0321021a52@varnish-cache.org> Message-ID: <061.119ab2157c25d47fa50b722a53dd0982@varnish-cache.org> #1270: Any way to detect/distinguish ESI requests? -------------------------+---------------------- Reporter: whocares | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Resolution: invalid Keywords: | -------------------------+---------------------- Comment (by whocares): Thanks and I'm sorry for overlooking it in the docs more than once :/ -Stefan -- Ticket URL: Varnish The Varnish HTTP Accelerator From engtmk at gmail.com Mon Mar 4 19:01:39 2013 From: engtmk at gmail.com (TMK) Date: Mon, 4 Mar 2013 21:01:39 +0200 Subject: Fwd: varnish keep crashing In-Reply-To: References: Message-ID: I have installed varnish varnish-3.0.3 revision 9e6a70f from the yum repo. however it keep crashing with the below logged message. kernel: varnishd[5441]: segfault at 0 ip 00007f8a91fff234 sp 00007f8184fbf2f0 error 4 in libvarnish.so[7f8a91ff3000+13000 the machine is centos with kernel 6.32-279.22.1.el6.x86_64. i have another one with the same kernel and same varnish version working just fine. any clue to solve this issue is very much appreciated. -------------- next part -------------- An HTML attachment was scrubbed... URL: From varnish-bugs at varnish-cache.org Wed Mar 13 15:42:02 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 13 Mar 2013 15:42:02 -0000 Subject: [Varnish] #1281: Documentation inconsistency wrt gzip Message-ID: <043.bd50c282914cee08d24ea130407d85bb@varnish-cache.org> #1281: Documentation inconsistency wrt gzip ---------------------------+----------------------------- Reporter: perbu | Owner: Type: documentation | Status: new Priority: normal | Milestone: Varnish 3.0 dev Component: build | Version: 3.0.3 Severity: normal | Keywords: gzip docs ---------------------------+----------------------------- There is some inconsistency in man vcl and man varnishd wrt. gzip. I can fix it if I get some pointers to what the semantics are. man vcl: beresp.do_gzip: Gzip the object (..) Defaults to false. and then, man varnishd says that when http_gzip_support is on Varnish will compress the object. It also states that this is on per default. Which one is correct? Bonus question: Is the correct way disable compression for a request to tamper with req.can_gzip or to remove the Accept-Encoding header? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 14 17:34:00 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 14 Mar 2013 17:34:00 -0000 Subject: [Varnish] #1282: varnishncsa leaves URLs cuttoff for Message-ID: <049.8f18fb5e2274cd0803831bde1d043cb6@varnish-cache.org> #1282: varnishncsa leaves URLs cuttoff for -------------------------+------------------------- Reporter: raymondjiii | Type: defect Status: new | Priority: normal Milestone: | Component: varnishncsa Version: trunk | Severity: normal Keywords: | -------------------------+------------------------- It appears that varnishncsa cuts off URLs at about the 300 character mark. I set the format using: -F %h %l %u %t %r %s %b %{Referer}i [%{X-Forwarded-For}i] %{X-Real-IP}i %{VCL_Log:DU_url}x %{Varnish:handling}x The VCL_Log:DU_url is the req.url at the end of sub vcl_recv which cuts off at 248 characters Is tere anyway to increase this even to the limit that Apache uses? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 18 11:38:47 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 18 Mar 2013 11:38:47 -0000 Subject: [Varnish] #1282: varnishncsa leaves URLs cuttoff for In-Reply-To: <049.8f18fb5e2274cd0803831bde1d043cb6@varnish-cache.org> References: <049.8f18fb5e2274cd0803831bde1d043cb6@varnish-cache.org> Message-ID: <064.0010e1c3b25ca7c054f0dbe87fb0601f@varnish-cache.org> #1282: varnishncsa leaves URLs cuttoff for -------------------------+---------------------- Reporter: raymondjiii | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishncsa | Version: trunk Severity: normal | Resolution: invalid Keywords: | -------------------------+---------------------- Changes (by daghf): * status: new => closed * resolution: => invalid Comment: You need to increase shm_reclen, which specifies is the maximum length of a log record. Default is 255. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 18 14:18:47 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 18 Mar 2013 14:18:47 -0000 Subject: [Varnish] #1283: varnishd assert in http1_cleanup after vcl_error if Transient is full Message-ID: <044.57a09552f2c35ada7956cd5f84d136e6@varnish-cache.org> #1283: varnishd assert in http1_cleanup after vcl_error if Transient is full ----------------------+------------------- Reporter: martin | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+------------------- Applicable only to master. Assert message: {{{ Child (1595) Panic message: Assert error in http1_cleanup(), cache/cache_http1_fsm.c line 186:\n Condition((req->busyobj) == 0) not true.\n thread = (cache-worker)\n ident = Linux,3.2.0-4-amd64,x86_64,-smalloc,-smalloc,-hcritbit,epoll\n Backtrace:\n 0x43a7cb: sess_close_2str+12b4\n 0x43aaf8: sess_close_2str+15e1\n 0x433450: HTTP_Init+d11\n 0x433fc1: HTTP1_Session+48d\n 0x444538: SES_Charge+7ab\n 0x444783: SES_Charge+9f6\n 0x444be5: SES_pool_accept_task+210\n 0x43c35c: Pool_Work_Thread+3eb\n 0x4566d0: WRK_BgThread+28f\n 0x456837: WRK_thread+36\n req = 0x7f367430b020 {\n sp = 0x7f3674302320, vxid = 0, step = R_STP_ERROR,\n req_body = R_BODY_INIT,\n handling = hash,\n err_code = 500, err_reason = Internal Server Error,\n restarts = 0, esi_level = 0\n sp = 0x7f3674302320 {\n fd = 14, vxid = 1006,\n client = 127.0.0.1 51031,\n step = S_STP_WORKING,\n },\n ws = 0x7f367430b1b8 { \n id = "req",\n {s,f,r,e} = {0x7f367430c7c8,+56,(nil),+59480},\n },\n http[req] = {\n ws = 0x7f367430b1b8[req]\n "GET",\n "/",\n "HTTP/1.1",\n "X-Do-Error: true",\n },\n vcl = {\n srcname = {\n "input",\n "Default",\n },\n },\n busyobj = 0x7f3674320020 {\n ws = 0x7f3674320070 { \n id = "bo",\n {s,f,r,e} = {0x7f3674321ab0,0x7f3674321ab0,(nil),+58736},\n },\n do_stream\n bodystatus = 0 (none),\n },\n }\n },\n \n \n }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 18 14:34:55 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 18 Mar 2013 14:34:55 -0000 Subject: [Varnish] #1284: varnishd assert in cnt_error when producing 503 after STV_NewObject fails in cnt_fetchbody() Message-ID: <044.a41132c2c8e9ade4adb0cf081de8052c@varnish-cache.org> #1284: varnishd assert in cnt_error when producing 503 after STV_NewObject fails in cnt_fetchbody() ----------------------+------------------- Reporter: martin | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+------------------- Only applicable to master. Assert message: {{{ Child (20807) Panic message: Assert error in cnt_error(), cache/cache_req_fsm.c line 266:\n Condition((req->objcore) == 0) not true.\n thread = (cache-worker)\n ident = Linux,3.2.0-4-amd64,x86_64,-smalloc,-smalloc,-hcritbit,epoll\n Backtrace:\n 0x43a803: sess_close_2str+12b4\n 0x43ab30: sess_close_2str+15e1\n 0x43de0a: Pool_Init+e77\n 0x442092: CNT_Request+5e3\n 0x433fa2: HTTP1_Session+436\n 0x444654: SES_Charge+7ab\n 0x44489f: SES_Charge+9f6\n 0x444d01: SES_pool_accept_task+210\n 0x43c394: Pool_Work_Thread+3eb\n 0x4567ec: WRK_BgThread+28f\n req = 0x7f532eb15020 {\n sp = 0x7f532eb0c320, vxid = 1073742831, step = R_STP_ERROR,\n req_body = R_BODY_NONE,\n handling = deliver,\n err_code = 503, err_reason = (null),\n restarts = 0, esi_level = 0\n sp = 0x7f532eb0c320 {\n fd = 14, vxid = 1006,\n client = 127.0.0.1 46731,\n step = S_STP_WORKING,\n },\n worker = 0x7f5328ecec70 {\n ws = 0x7f5328ecee60 { \n id = "wrk",\n {s,f,r,e} = {0x7f5328ece430,0x7f5328ece430,(nil),+2048},\n },\n },\n ws = 0x7f532eb151b8 { \n id = "req",\n {s,f,r,e} = {0x7f532eb167c8,+88,(nil),+59480},\n },\n http[req] = {\n ws = 0x7f532eb151b8[req]\n "GET",\n "/obj3",\n "HTTP/1.1",\n "X-Forwarded-For: 127.0.0.1",\n },\n vcl = {\n srcname = {\n "input",\n "Default",\n },\n },\n },\n \n \n }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 18 16:20:47 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 18 Mar 2013 16:20:47 -0000 Subject: [Varnish] #1285: All worker threads can block on the vca_pipe under high load Message-ID: <042.145d58b96f09e62e2c8788620df1a218@varnish-cache.org> #1285: All worker threads can block on the vca_pipe under high load -------------------+-------------------- Reporter: mark | Type: defect Status: new | Priority: high Milestone: | Component: build Version: 3.0.3 | Severity: major Keywords: | -------------------+-------------------- Varnish uses a pipe in non-blocking mode to communicate between the worker threads and the (epoll/kqueue) waiter thread. Under high load, the pipe can fill up, quickly blocking all worker threads. At this point, everything goes to hell, and Varnish does not recover from it until a restart. It appears that seemingly several high traffic sites have experienced this problem regularly over the years, but somehow a fix never made it into Varnish. Let's change that. :) I've attached a patch that fixes the problem, in two ways. It changes the waiter thread loop to read from the vca_pipe first, before doing anything else. This reduces the chance of blocking any worker threads. The patch also changes the worker thread side of the vca_pipe to non- blocking, as Varnish doesn't actually depend on blocking mode at all. This change alone probably suffices as well. (based on a patch originally for Varnish 2.x by Artur Bergman) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 19 14:43:21 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 19 Mar 2013 14:43:21 -0000 Subject: [Varnish] #1284: varnishd assert in cnt_error when producing 503 after STV_NewObject fails in cnt_fetchbody() In-Reply-To: <044.a41132c2c8e9ade4adb0cf081de8052c@varnish-cache.org> References: <044.a41132c2c8e9ade4adb0cf081de8052c@varnish-cache.org> Message-ID: <059.8d78f6ebdd24db76952f02d19b9e1dd9@varnish-cache.org> #1284: varnishd assert in cnt_error when producing 503 after STV_NewObject fails in cnt_fetchbody() ----------------------+-------------------- Reporter: martin | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Comment (by Martin Blix Grydeland ): In [d1bbd0b38fe067da391a1ad9cba42484321c6b8b]: {{{ #!CommitTicketReference repository="" revision="d1bbd0b38fe067da391a1ad9cba42484321c6b8b" Properly clean up resources after STV_NewObject fails before jumping to error. Fixes: #1284 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 19 14:43:22 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 19 Mar 2013 14:43:22 -0000 Subject: [Varnish] #1274: Panic when field-name in Vary header is too long (>127 chars) In-Reply-To: <043.a64356674baeac7cb37102ae1901d42d@varnish-cache.org> References: <043.a64356674baeac7cb37102ae1901d42d@varnish-cache.org> Message-ID: <058.e5267c9a111ee2bb8547ded51b34270c@varnish-cache.org> #1274: Panic when field-name in Vary header is too long (>127 chars) --------------------+--------------------- Reporter: daghf | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+--------------------- Comment (by Martin Blix Grydeland ): In [f5c42c6aaf9bdadf58f58dddb2b9e755d12d790b]: {{{ #!CommitTicketReference repository="" revision="f5c42c6aaf9bdadf58f58dddb2b9e755d12d790b" Return 503 when Vary-headers references header names more than 127 (out limit) characters long. Fixes: #1274 Test case by: Dag Haavi Finstad }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 19 14:43:26 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 19 Mar 2013 14:43:26 -0000 Subject: [Varnish] #1274: Panic when field-name in Vary header is too long (>127 chars) In-Reply-To: <043.a64356674baeac7cb37102ae1901d42d@varnish-cache.org> References: <043.a64356674baeac7cb37102ae1901d42d@varnish-cache.org> Message-ID: <058.b1370505e3dac1dd7fec932d6df8e73f@varnish-cache.org> #1274: Panic when field-name in Vary header is too long (>127 chars) --------------------+--------------------- Reporter: daghf | Owner: martin Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+--------------------- Changes (by Martin Blix Grydeland ): * status: new => closed * resolution: => fixed Comment: (In [f5c42c6aaf9bdadf58f58dddb2b9e755d12d790b]) Return 503 when Vary- headers references header names more than 127 (out limit) characters long. Fixes: #1274 Test case by: Dag Haavi Finstad -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 19 14:43:33 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 19 Mar 2013 14:43:33 -0000 Subject: [Varnish] #1284: varnishd assert in cnt_error when producing 503 after STV_NewObject fails in cnt_fetchbody() In-Reply-To: <044.a41132c2c8e9ade4adb0cf081de8052c@varnish-cache.org> References: <044.a41132c2c8e9ade4adb0cf081de8052c@varnish-cache.org> Message-ID: <059.51124be1756b18ccdacdd8b5d2a68552@varnish-cache.org> #1284: varnishd assert in cnt_error when producing 503 after STV_NewObject fails in cnt_fetchbody() ----------------------+--------------------- Reporter: martin | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+--------------------- Changes (by Martin Blix Grydeland ): * status: new => closed * resolution: => fixed Comment: (In [d1bbd0b38fe067da391a1ad9cba42484321c6b8b]) Properly clean up resources after STV_NewObject fails before jumping to error. Fixes: #1284 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 19 14:43:34 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 19 Mar 2013 14:43:34 -0000 Subject: [Varnish] #1283: varnishd assert in http1_cleanup after vcl_error if Transient is full In-Reply-To: <044.57a09552f2c35ada7956cd5f84d136e6@varnish-cache.org> References: <044.57a09552f2c35ada7956cd5f84d136e6@varnish-cache.org> Message-ID: <059.f161850bd4ff7216c63eeab10126f2db@varnish-cache.org> #1283: varnishd assert in http1_cleanup after vcl_error if Transient is full ----------------------+--------------------- Reporter: martin | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+--------------------- Changes (by Martin Blix Grydeland ): * status: new => closed * resolution: => fixed Comment: (In [d770a105b5587c7b402a1dff1629b78eaa82b0e9]) Resource cleanup in cnt_error() when Transient is full. Fixes: #1283 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 19 14:43:21 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 19 Mar 2013 14:43:21 -0000 Subject: [Varnish] #1283: varnishd assert in http1_cleanup after vcl_error if Transient is full In-Reply-To: <044.57a09552f2c35ada7956cd5f84d136e6@varnish-cache.org> References: <044.57a09552f2c35ada7956cd5f84d136e6@varnish-cache.org> Message-ID: <059.e823503f1c0fcce591506d3e828e882f@varnish-cache.org> #1283: varnishd assert in http1_cleanup after vcl_error if Transient is full ----------------------+-------------------- Reporter: martin | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Comment (by Martin Blix Grydeland ): In [d770a105b5587c7b402a1dff1629b78eaa82b0e9]: {{{ #!CommitTicketReference repository="" revision="d770a105b5587c7b402a1dff1629b78eaa82b0e9" Resource cleanup in cnt_error() when Transient is full. Fixes: #1283 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 19 14:43:28 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 19 Mar 2013 14:43:28 -0000 Subject: [Varnish] #1275: Panic with malformed Vary header In-Reply-To: <043.5457d0fc1a6c89f8914b8ab213dda1bc@varnish-cache.org> References: <043.5457d0fc1a6c89f8914b8ab213dda1bc@varnish-cache.org> Message-ID: <058.d9359a69d247d43409a1731f8c7d207e@varnish-cache.org> #1275: Panic with malformed Vary header --------------------+--------------------- Reporter: daghf | Owner: martin Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+--------------------- Changes (by Martin Blix Grydeland ): * status: new => closed * resolution: => fixed Comment: (In [f8f75cb1a7f4d391bf1c0684c393c336628fb3d5]) Don't panic on malformed Vary headers. Fixes: #1275 Test case by: Dag Haavi Finstad -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 19 14:43:22 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 19 Mar 2013 14:43:22 -0000 Subject: [Varnish] #1275: Panic with malformed Vary header In-Reply-To: <043.5457d0fc1a6c89f8914b8ab213dda1bc@varnish-cache.org> References: <043.5457d0fc1a6c89f8914b8ab213dda1bc@varnish-cache.org> Message-ID: <058.556a1d25195f1453c73eb701190177cb@varnish-cache.org> #1275: Panic with malformed Vary header --------------------+--------------------- Reporter: daghf | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+--------------------- Comment (by Martin Blix Grydeland ): In [f8f75cb1a7f4d391bf1c0684c393c336628fb3d5]: {{{ #!CommitTicketReference repository="" revision="f8f75cb1a7f4d391bf1c0684c393c336628fb3d5" Don't panic on malformed Vary headers. Fixes: #1275 Test case by: Dag Haavi Finstad }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 20 09:52:11 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 20 Mar 2013 09:52:11 -0000 Subject: [Varnish] #1227: Documentation of .initial default is wrong. In-Reply-To: <047.c6dfc3bcd2422ddc524af5f7feb99a76@varnish-cache.org> References: <047.c6dfc3bcd2422ddc524af5f7feb99a76@varnish-cache.org> Message-ID: <062.05e29e9e8229f932ccec7545d95b9fe3@varnish-cache.org> #1227: Documentation of .initial default is wrong. ---------------------------+-------------------- Reporter: perplexes | Owner: daghf Type: documentation | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | ---------------------------+-------------------- Comment (by Dag Haavi Finstad ): In [b7572affa9e7cc4c2d77c90c51e8bf2418ac9613]: {{{ #!CommitTicketReference repository="" revision="b7572affa9e7cc4c2d77c90c51e8bf2418ac9613" Fixes an issue in backend probe initialization that causes the default value of .initial to equal .threshold. The default for .initial is now .threshold - 1, meaning that the backend starts up as sick and a single successful poll is required for it to be considered healthy. With the previous behaviour, a sick backend would not be considered sick until after the initial polls exit the polling window. Thanks to Colin Curtin. Fixes: #1227 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 20 09:52:13 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 20 Mar 2013 09:52:13 -0000 Subject: [Varnish] #1227: Documentation of .initial default is wrong. In-Reply-To: <047.c6dfc3bcd2422ddc524af5f7feb99a76@varnish-cache.org> References: <047.c6dfc3bcd2422ddc524af5f7feb99a76@varnish-cache.org> Message-ID: <062.e80cf0ceee6b968de4a7efc90e8e8b09@varnish-cache.org> #1227: Documentation of .initial default is wrong. ---------------------------+--------------------- Reporter: perplexes | Owner: daghf Type: documentation | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | ---------------------------+--------------------- Changes (by Dag Haavi Finstad ): * status: new => closed * resolution: => fixed Comment: (In [b7572affa9e7cc4c2d77c90c51e8bf2418ac9613]) Fixes an issue in backend probe initialization that causes the default value of .initial to equal .threshold. The default for .initial is now .threshold - 1, meaning that the backend starts up as sick and a single successful poll is required for it to be considered healthy. With the previous behaviour, a sick backend would not be considered sick until after the initial polls exit the polling window. Thanks to Colin Curtin. Fixes: #1227 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 22 10:06:38 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 22 Mar 2013 10:06:38 -0000 Subject: [Varnish] #1263: Varnish Crash In-Reply-To: <043.4fecdbacf5db6c2385e7c0167e5aff67@varnish-cache.org> References: <043.4fecdbacf5db6c2385e7c0167e5aff67@varnish-cache.org> Message-ID: <058.7741996e5cb641f874c34f6cbb4f6ecf@varnish-cache.org> #1263: Varnish Crash ----------------------+--------------------- Reporter: comur | Owner: daghf Type: defect | Status: closed Priority: high | Milestone: Component: varnishd | Version: 3.0.2 Severity: major | Resolution: fixed Keywords: crash | ----------------------+--------------------- Changes (by daghf): * status: new => closed * resolution: => fixed Comment: The test case fails with the following: {{{ **** v1 0.4 vsl| 0 Debug - INCOMPLETE AT: cnt_miss(1231) }}} this is really Varnish's way of saying "this feature hasn't been implemented". Using return (restart) in vcl_miss has since been implemented in master (see commit 3d52af78) and will be part of a future release. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sun Mar 24 19:27:51 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sun, 24 Mar 2013 19:27:51 -0000 Subject: [Varnish] #1286: 3 of 322 tests failed with varnish-trunk+2013-03-22.tar.gz Message-ID: <050.b7b48f5ca353d6d5fc1cce040d870c7c@varnish-cache.org> #1286: 3 of 322 tests failed with varnish-trunk+2013-03-22.tar.gz --------------------------+--------------------- Reporter: plamenpetrov | Type: defect Status: new | Priority: low Milestone: | Component: regress Version: trunk | Severity: minor Keywords: tests fail | --------------------------+--------------------- Found these while trying to create an up-to-date port of varnish for CRUX.[[BR]] Used varnish-trunk+2013-03-22.tar.gz from[[BR]] http://repo.varnish-cache.org/snapshots/[[BR]] Got this while running [[BR]] make check[[BR]] ==============================================[[BR]] 3 of 322 tests failed[[BR]] See bin/varnishtest/test-suite.log[[BR]] Please report to varnish-dev at varnish-cache.org[[BR]] ==============================================[[BR]] test-suite.log is attached.[[BR]] Otherwise - the build was clean.[[BR]] Please, e-mail me if you need more info. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 25 10:59:00 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 25 Mar 2013 10:59:00 -0000 Subject: [Varnish] #1287: Varnish 3.0.3 - segfault in libvarnish.so. Message-ID: <044.f166c5ec2ec8ea0bd77090495e866ce4@varnish-cache.org> #1287: Varnish 3.0.3 - segfault in libvarnish.so. ------------------------------------+---------------------- Reporter: robroy | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: trunk | Severity: normal Keywords: segfault libvarnish.so | ------------------------------------+---------------------- I use varnish 3.0.3 on my production server: rpm -qa | grep varnish varnish-3.0.3-1.el6.x86_64 varnish-libs-3.0.3-1.el6.x86_64 varnish-libs-devel-3.0.3-1.el6.x86_64 uname -r 2.6.32-279.19.1.el6.x86_64 cat /etc/redhat-release CentOS release 6.3 (Final) My varnish process suddenly dies and logs: Mar 22 09:00:07 server.local kernel: : varnishd[2085]: segfault at 0 ip 0000003f60c0c234 sp 00007fa9217cc2e0 error 4 in libvarnish.so[3f60c00000+13000] Mar 22 08:00:14 server.local varnishd[28424]: Child (2043) not responding to CLI, killing it. Mar 22 08:00:14 server.local varnishd[28424]: Child (2043) not responding to CLI, killing it. Mar 22 08:00:14 server.local varnishd[28424]: Child (2043) died signal=11 (core dumped) Mar 22 08:00:14 server.local varnishd[28424]: Child cleanup complete Mar 22 08:00:14 server.local varnishd[28424]: child (1129) Started Mar 22 08:00:14 server.local varnishd[28424]: Child (1129) said Child starts I've attached my configuration. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 26 21:40:44 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 26 Mar 2013 21:40:44 -0000 Subject: [Varnish] #1288: Varnishlog -i doesn't accept hit Message-ID: <041.297e1ef20d34270c2df48a696429c6aa@varnish-cache.org> #1288: Varnishlog -i doesn't accept hit -------------------+------------------------ Reporter: mha | Type: defect Status: new | Priority: normal Milestone: | Component: varnishlog Version: 3.0.3 | Severity: normal Keywords: | -------------------+------------------------ {{{ [root at mha-laptop ~]# varnishlog -i Hit "Hit" matches multiple tags usage: varnishlog [-bCcd] [-i tag] [-I regexp] [-k keep] [-m tag:regex] [-n varnish_name] [-r file] [-s skip] [-X regexp] [-x tag] [-aDV] [-o [tag regex]] [-n varnish_name] [-P file] [-w file] }}} Seems like varnishlog is doing a wildcard match (regexp?) even though the documentation says it includes the specific tag. Works for other tags, but Hit also matches HitPass, likely. Also seems to affect varnishtop. -- Ticket URL: Varnish The Varnish HTTP Accelerator