From varnish-bugs at varnish-cache.org Sat Jan 3 19:22:59 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sat, 03 Jan 2015 19:22:59 -0000 Subject: [Varnish] #1654: died signal=6 (core dumped) Message-ID: <047.ae58892120cd4757d3772f85ce15685c@varnish-cache.org> #1654: died signal=6 (core dumped) ---------------------------------+---------------------- Reporter: rfordinal | Type: defect Status: new | Priority: high Milestone: Varnish 4.0 release | Component: varnishd Version: 4.0.2 | Severity: blocker Keywords: | ---------------------------------+---------------------- varnishd died every few minutes with this message: Panic message:#012Assert error in SES_ScheduleReq(), cache/cache_session.c line 229:#012 Condition((sp)->magic == 0x2c2f9c5a) not true.#012thread = (cache-worker)#012ident = Linux,3.13.0-39-generic,x86_64,-sfile,-smalloc,-hcritbit,epoll#012Backtrace:#012 0x433135: /usr/sbin/varnishd() [0x433135]#012 0x43be2d: /usr/sbin/varnishd(SES_ScheduleReq+0x16d) [0x43be2d]#012 0x425338: /usr/sbin/varnishd() [0x425338]#012 0x42696a: /usr/sbin/varnishd(HSH_DerefObjCore+0xba) [0x42696a]#012 0x4176a4: /usr/sbin/varnishd(VBO_DerefBusyObj+0x1b4) [0x4176a4]#012 0x4371a9: /usr/sbin/varnishd(CNT_Request+0x3a9) [0x4371a9]#012 0x42d17b: /usr/sbin/varnishd(HTTP1_Session+0x3eb) [0x42d17b]#012 0x43b738: /usr/sbin/varnishd() [0x43b738]#012 0x436033: /usr/sbin/varnishd(Pool_Work_Thread+0x373) [0x436033]#012 0x4492f8: /usr/sbin/varnishd() [0x4492f8]#012req = 0x7fac0f017020 {#012 sp = 0x7fac1a828ea0, vxid = 1077870657, step = R_STP_DELIVER,#012 req_body = R_BODY_NONE,#012 restarts = 0, esi_level = 0#012 sp = 0x7fac1a828ea0 {#012 fd = 369, vxid = 2752528,#012 client = 95.103.62.62 50620,#012 step = S_STP_WORKING,#012 },#012 worker = 0x7fac155acc50 {#012 ws = 0x7fac155ace68 {#012 id = "wrk",#012 {s,f,r,e} = {0x7fac155ac440,0x7fac155ac440,(nil),+2048},#012 },#012 VCL::method = 0x0,#012 VCL::return = deliver,#012 },#012 ws = 0x7fac0f0171b8 {#012 id = "req",#012 {s,f,r,e} = {0x7fac0f019010,+880,(nil),+57360},#012 },#012 http[req] = {#012 ws = 0x7fac0f0171b8[req]#012 ... -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 5 08:08:18 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 05 Jan 2015 08:08:18 -0000 Subject: [Varnish] #1654: died signal=6 (core dumped) In-Reply-To: <047.ae58892120cd4757d3772f85ce15685c@varnish-cache.org> References: <047.ae58892120cd4757d3772f85ce15685c@varnish-cache.org> Message-ID: <062.9ec9101a0ceb0927cc73db882e918ab6@varnish-cache.org> #1654: died signal=6 (core dumped) -----------------------+---------------------------------- Reporter: rfordinal | Owner: Type: defect | Status: new Priority: high | Milestone: Varnish 4.0 release Component: varnishd | Version: 4.0.2 Severity: blocker | Resolution: Keywords: | -----------------------+---------------------------------- Description changed by phk: Old description: > varnishd died every few minutes with this message: > > Panic message:#012Assert error in SES_ScheduleReq(), > cache/cache_session.c line 229:#012 Condition((sp)->magic == 0x2c2f9c5a) > not true.#012thread = (cache-worker)#012ident = > Linux,3.13.0-39-generic,x86_64,-sfile,-smalloc,-hcritbit,epoll#012Backtrace:#012 > 0x433135: /usr/sbin/varnishd() [0x433135]#012 0x43be2d: > /usr/sbin/varnishd(SES_ScheduleReq+0x16d) [0x43be2d]#012 0x425338: > /usr/sbin/varnishd() [0x425338]#012 0x42696a: > /usr/sbin/varnishd(HSH_DerefObjCore+0xba) [0x42696a]#012 0x4176a4: > /usr/sbin/varnishd(VBO_DerefBusyObj+0x1b4) [0x4176a4]#012 0x4371a9: > /usr/sbin/varnishd(CNT_Request+0x3a9) [0x4371a9]#012 0x42d17b: > /usr/sbin/varnishd(HTTP1_Session+0x3eb) [0x42d17b]#012 0x43b738: > /usr/sbin/varnishd() [0x43b738]#012 0x436033: > /usr/sbin/varnishd(Pool_Work_Thread+0x373) [0x436033]#012 0x4492f8: > /usr/sbin/varnishd() [0x4492f8]#012req = 0x7fac0f017020 {#012 sp = > 0x7fac1a828ea0, vxid = 1077870657, step = R_STP_DELIVER,#012 req_body = > R_BODY_NONE,#012 restarts = 0, esi_level = 0#012 sp = 0x7fac1a828ea0 > {#012 fd = 369, vxid = 2752528,#012 client = 95.103.62.62 > 50620,#012 step = S_STP_WORKING,#012 },#012 worker = 0x7fac155acc50 > {#012 ws = 0x7fac155ace68 {#012 id = "wrk",#012 {s,f,r,e} = > {0x7fac155ac440,0x7fac155ac440,(nil),+2048},#012 },#012 VCL::method = > 0x0,#012 VCL::return = deliver,#012 },#012 ws = 0x7fac0f0171b8 {#012 > id = "req",#012 {s,f,r,e} = {0x7fac0f019010,+880,(nil),+57360},#012 > },#012 http[req] = {#012 ws = 0x7fac0f0171b8[req]#012 ... New description: varnishd died every few minutes with this message: {{{ Panic message: Assert error in SES_ScheduleReq(), cache/cache_session.c line 229: Condition((sp)->magic == 0x2c2f9c5a) not true. thread = (cache-worker) ident = Linux,3.13.0-39-generic,x86_64,-sfile,-smalloc,-hcritbit,epoll Backtrace: 0x433135: /usr/sbin/varnishd() [0x433135] 0x43be2d: /usr/sbin/varnishd(SES_ScheduleReq+0x16d) [0x43be2d] 0x425338: /usr/sbin/varnishd() [0x425338] 0x42696a: /usr/sbin/varnishd(HSH_DerefObjCore+0xba) [0x42696a] 0x4176a4: /usr/sbin/varnishd(VBO_DerefBusyObj+0x1b4) [0x4176a4] 0x4371a9: /usr/sbin/varnishd(CNT_Request+0x3a9) [0x4371a9] 0x42d17b: /usr/sbin/varnishd(HTTP1_Session+0x3eb) [0x42d17b] 0x43b738: /usr/sbin/varnishd() [0x43b738] 0x436033: /usr/sbin/varnishd(Pool_Work_Thread+0x373) [0x436033] 0x4492f8: /usr/sbin/varnishd() [0x4492f8] req = 0x7fac0f017020 { sp = 0x7fac1a828ea0, vxid = 1077870657, step = R_STP_DELIVER, req_body = R_BODY_NONE, restarts = 0, esi_level = 0 sp = 0x7fac1a828ea0 { fd = 369, vxid = 2752528, client = 95.103.62.62 50620, step = S_STP_WORKING, }, worker = 0x7fac155acc50 { ws = 0x7fac155ace68 { id = "wrk", {s,f,r,e} = {0x7fac155ac440,0x7fac155ac440,(nil),+2048}, }, VCL::method = 0x0, VCL::return = deliver, }, ws = 0x7fac0f0171b8 { id = "req", {s,f,r,e} = {0x7fac0f019010,+880,(nil),+57360}, }, http[req] = { ws = 0x7fac0f0171b8[req] ... }}} -- -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 5 10:42:09 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 05 Jan 2015 10:42:09 -0000 Subject: [Varnish] #1655: Varnishncsa + Range request Message-ID: <045.6058b59bc20eb09e65a41d785519d11b@varnish-cache.org> #1655: Varnishncsa + Range request -------------------------------+------------------------- Reporter: vrobert | Type: defect Status: new | Priority: normal Milestone: | Component: varnishncsa Version: 4.0.2 | Severity: normal Keywords: varnishncsa range | -------------------------------+------------------------- Hi there, Since two days, we have a huge increasing of traffic on one of our PDF, passing from 11000 hits/day to 300000hits/day (in our varnishncsa logs). After investigating, this is due to the new version of Adobe Reader. This one has starting to use the http range header. There is no problem with the loading of the pdf by range, Varnish is doing the job. But in our varnishncsa log, we have now multiple lines for each range. We think this is a bug, are you ok ? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 5 12:07:23 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 05 Jan 2015 12:07:23 -0000 Subject: [Varnish] #1655: Varnishncsa + Range request In-Reply-To: <045.6058b59bc20eb09e65a41d785519d11b@varnish-cache.org> References: <045.6058b59bc20eb09e65a41d785519d11b@varnish-cache.org> Message-ID: <060.c2e5e0af8fce0c6ea334829efdfd1f8f@varnish-cache.org> #1655: Varnishncsa + Range request -------------------------------+------------------------ Reporter: vrobert | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishncsa | Version: 4.0.2 Severity: normal | Resolution: duplicate Keywords: varnishncsa range | -------------------------------+------------------------ Changes (by lkarsten): * status: new => closed * resolution: => duplicate Comment: Hi. I think the real issue here is that varnishncsa logs a 200 return code on something that is a 206. We have an open bug report on this in #1462. Closing this now, reopen if you feel this is incorrect. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 5 12:09:06 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 05 Jan 2015 12:09:06 -0000 Subject: [Varnish] #1462: ReqURL is emitted twice In-Reply-To: <043.4c15f0afe4e6c22dd922a9ce48ae670c@varnish-cache.org> References: <043.4c15f0afe4e6c22dd922a9ce48ae670c@varnish-cache.org> Message-ID: <058.70933cdf3f14d37d4bb01493b26f891c@varnish-cache.org> #1462: ReqURL is emitted twice --------------------+----------------------------------------------- Reporter: scoof | Owner: Martin Blix Grydeland Type: defect | Status: reopened Priority: normal | Milestone: Varnish 4.0-TP2 Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+----------------------------------------------- Comment (by lkarsten): Related/closed duplicate: 1655 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 5 12:10:54 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 05 Jan 2015 12:10:54 -0000 Subject: [Varnish] #1652: Vary: * should be handled in core In-Reply-To: <043.35197030f92fde6a194655a060a20e5d@varnish-cache.org> References: <043.35197030f92fde6a194655a060a20e5d@varnish-cache.org> Message-ID: <058.af131a981edb997b614443300638b13c@varnish-cache.org> #1652: Vary: * should be handled in core ----------------------+-------------------- Reporter: slink | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Changes (by slink): * owner: => phk -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 5 12:12:06 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 05 Jan 2015 12:12:06 -0000 Subject: [Varnish] #1643: corrupt range response In-Reply-To: <041.113f5e6ae1e1582a5da6631379ba3e37@varnish-cache.org> References: <041.113f5e6ae1e1582a5da6631379ba3e37@varnish-cache.org> Message-ID: <056.a55e3b4f566639ae73892d6d241b415e@varnish-cache.org> #1643: corrupt range response --------------------------------------+-------------------- Reporter: Jay | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Later Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: byte-range request range | --------------------------------------+-------------------- Changes (by slink): * status: needinfo => new * owner: => phk -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 5 12:13:49 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 05 Jan 2015 12:13:49 -0000 Subject: [Varnish] #1654: died signal=6 (core dumped) In-Reply-To: <047.ae58892120cd4757d3772f85ce15685c@varnish-cache.org> References: <047.ae58892120cd4757d3772f85ce15685c@varnish-cache.org> Message-ID: <062.d116460b0a6616e290a5a87f4a26e91a@varnish-cache.org> #1654: died signal=6 (core dumped) -----------------------+---------------------------------- Reporter: rfordinal | Owner: Type: defect | Status: closed Priority: high | Milestone: Varnish 4.0 release Component: varnishd | Version: 4.0.2 Severity: blocker | Resolution: duplicate Keywords: | -----------------------+---------------------------------- Changes (by daghf): * status: new => closed * resolution: => duplicate Comment: Hi This is a duplicate of issue #1607, which has since been fixed in master. The fix will likely go into the next release of Varnish, or you could give the master branch a try in the meantime. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 5 12:20:53 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 05 Jan 2015 12:20:53 -0000 Subject: [Varnish] #1520: m00011.vtc fails on OSX x86_64 In-Reply-To: <046.929f5151093fa67f4bf5581f3f019af2@varnish-cache.org> References: <046.929f5151093fa67f4bf5581f3f019af2@varnish-cache.org> Message-ID: <061.50912257e760c3fb2dfea69c27aad35e@varnish-cache.org> #1520: m00011.vtc fails on OSX x86_64 -------------------------+----------------------- Reporter: yoloseem | Owner: lkarsten Type: defect | Status: new Priority: normal | Milestone: Component: varnishtest | Version: 4.0.2 Severity: normal | Resolution: Keywords: | -------------------------+----------------------- Changes (by slink): * status: reopened => new * owner: => lkarsten Comment: as discussed on IRC, please exclude name service issues as the cause -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 5 18:44:45 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 05 Jan 2015 18:44:45 -0000 Subject: [Varnish] #1656: do_stream is backend request specific and not client request specific Message-ID: <051.4f08cd066507dd8d65e34b4c0182acc8@varnish-cache.org> #1656: do_stream is backend request specific and not client request specific ---------------------------+-------------------- Reporter: imoverclocked | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: 4.0.0 | Severity: major Keywords: | ---------------------------+-------------------- When varnish gets two overlapping non-cached requests: 1) Client that handles streaming 2) Client that does not handle streaming then the second client gets a streaming response regardless of configuration. Inside of vcl_backend_response I have a snippet that sets beresp.do_stream depending on the client that is connecting. Of course, the other side of the problem is when a non-streaming client connects first then the streaming client doesn't get a stream from the backend. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 6 03:32:30 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 06 Jan 2015 03:32:30 -0000 Subject: [Varnish] #1656: do_stream is backend request specific and not client request specific In-Reply-To: <051.4f08cd066507dd8d65e34b4c0182acc8@varnish-cache.org> References: <051.4f08cd066507dd8d65e34b4c0182acc8@varnish-cache.org> Message-ID: <066.5ef9910a52dfa320b7a9d2b2c20ae42c@varnish-cache.org> #1656: do_stream is backend request specific and not client request specific ---------------------------+-------------------- Reporter: imoverclocked | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: 4.0.0 Severity: major | Resolution: Keywords: | ---------------------------+-------------------- Comment (by fgsch): What is a client that does not handle streaming? A http 1.0 client? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 6 03:33:17 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 06 Jan 2015 03:33:17 -0000 Subject: [Varnish] #1653: Make numbers in varnishstat human-readable In-Reply-To: <047.f46732d5f2705010f7f9e468bfaca1d8@varnish-cache.org> References: <047.f46732d5f2705010f7f9e468bfaca1d8@varnish-cache.org> Message-ID: <062.ea5b8efea64c881b458e5c3adf427618@varnish-cache.org> #1653: Make numbers in varnishstat human-readable -------------------------+-------------------- Reporter: Centurion | Owner: Type: enhancement | Status: new Priority: low | Milestone: Component: varnishstat | Version: trunk Severity: normal | Resolution: Keywords: | -------------------------+-------------------- Changes (by fgsch): * version: 4.0.0 => trunk -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 6 03:33:51 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 06 Jan 2015 03:33:51 -0000 Subject: [Varnish] #1653: Make numbers in varnishstat human-readable In-Reply-To: <047.f46732d5f2705010f7f9e468bfaca1d8@varnish-cache.org> References: <047.f46732d5f2705010f7f9e468bfaca1d8@varnish-cache.org> Message-ID: <062.c71e4bd0b2282094a0e1cda165e669d2@varnish-cache.org> #1653: Make numbers in varnishstat human-readable -------------------------+-------------------- Reporter: Centurion | Owner: fgsch Type: enhancement | Status: new Priority: low | Milestone: Component: varnishstat | Version: trunk Severity: normal | Resolution: Keywords: | -------------------------+-------------------- Changes (by fgsch): * owner: => fgsch -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 6 03:38:14 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 06 Jan 2015 03:38:14 -0000 Subject: [Varnish] #1656: do_stream is backend request specific and not client request specific In-Reply-To: <051.4f08cd066507dd8d65e34b4c0182acc8@varnish-cache.org> References: <051.4f08cd066507dd8d65e34b4c0182acc8@varnish-cache.org> Message-ID: <066.85f8c51141f0ca8b120706068469468f@varnish-cache.org> #1656: do_stream is backend request specific and not client request specific ---------------------------+-------------------- Reporter: imoverclocked | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 4.0.0 Severity: major | Resolution: Keywords: | ---------------------------+-------------------- Changes (by fgsch): * component: build => varnishd -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 6 13:01:57 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 06 Jan 2015 13:01:57 -0000 Subject: [Varnish] #1652: Vary: * should be handled in core In-Reply-To: <043.35197030f92fde6a194655a060a20e5d@varnish-cache.org> References: <043.35197030f92fde6a194655a060a20e5d@varnish-cache.org> Message-ID: <058.b4d234bd2b3af5fa40d4b220b247ea67@varnish-cache.org> #1652: Vary: * should be handled in core ----------------------+---------------------- Reporter: slink | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: wontfix Keywords: | ----------------------+---------------------- Changes (by slink): * status: new => closed * resolution: => wontfix Comment: phk any myself have discussed this and we don't see much sense in making a change. The main motivation for the ticket was that we create a '*' entry in the vary string which has no effect on vary processing except for the exotic corner case of a '*' request header. Changing core code to mark beresp uncacheable after v_b_r if {{{Vary: *}}} is present would be an option, but it would change semantics for no obvious benefit. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 6 15:32:03 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 06 Jan 2015 15:32:03 -0000 Subject: [Varnish] #1644: VMOD gets incorrect values for cache_param->vre_limits.* In-Reply-To: <043.a394607fa94347f8161bbaff718dfef6@varnish-cache.org> References: <043.a394607fa94347f8161bbaff718dfef6@varnish-cache.org> Message-ID: <058.310a5181cc3137a6a0e3249b4d8e8420@varnish-cache.org> #1644: VMOD gets incorrect values for cache_param->vre_limits.* --------------------+-------------------- Reporter: geoff | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: vmod | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+-------------------- Comment (by geoff): master now has r01644.vtc, which calls essentially the same function in vmod_debug as in the attached VMOD, and it passes on my machine. Nevertheless, both of my VMODs (the test VMOD and vmod_re) are still running into the same problem, on the same machine. So far I've tried setting up the --enable-* options for configure to match Varnish, but no joy. I'll have to figure out what manner of weirdness I have going on with the VMODs in my environment. But there's no reason to believe that there's a bug in Varnish, so this ticket can be closed. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 6 21:42:06 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 06 Jan 2015 21:42:06 -0000 Subject: [Varnish] #1656: do_stream is backend request specific and not client request specific In-Reply-To: <051.4f08cd066507dd8d65e34b4c0182acc8@varnish-cache.org> References: <051.4f08cd066507dd8d65e34b4c0182acc8@varnish-cache.org> Message-ID: <066.c057a2b1cabd7419bc2866c653225ba5@varnish-cache.org> #1656: do_stream is backend request specific and not client request specific ---------------------------+-------------------- Reporter: imoverclocked | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 4.0.0 Severity: major | Resolution: Keywords: | ---------------------------+-------------------- Comment (by imoverclocked): A broken client that expects Content-Length no matter what (in this case: aria2c.) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 6 21:46:23 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 06 Jan 2015 21:46:23 -0000 Subject: [Varnish] #1644: VMOD gets incorrect values for cache_param->vre_limits.* In-Reply-To: <043.a394607fa94347f8161bbaff718dfef6@varnish-cache.org> References: <043.a394607fa94347f8161bbaff718dfef6@varnish-cache.org> Message-ID: <058.05efb3e01a918bcc167bbc36a85ad9af@varnish-cache.org> #1644: VMOD gets incorrect values for cache_param->vre_limits.* --------------------+------------------------- Reporter: geoff | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: vmod | Version: trunk Severity: normal | Resolution: worksforme Keywords: | --------------------+------------------------- Changes (by slink): * status: new => closed * resolution: => worksforme -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 7 22:58:21 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 07 Jan 2015 22:58:21 -0000 Subject: [Varnish] #1653: Make numbers in varnishstat human-readable In-Reply-To: <047.f46732d5f2705010f7f9e468bfaca1d8@varnish-cache.org> References: <047.f46732d5f2705010f7f9e468bfaca1d8@varnish-cache.org> Message-ID: <062.54ddbcda2ea34f60e27e96b1bd09dc8b@varnish-cache.org> #1653: Make numbers in varnishstat human-readable -------------------------+-------------------- Reporter: Centurion | Owner: fgsch Type: enhancement | Status: new Priority: low | Milestone: Component: varnishstat | Version: trunk Severity: normal | Resolution: Keywords: | -------------------------+-------------------- Comment (by fgsch): See attached 2 patches against master. This adds support to cycle through different units in the varnishstat curses interface using 'e'. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 9 06:02:16 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 09 Jan 2015 06:02:16 -0000 Subject: [Varnish] #1657: Use Coupons Codes For Your Online Shopping Message-ID: <048.9f42638e236206cbe0fb9812be478e2c@varnish-cache.org> #1657: Use Coupons Codes For Your Online Shopping -------------------------------------------------+------------------------- Reporter: shanrobert | Type: task Status: new | Priority: high Milestone: | Component: build Version: 4.0.2 | Severity: normal Keywords: coupons,coupon codes,india coupon | codes,promotional codes,promo codes,promotion | codes,discount codes,online coupon | codes,online coupons | -------------------------------------------------+------------------------- Considering the economic conditions, it isn?t very easy to get everything we want within our budget. However the discount coupons available online gives us an opportunity to save huge amount of money. All we need to do is look out for different kinds of online [http://www.crazycoupons.in/ discount coupons] which will give us a big discount while shopping.Visit us at [http://www.crazycoupons.in/ http://www.crazycoupons.in/] -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sat Jan 10 15:36:13 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sat, 10 Jan 2015 15:36:13 -0000 Subject: [Varnish] #1645: apt-get source does not work for varnish on precise and trusty In-Reply-To: <049.39e406a6b89a08b089f4e61c37871c86@varnish-cache.org> References: <049.39e406a6b89a08b089f4e61c37871c86@varnish-cache.org> Message-ID: <064.a49032a6cce9527f46f6982fff670fdd@varnish-cache.org> #1645: apt-get source does not work for varnish on precise and trusty -------------------------+---------------------- Reporter: timhilliard | Owner: fgsch Type: defect | Status: new Priority: normal | Milestone: Component: packaging | Version: unknown Severity: normal | Resolution: Keywords: | -------------------------+---------------------- Comment (by dbu): I think this is a problem for all debian varnish 4 versions too. https://repo.varnish-cache.org/debian/dists/wheezy/varnish-4.0/binary- all/Packages.bz2 only lists varnish-doc but not the repository for varnish itself. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sun Jan 11 22:10:58 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sun, 11 Jan 2015 22:10:58 -0000 Subject: [Varnish] #1658: Hash and Random director is deflected at the health-check failover Message-ID: <042.711b6c5aa82af63b78fa7c6c84b3ae5f@varnish-cache.org> #1658: Hash and Random director is deflected at the health-check failover -------------------+-------------------- Reporter: xcir | Type: defect Status: new | Priority: normal Milestone: | Component: vmod Version: trunk | Severity: normal Keywords: | -------------------+-------------------- I have noticed that failover is deflected. If health-check failures, select to other backend. But, selected backend is near for seed is same. --vcl {{{ vcl 4.0; import directors; backend b1 { .host = "127.0.0.1";.port = "88";} backend b2 { .host = "127.0.0.1";.port = "88";} backend b3 { .host = "127.0.0.1";.port = "88";} backend b4 { .host = "127.0.0.1";.port = "88";} sub vcl_init{ new ws_rand = directors.random(); ws_rand.add_backend(b1, 1.0); ws_rand.add_backend(b2, 1.0); ws_rand.add_backend(b3, 1.0); ws_rand.add_backend(b4, 1.0); } sub vcl_recv{ set req.backend_hint = ws_rand.backend(); return(pass); } }}} --command {{{ test: #ab -n 1200 -c1 http://localhost/ get log: # varnishlog -graw -ibackend> z # cat z|sed -e 's/\s\+/\t/g'|cut -f 7|sort | uniq -c }}} --log {{{ All backend is healthy: 298 b1(127.0.0.1,,88) 313 b2(127.0.0.1,,88) 304 b3(127.0.0.1,,88) 285 b4(127.0.0.1,,88) b1 is sick: 605 b2(127.0.0.1,,88)<-It's heavy.. 307 b3(127.0.0.1,,88) 288 b4(127.0.0.1,,88) b2 is sick: 388 b1(127.0.0.1,,88) 519 b3(127.0.0.1,,88) 293 b4(127.0.0.1,,88) b3 is sick: 325 b1(127.0.0.1,,88) 488 b2(127.0.0.1,,88) 387 b4(127.0.0.1,,88) b4 is sick: 301 b1(127.0.0.1,,88) 310 b2(127.0.0.1,,88) 589 b3(127.0.0.1,,88) }}} I've created a patch to re-hash the seed at the failover. --log(patched) {{{ All backend is healthy: 294 b1(127.0.0.1,,88) 303 b2(127.0.0.1,,88) 318 b3(127.0.0.1,,88) 285 b4(127.0.0.1,,88) b1 is sick: 356 b2(127.0.0.1,,88) 429 b3(127.0.0.1,,88) 415 b4(127.0.0.1,,88) b2 is sick: 439 b1(127.0.0.1,,88) 366 b3(127.0.0.1,,88) 395 b4(127.0.0.1,,88) b3 is sick: 425 b1(127.0.0.1,,88) 394 b2(127.0.0.1,,88) 381 b4(127.0.0.1,,88) b4 is sick: 394 b1(127.0.0.1,,88) 405 b2(127.0.0.1,,88) 401 b3(127.0.0.1,,88) }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 12 12:22:32 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Jan 2015 12:22:32 -0000 Subject: [Varnish] #1650: X-Forwarded-For looses the first ip in list In-Reply-To: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> References: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> Message-ID: <065.c02de19fa0cf1f6b72bf076c2ee61b2c@varnish-cache.org> #1650: X-Forwarded-For looses the first ip in list --------------------------+----------------------- Reporter: KlavsKlavsen | Owner: Type: defect | Status: needinfo Priority: normal | Milestone: Component: build | Version: 4.0.2 Severity: normal | Resolution: Keywords: | --------------------------+----------------------- Comment (by phk): any news ? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 12 12:39:45 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Jan 2015 12:39:45 -0000 Subject: [Varnish] #1642: Assert error in VGZ_Ibuf() In-Reply-To: <045.985190b764fa9780a1b24d2b8ab90094@varnish-cache.org> References: <045.985190b764fa9780a1b24d2b8ab90094@varnish-cache.org> Message-ID: <060.2f14607845d9d0a3e14a512096ba6f64@varnish-cache.org> #1642: Assert error in VGZ_Ibuf() --------------------------+--------------------- Reporter: llavaud | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: major | Resolution: Keywords: assert error | --------------------------+--------------------- Comment (by llavaud): me i choose the quickest way ! ;) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 12 14:02:31 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Jan 2015 14:02:31 -0000 Subject: [Varnish] #1650: X-Forwarded-For looses the first ip in list In-Reply-To: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> References: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> Message-ID: <065.024af2022160d04b07f1ab5b7acf89d7@varnish-cache.org> #1650: X-Forwarded-For looses the first ip in list --------------------------+----------------------- Reporter: KlavsKlavsen | Owner: Type: defect | Status: needinfo Priority: normal | Milestone: Component: build | Version: 4.0.2 Severity: normal | Resolution: Keywords: | --------------------------+----------------------- Comment (by KlavsKlavsen): Finally got to debug it, and found the reason. The cisco ACE box in front, adds a new x-forwarded-header - even though there already is one :( So varnish receives this: - ReqHeader X-Forwarded-For: 10.230.103.96 - ReqHeader X-Forwarded-For: 77.66.12.106, 10.230.1.34 which then gets sanitized to: - ReqHeader X-Forwarded-For: 10.233.113.96, $ip-of-client- contacting-varnish whereas on our current setup, we simply return in varnish 3 - so it does not touch the x-forwarded-for headers - and appearently php (the website behind this - not something I work on :) magicly converts these two x -forwarded-headers into one list. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 12 14:17:50 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Jan 2015 14:17:50 -0000 Subject: [Varnish] #1658: Hash and Random director is deflected at the health-check failover In-Reply-To: <042.711b6c5aa82af63b78fa7c6c84b3ae5f@varnish-cache.org> References: <042.711b6c5aa82af63b78fa7c6c84b3ae5f@varnish-cache.org> Message-ID: <057.622aa5bc1253a21d31ac4eeff186872d@varnish-cache.org> #1658: Hash and Random director is deflected at the health-check failover --------------------+-------------------- Reporter: xcir | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: vmod | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+-------------------- Comment (by xcir): I add vtc file. Check varnish version is {{{ varnishd (varnish-4.0.2 revision bfe7cd1) and varnishd (varnish-trunk revision a6ad0ea) }}} --- healthy.vtc is all backend is healthy. Count of this direction is {{{ s1=12 s2=16 s3=12 }}} --- sick1.vtc is s1 is sick. Count of this direction is {{{ s2=28 (+12) s3=12 }}} All s1 to failover to the s2. --- sick3.vtc is s3 is sick. Count of this direction is {{{ s1=12 s2=28 (+12) }}} All s3 to failover to the s2. --- sick1_patch.vtc is s1 is sick.(for patched) Count of this direction is {{{ s2=25 (+9) s3=15 (+3) }}} --- sick3_patch.vtc is s3 is sick.(for patched) Count of this direction is {{{ s1=17 (+5) s2=23 (+7) }}} It's seem to be imbalanced. https://github.com/varnish/Varnish- Cache/blob/418cea5d6c32f14aaa16a7d0b58b8e8a6e287bb9/lib/libvmod_directors/vdir.c#L203 This code was subtraction total weight. But, not regenerate w value. If backend number is 3. select backend is following by w value. {{{ s1 0.0~0.3 s2 0.3~0.6 s3 0.7~1.0 }}} And, If sick a s1 backend. select backend is following by w value. {{{ s2 0.0~0.5 s3 0.5~1.0 }}} If value over 0.3 and s1 sick in vdir_pick_be. select to s2 or s3 without check healthy. But, if value less 0.3. select s2 with check healthy. s1(healthy) and s2(sick) range is duplicated. This is the imbalance reason. You might want to regenerate the w value. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 12 15:38:21 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Jan 2015 15:38:21 -0000 Subject: [Varnish] #1658: Hash and Random director is deflected at the health-check failover In-Reply-To: <042.711b6c5aa82af63b78fa7c6c84b3ae5f@varnish-cache.org> References: <042.711b6c5aa82af63b78fa7c6c84b3ae5f@varnish-cache.org> Message-ID: <057.6618088d6ceb5939b61d71d051449bca@varnish-cache.org> #1658: Hash and Random director is deflected at the health-check failover --------------------+----------------------------------------------- Reporter: xcir | Owner: Martin Blix Grydeland Type: defect | Status: closed Priority: normal | Milestone: Component: vmod | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+----------------------------------------------- Changes (by Martin Blix Grydeland ): * owner: => Martin Blix Grydeland * status: new => closed * resolution: => fixed Comment: In [a49d5507fdd2abc5cbd6245ae93e768722e96733]: {{{ #!CommitTicketReference repository="" revision="a49d5507fdd2abc5cbd6245ae93e768722e96733" Always take the number of healthy backends into account when selecting a backend by weight. This removes the bias problems the current code exhibits when there is a sick backend in the set. Spotted by: xcir Fixes: #1658 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 12 16:27:30 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Jan 2015 16:27:30 -0000 Subject: [Varnish] #1658: Hash and Random director is deflected at the health-check failover In-Reply-To: <042.711b6c5aa82af63b78fa7c6c84b3ae5f@varnish-cache.org> References: <042.711b6c5aa82af63b78fa7c6c84b3ae5f@varnish-cache.org> Message-ID: <057.639c4979b5b57b2b9cf9414bb60a94db@varnish-cache.org> #1658: Hash and Random director is deflected at the health-check failover --------------------+----------------------------------------------- Reporter: xcir | Owner: Martin Blix Grydeland Type: defect | Status: closed Priority: normal | Milestone: Component: vmod | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+----------------------------------------------- Comment (by xcir): This commit have problem in hash director. Selected backend. {{{ healthy | patch | a49d550 | --------------------------- 2 |2 |3(upd) 3 |3 |3 4 |4 |4 2 |2 |2 2 |2 |3(upd) 1 |4(upd) |2(upd) 1 |4(upd) |2(upd) 1 |3(upd) |2(upd) 1 |3(upd) |2(upd) 2 |2 |3(upd) }}} a49d550 has object relocation occurs. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 12 16:29:53 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Jan 2015 16:29:53 -0000 Subject: [Varnish] #1658: Hash and Random director is deflected at the health-check failover In-Reply-To: <042.711b6c5aa82af63b78fa7c6c84b3ae5f@varnish-cache.org> References: <042.711b6c5aa82af63b78fa7c6c84b3ae5f@varnish-cache.org> Message-ID: <057.a9751c19cebba97395920e3a170f644e@varnish-cache.org> #1658: Hash and Random director is deflected at the health-check failover --------------------+----------------------------------------------- Reporter: xcir | Owner: Martin Blix Grydeland Type: defect | Status: reopened Priority: normal | Milestone: Component: vmod | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+----------------------------------------------- Changes (by xcir): * status: closed => reopened * resolution: fixed => -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 12 16:30:04 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Jan 2015 16:30:04 -0000 Subject: [Varnish] #1658: Hash and Random director is deflected at the health-check failover In-Reply-To: <042.711b6c5aa82af63b78fa7c6c84b3ae5f@varnish-cache.org> References: <042.711b6c5aa82af63b78fa7c6c84b3ae5f@varnish-cache.org> Message-ID: <057.2a010690ce8d269219b6d663d5078749@varnish-cache.org> #1658: Hash and Random director is deflected at the health-check failover --------------------+----------------------------------------------- Reporter: xcir | Owner: Martin Blix Grydeland Type: defect | Status: reopened Priority: normal | Milestone: Component: vmod | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+----------------------------------------------- Comment (by xcir): I think this commit have problem in hash director. Selected backend. {{{ healthy | patch | a49d550 | --------------------------- 2 |2 |3(upd) 3 |3 |3 4 |4 |4 2 |2 |2 2 |2 |3(upd) 1 |4(upd) |2(upd) 1 |4(upd) |2(upd) 1 |3(upd) |2(upd) 1 |3(upd) |2(upd) 2 |2 |3(upd) }}} a49d550 has object relocation occurs. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 12 16:35:37 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Jan 2015 16:35:37 -0000 Subject: [Varnish] #1650: X-Forwarded-For looses the first ip in list In-Reply-To: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> References: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> Message-ID: <065.c78f875693d6b036b491f14584d32b82@varnish-cache.org> #1650: X-Forwarded-For looses the first ip in list --------------------------+------------------------- Reporter: KlavsKlavsen | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: 4.0.2 Severity: normal | Resolution: worksforme Keywords: | --------------------------+------------------------- Changes (by daghf): * status: needinfo => closed * resolution: => worksforme Comment: Thanks for getting back to us. It sounds like Varnish is doing the right thing here, so I'll just close this. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 12 17:03:43 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Jan 2015 17:03:43 -0000 Subject: [Varnish] #1650: X-Forwarded-For looses the first ip in list In-Reply-To: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> References: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> Message-ID: <065.518d37a66c8b4ffe38c5b7d8a9397c47@varnish-cache.org> #1650: X-Forwarded-For looses the first ip in list --------------------------+------------------------- Reporter: KlavsKlavsen | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: 4.0.2 Severity: normal | Resolution: worksforme Keywords: | --------------------------+------------------------- Comment (by KlavsKlavsen): while I do realize it's fairly sensible to do so - there's no actual standard saying that there cannot be multiple x-forwarded-for headers (and the Forwarded header (RFC7239) actually is going to use multiple lines) - it would be fair for someone to want to accept x-forwarded-headers like that. So perhaps an option in varnish 4 - to make it work as is possible with varnish 3 - without modifying x-forwarded-for headers.. so one can simply handle it how one wants. I will try to get the defective cisco box fixed, but I would appreciate being able to choose how Varnish handles x-forwarded-for - if at all.. it should be an optional header (in varnish 4 I can only choose to unset it - not to leave it as-is). -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 12 20:06:01 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Jan 2015 20:06:01 -0000 Subject: [Varnish] #1650: X-Forwarded-For looses the first ip in list In-Reply-To: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> References: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> Message-ID: <065.7b642dbbc39a759b48bea67305e043b5@varnish-cache.org> #1650: X-Forwarded-For looses the first ip in list --------------------------+------------------------- Reporter: KlavsKlavsen | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: 4.0.2 Severity: normal | Resolution: worksforme Keywords: | --------------------------+------------------------- Comment (by fgsch): I think we should collect the header, collapsing multiple x-f-f into one before appending the client ip. Patch attached. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 12 20:15:05 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 12 Jan 2015 20:15:05 -0000 Subject: [Varnish] #1650: X-Forwarded-For looses the first ip in list In-Reply-To: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> References: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> Message-ID: <065.8dabb0a23a157223f39a07b7dc386a41@varnish-cache.org> #1650: X-Forwarded-For looses the first ip in list --------------------------+----------------------- Reporter: KlavsKlavsen | Owner: Type: defect | Status: reopened Priority: normal | Milestone: Component: build | Version: 4.0.2 Severity: normal | Resolution: Keywords: | --------------------------+----------------------- Changes (by daghf): * status: closed => reopened * resolution: worksforme => -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 13 09:05:43 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 13 Jan 2015 09:05:43 -0000 Subject: [Varnish] #1650: X-Forwarded-For looses the first ip in list In-Reply-To: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> References: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> Message-ID: <065.85065ab23a3bb383f5b7dd7f7bc33d53@varnish-cache.org> #1650: X-Forwarded-For looses the first ip in list --------------------------+----------------------- Reporter: KlavsKlavsen | Owner: Type: defect | Status: reopened Priority: normal | Milestone: Component: build | Version: 4.0.2 Severity: normal | Resolution: Keywords: | --------------------------+----------------------- Comment (by fgsch): On second thought this might be a bit convoluted. Calling http_CollectHdr() should be enough. New patch attached. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 13 14:45:04 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 13 Jan 2015 14:45:04 -0000 Subject: [Varnish] #1462: ReqURL is emitted twice In-Reply-To: <043.4c15f0afe4e6c22dd922a9ce48ae670c@varnish-cache.org> References: <043.4c15f0afe4e6c22dd922a9ce48ae670c@varnish-cache.org> Message-ID: <058.84f92271ccd4aae47da864e110783f69@varnish-cache.org> #1462: ReqURL is emitted twice --------------------+------------------------------ Reporter: scoof | Owner: aondio Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP2 Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+------------------------------ Changes (by lkarsten): * owner: Martin Blix Grydeland => aondio * status: reopened => new -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 14 04:35:00 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 14 Jan 2015 04:35:00 -0000 Subject: [Varnish] #1653: Make numbers in varnishstat human-readable In-Reply-To: <047.f46732d5f2705010f7f9e468bfaca1d8@varnish-cache.org> References: <047.f46732d5f2705010f7f9e468bfaca1d8@varnish-cache.org> Message-ID: <062.825d056c233e26381dd4a2a30499e486@varnish-cache.org> #1653: Make numbers in varnishstat human-readable -------------------------+--------------------- Reporter: Centurion | Owner: martin Type: enhancement | Status: new Priority: low | Milestone: Component: varnishstat | Version: trunk Severity: normal | Resolution: Keywords: | -------------------------+--------------------- Changes (by fgsch): * owner: fgsch => martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 14 05:21:25 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 14 Jan 2015 05:21:25 -0000 Subject: [Varnish] #1650: xff handling discards multiple headers (was: X-Forwarded-For looses the first ip in list) In-Reply-To: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> References: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> Message-ID: <065.63b9c5f36a380d543ea9a5a37547f020@varnish-cache.org> #1650: xff handling discards multiple headers --------------------------+----------------------- Reporter: KlavsKlavsen | Owner: Type: defect | Status: reopened Priority: normal | Milestone: Component: build | Version: 4.0.2 Severity: normal | Resolution: Keywords: | --------------------------+----------------------- -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 14 05:27:23 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 14 Jan 2015 05:27:23 -0000 Subject: [Varnish] #1650: xff handling discards multiple headers In-Reply-To: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> References: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> Message-ID: <065.b1853d53ec4939e56d02b0d0116b858c@varnish-cache.org> #1650: xff handling discards multiple headers --------------------------+--------------------------------------------- Reporter: KlavsKlavsen | Owner: Federico G. Schwindt Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: 4.0.2 Severity: normal | Resolution: fixed Keywords: | --------------------------+--------------------------------------------- Changes (by Federico G. Schwindt ): * owner: => Federico G. Schwindt * status: reopened => closed * resolution: => fixed Comment: In [bbd4e79adc2ac44fe3866b5288fed8a3ecb05bb0]: {{{ #!CommitTicketReference repository="" revision="bbd4e79adc2ac44fe3866b5288fed8a3ecb05bb0" Collapse multiple X-Forwarded-For headers Fixes #1650 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 14 13:47:56 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 14 Jan 2015 13:47:56 -0000 Subject: [Varnish] #1659: ban lurker doesn't purge all effected objects Message-ID: <059.d0008c342b62ce4e6a704e0084bc4f28@varnish-cache.org> #1659: ban lurker doesn't purge all effected objects -----------------------+---------------------- Reporter: varnish@? | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: 3.0.6 | Severity: normal Keywords: | -----------------------+---------------------- Hi *, couple months ago I had a purging problem, where it seems that not all objects where purged by the ban lurker thread. Today this issue happens again and I had the chance to capture some logs and requests. Story: Our customer purges varnish every night at 1pm CET, which he does with a PURGE-Request which is handled by the following vcl: {{{ if (req.url ~ "\*") { ban("obj.http.X-Purge-URL ~ " + req.url + " && obj.http.X -Purge-Host ~ " + req.http.host); error 200 "Purge added"; } }}} This request results in the following ban entry: {{{ 1421192472.105130 0G obj.http.X-Purge-URL ~ /* && obj.http.X -Purge-Host ~ domain.tld }}} I know, the regex "/*" is some kind of weird, but it shoul match every URL since the URL starts with a "/". But now we got the problem, that not all URLs are purged, following a varnishlog trace for an object which had have purged last night: {{{ 420 SessionOpen c X.X.X.X 38584 X.X.X.X:80 420 ReqStart c X.X.X.X 38584 2713433276 420 RxRequest c HEAD 420 RxURL c /en-gb/printed-denim-skirt-with-leather-trim.html 420 RxProtocol c HTTP/1.1 420 RxHeader c User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.15.3 zlib/1.2.3 libidn/1.18 libssh2/1.4.2 420 RxHeader c Host: www.domain.tld 420 RxHeader c Accept: */* 420 RxHeader c X-DEBUG:XXXXX 420 VCL_call c recv lookup 420 VCL_call c hash 420 Hash c /en-gb/printed-denim-skirt-with-leather-trim.html 420 Hash c www.domain.tld 420 VCL_return c hash 420 Hit c 2700988225 420 VCL_call c hit deliver 420 VCL_call c deliver deliver 420 TxProtocol c HTTP/1.1 420 TxStatus c 200 420 TxResponse c OK 420 TxHeader c Server: Apache 420 TxHeader c P3p: CP="CAO PSA OUR" 420 TxHeader c X-Cache-Debug: 1 420 TxHeader c X-Cache-Tags: catalog_product_327804 420 TxHeader c Vary: Accept-Encoding 420 TxHeader c Content-Type: text/html; charset=UTF-8 420 TxHeader c X-Purge-URL: /en-gb/printed-denim-skirt-with-leather- trim.html 420 TxHeader c X-Purge-Host: www.domain.tld 420 TxHeader c X-Orig-Query-String: 420 TxHeader c X-Striped-Query-String: 420 TxHeader c Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 420 TxHeader c Pragma: no-cache 420 TxHeader c Expires: Mon, 31 Mar 2008 10:00:00 GMT 420 TxHeader c Date: Wed, 14 Jan 2015 12:42:02 GMT 420 TxHeader c X-Varnish: 2713433276 2700988225 420 TxHeader c Age: 74851 420 TxHeader c Via: 1.1 varnish 420 TxHeader c Connection: keep-alive 420 TxHeader c X-Cache: HIT 420 TxHeader c X-Cache-Hits: 12 420 TxHeader c X-BE: dir_domain_tld_random 420 TxHeader c X-BE-Name: 420 TxHeader c X-Lifetime: 11548.540 420 Length c 0 420 ReqEnd c 2713433276 1421239322.510934830 1421239322.511025429 0.000041962 0.000051498 0.000039101 }}} The indicator for myself is the Age header of the object. Some background infos, normally the varnish cache holds around 300.000 objects when the nightly purging starts. It takes about 30 minutes to purge all objects from the cache. Give me a hint if you need some more information. Best regards, Martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 14 14:15:08 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 14 Jan 2015 14:15:08 -0000 Subject: [Varnish] #1659: ban lurker doesn't purge all effected objects In-Reply-To: <059.d0008c342b62ce4e6a704e0084bc4f28@varnish-cache.org> References: <059.d0008c342b62ce4e6a704e0084bc4f28@varnish-cache.org> Message-ID: <074.965488bde9f6e6b9e2d01c26f6e13e7a@varnish-cache.org> #1659: ban lurker doesn't purge all effected objects -----------------------+-------------------- Reporter: varnish@? | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.6 Severity: normal | Resolution: Keywords: | -----------------------+-------------------- Comment (by varnish@?): As requested, following a trace of an object entering the cache: {{{ 587 SessionOpen c X.X.X.X 42360 X.X.X.X:80 587 ReqStart c X.X.X.X 42360 2714897186 587 RxRequest c HEAD 587 RxURL c /en-gb/printed-denim-skirt-with-leather-trim.html?foo 587 RxProtocol c HTTP/1.1 587 RxHeader c User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.15.3 zlib/1.2.3 libidn/1.18 libssh2/1.4.2 587 RxHeader c Host: www.domain.tld 587 RxHeader c Accept: */* 587 RxHeader c X-DEBUG:XXXXXX 587 VCL_call c recv lookup 587 VCL_call c hash 587 Hash c /en-gb/printed-denim-skirt-with-leather-trim.html?foo 587 Hash c www.domain.tld 587 VCL_return c hash 587 VCL_call c miss fetch 587 Backend c 647 dir_domain_tld_random be_domain_server 587 TTL c 2714897186 RFC 86400 -1 -1 1421244637 0 1421244631 375007920 86400 587 VCL_call c fetch 587 TTL c 2714897186 VCL 86406 300 -1 1421244632 -6 587 VCL_return c deliver 587 ObjProtocol c HTTP/1.1 587 ObjResponse c OK 587 ObjHeader c Date: Wed, 14 Jan 2015 14:10:31 GMT 587 ObjHeader c Server: Apache 587 ObjHeader c P3p: CP="CAO PSA OUR" 587 ObjHeader c X-Cache-Debug: 1 587 ObjHeader c X-Cache-Tags: catalog_product_327804 587 ObjHeader c Vary: Accept-Encoding 587 ObjHeader c Content-Encoding: gzip 587 ObjHeader c Content-Type: text/html; charset=UTF-8 587 ObjHeader c X-Purge-URL: /en-gb/printed-denim-skirt-with-leather- trim.html?foo 587 ObjHeader c X-Purge-Host: www.domain.tld 587 ObjHeader c X-Orig-Query-String: /en-gb/printed-denim-skirt-with- leather-trim.html?foo 587 ObjHeader c X-Striped-Query-String: /en-gb/printed-denim-skirt- with-leather-trim.html?foo 587 ObjHeader c Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 587 ObjHeader c Pragma: no-cache 587 ObjHeader c Expires: Mon, 31 Mar 2008 10:00:00 GMT 587 Gzip c U F E 34291 176585 80 214240 274260 587 Gzip c G F E 176585 34257 80 273976 273986 587 VCL_call c deliver deliver 587 TxProtocol c HTTP/1.1 587 TxStatus c 200 587 TxResponse c OK 587 TxHeader c Server: Apache 587 TxHeader c P3p: CP="CAO PSA OUR" 587 TxHeader c X-Cache-Debug: 1 587 TxHeader c X-Cache-Tags: catalog_product_327804 587 TxHeader c Vary: Accept-Encoding 587 TxHeader c Content-Type: text/html; charset=UTF-8 587 TxHeader c X-Purge-URL: /en-gb/printed-denim-skirt-with-leather- trim.html?foo 587 TxHeader c X-Purge-Host: www.domain.tld 587 TxHeader c X-Orig-Query-String: /en-gb/printed-denim-skirt-with- leather-trim.html?foo 587 TxHeader c X-Striped-Query-String: /en-gb/printed-denim-skirt- with-leather-trim.html?foo 587 TxHeader c Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 587 TxHeader c Pragma: no-cache 587 TxHeader c Expires: Mon, 31 Mar 2008 10:00:00 GMT 587 TxHeader c Date: Wed, 14 Jan 2015 14:10:37 GMT 587 TxHeader c X-Varnish: 2714897186 587 TxHeader c Age: 0 587 TxHeader c Via: 1.1 varnish 587 TxHeader c Connection: keep-alive 587 TxHeader c X-Cache: MISS 587 TxHeader c X-BE: dir_domain_tld_random 587 TxHeader c X-BE-Name: be_domain_server 587 TxHeader c X-Lifetime: 587 Length c 0 587 ReqEnd c 2714897186 1421244631.851499319 1421244637.513417721 0.000064611 5.661878824 0.000039577 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 14 15:21:07 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 14 Jan 2015 15:21:07 -0000 Subject: [Varnish] #1628: Assert error in VBO_DerefBusyObj() In-Reply-To: <041.d988225a70fb3421845c28c4830e2c87@varnish-cache.org> References: <041.d988225a70fb3421845c28c4830e2c87@varnish-cache.org> Message-ID: <056.2ee7c63fdc52b92fe90eacfa52a8b2aa@varnish-cache.org> #1628: Assert error in VBO_DerefBusyObj() ----------------------+----------------------------------------------- Reporter: Jay | Owner: Martin Blix Grydeland Type: defect | Status: reopened Priority: normal | Milestone: Later Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------- Comment (by martin): That last assertion error reported by chrisj should is related to #1648, and should be fixed by dba9daad80db5cfefa43890fc463fbd42f4ee825 Martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 14 15:29:12 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 14 Jan 2015 15:29:12 -0000 Subject: [Varnish] #1628: Assert error in VBO_DerefBusyObj() In-Reply-To: <041.d988225a70fb3421845c28c4830e2c87@varnish-cache.org> References: <041.d988225a70fb3421845c28c4830e2c87@varnish-cache.org> Message-ID: <056.315909a514e4a706ed87907c413b0a8d@varnish-cache.org> #1628: Assert error in VBO_DerefBusyObj() ----------------------+----------------------------------------------- Reporter: Jay | Owner: Martin Blix Grydeland Type: defect | Status: closed Priority: normal | Milestone: Later Component: varnishd | Version: trunk Severity: normal | Resolution: worksforme Keywords: | ----------------------+----------------------------------------------- Changes (by martin): * status: reopened => closed * resolution: => worksforme Comment: Please check the latest trunk revision and see if you can still reproduce this error. Martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 14 15:59:15 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 14 Jan 2015 15:59:15 -0000 Subject: [Varnish] #1650: xff handling discards multiple headers In-Reply-To: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> References: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> Message-ID: <065.075b34a0c385d26fd0c3ffc63dfb282a@varnish-cache.org> #1650: xff handling discards multiple headers --------------------------+--------------------------------------------- Reporter: KlavsKlavsen | Owner: Federico G. Schwindt Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: 4.0.2 Severity: normal | Resolution: fixed Keywords: | --------------------------+--------------------------------------------- Comment (by KlavsKlavsen): I tried building v4.0.2 with this patch added - but 1 test fails.. output from rpmbuild -bb varnish.spec (modd'ed to apply the patch).. I reworked the patch to fit v4.0.2: --- a/bin/varnishd/cache/cache_req_fsm.c 2014-10-08 09:48:41.000000000 +0200 +++ b/bin/varnishd/cache/cache_req_fsm.c 2015-01-14 16:51:03.984994158 +0100 @@ -723,6 +723,7 @@ * This really should be done earlier, but we want to capture * it in the VSL log. */ + http_CollectHdr(req->http, H_X_Forwarded_For); if (http_GetHdr(req->http, H_X_Forwarded_For, &xff)) { http_Unset(req->http, H_X_Forwarded_For); http_PrintfHeader(req->http, "X-Forwarded-For: %s, %s", -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 14:09:45 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 14:09:45 -0000 Subject: [Varnish] #1650: xff handling discards multiple headers In-Reply-To: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> References: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> Message-ID: <065.2d425dff3bc93d7516a966c31995681e@varnish-cache.org> #1650: xff handling discards multiple headers --------------------------+--------------------------------------------- Reporter: KlavsKlavsen | Owner: Federico G. Schwindt Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: 4.0.2 Severity: normal | Resolution: fixed Keywords: | --------------------------+--------------------------------------------- Comment (by KlavsKlavsen): if I compile without this patch - all tests pass. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 14:16:54 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 14:16:54 -0000 Subject: [Varnish] #1650: xff handling discards multiple headers In-Reply-To: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> References: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> Message-ID: <065.1307116dfce00e93aba892be19f810d0@varnish-cache.org> #1650: xff handling discards multiple headers --------------------------+--------------------------------------------- Reporter: KlavsKlavsen | Owner: Federico G. Schwindt Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: 4.0.2 Severity: normal | Resolution: fixed Keywords: | --------------------------+--------------------------------------------- Comment (by fgsch): I don't understand what the problem. What is it failing? Please note the patch is for master. It will apply to 4.0.2 with some changes. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 14:27:52 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 14:27:52 -0000 Subject: [Varnish] #1650: xff handling discards multiple headers In-Reply-To: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> References: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> Message-ID: <065.e16ede3a10086a2e3052ece5953cebac@varnish-cache.org> #1650: xff handling discards multiple headers --------------------------+--------------------------------------------- Reporter: KlavsKlavsen | Owner: Federico G. Schwindt Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------------+--------------------------------------------- Changes (by fgsch): * version: 4.0.2 => trunk -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 14:37:42 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 14:37:42 -0000 Subject: [Varnish] #1650: xff handling discards multiple headers In-Reply-To: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> References: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> Message-ID: <065.fe83476a89e8e92387f0a64a37c53e45@varnish-cache.org> #1650: xff handling discards multiple headers --------------------------+--------------------------------------------- Reporter: KlavsKlavsen | Owner: Federico G. Schwindt Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------------+--------------------------------------------- Comment (by fgsch): From IRC: {{{ 14:34 < FiXion> fgs: arghh.. typicly it failed the first time.. when I then ran it with 2>&1 >output.. it didn't fail.. 14:34 < FiXion> and doesn't fail now 14:34 < FiXion> just ignore me.. :( 14:34 < FiXion> now I can test atleast :) }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 15:35:45 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 15:35:45 -0000 Subject: [Varnish] #1610: Varnish 4.0 troubleshooting guide's varnishlog example is out of date In-Reply-To: <045.d2e4c622b3a4d0b67ccf4dc8df052246@varnish-cache.org> References: <045.d2e4c622b3a4d0b67ccf4dc8df052246@varnish-cache.org> Message-ID: <060.0effe878ab69a4ca2ac9d61aca526f1c@varnish-cache.org> #1610: Varnish 4.0 troubleshooting guide's varnishlog example is out of date ------------------------------+---------------------------------- Reporter: gtaylor | Owner: daghf Type: defect | Status: closed Priority: normal | Milestone: Varnish 4.0 release Component: documentation | Version: trunk Severity: normal | Resolution: fixed Keywords: varnishlog guide | ------------------------------+---------------------------------- Comment (by Lasse Karstensen ): In [a87c23f3bd71a71c8542ca38bec95e8db02769d8]: {{{ #!CommitTicketReference repository="" revision="a87c23f3bd71a71c8542ca38bec95e8db02769d8" Update forgotten varnishlog example to 4.0 syntax. Fixes: #1610 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 15:35:45 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 15:35:45 -0000 Subject: [Varnish] #1623: varnishhist -d segfault In-Reply-To: <046.76e8f76d5dcfa6795373e0508a173d93@varnish-cache.org> References: <046.76e8f76d5dcfa6795373e0508a173d93@varnish-cache.org> Message-ID: <061.3f1e1ea39c5c836c5a835e2676c53b7e@varnish-cache.org> #1623: varnishhist -d segfault ----------------------+----------------------------------------------- Reporter: lkarsten | Owner: Martin Blix Grydeland Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: 4.0.2 Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------- Comment (by Lasse Karstensen ): In [0672a5e56bffc2b22fc5e4c1e4bdc1f14a249718]: {{{ #!CommitTicketReference repository="" revision="0672a5e56bffc2b22fc5e4c1e4bdc1f14a249718" Use n + hist_buckets as hit flag in varnishhist bucket history Because -0 == +0, the use of negative numbers as a distinction between hits and misses in the recorded bucket history fails when there are entries of index 0. Fixes: #1623 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 15:35:46 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 15:35:46 -0000 Subject: [Varnish] #1378: varnishncsa does not escape log items In-Reply-To: <046.c965e13022034e658e261f1b7ddb7f49@varnish-cache.org> References: <046.c965e13022034e658e261f1b7ddb7f49@varnish-cache.org> Message-ID: <061.6428ed3e1bccb318886ec215b5896df6@varnish-cache.org> #1378: varnishncsa does not escape log items -------------------------+--------------------- Reporter: simonvik | Owner: aondio Type: defect | Status: closed Priority: low | Milestone: Component: varnishncsa | Version: 3.0.4 Severity: minor | Resolution: fixed Keywords: | -------------------------+--------------------- Comment (by Lasse Karstensen ): In [3fbeda80f5349c2b502f3ab9a28a4ec8d3f31c1f]: {{{ #!CommitTicketReference repository="" revision="3fbeda80f5349c2b502f3ab9a28a4ec8d3f31c1f" Varnishncsa escapes non-printable chars. Fixes: #1378 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 15:35:45 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 15:35:45 -0000 Subject: [Varnish] #1636: Outdated paragraph in Vary: documentation for Varnish 4.0 In-Reply-To: <043.4d744112853e344703907f1c44f6decf@varnish-cache.org> References: <043.4d744112853e344703907f1c44f6decf@varnish-cache.org> Message-ID: <058.184839c6cad1412e76834df9b436fc5a@varnish-cache.org> #1636: Outdated paragraph in Vary: documentation for Varnish 4.0 -----------------------------+--------------------------------------------- Reporter: mabes | Owner: Federico G. Schwindt Type: documentation | Status: closed Priority: lowest | Milestone: Component: build | Version: trunk Severity: trivial | Resolution: fixed Keywords: vary | documentation | -----------------------------+--------------------------------------------- Comment (by Lasse Karstensen ): In [304f203b316ef2fa7a71bb6e37b93ca72ec7e276]: {{{ #!CommitTicketReference repository="" revision="304f203b316ef2fa7a71bb6e37b93ca72ec7e276" Rework example Fixes #1636 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 15:35:45 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 15:35:45 -0000 Subject: [Varnish] #1349: No exact match on varnishadm backend.set_health In-Reply-To: <046.8a05e196ff21820ddf1411b60bf8db31@varnish-cache.org> References: <046.8a05e196ff21820ddf1411b60bf8db31@varnish-cache.org> Message-ID: <061.de792d6fdd4c0dda560d899a75ed1d3c@varnish-cache.org> #1349: No exact match on varnishadm backend.set_health --------------------------------------------+--------------------- Reporter: tmagnien | Owner: daghf Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: exact match backend.set_health | --------------------------------------------+--------------------- Comment (by Lasse Karstensen ): In [8c7e93833db8aa898db74878bb076c1ca093bf33]: {{{ #!CommitTicketReference repository="" revision="8c7e93833db8aa898db74878bb076c1ca093bf33" Prefer exact matches in varnishadm backend.set_health. Fixes: #1349 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 15:35:45 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 15:35:45 -0000 Subject: [Varnish] #1557: regsuball() doesn't honor lookahead assertion on repeated strings In-Reply-To: <059.714287d6d2b95c176d62f92faff8648e@varnish-cache.org> References: <059.714287d6d2b95c176d62f92faff8648e@varnish-cache.org> Message-ID: <074.846e78d3626f4acac49a60dbed51c98e@varnish-cache.org> #1557: regsuball() doesn't honor lookahead assertion on repeated strings --------------------------------------+--------------------- Reporter: varnish@? | Owner: martin Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: lookahead pcre regsuball | --------------------------------------+--------------------- Comment (by Lasse Karstensen ): In [efdd025439d5914fb256ae2b2576a36c0be424a7]: {{{ #!CommitTicketReference repository="" revision="efdd025439d5914fb256ae2b2576a36c0be424a7" Fix lookbehind handling in regsuball Do not advance the subject but use the ovector information as offset, pcre might need to peek back when handling lookbehinds. Original patch from MegaMaddin via github. Fixes: #1557 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 15:35:46 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 15:35:46 -0000 Subject: [Varnish] #1648: Corrupt object in cache through IMS update on an object that fails during body fetch In-Reply-To: <044.996b72ce6ad80b6ca93dd0c20722dc84@varnish-cache.org> References: <044.996b72ce6ad80b6ca93dd0c20722dc84@varnish-cache.org> Message-ID: <059.26fe46236ac07871305d9a0cfba69d4d@varnish-cache.org> #1648: Corrupt object in cache through IMS update on an object that fails during body fetch --------------------+----------------------------------------------- Reporter: martin | Owner: Martin Blix Grydeland Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: unknown Severity: normal | Resolution: fixed Keywords: | --------------------+----------------------------------------------- Comment (by Lasse Karstensen ): In [2b931fed8ade30933485833a6a9fd0e3cd1d1db1]: {{{ #!CommitTicketReference repository="" revision="2b931fed8ade30933485833a6a9fd0e3cd1d1db1" Handle template object failures during condfetch Fixes: #1648 Conflicts: bin/varnishd/cache/cache_fetch.c }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 15:35:46 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 15:35:46 -0000 Subject: [Varnish] #1647: Varnish 4 crashes occasionally under stress test: Assert error in cnt_lookup() In-Reply-To: <041.e9d6d4012b20edd5534d3b4f45c91794@varnish-cache.org> References: <041.e9d6d4012b20edd5534d3b4f45c91794@varnish-cache.org> Message-ID: <056.7d032dae698429031a350401cc41b583@varnish-cache.org> #1647: Varnish 4 crashes occasionally under stress test: Assert error in cnt_lookup() ----------------------+----------------------------------------------- Reporter: wjy | Owner: Martin Blix Grydeland Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 4.0.2 Severity: major | Resolution: fixed Keywords: | ----------------------+----------------------------------------------- Comment (by Lasse Karstensen ): In [d381e2458f39989df202be7c5719e1f60b20fb19]: {{{ #!CommitTicketReference repository="" revision="d381e2458f39989df202be7c5719e1f60b20fb19" Relax an assertion for the IMS update candidate object The streaming fetch of an object can fail between lookup time and when we actually use it. Relax this assertion. Fixes: #1647 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 15:35:45 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 15:35:45 -0000 Subject: [Varnish] #1639: sigsegv_handler can hide panic In-Reply-To: <043.974becac8432bbf63f8ef8d19918851a@varnish-cache.org> References: <043.974becac8432bbf63f8ef8d19918851a@varnish-cache.org> Message-ID: <058.efb762a85f9b30ccaf4980ddc43ecca0@varnish-cache.org> #1639: sigsegv_handler can hide panic ----------------------+------------------------------------------ Reporter: slink | Owner: Nils Goroll Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+------------------------------------------ Comment (by Lasse Karstensen ): In [db1185dc3ee1adee6deb0b2b65bdb9b615395504]: {{{ #!CommitTicketReference repository="" revision="db1185dc3ee1adee6deb0b2b65bdb9b615395504" Restore the default SIGSEGV handler during pan_ic Leaving it enabled could hide panics. Fixes #1639 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 15:35:46 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 15:35:46 -0000 Subject: [Varnish] #1646: Assert error in VFP_GetStorage(), cache/cache_fetch_proc.c line 84 In-Reply-To: <046.faacb661f65c2a9d5c752e6df2f5668e@varnish-cache.org> References: <046.faacb661f65c2a9d5c752e6df2f5668e@varnish-cache.org> Message-ID: <061.d245c800df7524b260afa9524c64c3b4@varnish-cache.org> #1646: Assert error in VFP_GetStorage(), cache/cache_fetch_proc.c line 84 ----------------------+---------------------------------------- Reporter: lkarsten | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+---------------------------------------- Comment (by Lasse Karstensen ): In [97da7f346db387033fbda38c5a827af91ddb95cf]: {{{ #!CommitTicketReference repository="" revision="97da7f346db387033fbda38c5a827af91ddb95cf" Continuously update our total object size estimate when cond-fetching a still-being-streamed object. Fixes: #1646 Keeping only the test case as the issue isn't in 4.0. Conflicts: bin/varnishd/cache/cache_fetch.c }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 15:35:46 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 15:35:46 -0000 Subject: [Varnish] #1641: Assert error in vbf_stp_startfetch() In-Reply-To: <045.6003a667979ac910bd18c9af0365c470@varnish-cache.org> References: <045.6003a667979ac910bd18c9af0365c470@varnish-cache.org> Message-ID: <060.77172f80678c40a26099937e1ea81038@varnish-cache.org> #1641: Assert error in vbf_stp_startfetch() --------------------------+---------------------------------------- Reporter: llavaud | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: major | Resolution: fixed Keywords: assert error | --------------------------+---------------------------------------- Comment (by Lasse Karstensen ): In [fc3d123ce7ed2a691c4ea2a461830f749f57f85c]: {{{ #!CommitTicketReference repository="" revision="fc3d123ce7ed2a691c4ea2a461830f749f57f85c" Nils patch for retrying partial fetches, with minor changes by me. Fixes #1638 Fixes #1641 Ported to 4.0 by Martin Conflicts: bin/varnishd/cache/cache_fetch.c }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 15:35:46 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 15:35:46 -0000 Subject: [Varnish] #1638: 82b29b1 retry of short server read : Assert error in vbf_stp_startfetch() : Condition(bo->doclose == SC_NULL) not true. In-Reply-To: <043.531de57203cb30d1d236fb877abf9455@varnish-cache.org> References: <043.531de57203cb30d1d236fb877abf9455@varnish-cache.org> Message-ID: <058.b8a3e39583c772c357d4144154e669e3@varnish-cache.org> #1638: 82b29b1 retry of short server read : Assert error in vbf_stp_startfetch() : Condition(bo->doclose == SC_NULL) not true. ----------------------+--------------------- Reporter: slink | Owner: slink Type: defect | Status: closed Priority: normal | Milestone: Later Component: varnishd | Version: trunk Severity: major | Resolution: fixed Keywords: | ----------------------+--------------------- Comment (by Lasse Karstensen ): In [fc3d123ce7ed2a691c4ea2a461830f749f57f85c]: {{{ #!CommitTicketReference repository="" revision="fc3d123ce7ed2a691c4ea2a461830f749f57f85c" Nils patch for retrying partial fetches, with minor changes by me. Fixes #1638 Fixes #1641 Ported to 4.0 by Martin Conflicts: bin/varnishd/cache/cache_fetch.c }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 15:35:46 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 15:35:46 -0000 Subject: [Varnish] #1650: xff handling discards multiple headers In-Reply-To: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> References: <050.2763cd420782dfaf2b4b47bc82076d98@varnish-cache.org> Message-ID: <065.bc64eb90877c78b3051d0476489ad483@varnish-cache.org> #1650: xff handling discards multiple headers --------------------------+--------------------------------------------- Reporter: KlavsKlavsen | Owner: Federico G. Schwindt Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------------+--------------------------------------------- Comment (by Lasse Karstensen ): In [3e8874ed945de580a92819b01c457b2734c6888b]: {{{ #!CommitTicketReference repository="" revision="3e8874ed945de580a92819b01c457b2734c6888b" Collapse multiple X-Forwarded-For headers Fixes #1650 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 15:35:45 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 15:35:45 -0000 Subject: [Varnish] #1607: Assert error in SES_ScheduleReq(), cache/cache_session.c line 229 In-Reply-To: <046.9e6bd8d750958a8524136f038db2e568@varnish-cache.org> References: <046.9e6bd8d750958a8524136f038db2e568@varnish-cache.org> Message-ID: <061.35dc29e593b5e1ab5b2f85b129f335d3@varnish-cache.org> #1607: Assert error in SES_ScheduleReq(), cache/cache_session.c line 229 ----------------------+--------------------- Reporter: coredump | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 4.0.2 Severity: normal | Resolution: fixed Keywords: | ----------------------+--------------------- Comment (by Lasse Karstensen ): In [795bc31f168ae64a30d1e61d01bd4e69f0016092]: {{{ #!CommitTicketReference repository="" revision="795bc31f168ae64a30d1e61d01bd4e69f0016092" Fix the leaking req on failure to put a waiting-list session back in play in a way that does not lead to panics. Spotted by: Martin Fixes #1607 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 15 15:35:45 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 15 Jan 2015 15:35:45 -0000 Subject: [Varnish] #1343: Storage file handling is confused if file exists In-Reply-To: <046.7e806953bab79cec3b63fad3eb7638f4@varnish-cache.org> References: <046.7e806953bab79cec3b63fad3eb7638f4@varnish-cache.org> Message-ID: <061.926e065e479648585efa9b28336da6f5@varnish-cache.org> #1343: Storage file handling is confused if file exists ----------------------+----------------------------------------------- Reporter: lkarsten | Owner: Martin Blix Grydeland Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: minor | Resolution: fixed Keywords: | ----------------------+----------------------------------------------- Comment (by Lasse Karstensen ): In [a710884ba3076c45be2f092983a19176dde908a8]: {{{ #!CommitTicketReference repository="" revision="a710884ba3076c45be2f092983a19176dde908a8" Remove the 80% file system free space check This check never worked as intended for several reasons: - Didn't take the existing file size into account, causing it to succeed on first startup but fail on next - Sparse files were not handled, and can't be handled as we don't know where in the file a hole could be and whether truncation actually would change the number of blocks used at all Fixes: #1343 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sat Jan 17 14:04:43 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sat, 17 Jan 2015 14:04:43 -0000 Subject: [Varnish] #1576: default pcre_match_limit_recursion and thread_pool_stack dont match - varnishd child process crashes with segfault error 6 in libpcre.so.3.13.1 In-Reply-To: <042.4a3d8a5cb69dc6179ad46be4f593a479@varnish-cache.org> References: <042.4a3d8a5cb69dc6179ad46be4f593a479@varnish-cache.org> Message-ID: <057.9bc0e29cc46a06e3c66c8213a1bbc16b@varnish-cache.org> #1576: default pcre_match_limit_recursion and thread_pool_stack dont match - varnishd child process crashes with segfault error 6 in libpcre.so.3.13.1 ----------------------+-------------------- Reporter: abdi | Owner: slink Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 4.0.1 Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Comment (by quintonparker): Hi I believe I'm experiencing the same issue in varnish 4.0.2 on ubuntu precise lts server Linux app1.spreeza.net 3.11.0-26-generic #45~precise1-Ubuntu SMP Tue Jul 15 04:02:35 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux This is my syslog snippet Jan 16 07:48:11 app1 kernel: [11057670.418598] varnishd[11360]: segfault at 7f14469bcec0 ip 00007f1445e03a7a sp 00007f14469bce50 error 6 in libpcre.so.3.12.1[7f1445df1000+3c000] Jan 16 07:48:13 app1 varnishd[47915]: Child (11325) died signal=11 (core dumped) Jan 16 07:48:13 app1 varnishd[47915]: Child cleanup complete Jan 16 07:48:13 app1 varnishd[47915]: child (12116) Started Jan 16 07:48:13 app1 varnishd[47915]: Child (12116) said Child starts Worth noting that I'm also using devicedetect.vcl Increasing thread_pool_stack from 48k to 64k seems to have alleviated the problem. Child processes were crashing on an hourly basis but I can now report 15 hours of uptime. Not sure if that solved the issue for good :/ -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 19 10:52:42 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 19 Jan 2015 10:52:42 -0000 Subject: [Varnish] #1629: Assert error in SES_ReleaseReq(), ../../include/tbl/acct_fields_req.h line 33 In-Reply-To: <046.1f51127ba4909c87efc53a43f32f4411@varnish-cache.org> References: <046.1f51127ba4909c87efc53a43f32f4411@varnish-cache.org> Message-ID: <061.5299f33dda70bc0a35d6f4183aed5adc@varnish-cache.org> #1629: Assert error in SES_ReleaseReq(), ../../include/tbl/acct_fields_req.h line 33 ----------------------+--------------------- Reporter: xieyugui | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: Severity: normal | Resolution: fixed Keywords: | ----------------------+--------------------- Changes (by daghf): * status: new => closed * resolution: => fixed Comment: Fixed in 795bc31f168ae64a30d1e61d01bd4e -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 19 12:13:53 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 19 Jan 2015 12:13:53 -0000 Subject: [Varnish] #1629: Assert error in SES_ReleaseReq(), ../../include/tbl/acct_fields_req.h line 33 In-Reply-To: <046.1f51127ba4909c87efc53a43f32f4411@varnish-cache.org> References: <046.1f51127ba4909c87efc53a43f32f4411@varnish-cache.org> Message-ID: <061.5e58e4ae9d12a8d038b83c713ebf6e2a@varnish-cache.org> #1629: Assert error in SES_ReleaseReq(), ../../include/tbl/acct_fields_req.h line 33 ----------------------+----------------------- Reporter: xieyugui | Owner: Type: defect | Status: reopened Priority: normal | Milestone: Component: varnishd | Version: Severity: normal | Resolution: Keywords: | ----------------------+----------------------- Changes (by daghf): * status: closed => reopened * resolution: fixed => Comment: It seems I overlooked that 9fbcb4 is still not in 4.0. Reopened until that's in place. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 19 14:10:21 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 19 Jan 2015 14:10:21 -0000 Subject: [Varnish] #1658: Hash and Random director is deflected at the health-check failover In-Reply-To: <042.711b6c5aa82af63b78fa7c6c84b3ae5f@varnish-cache.org> References: <042.711b6c5aa82af63b78fa7c6c84b3ae5f@varnish-cache.org> Message-ID: <057.74e2c765a7452669f66fe8ca823824bc@varnish-cache.org> #1658: Hash and Random director is deflected at the health-check failover --------------------+----------------------------------------------- Reporter: xcir | Owner: Martin Blix Grydeland Type: defect | Status: closed Priority: normal | Milestone: Component: vmod | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+----------------------------------------------- Changes (by martin): * status: reopened => closed * resolution: => fixed Comment: The hash director in Varnish doesn't have consistent hashing support. If that is needed you should have a look at Uplex' vlsp director vmod: https://www.varnish-cache.org/vmod/vlsp-consistent-hashing-director-vmod Martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 19 15:21:21 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 19 Jan 2015 15:21:21 -0000 Subject: [Varnish] #1629: Assert error in SES_ReleaseReq(), ../../include/tbl/acct_fields_req.h line 33 In-Reply-To: <046.1f51127ba4909c87efc53a43f32f4411@varnish-cache.org> References: <046.1f51127ba4909c87efc53a43f32f4411@varnish-cache.org> Message-ID: <061.0f43888b2f0de600bff0a16e56886405@varnish-cache.org> #1629: Assert error in SES_ReleaseReq(), ../../include/tbl/acct_fields_req.h line 33 ----------------------+-------------------------------------------- Reporter: xieyugui | Owner: Lasse Karstensen Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: Severity: normal | Resolution: fixed Keywords: | ----------------------+-------------------------------------------- Changes (by Lasse Karstensen ): * owner: => Lasse Karstensen * status: reopened => closed * resolution: => fixed Comment: In [29e4a01c5243c5fac87556a5828971685050254b]: {{{ #!CommitTicketReference repository="" revision="29e4a01c5243c5fac87556a5828971685050254b" If we fail to reschedule from the waiting list, we ditch the entire waiting list in an attempt to recover. This also fixes buglet in previous commit which failed to call CNT_AcctLogCharge() Fixes: #1629 (cherry picked from commit 9fbcb4e94942a1bc7ff540f0a475b057a616b1ae) }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 19 15:21:21 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 19 Jan 2015 15:21:21 -0000 Subject: [Varnish] #1621: Synth code path fails when no backend threads are available In-Reply-To: <044.d6b22920154b20eb08a93044b39fd41e@varnish-cache.org> References: <044.d6b22920154b20eb08a93044b39fd41e@varnish-cache.org> Message-ID: <059.2c3d1eb3a981c36e030139fc127aa327@varnish-cache.org> #1621: Synth code path fails when no backend threads are available ----------------------+---------------------------------------- Reporter: martin | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: unknown Severity: normal | Resolution: fixed Keywords: | ----------------------+---------------------------------------- Comment (by Lasse Karstensen ): In [51cee0bff0072ef2d2b39be77b92f475694540d4]: {{{ #!CommitTicketReference repository="" revision="51cee0bff0072ef2d2b39be77b92f475694540d4" Don't attempt to run the fetch in the request thread if there are no threads available in the pool, fail the fetch and count it. Fixes #1620 Fixes #1621 (cherry picked from commit 969674dcb3b4d430a38b7f1b1e41199b25cc8491) }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 19 15:21:21 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 19 Jan 2015 15:21:21 -0000 Subject: [Varnish] #1620: ESI asserts when no threads are available In-Reply-To: <044.835601ea2e67939602ff155a91200ecb@varnish-cache.org> References: <044.835601ea2e67939602ff155a91200ecb@varnish-cache.org> Message-ID: <059.0367ef4cb5000dbea60882f860c0ac83@varnish-cache.org> #1620: ESI asserts when no threads are available --------------------+---------------------------------------- Reporter: martin | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: unknown Severity: normal | Resolution: fixed Keywords: | --------------------+---------------------------------------- Comment (by Lasse Karstensen ): In [51cee0bff0072ef2d2b39be77b92f475694540d4]: {{{ #!CommitTicketReference repository="" revision="51cee0bff0072ef2d2b39be77b92f475694540d4" Don't attempt to run the fetch in the request thread if there are no threads available in the pool, fail the fetch and count it. Fixes #1620 Fixes #1621 (cherry picked from commit 969674dcb3b4d430a38b7f1b1e41199b25cc8491) }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 19 15:38:37 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 19 Jan 2015 15:38:37 -0000 Subject: [Varnish] #1628: Assert error in VBO_DerefBusyObj() In-Reply-To: <041.d988225a70fb3421845c28c4830e2c87@varnish-cache.org> References: <041.d988225a70fb3421845c28c4830e2c87@varnish-cache.org> Message-ID: <056.e3079246207e7fd34c8fcdf6e85906b1@varnish-cache.org> #1628: Assert error in VBO_DerefBusyObj() ----------------------+----------------------------------------------- Reporter: Jay | Owner: Martin Blix Grydeland Type: defect | Status: closed Priority: normal | Milestone: Later Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------- Changes (by Lasse Karstensen ): * resolution: worksforme => fixed Comment: In [653a9ea1af81fdcdf16c34f7d910da6a77400132]: {{{ #!CommitTicketReference repository="" revision="653a9ea1af81fdcdf16c34f7d910da6a77400132" Keep the fetch thread busyobj pointer-ref separate from the client thread pointer-ref, and deref it on thread scheduling failure. The code tried to deref the same pointer twice, which failed because the VBO_DerefBusyobj() will clear the pointer when called. Separating allows calling VBO_DerefBusyobj() for each of them. Fixes: #1628 (cherry picked from commit 7746e30e2c53cf55f0f2525bb3f49c9ee83e9611) Conflicts: bin/varnishd/cache/cache_fetch.c }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 20 13:10:35 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 20 Jan 2015 13:10:35 -0000 Subject: [Varnish] #1660: range and synth doesn't mix causing assert Message-ID: <044.e8ae6b06f4f85bde7e0b44196c987687@varnish-cache.org> #1660: range and synth doesn't mix causing assert ----------------------+------------------- Reporter: martin | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 4.0.2 Severity: normal | Keywords: ----------------------+------------------- If a range delivery is attempted on a synth response, it will cause assertion. {{{ *** v1 1.4 debug| Assert error in v1d_dorange(), cache/cache_http1_deliver.c line 95:\n *** v1 1.4 debug| Condition((req->obj) != NULL) not true.\n *** v1 1.4 debug| thread = (cache-worker)\n *** v1 1.4 debug| version = varnish-4.0.3-rc1 revision 653a9ea\n *** v1 1.4 debug| ident = Linux,3.16.0-4-amd64,x86_64,-smalloc,-smalloc,-hcritbit,epoll\n *** v1 1.4 debug| Backtrace:\n *** v1 1.4 debug| 0x451049: pan_backtrace+0x19\n *** v1 1.4 debug| 0x450f40: pan_ic+0x330\n *** v1 1.4 debug| 0x45e0a3: v1d_dorange+0x133\n *** v1 1.4 debug| 0x45f154: V1D_Deliver_Synth+0x474\n *** v1 1.4 debug| 0x45ca44: cnt_synth+0x5d4\n *** v1 1.4 debug| 0x45793f: CNT_Request+0x79f\n *** v1 1.4 debug| 0x445494: HTTP1_Session+0x604\n *** v1 1.4 debug| 0x46179e: ses_req_pool_task+0x22e\n *** v1 1.4 debug| 0x461255: ses_sess_pool_task+0x285\n *** v1 1.4 debug| 0x46078f: SES_pool_accept_task+0x2bf\n *** v1 1.4 debug| req = 0x7f79a0819020 {\n *** v1 1.4 debug| sp = 0x7f79a080e1e0, vxid = 1073742825, step = R_STP_SYNTH,\n *** v1 1.4 debug| req_body = R_BODY_NONE,\n *** v1 1.4 debug| err_code = 200, err_reason = asdf,\n *** v1 1.4 debug| restarts = 0, esi_level = 0,\n *** v1 1.4 debug| sp = 0x7f79a080e1e0 {\n *** v1 1.4 debug| fd = 11, vxid = 1000,\n *** v1 1.4 debug| client = 127.0.0.1 46065,\n *** v1 1.4 debug| step = S_STP_WORKING,\n *** v1 1.4 debug| },\n *** v1 1.4 debug| worker = 0x7f79adfbbc78 {\n *** v1 1.4 debug| ws = 0x7f79adfbbe98 {\n *** v1 1.4 debug| id = "wrk",\n *** v1 1.4 debug| {s,f,r,e} = {0x7f79adfbb440,0x7f79adfbb440,(nil),+2048},\n *** v1 1.4 debug| },\n *** v1 1.4 debug| VCL::method = 0x0,\n *** v1 1.4 debug| VCL::return = deliver,\n *** v1 1.4 debug| },\n *** v1 1.4 debug| ws = 0x7f79a08191b8 {\n *** v1 1.4 debug| id = "req",\n *** v1 1.4 debug| {s,f,r,e} = {0x7f79a081b010,+248,(nil),+57360},\n *** v1 1.4 debug| },\n *** v1 1.4 debug| http[req] = {\n *** v1 1.4 debug| ws = 0x7f79a08191b8[req]\n *** v1 1.4 debug| "GET",\n *** v1 1.4 debug| "/",\n *** v1 1.4 debug| "HTTP/1.1",\n *** v1 1.4 debug| "Range: 0-1",\n *** v1 1.4 debug| "X-Forwarded-For: 127.0.0.1",\n *** v1 1.4 debug| },\n *** v1 1.4 debug| http[resp] = {\n *** v1 1.4 debug| ws = 0x7f79a08191b8[req]\n *** v1 1.4 debug| "HTTP/1.1",\n *** v1 1.4 debug| "200",\n *** v1 1.4 debug| "asdf",\n *** v1 1.4 debug| "Date: Tue, 20 Jan 2015 13:08:48 GMT",\n *** v1 1.4 debug| "Server: Varnish",\n *** v1 1.4 debug| "X-Varnish: 1001",\n *** v1 1.4 debug| "Content-Type: text/html; charset=utf-8",\n *** v1 1.4 debug| "Retry-After: 5",\n *** v1 1.4 debug| "Content-Length: 233",\n *** v1 1.4 debug| "Connection: keep-alive",\n *** v1 1.4 debug| "Accept-Ranges: bytes",\n *** v1 1.4 debug| },\n *** v1 1.4 debug| vcl = {\n *** v1 1.4 debug| srcname = {\n *** v1 1.4 debug| "input",\n *** v1 1.4 debug| "Builtin",\n *** v1 1.4 debug| },\n *** v1 1.4 debug| },\n *** v1 1.4 debug| },\n *** v1 1.4 debug| \n *** v1 1.4 debug| \n }}} This will happen only for a synth of status 200, as rangeisn't attempted for other status codes. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 20 13:38:45 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 20 Jan 2015 13:38:45 -0000 Subject: [Varnish] #1660: range and synth doesn't mix causing assert In-Reply-To: <044.e8ae6b06f4f85bde7e0b44196c987687@varnish-cache.org> References: <044.e8ae6b06f4f85bde7e0b44196c987687@varnish-cache.org> Message-ID: <059.6fe4c5776b99978cff286b02adba77b1@varnish-cache.org> #1660: range and synth doesn't mix causing assert ----------------------+----------------------------------------------- Reporter: martin | Owner: Martin Blix Grydeland Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 4.0.2 Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------- Changes (by Martin Blix Grydeland ): * owner: => Martin Blix Grydeland * status: new => closed * resolution: => fixed Comment: In [b661f7e9f2a4aab29d0f16f11a0aa27513afb63c]: {{{ #!CommitTicketReference repository="" revision="b661f7e9f2a4aab29d0f16f11a0aa27513afb63c" Don't attempt range delivery on a synth response This could happen on a 200 synth object if the client request had a Range header. The range code path would fail because it requires an obj which the synth path doesn't have. Fixes: #1660 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 20 18:26:48 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 20 Jan 2015 18:26:48 -0000 Subject: [Varnish] #1629: Assert error in SES_ReleaseReq(), ../../include/tbl/acct_fields_req.h line 33 In-Reply-To: <046.1f51127ba4909c87efc53a43f32f4411@varnish-cache.org> References: <046.1f51127ba4909c87efc53a43f32f4411@varnish-cache.org> Message-ID: <061.e119ffd4f94e3c2de9bafc0a6ccd71c8@varnish-cache.org> #1629: Assert error in SES_ReleaseReq(), ../../include/tbl/acct_fields_req.h line 33 ----------------------+-------------------------------------------- Reporter: xieyugui | Owner: Lasse Karstensen Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: Severity: normal | Resolution: fixed Keywords: | ----------------------+-------------------------------------------- Comment (by mattrobenolt): Just bumping this to note that this still happens in 4.0.3-rc1 so it doesn't get missed for rc2. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 20 18:32:05 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 20 Jan 2015 18:32:05 -0000 Subject: [Varnish] #1661: Assert error in VRY_Validate(), cache/cache_vary.c line 377 Message-ID: <050.a0d7a51674fccc155f59afe0a5199aa8@varnish-cache.org> #1661: Assert error in VRY_Validate(), cache/cache_vary.c line 377 --------------------------+---------------------- Reporter: mattrobenolt | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: unknown | Severity: major Keywords: vary, panic | --------------------------+---------------------- This is in 4.0.3-rc1: {{{ varnish> panic.show 200 Last panic at: Tue, 20 Jan 2015 08:50:18 GMT Assert error in VRY_Validate(), cache/cache_vary.c line 377: Condition(strlen((const char*)vary+3) == vary[2]) not true. thread = (cache-worker) version = varnish-4.0.3-rc1 revision eea73f6 ident = Linux,3.13.0-43-generic,x86_64,-smalloc,-smalloc,-hcritbit,epoll Backtrace: 0x4333fa: /usr/sbin/varnishd() [0x4333fa] 0x43ef5b: /usr/sbin/varnishd() [0x43ef5b] 0x43f24c: /usr/sbin/varnishd(VRY_Finish+0x2c) [0x43f24c] 0x43677f: /usr/sbin/varnishd() [0x43677f] 0x437909: /usr/sbin/varnishd(CNT_Request+0x869) [0x437909] 0x42d3cb: /usr/sbin/varnishd(HTTP1_Session+0x3eb) [0x42d3cb] 0x43b9f8: /usr/sbin/varnishd() [0x43b9f8] 0x43c7a9: /usr/sbin/varnishd(SES_pool_accept_task+0x2a9) [0x43c7a9] 0x4362d3: /usr/sbin/varnishd(Pool_Work_Thread+0x373) [0x4362d3] 0x449478: /usr/sbin/varnishd() [0x449478] req = 0x7f8484162020 { sp = 0x7f84835c83a0, vxid = 1093206021, step = R_STP_LOOKUP, req_body = R_BODY_NONE, restarts = 0, esi_level = 0, sp = 0x7f84835c83a0 { fd = 1780, vxid = 19464196, client = 139.216.143.85 56733, step = S_STP_WORKING, }, worker = 0x7f847dbcec20 { ws = 0x7f847dbcee38 { id = "wrk", {s,f,r,e} = {0x7f847dbce410,0x7f847dbce410,(nil),+2048}, }, VCL::method = 0x0, VCL::return = lookup, }, ws = 0x7f84841621b8 { id = "req", {s,f,r,e} = {0x7f8484164010,+57360,+57360,+57360}, }, http[req] = { ws = 0x7f84841621b8[req] "GET", "/api/3.0/embed/threadDetails.json?thread=3437164122&post=1803766928&post=1803768038&post=1803768451&post=1803769482&post=1803769704&post=1803770164&post=1803770423&post=1803770527&post=1803771199&post=1803771778&post=1803776215&post=1803776846&post=1803772192&post=1803774533&post=1803778326&post=1803780042&post=1803779439&post=1803779000&post=1803779581&post=1803779969&post=1803779385&post=1803780619&post=1803780362&post=1803781117&post=1803780604&post=1803780970&post=1803781938&post=1803783331&post=1803784340&post=1803784695&post=1803784944&post=1803785458&post=1803785913&post=1803787313&post=1803788789&post=1803789169&post=1803789458&post=1803789692&post=1803790232&post=1803790262&post=1803787229&post=1803787445&post=1803792488&post=1803790856&post=1803791050&post=1803792845&post=1803793364&post=1803793960&post=1803794542&post=1803794777&post=1803795279&post=1803798995&post=1803797360&post=1803797904&post=1803798399&post=1803794310&post=1803795071&post=1803796109&post=1803796351&post=1803796886&post=1803797943&post=1803799538&post=1803799765&post=1803799711&post=1803800126&post=1803800771&post=1803800243&post=1803800953&post=1803801055&post=1803801933&post=1803802118&post=1803802488&post=1803803994&post=1803804069&post=1803804190&post=1803804866&post=1803803350&post=1803809275&post=1803802353&post=1803801973&post=1803802675&post=1803803880&post=1803804145&post=1803804720&post=1803805244&post=1803805465&post=1803805734&post=1803805751&post=1803806375&post=1803806393&post=1803806426&post=1803806857&post=1803806938&post=1803807262&post=1803807275&post=1803807972&post=1803808064&post=1803808686&post=1803809180&post=1803809763&post=1803810570&post=1803810684&post=1803811157&post=1803811663&post=1803812041&post=1803811693&post=1803811991&post=1803812098&post=1803813225&post=1803817939&post=1803819706&post=1803813111&post=1803813975&post=1803816704&post=1803818767&post=1803819068&post=1803819923&post=1803812856&post=1803814869&post=1803817732&post=1803818079&post=1803819293&post=1803819367&post=1803820186&post=1803821100&post=1803823636&post=1803820258&post=1803820479&post=1803820971&post=1803823673&post=1803820678&post=1803821326&post=1803821416&post=1803821985&post=1803822539&post=1803822681&post=1803822699&post=1803823038&post=1803824185&post=1803824218&post=1803820397&post=1803812639&post=1803817614&post=1803811669&post=1803813341&post=1803814807&post=1803821781&post=1803823604&post=1803825156&post=1803829041&post=1803827092&post=1803821121&post=1803821728&post=1803822445&post=1803823806&post=1803824317&post=1803825423&post=1803826169&post=1803826921&post=1803828614&post=1803828796&post=1803825323&post=1803826440&post=1803827054&post=1803828042&post=1803829050&post=1803824867&post=1803827297&post=1803827923&post=1803828684&post=1803830789&post=1803825960&post=1803832491&post=1803825548&post=1803825729&post=1803826591&post=1803827339&post=1803827684&post=1803827782&post=1803827920&post=1803830423&post=1803830606&post=1803830752&post=1803832619&post=1803830006&post=1803830862&post=1803832476&post=1803833055&post=1803831263&post=1803829759&post=1803829960&post=1803832598&post=1803833725&post=1803832018&post=1803829682&post=1803829547&post=1803830404&post=1803831253&post=1803832881&post=1803833024&post=1803836698&post=1803839456&post=1803823195&post=1803838545&post=1803838849&post=1803830290&post=1803831670&post=1803834030&post=1803834460&post=1803835632&post=1803836703&post=1803834064&post=1803834077&post=1803835226&post=1803836050&post=1803837253&post=1803839237&post=1803840274&post=1803840293&post=1803840767&post=1803840970&post=1803842194&post=1803842310&post=1803843155&post=1803844815&post=1803845448&post=1803834768&post=1803836184&post=1803840582&post=1803841416&post=1803843180&post=1803845946&post=1803836005&post=1803837048&post=1803837176&post=1803837250&post=1803837420&post=1803837771&post=1803837894&post=1803837946&post=1803837990&post=1803837995&post=1803838151&post=1803838163&post=1803838348&post=1803838534&post=1803838672&post=1803838725&post=1803839620&post=1803840125&post=1803840377&post=1803841317&post=1803841401&post=1803842130&post=1803843013&post=1803843045&post=1803843130&post=1803843259&post=1803843582&post=1803843815&post=1803843902&post=1803844408&post=1803845040&post=1803845559&post=1803845674&post=1803845816&post=1803845819&post=1803845862&post=1803845905&post=1803846354&post=1803801507&post=1803801951&post=1803803080&post=1803803396&post=1803825635&post=1803804460&post=1803846420&post=1803847030&post=1803847564&post=1803847837&post=1803847870&post=1803848375&post=1803848774&post=1803849122&post=1803846526&post=1803848120&post=1803848570&post=1803848845&post=1803847046&post=1803848500&post=1803849371&post=1803849443&post=1803849656&post=1803849738&post=1803849833&post=1803849926&post=1803849987&post=1803850244&post=1803850303&post=1803851750&post=1803851651&post=1803851795&post=1803853359&post=1803853572&post=1803854567&post=1803852417&post=1803854359&post=1803851085&post=1803851794&post=1803852380&post=1803852614&post=1803852914&post=1803853792&post=1803853892&post=1803853986&post=1803854065&post=1803854128&post=1803854221&post=1803854607&post=1803854674&post=1803855101&post=1803855501&post=1803855723&post=1803854856&post=1803850647&post=1803850688&post=1803851191&post=1803852288&post=1803850516&post=1803852522&post=1803852892&post=1803851914&post=1803846864&post=1803847831&post=1803848372&post=1803847413&post=1803853244&post=1803847081&post=1803848162&post=1803848702&post=1803849262&post=1803851376&post=1803853185&post=1803846601&post=1803846799&post=1803856015&post=1803855924&post=1803856300&post=1803856585&post=1803856617&post=1803856624&post=1803856724&post=1803856773&post=1803859083&post=1803859476&post=1803857054&post=1803857276&post=1803857224&post=1803857959&post=1803857988&post=1803858106&post=1803858194&post=1803858352&post=1803858711&post=1803858794&post=1803858945&post=1803858981&post=1803859165&post=1803859174&post=1803859467&post=1803859482&post=1803856787&post=1803857403&post=1803856333&post=1803856369&post=1803857744&post=1803856364&post=1803859520&post=1803857646&post=1803858408&post=1803857896&post=1803856641&post=1803857353&post=1803858264&post=1803857498&post=1803859790&post=1803859801&post=1803859993&post=1803860235&post=1803860568&post=1803860156&post=1803860701&post=1803860869&post=1803860229&post=1803860939&post=1803861037&post=1803861402&post=1803861784&post=1803862349&post=1803862683&post=1803863125&post=1803864025&post=1803862207&post=1803862635&post=1803864505&post=1803864679&post=1803865006&post=1803865605&post=1803865716&post=1803865738&post=1803865813&post=1803866068&post=1803866290&post=1803866351&post=1803866416&post=1803866473&post=1803866490&post=1803863422&post=1803863131&post=1803862755&post=1803862963&post=1803863603&post=1803864852&post=1803866080&post=1803866711&post=1803864475&post=1803869305&post=1803868616&post=1803868474&post=1803873984&post=1803868392&post=1803868770&post=1803868641&post=1803869466&post=1803870106&post=1803871894&post=1803872766&post=1803873866&post=1803868318&post=1803869075&post=1803869586&post=1803869821&post=1803869109&post=1803869965&post=1803870075&post=1803870398&post=1803871158&post=1803871221&post=1803872131&post=1803872711&post=1803873401&post=1803874172&post=1803874214&post=1803875041&post=1803875501&post=1803875679&post=1803876129&post=1803874834&post=1803875115&post=1803879129&post=1803878354&post=1803881080&post=1803876765&post=1803880556&post=1803881324&post=1803872316&post=1803879657&post=1803878804&post=1803879418&post=1803883657&post=1803883671&post=1803884259&post=1803884429&post=1803884352&post=1803885139&post=1803886340&api_key=xxx", "HTTP/1.1", "User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:34.0) Gecko/20100101 Firefox/34.0", "Accept: */*", "Accept-Language: en-us,el;q=0.7,en;q=0.3", "DNT: 1", "X-Requested-With: XMLHttpRequest", "Referer: http://disqus.com/embed/comments/?base=default&disqus_version=7a9534a2&version=d7cfc2b66e4c2426e19da7b9195cf0c4&f=defencenet&t_i=node%2F244623&t_u=http%3A%2F%2Fwww.defencenet.gr%2Fdefence%2Fitem%2F%25CF%2584%25CE%25B5%25CF%2581%25CE%25AC%25CF%2583%25CF%2584%25CE%25B9%25CE%25B1-%25CE%25B4%25CE%25B9%25CE%25B1%25CF%2581%25CF%2581%25CE%25BF%25CE%25AE-%25CE%25B4%25CE%25B5%25CE%25BE%25CE%25B9%25CF%258E%25CE%25BD-%25CF%2588%25CE%25B7%25CF%2586%25CE%25BF%25CF%2586%25CF%258C%25CF%2581%25CF%2589%25CE%25BD-%25CF%2580%25CF%2581%25CE%25BF%25CF%2582-%25CF%2583%25CF%2585%25CF%2581%25CE%25B9%25CE%25B6%25CE%25B1-%25CE%25B4%25CE%25B5%25CE%25AF%25CF%2587%25CE%25BD%25CE%25BF%25CF%2585%25CE%25BD-%25CF%2583%25CF%2584%25CE%25BF%25CE%25BD-%25CE%25B1%25CF%2583%25CE%25B1%25CE%25BC%25CE%25B1%25CF%2581%25CE%25AC-%25CF%2584%25CE%25B7%25CE%25BD-%25CE%25AD%25CE%25BE%25CE%25BF%25CE%25B4%25CE%25BF&t_e=%CE%A4%CE%B5%CF%81%CE%AC%CF%83%CF%84%CE%B9%CE%B1%20%CE%B4%CE%B9%CE%B1%CF%81%CF%81%CE%BF%CE%AE%20%CE%B4%CE%B5%CE%BE%CE%B9%CF%8E%CE%BD%20%CF%88%CE%B7%CF%86%CE%BF%CF%86%CF%8C%CF%81%CF%89%CE%BD%20%CF%80%CF%81%CE%BF%CF%82%20%CE%A3%CE%A5%CE%A1%CE%99%CE%96%CE%91%20-%20%CE%94%CE%B5%CE%AF%CF%87%CE%BD%CE%BF%CF%85%CE%BD%20%CF%83%CF%84%CE%BF%CE%BD%20%CE%91.%CE%A3%CE%B1%CE%BC%CE%B1%CF%81%CE%AC%20%CF%84%CE%B7%CE%BD%20%CE%AD%CE%BE%CE%BF%CE%B4%CE%BF&t_d=%CE%A4%CE%B5%CF%81%CE%AC%CF%83%CF%84%CE%B9%CE%B1%20%CE%B4%CE%B9%CE%B1%CF%81%CF%81%CE%BF%CE%AE%20%CE%B4%CE%B5%CE%BE%CE%B9%CF%8E%CE%BD%20%CF%88%CE%B7%CF%86%CE%BF%CF%86%CF%8C%CF%81%CF%89%CE%BD%20%CF%80%CF%81%CE%BF%CF%82%20%CE%A3%CE%A5%CE%A1%CE%99%CE%96%CE%91%20-%20%CE%94%CE%B5%CE%AF%CF%87%CE%BD%CE%BF%CF%85%CE%BD%20%CF%83%CF%84%CE%BF%CE%BD%20%CE%91.%CE%A3%CE%B1%CE%BC%CE%B1%CF%81%CE%AC%20%CF%84%CE%B7%CE%BD%20%CE%AD%CE%BE%CE%BF%CE%B4%CE%BF%20%7C%20DefenceNet.gr&t_t=%CE%A4%CE%B5%CF%81%CE%AC%CF%83%CF%84%CE%B9%CE%B1%20%CE%B4%CE%B9%CE%B1%CF%81%CF%81%CE%BF%CE%AE%20%CE%B4%CE%B5%CE%BE%CE%B9%CF%8E%CE%BD%20%CF%88%CE%B7%CF%86%CE%BF%CF%86%CF%8C%CF%81%CF%89%CE%BD%20%CF%80%CF%81%CE%BF%CF%82%20%CE%A3%CE%A5%CE%A1%CE%99%CE%96%CE%91%20-%20%CE%94%CE%B5%CE%AF%CF%87%CE%BD%CE%BF%CF%85%CE%BD%20%CF%83%CF%84%CE%BF%CE%BD%20%CE%91.%CE%A3%CE%B1%CE%BC%CE%B1%CF%81%CE%AC%20%CF%84%CE%B7%CE%BD%20%CE%AD%CE%BE%CE%BF%CE%B4%CE%BF&s_o=default", "Connection: keep-alive", "X-Forwarded-For: 139.216.143.85", "X-Forwarded-Proto: http", "Host: disqus.com", "Disqus-Root: 1", "Disqus-Cookie-sessionid: c0235546-a054-11e4-a704-xxx", "Disqus-Logged-In: 1", "Cookie: ;;sessionid=c0235546-a054-11e4-a704-xxx", }, vcl = { srcname = { "input", "Builtin", "includes/4.0/recv-common.vcl", "includes/downgrade.vcl", "includes/4.0/responses/301-moved.vcl", "includes/4.0/responses/302-found.vcl", "includes/4.0/responses/404-not-found.vcl", "includes/4.0/responses/999-any.vcl", "includes/x-served-by.vcl", }, }, }, }}} I haven't been able to reproduce this, but it was happening with production traffic. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 21 13:50:44 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 21 Jan 2015 13:50:44 -0000 Subject: [Varnish] #1662: BereqProtocol showing twice for HTTP 1.0 requests Message-ID: <043.cd65aaf168b645e5087eb24ca7cc84b1@varnish-cache.org> #1662: BereqProtocol showing twice for HTTP 1.0 requests --------------------+------------------- Reporter: fgsch | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------- The attached case displays BereqProtocol twice, one for HTTP 1.0 and one for HTTP 1.1. **** v1 0.4 vsl| 1002 BereqMethod b GET **** v1 0.4 vsl| 1002 BereqURL b / **** v1 0.4 vsl| 1002 BereqProtocol b HTTP/1.0 **** v1 0.4 vsl| 1002 BereqHeader b X-Forwarded-For: 127.0.0.1 **** v1 0.4 vsl| 1002 BereqProtocol b HTTP/1.1 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 21 13:51:58 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 21 Jan 2015 13:51:58 -0000 Subject: [Varnish] #1662: BereqProtocol showing twice for HTTP 1.0 requests In-Reply-To: <043.cd65aaf168b645e5087eb24ca7cc84b1@varnish-cache.org> References: <043.cd65aaf168b645e5087eb24ca7cc84b1@varnish-cache.org> Message-ID: <058.cc7ba7d8bd3e59ec8bb05b42f62d42df@varnish-cache.org> #1662: BereqProtocol showing twice for HTTP 1.0 requests --------------------+-------------------- Reporter: fgsch | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+-------------------- Description changed by fgsch: Old description: > The attached case displays BereqProtocol twice, one for HTTP 1.0 and one > for HTTP 1.1. > > **** v1 0.4 vsl| 1002 BereqMethod b GET > **** v1 0.4 vsl| 1002 BereqURL b / > **** v1 0.4 vsl| 1002 BereqProtocol b HTTP/1.0 > **** v1 0.4 vsl| 1002 BereqHeader b X-Forwarded-For: 127.0.0.1 > **** v1 0.4 vsl| 1002 BereqProtocol b HTTP/1.1 New description: The attached case displays BereqProtocol twice, one for HTTP 1.0 and one for HTTP 1.1. {{{ **** v1 0.4 vsl| 1002 BereqMethod b GET **** v1 0.4 vsl| 1002 BereqURL b / **** v1 0.4 vsl| 1002 BereqProtocol b HTTP/1.0 **** v1 0.4 vsl| 1002 BereqHeader b X-Forwarded-For: 127.0.0.1 **** v1 0.4 vsl| 1002 BereqProtocol b HTTP/1.1 }}} -- -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 21 13:59:28 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 21 Jan 2015 13:59:28 -0000 Subject: [Varnish] #1661: Assert error in VRY_Validate(), cache/cache_vary.c line 377 In-Reply-To: <050.a0d7a51674fccc155f59afe0a5199aa8@varnish-cache.org> References: <050.a0d7a51674fccc155f59afe0a5199aa8@varnish-cache.org> Message-ID: <065.fa8f66d9a7441c51d5833e71f5f956e1@varnish-cache.org> #1661: Assert error in VRY_Validate(), cache/cache_vary.c line 377 --------------------------+---------------------- Reporter: mattrobenolt | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: unknown Severity: major | Resolution: Keywords: vary, panic | --------------------------+---------------------- Comment (by lkarsten): Can you describe how Vary is being used from the backend in this application? If possible, can you provide the complete backend headers on a miss to this API endpoint? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 21 18:45:00 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 21 Jan 2015 18:45:00 -0000 Subject: [Varnish] #1663: Both chmod 0755 and chown mgmt.uid used Message-ID: <048.6c04e642e3b0b687751b8da68f22ad7a@varnish-cache.org> #1663: Both chmod 0755 and chown mgmt.uid used ------------------------+---------------------- Reporter: puiterwijk | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: trunk | Severity: normal Keywords: | ------------------------+---------------------- For ticket #1072, a line was added to mgmt_vcc.c to chmod the output VCL library to 0755 (commit ee4396), saying that you didn't want to rely on the file ownership being the unprivileged user. Later on, for ticket #1153, this has seemingly be reconsidered, and the file is now given a fchown to the unprivileged user (commit b7175b). The problem now is that since the file is no longer owner by the user running the management process (it's now owned by the unprivileged user, while the management process is running as root), it requires the fowner (file owner) linux kernel permission. Would it be required to do both, or would just the fchown suffice, as then it would require less permissions? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 22 12:55:34 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 22 Jan 2015 12:55:34 -0000 Subject: [Varnish] #1661: Assert error in VRY_Validate(), cache/cache_vary.c line 377 In-Reply-To: <050.a0d7a51674fccc155f59afe0a5199aa8@varnish-cache.org> References: <050.a0d7a51674fccc155f59afe0a5199aa8@varnish-cache.org> Message-ID: <065.471c529cce2254a582c7c471cca89174@varnish-cache.org> #1661: Assert error in VRY_Validate(), cache/cache_vary.c line 377 --------------------------+---------------------- Reporter: mattrobenolt | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: unknown Severity: major | Resolution: Keywords: vary, panic | --------------------------+---------------------- Comment (by lkarsten): I asked reporter for any changed parameters. startup options are: -p shortlived=0 -p shm_reclen=4084 -p fetch_chunksize=4k -p timeout_idle=5 -p timeout_req=2 Martin have dug into this and it looks like bad ws overflow handling in the request parsing vary code. Anyone hitting this assert should either reduce their workspace use in vcl_recv (regsub/header operations or hungry vmods), or increase the workspace_client parameter. Martin is cooking on some (failing) test cases that will be reported as separate bugs. Leaving this issue open until that is in place and referenced here. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 22 15:45:35 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 22 Jan 2015 15:45:35 -0000 Subject: [Varnish] #1616: RH packages for varnish4 installs headers at the wrong place In-Reply-To: <047.10a5b7a71076bf8edeedc8500ef75678@varnish-cache.org> References: <047.10a5b7a71076bf8edeedc8500ef75678@varnish-cache.org> Message-ID: <062.9cdd08fc366a7a17844e648e55e2afd5@varnish-cache.org> #1616: RH packages for varnish4 installs headers at the wrong place ------------------------+----------------------- Reporter: mfournier | Owner: lkarsten Type: defect | Status: closed Priority: normal | Milestone: Component: packaging | Version: 4.0.2 Severity: normal | Resolution: fixed Keywords: rpm redhat | ------------------------+----------------------- Comment (by Lasse Karstensen ): In [83e40dfac66109250d4d13054a2238e5875aa0de]: {{{ #!CommitTicketReference repository="" revision="83e40dfac66109250d4d13054a2238e5875aa0de" Install _all_ headers under ${prefix}/include/.. Fixes #1616 Conflicts: varnish.m4 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 22 15:45:35 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 22 Jan 2015 15:45:35 -0000 Subject: [Varnish] #1616: RH packages for varnish4 installs headers at the wrong place In-Reply-To: <047.10a5b7a71076bf8edeedc8500ef75678@varnish-cache.org> References: <047.10a5b7a71076bf8edeedc8500ef75678@varnish-cache.org> Message-ID: <062.319461deb52b5831a11e1159a25ca778@varnish-cache.org> #1616: RH packages for varnish4 installs headers at the wrong place ------------------------+----------------------- Reporter: mfournier | Owner: lkarsten Type: defect | Status: closed Priority: normal | Milestone: Component: packaging | Version: 4.0.2 Severity: normal | Resolution: fixed Keywords: rpm redhat | ------------------------+----------------------- Comment (by Lasse Karstensen ): In [de40d3ee2a2f1e6eff33aa9d56e718aaa149f702]: {{{ #!CommitTicketReference repository="" revision="de40d3ee2a2f1e6eff33aa9d56e718aaa149f702" Install _all_ headers under ${prefix}/include/.. Fixes #1616 Conflicts: bin/varnishd/Makefile.am varnish.m4 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 22 15:45:35 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 22 Jan 2015 15:45:35 -0000 Subject: [Varnish] #1479: Building man pages fails when building outside of the source tree. In-Reply-To: <063.6f43cc0cf0e819832d5e81676f409af7@varnish-cache.org> References: <063.6f43cc0cf0e819832d5e81676f409af7@varnish-cache.org> Message-ID: <078.8a0e7f409c0cfdca5c1ed22efdc17f67@varnish-cache.org> #1479: Building man pages fails when building outside of the source tree. ----------------------+--------------------- Reporter: basile@? | Owner: slink Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: 4.0.0 Severity: normal | Resolution: fixed Keywords: | ----------------------+--------------------- Comment (by Lasse Karstensen ): In [ef241692250c35735ce71d0f2715bacd7e192b05]: {{{ #!CommitTicketReference repository="" revision="ef241692250c35735ce71d0f2715bacd7e192b05" Fix out-of-tree builds Fixes #1479 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 23 10:09:05 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 23 Jan 2015 10:09:05 -0000 Subject: [Varnish] #1628: Assert error in VBO_DerefBusyObj() In-Reply-To: <041.d988225a70fb3421845c28c4830e2c87@varnish-cache.org> References: <041.d988225a70fb3421845c28c4830e2c87@varnish-cache.org> Message-ID: <056.c27643be215c214e91b58c257590d57b@varnish-cache.org> #1628: Assert error in VBO_DerefBusyObj() ----------------------+----------------------------------------------- Reporter: Jay | Owner: Martin Blix Grydeland Type: defect | Status: closed Priority: normal | Milestone: Later Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------- Comment (by franveux): I don't have this error anymore since i use varnishd (varnish-trunk revision 165b4ca). The child ran twice for 15 days, ending with OOM Killer ... I experienced new child crash but for other reason that i'll look for in other ticket. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 23 12:20:44 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 23 Jan 2015 12:20:44 -0000 Subject: [Varnish] #1462: ReqURL is emitted twice In-Reply-To: <043.4c15f0afe4e6c22dd922a9ce48ae670c@varnish-cache.org> References: <043.4c15f0afe4e6c22dd922a9ce48ae670c@varnish-cache.org> Message-ID: <058.0aeb1bf3e89b4255320cbd9aa0859d80@varnish-cache.org> #1462: ReqURL is emitted twice --------------------+------------------------------ Reporter: scoof | Owner: aondio Type: defect | Status: closed Priority: normal | Milestone: Varnish 4.0-TP2 Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+------------------------------ Changes (by arianna-aondio ): * status: new => closed * resolution: => fixed Comment: In [e819618961324937a1c8b6d45db36d2287a5ffa9]: {{{ #!CommitTicketReference repository="" revision="e819618961324937a1c8b6d45db36d2287a5ffa9" Varnishncsa logs the first value if on request side and uses the last entry if on delivery side. Fixes #1462 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 23 13:07:42 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 23 Jan 2015 13:07:42 -0000 Subject: [Varnish] #1662: BereqProtocol showing twice for HTTP 1.0 requests In-Reply-To: <043.cd65aaf168b645e5087eb24ca7cc84b1@varnish-cache.org> References: <043.cd65aaf168b645e5087eb24ca7cc84b1@varnish-cache.org> Message-ID: <058.694a41673da2e96a6169919c228fd485@varnish-cache.org> #1662: BereqProtocol showing twice for HTTP 1.0 requests --------------------+--------------------- Reporter: fgsch | Owner: aondio Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+--------------------- Changes (by aondio): * owner: => aondio -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sun Jan 25 11:47:08 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sun, 25 Jan 2015 11:47:08 -0000 Subject: [Varnish] #1661: Assert error in VRY_Validate(), cache/cache_vary.c line 377 In-Reply-To: <050.a0d7a51674fccc155f59afe0a5199aa8@varnish-cache.org> References: <050.a0d7a51674fccc155f59afe0a5199aa8@varnish-cache.org> Message-ID: <065.2a078991e8e4f5a8a9f31ab41de88c45@varnish-cache.org> #1661: Assert error in VRY_Validate(), cache/cache_vary.c line 377 --------------------------+---------------------- Reporter: mattrobenolt | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: unknown Severity: major | Resolution: Keywords: vary, panic | --------------------------+---------------------- Comment (by mattrobenolt): Also, fwiw, the response Vary is simply `Vary: Accept-Encoding` if that's still valuable. Sorry for the delay. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 27 13:39:41 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 27 Jan 2015 13:39:41 -0000 Subject: [Varnish] #1566: escape sequence breaks regex In-Reply-To: <048.96582f05e1f84174e2f554fa6d8ea786@varnish-cache.org> References: <048.96582f05e1f84174e2f554fa6d8ea786@varnish-cache.org> Message-ID: <063.5bbf47b2b7d0900f3ab8033d2eb98610@varnish-cache.org> #1566: escape sequence breaks regex ------------------------+---------------------------------------- Reporter: RWOverdijk | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: unknown Severity: normal | Resolution: fixed Keywords: | ------------------------+---------------------------------------- Comment (by Lasse Karstensen ): In [4e3aa514ecf174bb549e5f0daa0d46957ba196c0]: {{{ #!CommitTicketReference repository="" revision="4e3aa514ecf174bb549e5f0daa0d46957ba196c0" Escape question marks in C-strings to avoid accidentally generating tri-graphs. Fixes #1566 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 27 15:47:13 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 27 Jan 2015 15:47:13 -0000 Subject: [Varnish] #1664: Assert error in VFP_Error(), cache/cache_fetch_proc.c line 61 Message-ID: <043.782dcf41379c991d410f1ae63ea4edff@varnish-cache.org> #1664: Assert error in VFP_Error(), cache/cache_fetch_proc.c line 61 ----------------------+--------------------- Reporter: daghf | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: unknown Severity: normal | Keywords: ----------------------+--------------------- If std.cache_req_body() is called with a POST body larger than the configured max size, we crash. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 27 16:17:57 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 27 Jan 2015 16:17:57 -0000 Subject: [Varnish] #1653: Make numbers in varnishstat human-readable In-Reply-To: <047.f46732d5f2705010f7f9e468bfaca1d8@varnish-cache.org> References: <047.f46732d5f2705010f7f9e468bfaca1d8@varnish-cache.org> Message-ID: <062.4df3aa26205a3075420c4c07f5502b23@varnish-cache.org> #1653: Make numbers in varnishstat human-readable -------------------------+--------------------- Reporter: Centurion | Owner: martin Type: enhancement | Status: closed Priority: low | Milestone: Component: varnishstat | Version: trunk Severity: normal | Resolution: fixed Keywords: | -------------------------+--------------------- Changes (by Martin Blix Grydeland ): * status: new => closed * resolution: => fixed Comment: In [ca16533cc4a6f346e4e96efbe4630f8c9322b4c8]: {{{ #!CommitTicketReference repository="" revision="ca16533cc4a6f346e4e96efbe4630f8c9322b4c8" Change presentation from 'i' (integer) to 'B' (bytes) for VSM counters representing bytes. Fixes: #1653 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 29 09:30:20 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 29 Jan 2015 09:30:20 -0000 Subject: [Varnish] #1665: Wrong behavior of timeout_req Message-ID: <047.e6f799ed399a9059522e2ae83022e4c0@varnish-cache.org> #1665: Wrong behavior of timeout_req -----------------------+---------------------- Reporter: sorinescu | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: 4.0.2 | Severity: normal Keywords: | -----------------------+---------------------- The documentation defines timeout_req as: Max time to receive clients request header, measured from first non-white- space character to double CRNL. The problem is that the code measures the time from t_idle, which is either the moment when the connection was accept()ed (which is fine) or the time of the last activity of the previous request on the same connection (which is wrong). This leads to prematurely closing the session with RX_TIMEOUT. I'm attaching a patch that fixes the problem for me. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 29 11:38:59 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 29 Jan 2015 11:38:59 -0000 Subject: [Varnish] #1539: Assert error in cnt_lookup(), cache/cache_req_fsm.c line 411: In-Reply-To: <047.9e25f0913e70f9b448183830fc7e3ec7@varnish-cache.org> References: <047.9e25f0913e70f9b448183830fc7e3ec7@varnish-cache.org> Message-ID: <062.4e3c883a343a6d64c585242573163303@varnish-cache.org> #1539: Assert error in cnt_lookup(), cache/cache_req_fsm.c line 411: -----------------------+---------------------------------- Reporter: shing6326 | Owner: Type: defect | Status: reopened Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: 4.0.1 Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------- Changes (by xcir): * status: closed => reopened * resolution: fixed => Comment: Hi, I caught the error that is similar in the varnish4.0.3-rc2 (b62b01144ed845a76455d2722c765ac47571605d) {{{ Last panic at: Mon, 26 Jan 2015 15:20:02 GMT Assert error in cnt_lookup(), cache/cache_req_fsm.c line 430: Condition((oc->exp_flags & (1<<7)) == 0) not true. thread = (cache-worker) version = varnish-4.0.3-rc2 revision NOGIT ident = Linux,2.6.32-431.17.1.el6.x86_64,x86_64,-smalloc,-sfile,-sfile,-smalloc,-hcritbit,epoll Backtrace: 0x431c15: pan_ic+0x145 0x435740: cnt_purge+0x0 0x436f71: CNT_Request+0x241 0x417b95: ESI_Deliver+0x855 0x439058: V1D_Deliver+0x748 0x436526: cnt_deliver+0x296 0x436e69: CNT_Request+0x139 0x42c183: HTTP1_Session+0x543 0x43ab48: ses_req_pool_task+0x68 0x434695: Pool_Work_Thread+0x365 req = 0x7f7cad641530 { sp = 0x18f8670, vxid = 1141003282, step = R_STP_LOOKUP, req_body = R_BODY_NONE, restarts = 0, esi_level = 1, sp = 0x18f8670 { fd = 122, vxid = 67324354, client = *** ***, step = S_STP_WORKING, }, worker = 0x7f7c8b3b0c30 { ws = 0x7f7c8b3b0e50 { id = "wrk", {s,f,r,e} = {0x7f7c8b3b0420,0x7f7c8b3b0420,(nil),+2048}, }, VCL::method = 0x0, VCL::return = deliver, }, ws = 0x7f7cad6416c8 { id = "req", {s,f,r,e} = {0x7f7cad643520,0x7f7cad643520,(nil),+122896}, }, http[req] = { ws = 0x7f7cae0c3538[req] "GET", "***", "HTTP/1.1", "Accept: text/html, application/xhtml+xml, */*", "Accept-Language: ja-JP", "User-Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/6.0)", "DNT: 1", "Connection: Keep-Alive", "X-Full-Uri: ***", "X-Forwarded-For: ***", "host: ***", "x-storage: file", "x-varnish-ttl: 600s", "x-v-doesi: 1", "Accept-Encoding: gzip", }, vcl = { srcname = { "input", "Builtin", "/etc/varnish/***.vcl", "/etc/varnish/***.vcl", "/etc/varnish/***.vcl", "/etc/varnish/***.vcl", "/etc/varnish/***.vcl", "/etc/varnish/***.vcl", "/etc/varnish/***.vcl", }, }, obj (REQ) = 0x7f7f94dcc000 { vxid = 2201367624, http[obj] = { ws = (nil)[] "HTTP/1.1", "200", "OK", "Server: Apache", "X-Powered-By: PHP/5.3.15", "Content-Type: text/html; charset=UTF-8", "Date: Mon, 26 Jan 2015 14:10:00 GMT", "X-Varnish: 290092700", "Via: 1.1 varnish", "Vary: Accept-Encoding", "x-storage: file", "x-src-url: ***", "x-src-host: ***", "Content-Encoding: gzip", }, len = 513, store = { 513 { 1f 8b 08 00 00 00 00 00 00 03 00 00 00 ff ff a4 |................| 94 df 6a d4 40 14 c6 5f 25 cc 85 77 cd 64 26 7f |..j. at .._%..w.d&.| 36 d1 24 3e 4a c8 ee ce 6e a6 4e b2 21 99 b4 b7 |6.$>J...n.N.!...| ce 44 11 b6 17 5e 88 08 de aa 45 59 0a 82 e0 45 |.D...^....EY...E| [449 more] }, }, }, }, }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 29 11:44:09 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 29 Jan 2015 11:44:09 -0000 Subject: [Varnish] #1666: make init script check config before restarting Message-ID: <050.d39f2f7511b733263cce920f8a427047@varnish-cache.org> #1666: make init script check config before restarting --------------------------+-------------------- Reporter: KlavsKlavsen | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: unknown | Severity: normal Keywords: | --------------------------+-------------------- Today, if I restart varnish and have made a config mistake - varnish dies and I'm having to scramble.. :( icinga, named, apache and other init scripts all check config BEFORE doing restart and simply exits with an error if config check fails. I'd very much like varnish to do the same - I'd suggest simply doing: varnishd -C -f /etc/varnish/default.vcl and checking return value from that. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 30 13:18:21 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 30 Jan 2015 13:18:21 -0000 Subject: [Varnish] #1617: Varnish 4 weird memory consumption / calculation In-Reply-To: <046.253c419c4f87de3d220969908bfcf866@varnish-cache.org> References: <046.253c419c4f87de3d220969908bfcf866@varnish-cache.org> Message-ID: <061.0a734ac92df116315cb4de2a6f3ef3b3@varnish-cache.org> #1617: Varnish 4 weird memory consumption / calculation ----------------------+-------------------- Reporter: whocares | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 4.0.2 Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Comment (by ioppermann): Same for me. Have a varnish3 with malloc,128M which can store ~14k objects. With varnish4 it can only store ~8k objects with malloc,1G. varnish4 is nuking objects because it thinks memory is full, but top tells me that only ~300M are effectively used. Now I reduced fetch_chunksize to 8k and it's geting better. However, this seems to be a very strange handling of chunked content. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 30 13:26:40 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 30 Jan 2015 13:26:40 -0000 Subject: [Varnish] #1617: Varnish 4 weird memory consumption / calculation In-Reply-To: <046.253c419c4f87de3d220969908bfcf866@varnish-cache.org> References: <046.253c419c4f87de3d220969908bfcf866@varnish-cache.org> Message-ID: <061.e315b64687f58d98a7ad483318dec7b9@varnish-cache.org> #1617: Varnish 4 weird memory consumption / calculation ----------------------+-------------------- Reporter: whocares | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 4.0.2 Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Comment (by whocares): Afaik this is already fixed in the Git repo trunk. So it should be good again once 4.0.3 is released. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 30 15:52:42 2015 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 30 Jan 2015 15:52:42 -0000 Subject: [Varnish] #1643: corrupt range response In-Reply-To: <041.113f5e6ae1e1582a5da6631379ba3e37@varnish-cache.org> References: <041.113f5e6ae1e1582a5da6631379ba3e37@varnish-cache.org> Message-ID: <056.1af0fa18d8262eb3d5ea72c90f525f44@varnish-cache.org> #1643: corrupt range response --------------------------------------+-------------------- Reporter: Jay | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Later Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: byte-range request range | --------------------------------------+-------------------- Comment (by jstrom): Hi, fgs on IRC thought my issues was related to this bug, so I'll repeat my findings here: I'm running varnish 4.0.3 on Mac OS 10.9.5 (dev) with a very basic VCL. I have a GET request which is pass'ed directly in vcl_recv. This request comes from FFMPeg and has a "Range: bytes=0-" header. The backend will reply with "Transfer-Encoding: chunked". One single chunk with 8220 bytes is present in the response. Every now and then (2 out of 5 requests maybe), varnish returns the full response. But some times it returns 206 Partial Content and "Content- Range: bytes 0-2667/2668". tcpdump indicates that varnish starts to reply after 3 response TCP packets has arrived, i..e before full response has been obtained. This response includes the Content-Range header. then nothing happens until it has received the rest of the backend packets, at which time the frontend connection is closed. My solution for now is just to remove the "Range: bytes=0-" header in the request, as I don't use that anyway. One guess from IRC: {{{ 16:22:53 < thierr1> jstrom: still guessing but what could lead to such a situation may be : varnish receives the range request, makes a background fetch and has received only 2668 bytes when it replies to client (streaming mode), so issues a 206 with the current content it has. From my point of view, this is RFC compliant, but not necessarily what is expected. Maybe you can check this with tcpdump, you will see if varnish has received full response when it starts stre }}} I agree, it *might* be compliant but definitely not what I expected. Also, no streaming stuff is enabled in the VCL, so I'd expect full reply. These are the Client -> Varnish headers: {{{ GET /some/path/to/file HTTP/1.1 User-Agent: Lavf/56.15.100 Accept: */* Range: bytes=0- Connection: close Host: localhost:8081 Icy-MetaData: 1 HTTP/1.1 206 Partial Content Date: Fri, 30 Jan 2015 14:14:13 GMT Server: Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.1j DAV/2 PHP/5.6.4 X-Powered-By: PHP/5.6.4 Content-Type: application/x-mpegURL X-Varnish: 100148 Age: 0 Via: 1.1 varnish-v4 Transfer-Encoding: chunked Connection: close Accept-Ranges: bytes Content-Range: bytes 0-2667/2668 }}} These are the Varnish -> Backend headers: {{{ GET /some/path/to/file HTTP/1.1 User-Agent: Lavf/56.15.100 Accept: */* Range: bytes=0- Icy-MetaData: 1 X-Forwarded-For: ::1 Host: example.com X-Varnish: 100149 HTTP/1.1 200 OK Date: Fri, 30 Jan 2015 14:14:13 GMT Server: Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.1j DAV/2 PHP/5.6.4 X-Powered-By: PHP/5.6.4 Transfer-Encoding: chunked Content-Type: application/x-mpegURL }}} Full VCL: {{{ vcl 4.0; import std; backend stream { .host = "example.com"; .port = "80"; } sub vcl_recv { # Pipe unknown requests if (req.method != "GET" && req.method != "HEAD" && req.method != "PUT" && req.method != "POST" && req.method != "TRACE" && req.method != "OPTIONS" && req.method != "DELETE") { /* Non-RFC2616 or CONNECT which is weird. */ return (pipe); } # Kill range header #unset req.http.Range; set req.http.Host = "example.com"; if(req.url ~ ".ts$") { return(hash); } return(pass); } sub vcl_backend_response { if (bereq.url ~ "\.ts$") { set beresp.uncacheable = false; set beresp.ttl = 86400s; } return (deliver); } }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator