From varnish-bugs at varnish-cache.org Mon Mar 3 11:20:01 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 03 Mar 2014 11:20:01 -0000 Subject: [Varnish] #1442: Backend IMS and ESI clashes Message-ID: <044.8dc828214eebfaca371136de78c48c06@varnish-cache.org> #1442: Backend IMS and ESI clashes ----------------------+------------------- Reporter: martin | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+------------------- If do_esi is set, the backend IMS code will assert on "XXXAZ(bo->ims_obj->esidata);" in vbf_stp_condfetch. See attached test case. If the same conditions is set for an ESI-included object being IMS updated, the code will assert on "assert(bo->do_stream || next != BOS_STREAM);". The assertion in that case comes from the backend IMS code always goes to BOS_STREAM for the update, but do_stream is false because of the ESI path. Martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 3 11:23:32 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 03 Mar 2014 11:23:32 -0000 Subject: [Varnish] #1442: Backend IMS and ESI clashes In-Reply-To: <044.8dc828214eebfaca371136de78c48c06@varnish-cache.org> References: <044.8dc828214eebfaca371136de78c48c06@varnish-cache.org> Message-ID: <059.0da57dbd7490332c003fe7e44488754b@varnish-cache.org> #1442: Backend IMS and ESI clashes ----------------------+-------------------- Reporter: martin | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Description changed by martin: Old description: > If do_esi is set, the backend IMS code will assert on > "XXXAZ(bo->ims_obj->esidata);" in vbf_stp_condfetch. See attached test > case. > > If the same conditions is set for an ESI-included object being IMS > updated, the code will assert on "assert(bo->do_stream || next != > BOS_STREAM);". The assertion in that case comes from the backend IMS code > always goes to BOS_STREAM for the update, but do_stream is false because > of the ESI path. > > Martin New description: If do_esi is set, the backend IMS code will assert on {{{"XXXAZ(bo->ims_obj->esidata);"}}} in vbf_stp_condfetch. See attached test case. If the same conditions is set for an ESI-included object being IMS updated, the code will assert on {{{"assert(bo->do_stream || next != BOS_STREAM);"}}}. The assertion in that case comes from the backend IMS code always goes to BOS_STREAM for the update, but do_stream is false because of the ESI path. Martin -- -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 3 11:27:57 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 03 Mar 2014 11:27:57 -0000 Subject: [Varnish] #1442: Backend IMS and ESI clashes In-Reply-To: <044.8dc828214eebfaca371136de78c48c06@varnish-cache.org> References: <044.8dc828214eebfaca371136de78c48c06@varnish-cache.org> Message-ID: <059.df5f8fdb61b106fb87376195fcac153d@varnish-cache.org> #1442: Backend IMS and ESI clashes ----------------------+-------------------- Reporter: martin | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Changes (by phk): * owner: => phk -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 3 11:52:11 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 03 Mar 2014 11:52:11 -0000 Subject: [Varnish] #1440: e00019.vtc occasionally trips an assert In-Reply-To: <044.1cf9d478ad322048a9826e01a403f898@varnish-cache.org> References: <044.1cf9d478ad322048a9826e01a403f898@varnish-cache.org> Message-ID: <059.683dcf4242bc8e1bcbdbc62a7d05c5fd@varnish-cache.org> #1440: e00019.vtc occasionally trips an assert ----------------------+---------------------------------------- Reporter: martin | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+---------------------------------------- Changes (by Martin Blix Grydeland ): * status: reopened => closed * resolution: => fixed Comment: In [2f05fe44f072373bd11da06b01586110412fc15c]: {{{ #!CommitTicketReference repository="" revision="2f05fe44f072373bd11da06b01586110412fc15c" Serve ESI-includes from a different backend. Serve ESI-includes from a different backend so that we don't race against when the backend connection is ready for reuse. Fixes: #1440 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 3 16:03:20 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 03 Mar 2014 16:03:20 -0000 Subject: [Varnish] #1436: VCL Compiler bug In-Reply-To: <043.61349668008cd62e039e675af2f166b9@varnish-cache.org> References: <043.61349668008cd62e039e675af2f166b9@varnish-cache.org> Message-ID: <058.d1a6af302130c73f476741118a69952f@varnish-cache.org> #1436: VCL Compiler bug -------------------------+---------------------- Reporter: perbu | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishhist | Version: unknown Severity: normal | Resolution: fixed Keywords: | -------------------------+---------------------- Changes (by Federico G. Schwindt ): * status: new => closed * resolution: => fixed Comment: In [f47908316d9ff23fdc2a438f68e92d27bd194853]: {{{ #!CommitTicketReference repository="" revision="f47908316d9ff23fdc2a438f68e92d27bd194853" Better error on missing import Fixes: #1436 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 3 23:26:50 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 03 Mar 2014 23:26:50 -0000 Subject: [Varnish] #1439: Backend name cannot start with if In-Reply-To: <045.791ad4e2323eca6b387dc78c2cbb9eb6@varnish-cache.org> References: <045.791ad4e2323eca6b387dc78c2cbb9eb6@varnish-cache.org> Message-ID: <060.46fb4862242fd57bd174fe5a45cfb949@varnish-cache.org> #1439: Backend name cannot start with if ----------------------+-------------------- Reporter: sambash | Owner: fgsch Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.5 Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Changes (by fgsch): * owner: => fgsch -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 3 23:27:28 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 03 Mar 2014 23:27:28 -0000 Subject: [Varnish] #1435: bereq.{first_byte_timeout, between_bytes_timeout} ignored in vcl_pipe In-Reply-To: <043.e912e54e9fcdfc8b8607ae03b6ea22cf@varnish-cache.org> References: <043.e912e54e9fcdfc8b8607ae03b6ea22cf@varnish-cache.org> Message-ID: <058.142c064f89785a8872b54693afe3ae57@varnish-cache.org> #1435: bereq.{first_byte_timeout,between_bytes_timeout} ignored in vcl_pipe ----------------------+-------------------- Reporter: fgsch | Owner: fgsch Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | 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 Mar 4 10:23:07 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 04 Mar 2014 10:23:07 -0000 Subject: [Varnish] #1442: Backend IMS and ESI clashes In-Reply-To: <044.8dc828214eebfaca371136de78c48c06@varnish-cache.org> References: <044.8dc828214eebfaca371136de78c48c06@varnish-cache.org> Message-ID: <059.30d1d079f932dde99633eb383b46d1bf@varnish-cache.org> #1442: Backend IMS and ESI clashes ----------------------+--------------------- Reporter: martin | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+--------------------- Changes (by Poul-Henning Kamp ): * status: new => closed * resolution: => fixed Comment: In [c48e48ad2cbf2bb4b8e957baeeed2784123dffd1]: {{{ #!CommitTicketReference repository="" revision="c48e48ad2cbf2bb4b8e957baeeed2784123dffd1" Fix IMS fetching of ESI objects. Fixes #1442 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 5 16:59:47 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 05 Mar 2014 16:59:47 -0000 Subject: [Varnish] #1439: Backend name cannot start with if In-Reply-To: <045.791ad4e2323eca6b387dc78c2cbb9eb6@varnish-cache.org> References: <045.791ad4e2323eca6b387dc78c2cbb9eb6@varnish-cache.org> Message-ID: <060.5448981f7b50e346c484f89de2778851@varnish-cache.org> #1439: Backend name cannot start with if ----------------------+--------------------- Reporter: sambash | Owner: fgsch Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 3.0.5 Severity: normal | Resolution: fixed Keywords: | ----------------------+--------------------- Changes (by Federico G. Schwindt ): * status: new => closed * resolution: => fixed Comment: In [ac7ced62b57e050a678a179d0701afdb83238366]: {{{ #!CommitTicketReference repository="" revision="ac7ced62b57e050a678a179d0701afdb83238366" Allow backends to start with if, include or else Cherry pick changes from master to allow it. Fixes: #1439 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 6 15:44:00 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 06 Mar 2014 15:44:00 -0000 Subject: [Varnish] #1435: bereq.{first_byte_timeout, between_bytes_timeout} ignored in vcl_pipe In-Reply-To: <043.e912e54e9fcdfc8b8607ae03b6ea22cf@varnish-cache.org> References: <043.e912e54e9fcdfc8b8607ae03b6ea22cf@varnish-cache.org> Message-ID: <058.2de0ce38620e77b79f38ddaeba49c612@varnish-cache.org> #1435: bereq.{first_byte_timeout,between_bytes_timeout} ignored in vcl_pipe ----------------------+--------------------- Reporter: fgsch | Owner: fgsch Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+--------------------- Changes (by Federico G. Schwindt ): * status: new => closed * resolution: => fixed Comment: In [41db0bc0b31b46cea33e6d93f598fa210eeb343d]: {{{ #!CommitTicketReference repository="" revision="41db0bc0b31b46cea33e6d93f598fa210eeb343d" Don't expose certain variables in vcl_pipe Accessing bereq.first_byte_timeout and bereq.between_bytes_timeout in vcl_pipe makes no sense so disallow it. Fixes: #1435 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 6 18:53:11 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 06 Mar 2014 18:53:11 -0000 Subject: [Varnish] #1443: Varnish crashes on attempt to return (restart) Message-ID: <051.4f50b3a72d284d79cc7772102141d1dd@varnish-cache.org> #1443: Varnish crashes on attempt to return (restart) ---------------------------+---------------------- Reporter: quintonparker | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: 3.0.5 | Severity: major Keywords: | ---------------------------+---------------------- Varnish child crashes when attempting to restart a transaction from vcl_fetch, vcl_miss or vcl_pass subroutines I'm trying to restart a "bad" request to change the backend in vcl_recv and thereby retry another backend Please help! -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 7 10:29:54 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 07 Mar 2014 10:29:54 -0000 Subject: [Varnish] #1443: Varnish crashes on attempt to return (restart) In-Reply-To: <051.4f50b3a72d284d79cc7772102141d1dd@varnish-cache.org> References: <051.4f50b3a72d284d79cc7772102141d1dd@varnish-cache.org> Message-ID: <066.2c632065db98ee68608d74712e5dd7bd@varnish-cache.org> #1443: Varnish crashes on attempt to return (restart) ---------------------------+-------------------- Reporter: quintonparker | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.5 Severity: major | Resolution: Keywords: | ---------------------------+-------------------- Comment (by lkarsten): Restart for vcl_fetch should work fine. Please provide a VCL if you mean otherwise. Restart in vcl_pass isn't handled explicitly, but documented to work. Restart in vcl_miss is INCOMPLETE(), as you noticed. In all cases you have a workaround in going via vcl_error where restarts work as expected. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 7 12:36:20 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 07 Mar 2014 12:36:20 -0000 Subject: [Varnish] #1443: Varnish crashes on attempt to return (restart) In-Reply-To: <051.4f50b3a72d284d79cc7772102141d1dd@varnish-cache.org> References: <051.4f50b3a72d284d79cc7772102141d1dd@varnish-cache.org> Message-ID: <066.611f564912e0bbb56e15be1a3ed01b2e@varnish-cache.org> #1443: Varnish crashes on attempt to return (restart) ---------------------------+-------------------- Reporter: quintonparker | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.5 Severity: major | Resolution: Keywords: | ---------------------------+-------------------- Comment (by quintonparker): Thanks Didn't realise vcl_miss was "incomplete" and I don't have to restart inside of vcl_pass so I?ll go with the vcl_error workaround Close this ticket if you wish Thanks for your time (and varnish!) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 7 12:41:08 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 07 Mar 2014 12:41:08 -0000 Subject: [Varnish] #1443: Varnish crashes on attempt to return (restart) In-Reply-To: <051.4f50b3a72d284d79cc7772102141d1dd@varnish-cache.org> References: <051.4f50b3a72d284d79cc7772102141d1dd@varnish-cache.org> Message-ID: <066.b3631f0dd55f88fc7c2e1442fd98e5d4@varnish-cache.org> #1443: Varnish crashes on attempt to return (restart) ---------------------------+-------------------- Reporter: quintonparker | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.5 Severity: major | Resolution: Keywords: | ---------------------------+-------------------- Comment (by lkarsten): I've updated the documentation a bit now, see git commit 0152502b. It was incorrectly documented that this would work. Thanks for reporting it so we could improve this. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 7 12:41:30 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 07 Mar 2014 12:41:30 -0000 Subject: [Varnish] #1443: Varnish crashes on attempt to return (restart) In-Reply-To: <051.4f50b3a72d284d79cc7772102141d1dd@varnish-cache.org> References: <051.4f50b3a72d284d79cc7772102141d1dd@varnish-cache.org> Message-ID: <066.1bfa114280f8269541495ded3042baaa@varnish-cache.org> #1443: Varnish crashes on attempt to return (restart) ---------------------------+--------------------- Reporter: quintonparker | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: documentation | Version: 3.0.5 Severity: minor | Resolution: fixed Keywords: | ---------------------------+--------------------- Changes (by lkarsten): * status: new => closed * resolution: => fixed * component: varnishd => documentation * severity: major => minor -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 7 14:13:39 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 07 Mar 2014 14:13:39 -0000 Subject: [Varnish] #1444: varnishncsa with %D format not working properly Message-ID: <049.3ea4c3048adb96b45082c7435628b21e@varnish-cache.org> #1444: varnishncsa with %D format not working properly -------------------------+------------------------- Reporter: raymondjiii | Type: defect Status: new | Priority: normal Milestone: | Component: varnishncsa Version: 3.0.5 | Severity: normal Keywords: | -------------------------+------------------------- 1) The man page for varnishncsa does not show a %D option but it is listed here: https://www.varnish-cache.org/docs/trunk/reference/varnishncsa.html 2) I am getting a few negative numbers in my varnishncsa output. Example: 10.181.167.183 - - [07/Mar/2014:07:48:33 -0500] GET http://du-api- internal.prd.use1.nytimes.com/svc/movies/v2/movie/awards/154976 HTTP/1.0 200 127 -0.086421 - [170.149.168.65] - /svc/movies/v2/movie/awards/154976 miss -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 10 11:09:26 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 10 Mar 2014 11:09:26 -0000 Subject: [Varnish] #1364: Assert error in mgt_sigsegv_handler(), mgt/mgt_child.c line 328 In-Reply-To: <046.4236638300da782ed48b50e2dd732f94@varnish-cache.org> References: <046.4236638300da782ed48b50e2dd732f94@varnish-cache.org> Message-ID: <061.e9600d51ec76f9e0303bfb58acd91583@varnish-cache.org> #1364: Assert error in mgt_sigsegv_handler(), mgt/mgt_child.c line 328 ----------------------+-------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Comment (by lkarsten): Note to self; try to recreate this on fryer. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 10 11:10:44 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 10 Mar 2014 11:10:44 -0000 Subject: [Varnish] #1393: segfault in varnish tools (but varnish is running fine) In-Reply-To: <053.c3c1a4a06aa4f7d4747421bb7f99b905@varnish-cache.org> References: <053.c3c1a4a06aa4f7d4747421bb7f99b905@varnish-cache.org> Message-ID: <068.f8f5697c929cdda59784e5cb86568ef3@varnish-cache.org> #1393: segfault in varnish tools (but varnish is running fine) -----------------------------+------------------------- Reporter: brandonwamboldt | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishlog | Version: 3.0.2 Severity: major | Resolution: worksforme Keywords: | -----------------------------+------------------------- Changes (by lkarsten): * status: new => closed * resolution: => worksforme Comment: Nothing heard back from reporter, closing. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 10 11:18:03 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 10 Mar 2014 11:18:03 -0000 Subject: [Varnish] #1388: Length is 0 for most responses In-Reply-To: <043.274a32f05d9b176ccb75ed7082dd7d70@varnish-cache.org> References: <043.274a32f05d9b176ccb75ed7082dd7d70@varnish-cache.org> Message-ID: <058.a5b884808785c734e068e706ba95a237@varnish-cache.org> #1388: Length is 0 for most responses --------------------+---------------------------------- Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0 release Component: build | Version: unknown Severity: normal | Resolution: Keywords: | --------------------+---------------------------------- Changes (by lkarsten): * milestone: Varnish 4.0-TP1 => Varnish 4.0 release -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 10 11:18:26 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 10 Mar 2014 11:18:26 -0000 Subject: [Varnish] #1417: Panic on abandon in vcl_backend_response In-Reply-To: <043.208fe12b447118500afdc89eb66f6dad@varnish-cache.org> References: <043.208fe12b447118500afdc89eb66f6dad@varnish-cache.org> Message-ID: <058.cc80f9f32b8efcf80e9aaf44050dbb84@varnish-cache.org> #1417: Panic on abandon in vcl_backend_response ----------------------+---------------------------------- Reporter: fgsch | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+---------------------------------- Changes (by lkarsten): * milestone: Varnish 4.0-TP2 => Varnish 4.0 release -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 10 11:19:02 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 10 Mar 2014 11:19:02 -0000 Subject: [Varnish] #1403: n_object becomes bogus every night In-Reply-To: <043.e8ea7fcf7ae28e33640a4bf2e3f04ab9@varnish-cache.org> References: <043.e8ea7fcf7ae28e33640a4bf2e3f04ab9@varnish-cache.org> Message-ID: <058.1441b2eb08e2d834d0210be5362cfc6d@varnish-cache.org> #1403: n_object becomes bogus every night ----------------------+---------------------------------- Reporter: scoof | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+---------------------------------- Changes (by lkarsten): * milestone: Varnish 4.0-TP1 => Varnish 4.0 release -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 10 11:19:03 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 10 Mar 2014 11:19:03 -0000 Subject: [Varnish] #1444: varnishncsa with %D format not working properly In-Reply-To: <049.3ea4c3048adb96b45082c7435628b21e@varnish-cache.org> References: <049.3ea4c3048adb96b45082c7435628b21e@varnish-cache.org> Message-ID: <064.99e623ece17a074a82dadddabae49889@varnish-cache.org> #1444: varnishncsa with %D format not working properly -------------------------+-------------------- Reporter: raymondjiii | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishncsa | Version: 3.0.5 Severity: normal | Resolution: Keywords: | -------------------------+-------------------- Comment (by martin): Hi, 1) The %D format specifier was undocumented for a couple of 3.0 releases, though it should be correct in the latest 3.0.5 release. Btw., the document you link to is for 'trunk' Varnish, which will become Varnish 4.0. The 3.0.5 version of that document can be found at https://www.varnish-cache.org/docs/3.0/reference/varnishncsa.html 2) Could you confirm that it is Varnish version 3.0.5 you are seeing this on? (There are some known defects in what's to become 4.0 that will cause something similar to happen). Also, is this happening during ESI requests? Regards, Martin Blix Grydeland -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 10 14:59:08 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 10 Mar 2014 14:59:08 -0000 Subject: [Varnish] #1444: varnishncsa with %D format not working properly In-Reply-To: <049.3ea4c3048adb96b45082c7435628b21e@varnish-cache.org> References: <049.3ea4c3048adb96b45082c7435628b21e@varnish-cache.org> Message-ID: <064.7e545ba52d714c3f880c6fe6af11d11e@varnish-cache.org> #1444: varnishncsa with %D format not working properly -------------------------+-------------------- Reporter: raymondjiii | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishncsa | Version: 3.0.5 Severity: normal | Resolution: Keywords: | -------------------------+-------------------- Comment (by raymondjiii): I am definitely using Varnish 3.0.5 $ varnishd -V varnishd (varnish-3.0.5 revision 1a89b1f) Copyright (c) 2006 Verdens Gang AS Copyright (c) 2006-2011 Varnish Software AS man varnishncsa does not show the %D option though: Varnish RPMs I am using: $ rpm -qa | grep varnish varnish-docs-3.0.5-1.el5.centos varnish-3.0.5-1.el5.centos varnish-libs-3.0.5-1.el5.centos I also have other ec2 instances that use el6 with Varnish 3.0.5 and the man page shows the same thing - no %D option. For now when I see a negative response time I am converting it to positive. This is for our Varnish dashboard (Ruben saw it when he visted us at The New York Times.) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 10 14:59:36 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 10 Mar 2014 14:59:36 -0000 Subject: [Varnish] #1444: varnishncsa with %D format not working properly In-Reply-To: <049.3ea4c3048adb96b45082c7435628b21e@varnish-cache.org> References: <049.3ea4c3048adb96b45082c7435628b21e@varnish-cache.org> Message-ID: <064.1bd327bb1fff5f0c3048e6efc36cac71@varnish-cache.org> #1444: varnishncsa with %D format not working properly -------------------------+-------------------- Reporter: raymondjiii | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishncsa | Version: 3.0.5 Severity: normal | Resolution: Keywords: | -------------------------+-------------------- Comment (by raymondjiii): Sorry, there are no ESI requests. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 11 09:54:58 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 11 Mar 2014 09:54:58 -0000 Subject: [Varnish] #1445: Missing provides in varnish rpm, varnish-4.0.0-tp2+2014-03-06, fedora 19 Message-ID: <044.6a2ead7fd03370bd700a92dffb4f5e2a@varnish-cache.org> #1445: Missing provides in varnish rpm, varnish-4.0.0-tp2+2014-03-06, fedora 19 -------------------------+------------------------------------------------- Reporter: ingvar | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP2 Component: build | Version: unknown Severity: normal | Keywords: rpm specfile redhat varnish-libs | provides -------------------------+------------------------------------------------- When building 4.0.0-tp2+2014-03-06 based on the provided redhat/varnish.spec, on fedora 19 (on which rhel7 will be based), I get missing provides in varnish-libs. I don't know if these are just missing automatic provides, or that the actual APIs are missing. {{{ $ sudo rpm -Uvh varnish-4.0.0-0.3.tp2+20140306tp2.fc19.x86_64.rpm varnish- libs-4.0.0-0.3.tp2+20140306tp2.fc19.x86_64.rpm feil: Failed dependencies: libvarnishapi.so.1(LIBVARNISHAPI_1.0)(64bit) is needed by varnish-4.0.0-0.3.tp2+20140306tp2.fc19.x86_64 libvarnishapi.so.1(LIBVARNISHAPI_1.1)(64bit) is needed by varnish-4.0.0-0.3.tp2+20140306tp2.fc19.x86_64 libvarnishapi.so.1(LIBVARNISHAPI_1.2)(64bit) is needed by varnish-4.0.0-0.3.tp2+20140306tp2.fc19.x86_64 libvarnishapi.so.1(LIBVARNISHAPI_1.3)(64bit) is needed by varnish-4.0.0-0.3.tp2+20140306tp2.fc19.x86_64 rpm -qpl varnish-libs-4.0.0-0.3.tp2+20140306tp2.fc19.x86_64.rpm | grep libvarnishapi.so /usr/lib64/libvarnishapi.so.1 /usr/lib64/libvarnishapi.so.1.0.0 }}} Adding the Provides by hand makes the package at least installable: {{{ %package libs #(...) Provides: libvarnishapi.so.1(LIBVARNISHAPI_1.0)(64bit) Provides: libvarnishapi.so.1(LIBVARNISHAPI_1.1)(64bit) Provides: libvarnishapi.so.1(LIBVARNISHAPI_1.2)(64bit) Provides: libvarnishapi.so.1(LIBVARNISHAPI_1.3)(64bit) }}} Ingvar -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 11 11:54:42 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 11 Mar 2014 11:54:42 -0000 Subject: [Varnish] #1446: Varnish and PIC, failing tests, varnish-4.0.0-tp2+2014-03-06 on Fedora 19/x86_64 Message-ID: <044.b5f6b8c9362a34a38d6e4dd88a9e1f43@varnish-cache.org> #1446: Varnish and PIC, failing tests, varnish-4.0.0-tp2+2014-03-06 on Fedora 19/x86_64 --------------------+---------------------------------------- Reporter: ingvar | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP2 Component: build | Version: unknown Severity: normal | Keywords: PIC PIE hardened_build f19 --------------------+---------------------------------------- Another bug on varnish-4.0.0-tp2+2014-03-06 on Fedora 19/x86_64 When packaging Varnish for Fedora, we are encouraged to use the "_hardened_build" macro globally, which implies compiling with the PIC/PIE flags. For details, have a look at https://fedoraproject.org/wiki/Packaging:Guidelines#PIE In practice, this means that at least the following will be added to CFLAGS and LDFLAGS: {{{ CFLAGS="$CFLAGS -fPIC -Wp,-D_FORTIFY_SOURCE=2" LDFLAGS="$LDFLAGS -z" }}} Varnish compiles fine with this, but the following tests fail: {{{ FAIL: tests/a00009.vtc (exit: 2) FAIL: tests/b00041.vtc (exit: 2) FAIL: tests/c00013.vtc (exit: 2) }}} Attached bin/varnishtest/test-suite.log Ingvar -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 11 12:21:20 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 11 Mar 2014 12:21:20 -0000 Subject: [Varnish] #1446: Varnish and PIC, failing tests, varnish-4.0.0-tp2+2014-03-06 on Fedora 19/x86_64 In-Reply-To: <044.b5f6b8c9362a34a38d6e4dd88a9e1f43@varnish-cache.org> References: <044.b5f6b8c9362a34a38d6e4dd88a9e1f43@varnish-cache.org> Message-ID: <059.cdac9a04b55ce15b3c515131796c2b96@varnish-cache.org> #1446: Varnish and PIC, failing tests, varnish-4.0.0-tp2+2014-03-06 on Fedora 19/x86_64 ----------------------------------------+------------------------------ Reporter: ingvar | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP2 Component: build | Version: unknown Severity: normal | Resolution: Keywords: PIC PIE hardened_build f19 | ----------------------------------------+------------------------------ Comment (by ingvar): Uh, skip that. This was caused by missing library path fragments. I'll post back when I have actual errors. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 11 12:49:14 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 11 Mar 2014 12:49:14 -0000 Subject: [Varnish] #1446: Varnish and PIC, failing tests, varnish-4.0.0-tp2+2014-03-06 on Fedora 19/x86_64 In-Reply-To: <044.b5f6b8c9362a34a38d6e4dd88a9e1f43@varnish-cache.org> References: <044.b5f6b8c9362a34a38d6e4dd88a9e1f43@varnish-cache.org> Message-ID: <059.4a1f22f98d59c7e17aebb810251fbe40@varnish-cache.org> #1446: Varnish and PIC, failing tests, varnish-4.0.0-tp2+2014-03-06 on Fedora 19/x86_64 ----------------------------------------+------------------------------ Reporter: ingvar | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP2 Component: build | Version: unknown Severity: normal | Resolution: Keywords: PIC PIE hardened_build f19 | ----------------------------------------+------------------------------ Comment (by ingvar): Ran make check with {{{ LD_LIBRARY_PATH="%{buildroot}%{_libdir}:%{buildroot}%{_libdir}/%{name}" }}} and the whole test suite ran without problems. You can close this ticket. Ingvar -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 12 09:31:58 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 12 Mar 2014 09:31:58 -0000 Subject: [Varnish] #1447: Panic message: Assert error in http_Write Message-ID: <046.4d292c524c5bcf6e4c46bbf1ff236ca0@varnish-cache.org> #1447: Panic message: Assert error in http_Write -------------------------------------+---------------------- Reporter: scorillo | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: 3.0.5 | Severity: major Keywords: panic assert http_write | -------------------------------------+---------------------- Varnish child dies multiple times a day. This happens on varnish versions 3.0.4 and 3.0.5 Find attached a few lines of /var/log/messages and the last panic. Other relevant informations: root 28579 0.0 0.0 113320 2224 ? Ss Feb18 0:39 /usr/sbin/varnishd -P /var/run/varnish-front.pid -a :80 -f /etc/varnish/front.vcl -T 127.0.0.1:6081 -t 120 -w 50,1000,120 -u varnish -g varnish -S /etc/varnish/secret -s malloc,2G -p http_req_hdr_len=16384 -p http_req_size=65536 -p http_resp_hdr_len=16384 -p http_resp_size=65536 -p sess_workspace=131072 -p sess_timeout=13 -p cli_timeout=15 -n front -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 12 11:34:43 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 12 Mar 2014 11:34:43 -0000 Subject: [Varnish] #1448: Segfault in jemalloc Message-ID: <046.4c03ddaddd5fbdf6a4f5e15b03fc8d18@varnish-cache.org> #1448: Segfault in jemalloc ----------------------+------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.5 Severity: normal | Keywords: ----------------------+------------------- {{{ Mar 11 xx:xx:xx kernel: varnishd[1257]: segfault at 0 ip 000000000045831d sp 00007fa98cdf9df0 error 4 in varnishd[400000+7a000] }}} {{{ #0 arena_dalloc_small (ptr=0x7fa940000bc0) at jemalloc_linux.c:3687 #1 arena_dalloc (ptr=0x7fa940000bc0) at jemalloc_linux.c:3939 #2 idalloc (ptr=0x7fa940000bc0) at jemalloc_linux.c:3957 #3 free (ptr=0x7fa940000bc0) at jemalloc_linux.c:5586 Cannot access memory at address 0x7fa98cdf9e38 }}} daghf dug up these seemingly related resources: http://99designs.com/tech-blog/blog/2014/01/30/debugging-varnish/ http://lists.freebsd.org/pipermail/freebsd- current/2010-January/015138.html Short version: our embedded jemalloc version has a bug. I find it a bit odd that we haven't seen this until now. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 12 13:05:43 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 12 Mar 2014 13:05:43 -0000 Subject: [Varnish] #1448: Segfault in jemalloc In-Reply-To: <046.4c03ddaddd5fbdf6a4f5e15b03fc8d18@varnish-cache.org> References: <046.4c03ddaddd5fbdf6a4f5e15b03fc8d18@varnish-cache.org> Message-ID: <061.bb80b08f06fac5ae196e09980eac7297@varnish-cache.org> #1448: Segfault in jemalloc ----------------------+-------------------------------------------- Reporter: lkarsten | Owner: Lasse Karstensen Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 3.0.5 Severity: normal | Resolution: fixed Keywords: | ----------------------+-------------------------------------------- Changes (by Lasse Karstensen ): * status: new => closed * owner: => Lasse Karstensen * resolution: => fixed Comment: In [f6f75eac911a433f86ce28df9f2a8f489eed3503]: {{{ #!CommitTicketReference repository="" revision="f6f75eac911a433f86ce28df9f2a8f489eed3503" Fix varnishd segfault in jemalloc's arena_dalloc() Merging tiny patch from: http://lists.freebsd.org/pipermail/freebsd- current/2010-January/015138.html Fixes: #1448 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 12 16:07:28 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 12 Mar 2014 16:07:28 -0000 Subject: [Varnish] #1447: Panic message: Assert error in http_Write In-Reply-To: <046.4d292c524c5bcf6e4c46bbf1ff236ca0@varnish-cache.org> References: <046.4d292c524c5bcf6e4c46bbf1ff236ca0@varnish-cache.org> Message-ID: <061.222188326fd698195cf75f9c9a37f7e5@varnish-cache.org> #1447: Panic message: Assert error in http_Write -------------------------------------+-------------------- Reporter: scorillo | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.5 Severity: major | Resolution: Keywords: panic assert http_write | -------------------------------------+-------------------- Description changed by lkarsten: Old description: > Varnish child dies multiple times a day. > This happens on varnish versions 3.0.4 and 3.0.5 > > Find attached a few lines of /var/log/messages and the last panic. > > Other relevant informations: > > root 28579 0.0 0.0 113320 2224 ? Ss Feb18 0:39 > /usr/sbin/varnishd -P /var/run/varnish-front.pid -a :80 -f > /etc/varnish/front.vcl -T 127.0.0.1:6081 -t 120 -w 50,1000,120 -u varnish > -g varnish -S /etc/varnish/secret -s malloc,2G -p http_req_hdr_len=16384 > -p http_req_size=65536 -p http_resp_hdr_len=16384 -p http_resp_size=65536 > -p sess_workspace=131072 -p sess_timeout=13 -p cli_timeout=15 -n front New description: Varnish child dies multiple times a day. This happens on varnish versions 3.0.4 and 3.0.5 Find attached a few lines of /var/log/messages and the last panic. Other relevant informations: {{{ root 28579 0.0 0.0 113320 2224 ? Ss Feb18 0:39 /usr/sbin/varnishd -P /var/run/varnish-front.pid -a :80 -f /etc/varnish/front.vcl -T 127.0.0.1:6081 -t 120 -w 50,1000,120 -u varnish -g varnish -S /etc/varnish/secret -s malloc,2G -p http_req_hdr_len=16384 -p http_req_size=65536 -p http_resp_hdr_len=16384 -p http_resp_size=65536 -p sess_workspace=131072 -p sess_timeout=13 -p cli_timeout=15 -n front }}} -- -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 13 11:47:01 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 13 Mar 2014 11:47:01 -0000 Subject: [Varnish] #1449: Assert error in ban_check_object(), cache/cache_ban.c line 915 Message-ID: <046.7113ebd1ce10ac27acc0986067f77f64@varnish-cache.org> #1449: Assert error in ban_check_object(), cache/cache_ban.c line 915 ----------------------+--------------------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+--------------------------------- The fryer-medialibrary job found a varnish master (gitref f2a0acec1566a38bdd41101773bf053cb6d103f3) panic. Fryer jobs have not been run for a while. 3 panics in the 2 hour run. Varnish is sending 180MB/s (maxing out our bundled 1G links) with minuscule 50-60 req/s. {{{ Last panic at: Thu, 13 Mar 2014 10:23:37 GMT Assert error in ban_check_object(), cache/cache_ban.c line 915: Condition((oc->ban) != NULL) not true. thread = (cache-worker) ident = Linux,3.2.0-51-generic,x86_64,-smalloc,-smalloc,-hcritbit,epoll Backtrace: 0x439cea: pan_backtrace+0x19 0x439ffb: pan_ic+0x1e9 0x416045: ban_check_object+0x1a5 0x416441: BAN_CheckObject+0x35 0x42a822: HSH_Lookup+0x734 0x43d894: cnt_lookup+0x227 0x43fc9e: CNT_Request+0x441 0x433035: HTTP1_Session+0x427 0x442d05: ses_req_pool_task+0x166 0x43b8d8: Pool_Work_Thread+0x416 req = 0x7f5fccb6bce0 { sp = 0x7f5fc1373570, vxid = 1076956506, step = R_STP_LOOKUP, req_body = R_BODY_NONE, restarts = 0, esi_level = 0 sp = 0x7f5fc1373570 { fd = 63, vxid = 3214681, client = 194.31.39.161 36497, step = S_STP_WORKING, }, worker = 0x7f5fe3b66c70 { ws = 0x7f5fe3b66e70 { id = "wrk", {s,f,r,e} = {0x7f5fe3b66420,0x7f5fe3b66420,(nil),+2048}, }, VCL::method = 0x0, VCL::return = lookup, }, ws = 0x7f5fccb6be60 { id = "req", {s,f,r,e} = {0x7f5fccb6dcb8,+272,+57384,+57384}, }, http[req] = { ws = 0x7f5fccb6be60[req] "GET", "/cacheabledata/set_medialibrary1/file295.bin", "HTTP/1.1", "Host: fryer1.varnish-software.com:6081", "Accept: */*", "Accept-Encoding: gzip", "User-Agent: Mozilla/5.0 (unknown-x86_64-linux-gnu) Siege/3.0.4", "Connection: close", "X-Forwarded-For: 194.31.39.161", }, vcl = { srcname = { "input", "Default", }, }, }, }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 13 13:55:22 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 13 Mar 2014 13:55:22 -0000 Subject: [Varnish] #1449: Assert error in ban_check_object(), cache/cache_ban.c line 915 In-Reply-To: <046.7113ebd1ce10ac27acc0986067f77f64@varnish-cache.org> References: <046.7113ebd1ce10ac27acc0986067f77f64@varnish-cache.org> Message-ID: <061.d21d92cbf4f64fe280752b21007f663c@varnish-cache.org> #1449: Assert error in ban_check_object(), cache/cache_ban.c line 915 ----------------------+---------------------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+---------------------------------- Comment (by lkarsten): Also, this testset does not use bans at all. The ban list is empty. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 14 09:25:16 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 14 Mar 2014 09:25:16 -0000 Subject: [Varnish] #1449: Assert error in ban_check_object(), cache/cache_ban.c line 915 In-Reply-To: <046.7113ebd1ce10ac27acc0986067f77f64@varnish-cache.org> References: <046.7113ebd1ce10ac27acc0986067f77f64@varnish-cache.org> Message-ID: <061.4499aa52f55b4ebd9d4ff127e07ff96f@varnish-cache.org> #1449: Assert error in ban_check_object(), cache/cache_ban.c line 915 ----------------------+---------------------------------------- Reporter: lkarsten | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+---------------------------------------- Changes (by Poul-Henning Kamp ): * owner: => Poul-Henning Kamp * status: new => closed * resolution: => fixed Comment: In [b135934f9eace9bc281b3e727f37dfd302170fa8]: {{{ #!CommitTicketReference repository="" revision="b135934f9eace9bc281b3e727f37dfd302170fa8" Fix a race when we Unbusy and abandonned oc which has no object. Fixes #1449 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 14 10:50:03 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 14 Mar 2014 10:50:03 -0000 Subject: [Varnish] #1450: Segfault in varnishstat with -l Message-ID: <046.cb082f0af3196092e65f34d669884e8d@varnish-cache.org> #1450: Segfault in varnishstat with -l -------------------------+------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: low | Milestone: Component: varnishstat | Version: trunk Severity: normal | Keywords: -------------------------+------------------- {{{ root at sierra:~# /opt/varnish/bin/varnishstat -f MAIN.shm_writes -l Varnishstat -f option fields: Field name Description ---------- ----------- Segmentation fault (core dumped) root at sierra:~# root at sierra:~# /opt/varnish/bin/varnishstat -V varnishstat (varnish-4.0.0-tp2 revision aa8c6e3) Copyright (c) 2006 Verdens Gang AS Copyright (c) 2006-2011 Varnish Software AS }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 14 11:57:18 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 14 Mar 2014 11:57:18 -0000 Subject: [Varnish] #1450: Segfault in varnishstat with -l In-Reply-To: <046.cb082f0af3196092e65f34d669884e8d@varnish-cache.org> References: <046.cb082f0af3196092e65f34d669884e8d@varnish-cache.org> Message-ID: <061.00ea6f87d811812010f3cc2ec64be9c8@varnish-cache.org> #1450: Segfault in varnishstat with -l -------------------------+-------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: low | Milestone: Component: varnishstat | Version: trunk Severity: normal | Resolution: Keywords: | -------------------------+-------------------- Comment (by daghf): {{{ (gdb) run Starting program: /opt/varnish4-git/bin/varnishstat -f MAIN.shm_writes -n /tmp/foo -l [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Varnishstat -f option fields: Field name Description ---------- ----------- Program received signal SIGSEGV, Segmentation fault. 0x0000000000402b9c in do_list_cb (priv=0x0, pt=0x0) at varnishstat.c:213 213 sec = pt->section; (gdb) bt #0 0x0000000000402b9c in do_list_cb (priv=0x0, pt=0x0) at varnishstat.c:213 #1 0x00007ffff79c644e in VSC_Iter (vd=0x609010, fantom=0x0, func=0x402b80 , priv=0x0) at vsc.c:516 #2 0x000000000040201d in list_fields (vd=0x609010) at varnishstat.c:233 #3 0x0000000000401d65 in main (argc=6, argv=0x7fffffffe1b8) at varnishstat.c:282 (gdb) }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 17 11:01:07 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 17 Mar 2014 11:01:07 -0000 Subject: [Varnish] #1450: Segfault in varnishstat with -l In-Reply-To: <046.cb082f0af3196092e65f34d669884e8d@varnish-cache.org> References: <046.cb082f0af3196092e65f34d669884e8d@varnish-cache.org> Message-ID: <061.6ea45b96052cf93eea732f88a1734db0@varnish-cache.org> #1450: Segfault in varnishstat with -l -------------------------+--------------------- Reporter: lkarsten | Owner: martin Type: defect | Status: new Priority: low | Milestone: Component: varnishstat | Version: trunk Severity: normal | Resolution: Keywords: | -------------------------+--------------------- Changes (by martin): * owner: => martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 17 12:23:33 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 17 Mar 2014 12:23:33 -0000 Subject: [Varnish] #1451: p00009.vtc is fragile Message-ID: <046.a43cd06901bb6cec45f2384dcd13c80d@varnish-cache.org> #1451: p00009.vtc is fragile -------------------------+------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishtest | Version: trunk Severity: minor | Keywords: -------------------------+------------------- p00009.vtc failed after a documentation commit just now. (793d67ad) Make check works fine on my clean tree. {{{ FAIL: tests/p00009.vtc (exit: 2) ================================ **** top 0.0 macro def varnishd=varnishd **** top 0.0 macro def varnishadm=varnishadm **** top 0.0 macro def varnishstat=varnishstat **** top 0.0 macro def varnishhist=varnishhist **** top 0.0 macro def varnishlog=varnishlog **** top 0.0 macro def varnishncsa=varnishncsa **** top 0.0 macro def vmod_std=std from "/var/lib/jenkins/jobs/varnish- master- src/workspace/varnish-4.0.0-tp2/_build/lib/libvmod_std/.libs/libvmod_std.so" **** top 0.0 macro def vmod_debug=debug from "/var/lib/jenkins/jobs /varnish-master- src/workspace/varnish-4.0.0-tp2/_build/lib/libvmod_debug/.libs/libvmod_debug.so" **** top 0.0 macro def vmod_directors=directors from "/var/lib/jenkins/jobs/varnish-master- src/workspace/varnish-4.0.0-tp2/_build/lib/libvmod_directors/.libs/libvmod_directors.so" **** top 0.0 macro def pwd=/var/lib/jenkins/jobs/varnish-master- src/workspace/varnish-4.0.0-tp2/_build/bin/varnishtest **** top 0.0 macro def topbuild=/var/lib/jenkins/jobs/varnish-master- src/workspace/varnish-4.0.0-tp2/_build **** top 0.0 macro def bad_ip=192.0.2.255 **** top 0.0 macro def tmpdir=/tmp/vtc.8405.4fdaaca5 * top 0.0 TEST ../../../bin/varnishtest/tests/p00009.vtc starting *** top 0.0 varnishtest * top 0.0 TEST Check that reloaded bans with completed flag are really completed on restart *** top 0.0 shell **** top 0.0 shell| rm -f /tmp/vtc.8405.4fdaaca5/_.per[12] *** top 0.0 server ** s1 0.0 Starting server **** s1 0.0 macro def s1_addr=127.0.0.1 **** s1 0.0 macro def s1_port=42265 **** s1 0.0 macro def s1_sock=127.0.0.1 42265 * s1 0.0 Listen on 127.0.0.1 42265 *** top 0.0 varnish ** s1 0.0 Started on 127.0.0.1 42265 ** v1 0.0 Launch *** v1 0.0 CMD: cd ${pwd} && ${varnishd} -d -d -n /tmp/vtc.8405.4fdaaca5/v1 -l 2m,1m,- -p auto_restart=off -p syslog_cli_traffic=off -p sigsegv_handler=on -a '127.0.0.1:0' -M '127.0.0.1 54701' -P /tmp/vtc.8405.4fdaaca5/v1/varnishd.pid -pfeature=+wait_silo -pban_lurker_sleep=0 -sper1=persistent,/tmp/vtc.8405.4fdaaca5/_.per1,10m -sper2=persistent,/tmp/vtc.8405.4fdaaca5/_.per2,10m *** v1 0.0 CMD: cd /var/lib/jenkins/jobs/varnish-master- src/workspace/varnish-4.0.0-tp2/_build/bin/varnishtest && varnishd -d -d -n /tmp/vtc.8405.4fdaaca5/v1 -l 2m,1m,- -p auto_restart=off -p syslog_cli_traffic=off -p sigsegv_handler=on -a '127.0.0.1:0' -M '127.0.0.1 54701' -P /tmp/vtc.8405.4fdaaca5/v1/varnishd.pid -pfeature=+wait_silo -pban_lurker_sleep=0 -sper1=persistent,/tmp/vtc.8405.4fdaaca5/_.per1,10m -sper2=persistent,/tmp/vtc.8405.4fdaaca5/_.per2,10m *** v1 0.0 PID: 8447 *** v1 0.0 debug| sizeof(struct smp_ident) = 112 = 0x70\n *** v1 0.0 debug| sizeof(struct smp_sign) = 32 = 0x20\n *** v1 0.0 debug| sizeof(struct smp_segptr) = 32 = 0x20\n *** v1 0.0 debug| sizeof(struct smp_object) = 56 = 0x38\n *** v1 0.0 debug| CHK(0x24b7a58 SILO 0x2b38f0420000 ) = 1\n *** v1 0.0 debug| Warning SILO (/tmp/vtc.8405.4fdaaca5/_.per1) not reloaded (reason=1)\n *** v1 0.1 debug| min_nseg = 10, max_segl = 628729\n *** v1 0.1 debug| max_nseg = 26212, min_segl = 239\n *** v1 0.1 debug| aim_nseg = 511, aim_segl = 12303\n *** v1 0.1 debug| free_reserve = 123030\n *** v1 0.1 debug| sizeof(struct smp_ident) = 112 = 0x70\n *** v1 0.1 debug| sizeof(struct smp_sign) = 32 = 0x20\n *** v1 0.1 debug| sizeof(struct smp_segptr) = 32 = 0x20\n *** v1 0.1 debug| sizeof(struct smp_object) = 56 = 0x38\n *** v1 0.1 debug| CHK(0x24b7ee8 SILO 0x2b38f0e20000 ) = 1\n *** v1 0.1 debug| Warning SILO (/tmp/vtc.8405.4fdaaca5/_.per2) not reloaded (reason=1)\n *** v1 0.1 debug| min_nseg = 10, max_segl = 628729\n *** v1 0.1 debug| max_nseg = 26212, min_segl = 239\n *** v1 0.1 debug| aim_nseg = 511, aim_segl = 12303\n *** v1 0.1 debug| free_reserve = 123030\n *** v1 0.2 debug| Platform: Linux,3.2.0-60-virtual,x86_64,-spersistent,-spersistent,-smalloc,-hcritbit\n *** v1 0.2 debug| 200 296 \n *** v1 0.2 debug| -----------------------------\n *** v1 0.2 debug| Varnish Cache CLI 1.0\n *** v1 0.2 debug| -----------------------------\n *** v1 0.2 debug| Linux,3.2.0-60-virtual,x86_64,-spersistent,-spersistent,-smalloc,-hcritbit\n *** v1 0.2 debug| varnish-4.0.0-tp2 revision 793d67a\n *** v1 0.2 debug| \n *** v1 0.2 debug| Type 'help' for command list.\n *** v1 0.2 debug| Type 'quit' to close CLI session.\n *** v1 0.2 debug| Type 'start' to launch worker process.\n *** v1 0.2 debug| \n **** v1 0.3 CLIPOLL 1 0x1 0x0 *** v1 0.3 CLI connection fd = 9 *** v1 0.3 CLI RX 107 **** v1 0.3 CLI RX| sdwmwtdxomqprgyvfqbwzmqzkqdjlieg\n **** v1 0.3 CLI RX| \n **** v1 0.3 CLI RX| Authentication required.\n **** v1 0.3 CLI TX| auth f0d6f51cb680dc1c21582f30a9c861c94d9d2e055d5ece86f7e56ca779079a3a\n *** v1 0.3 CLI RX 200 **** v1 0.3 CLI RX| -----------------------------\n **** v1 0.3 CLI RX| Varnish Cache CLI 1.0\n **** v1 0.3 CLI RX| -----------------------------\n **** v1 0.3 CLI RX| Linux,3.2.0-60-virtual,x86_64,-spersistent,-spersistent,-smalloc,-hcritbit\n **** v1 0.3 CLI RX| varnish-4.0.0-tp2 revision 793d67a\n **** v1 0.3 CLI RX| \n **** v1 0.3 CLI RX| Type 'help' for command list.\n **** v1 0.3 CLI RX| Type 'quit' to close CLI session.\n **** v1 0.3 CLI RX| Type 'start' to launch worker process.\n **** v1 0.3 CLI TX| vcl.inline vcl1 << %XJEIFLH|)Xspa8P\n **** v1 0.3 CLI TX| vcl 4.0;\n **** v1 0.3 CLI TX| backend s1 { .host = "127.0.0.1"; .port = "42265"; }\n **** v1 0.3 CLI TX| \n **** v1 0.3 CLI TX| \n **** v1 0.3 CLI TX| \t\n **** v1 0.3 CLI TX| %XJEIFLH|)Xspa8P\n *** v1 0.4 CLI RX 200 **** v1 0.4 CLI RX| Message from VCC-compiler:\n **** v1 0.4 CLI RX| Not running as root, no priv-sep\n **** v1 0.4 CLI RX| Message from C-compiler:\n **** v1 0.4 CLI RX| Not running as root, no priv-sep\n **** v1 0.4 CLI RX| Message from dlopen:\n **** v1 0.4 CLI RX| Not running as root, no priv-sep\n **** v1 0.4 CLI RX| \n **** v1 0.4 CLI RX| VCL compiled. **** v1 0.4 CLI TX| vcl.use vcl1 *** v1 0.4 CLI RX 200 **** v1 0.4 CLI RX| VCL 'vcl1' now active *** top 0.4 varnish ** v1 0.4 Start **** v1 0.4 CLI TX| start *** v1 0.5 debug| child (9322) Started\n **** v1 0.6 vsl| 0 CLI - Rd vcl.load "vcl1" ./vcl.lU8d_9fm.so *** v1 0.6 CLI RX 200 *** v1 0.6 wait-running **** v1 0.6 CLI TX| status *** v1 0.6 debug| Child (9322) said Not running as root, no priv-sep\n *** v1 0.6 debug| Child (9322) said Child starts\n *** v1 0.6 debug| Child (9322) said Wrapped silo\n *** v1 0.6 debug| Child (9322) said Wrapped silo\n *** v1 0.6 debug| Child (9322) said Silo completely loaded\n *** v1 0.6 debug| Child (9322) said Silo completely loaded\n *** v1 0.6 CLI RX 200 **** v1 0.6 CLI RX| Child in state running **** v1 0.6 CLI TX| debug.xid 999 **** v1 0.6 vsl| 0 CLI - Wr 200 36 Loaded "./vcl.lU8d_9fm.so" as "vcl1" **** v1 0.6 vsl| 0 CLI - Rd vcl.use "vcl1" **** v1 0.6 vsl| 0 CLI - Wr 200 0 **** v1 0.6 vsl| 0 CLI - Rd start **** v1 0.6 vsl| 0 CLI - Wr 200 0 *** v1 0.6 CLI RX 200 **** v1 0.6 CLI RX| XID is 999 **** v1 0.6 CLI TX| debug.listen_address **** v1 0.6 vsl| 0 CLI - Rd debug.xid 999 **** v1 0.6 vsl| 0 CLI - Wr 200 10 XID is 999 *** v1 0.6 CLI RX 200 **** v1 0.6 CLI RX| 127.0.0.1 49091\n ** v1 0.6 Listen on 127.0.0.1 49091 **** v1 0.6 macro def v1_addr=127.0.0.1 **** v1 0.6 macro def v1_port=49091 **** v1 0.6 macro def v1_sock=127.0.0.1 49091 *** top 0.6 client ** c1 0.6 Starting client ** c1 0.6 Waiting for client *** c1 0.6 Connect to 127.0.0.1 49091 *** c1 0.6 connected fd 10 from 127.0.0.1 35269 to 127.0.0.1 49091 *** c1 0.6 txreq **** c1 0.6 txreq| GET / HTTP/1.1\r\n **** c1 0.6 txreq| \r\n *** c1 0.6 rxresp *** s1 0.6 accepted fd 4 *** s1 0.6 rxreq **** s1 0.6 rxhdr| GET / HTTP/1.1\r\n **** s1 0.6 rxhdr| X-Forwarded-For: 127.0.0.1\r\n **** s1 0.6 rxhdr| Accept-Encoding: gzip\r\n **** s1 0.6 rxhdr| X-Varnish: 1002\r\n **** s1 0.6 rxhdr| Host: 127.0.0.1\r\n **** s1 0.6 rxhdr| \r\n **** s1 0.6 http[ 0] | GET **** s1 0.6 http[ 1] | / **** s1 0.6 http[ 2] | HTTP/1.1 **** s1 0.6 http[ 3] | X-Forwarded-For: 127.0.0.1 **** s1 0.6 http[ 4] | Accept-Encoding: gzip **** s1 0.6 http[ 5] | X-Varnish: 1002 **** s1 0.6 http[ 6] | Host: 127.0.0.1 **** s1 0.6 bodylen = 0 *** s1 0.6 txresp **** s1 0.6 txresp| HTTP/1.1 200 Ok\r\n **** s1 0.6 txresp| x-foo: foo\r\n **** s1 0.6 txresp| Content-Length: 0\r\n **** s1 0.6 txresp| \r\n *** s1 0.6 accept **** s1 0.6 Accepting **** c1 0.6 rxhdr| HTTP/1.1 200 Ok\r\n **** c1 0.6 rxhdr| x-foo: foo\r\n **** c1 0.6 rxhdr| Date: Mon, 17 Mar 2014 12:13:19 GMT\r\n **** c1 0.6 rxhdr| X-Varnish: 1001\r\n **** c1 0.6 rxhdr| Age: 0\r\n **** c1 0.6 rxhdr| Via: 1.1 varnish\r\n **** c1 0.6 rxhdr| Content-Length: 0\r\n **** c1 0.6 rxhdr| Connection: keep-alive\r\n **** c1 0.6 rxhdr| Accept-Ranges: bytes\r\n **** c1 0.6 rxhdr| \r\n **** c1 0.6 http[ 0] | HTTP/1.1 **** c1 0.6 http[ 1] | 200 **** c1 0.6 http[ 2] | Ok **** c1 0.6 http[ 3] | x-foo: foo **** c1 0.6 http[ 4] | Date: Mon, 17 Mar 2014 12:13:19 GMT **** c1 0.6 http[ 5] | X-Varnish: 1001 **** c1 0.6 http[ 6] | Age: 0 **** c1 0.6 http[ 7] | Via: 1.1 varnish **** c1 0.6 http[ 8] | Content-Length: 0 **** c1 0.6 http[ 9] | Connection: keep-alive **** c1 0.6 http[10] | Accept-Ranges: bytes **** c1 0.6 bodylen = 0 *** c1 0.6 expect **** c1 0.6 EXPECT resp.http.x-foo (foo) == "foo" match *** c1 0.6 closing fd 10 ** c1 0.6 Ending *** top 0.6 varnish **** v1 0.6 CLI TX| ban req.url == /test **** v1 0.6 vsl| 0 CLI - Rd debug.listen_address **** v1 0.6 vsl| 0 CLI - Wr 200 16 127.0.0.1 49091 **** v1 0.6 vsl| 1000 Begin c sess 0 HTTP/1 **** v1 0.6 vsl| 1000 SessOpen c 127.0.0.1 35269 127.0.0.1:0 127.0.0.1 49091 1395058399.582462 13 **** v1 0.6 vsl| 1000 Link c req 1001 rxreq **** v1 0.6 vsl| 1002 Begin b bereq 1001 fetch **** v1 0.6 vsl| 1002 BereqMethod b GET **** v1 0.6 vsl| 1002 BereqURL b / **** v1 0.6 vsl| 1002 BereqProtocol b HTTP/1.1 **** v1 0.6 vsl| 1002 BereqHeader b X-Forwarded-For: 127.0.0.1 **** v1 0.6 vsl| 1002 BereqHeader b Accept-Encoding: gzip **** v1 0.6 vsl| 1002 BereqHeader b X-Varnish: 1002 **** v1 0.6 vsl| 1002 VCL_call b BACKEND_FETCH **** v1 0.6 vsl| 1002 VCL_return b fetch **** v1 0.6 vsl| 1002 BackendOpen b 16 s1(127.0.0.1,,42265) 127.0.0.1 54416 **** v1 0.6 vsl| 1002 Backend b 16 s1 s1(127.0.0.1,,42265) **** v1 0.6 vsl| 1002 BereqHeader b Host: 127.0.0.1 **** v1 0.6 vsl| 1002 BerespProtocol b HTTP/1.1 **** v1 0.6 vsl| 1002 BerespStatus b 200 **** v1 0.6 vsl| 1002 BerespResponse b Ok **** v1 0.6 vsl| 1002 BerespHeader b x-foo: foo **** v1 0.6 vsl| 1002 BerespHeader b Content-Length: 0 **** v1 0.6 vsl| 1002 TTL b RFC 20 -1 -1 1395058400 1395058400 0 0 0 **** v1 0.6 vsl| 1002 VCL_call b BACKEND_RESPONSE **** v1 0.6 vsl| 1002 VCL_return b deliver **** v1 0.6 vsl| 1002 Storage b persistent per2 **** v1 0.6 vsl| 1002 ObjProtocol b HTTP/1.1 **** v1 0.6 vsl| 1002 ObjStatus b 200 **** v1 0.6 vsl| 1002 ObjResponse b Ok **** v1 0.6 vsl| 1002 ObjHeader b x-foo: foo **** v1 0.6 vsl| 1002 Fetch_Body b 3 length stream **** v1 0.6 vsl| 1002 BackendReuse b 16 s1(127.0.0.1,,42265) **** v1 0.6 vsl| 1002 Length b 0 **** v1 0.6 vsl| 1002 BereqEnd b 1395058399.583058596 1395058399.583804369 0.000028228 0.000366001 0.000046941 0.000412942 **** v1 0.6 vsl| 1002 End b **** v1 0.6 vsl| 0 ExpKill - EXP_Inbox p=0x2b3928000950 e=0.000000000 f=0x1c10 **** v1 0.6 vsl| 0 ExpKill - EXP_When p=0x2b3928000950 e=1395058429.582860470 f=0x1c10 **** v1 0.6 vsl| 1001 Begin c req 1000 rxreq **** v1 0.6 vsl| 1001 ReqStart c 127.0.0.1 35269 **** v1 0.6 vsl| 1001 ReqMethod c GET **** v1 0.6 vsl| 1001 ReqURL c / **** v1 0.6 vsl| 1001 ReqProtocol c HTTP/1.1 **** v1 0.6 vsl| 1001 VCL_call c RECV **** v1 0.6 vsl| 1001 ReqHeader c X-Forwarded-For: 127.0.0.1 **** v1 0.6 vsl| 1001 VCL_return c hash **** v1 0.6 vsl| 1001 VCL_call c HASH **** v1 0.6 vsl| 1001 VCL_return c lookup **** v1 0.6 vsl| 1001 Debug c XXXX MISS **** v1 0.6 vsl| 1001 VCL_call c MISS **** v1 0.6 vsl| 1001 VCL_return c fetch **** v1 0.6 vsl| 1001 Link c bereq 1002 fetch **** v1 0.6 vsl| 1001 RespProtocol c HTTP/1.1 **** v1 0.6 vsl| 1001 RespStatus c 200 **** v1 0.6 vsl| 1001 RespResponse c Ok **** v1 0.6 vsl| 1001 RespHeader c x-foo: foo **** v1 0.6 vsl| 1001 RespHeader c Date: Mon, 17 Mar 2014 12:13:19 GMT **** v1 0.6 vsl| 1001 RespHeader c X-Varnish: 1001 **** v1 0.6 vsl| 1001 RespHeader c Age: 0 **** v1 0.6 vsl| 1001 RespHeader c Via: 1.1 varnish **** v1 0.6 vsl| 1001 VCL_call c DELIVER **** v1 0.6 vsl| 1001 VCL_return c deliver **** v1 0.6 vsl| 1001 RespHeader c Content-Length: 0 **** v1 0.6 vsl| 1001 Debug c RES_MODE 2 **** v1 0.6 vsl| 1001 RespHeader c Connection: keep-alive **** v1 0.6 vsl| 1001 RespHeader c Accept-Ranges: bytes **** v1 0.6 vsl| 1001 Debug c XXX REF 2 **** v1 0.6 vsl| 1001 Length c 0 **** v1 0.6 vsl| 1001 ReqEnd c 1395058399.582860470 1395058399.582461596 -0.001381636 0.000982761 -0.001381636 **** v1 0.6 vsl| 1001 End c **** v1 0.6 vsl| 1000 SessClose c REM_CLOSE 0.002 1 0 0 1 1 0 **** v1 0.6 vsl| 1000 End c *** v1 0.7 CLI RX 200 ** v1 0.7 CLI 200 *** top 0.7 varnish **** v1 0.7 CLI TX| ban req.url == /test **** v1 0.7 vsl| 0 CLI - Rd ban req.url == /test **** v1 0.7 vsl| 0 CLI - Wr 200 0 *** v1 0.7 CLI RX 200 ** v1 0.7 CLI 200 *** top 0.7 varnish **** v1 0.7 CLI TX| ban.list **** v1 0.7 vsl| 0 CLI - Rd ban req.url == /test **** v1 0.7 vsl| 0 CLI - Wr 200 0 *** v1 0.8 CLI RX 200 **** v1 0.8 CLI RX| Present bans:\n **** v1 0.8 CLI RX| 1395058399.661653 0 req.url == /test\n **** v1 0.8 CLI RX| 1395058399.621650 0 C \n **** v1 0.8 CLI RX| 1395058399.431171 1 C \n ** v1 0.8 CLI 200 *** top 0.8 varnish ** v1 0.8 as expected: bans (3) == 3 *** top 0.8 varnish ** v1 0.8 as expected: bans_dups (1) == 1 *** top 0.8 varnish ** v1 0.8 as expected: bans_completed (2) == 2 *** top 0.8 varnish **** v1 0.8 macro undef v1_addr **** v1 0.8 macro undef v1_port **** v1 0.8 macro undef v1_sock ** v1 0.8 Stop **** v1 0.8 CLI TX| stop **** v1 0.8 vsl| 0 CLI - Rd ban.list **** v1 0.8 vsl| 0 CLI - Wr 200 114 Present bans: 1395058399.661653 0 req.url == /test 1395058399.621650 0 C 1395058399.431171 1 C *** v1 0.8 debug| Stopping Child\n **** v1 0.8 vsl| 0 CLI - EOF on CLI connection, worker stops *** v1 1.8 debug| Child (9322) died status=1\n *** v1 1.8 debug| Child (9322) said Child dies\n *** v1 1.8 debug| Child cleanup complete\n *** v1 1.8 CLI RX 200 **** v1 1.8 CLI TX| status *** v1 1.9 CLI RX 200 **** v1 1.9 CLI RX| Child in state stopped *** top 1.9 varnish ** v1 1.9 Start **** v1 1.9 CLI TX| start *** v1 1.9 debug| child (11852) Started\n **** v1 1.9 vsl| 0 ExpKill - EXP_Inbox p=0x2b390c0008c0 e=1395058429.582860470 f=0x1830 **** v1 1.9 vsl| 0 ExpKill - EXP_When p=0x2b390c0008c0 e=1395058429.582860470 f=0x1830 **** v1 2.9 vsl| 0 CLI - Rd vcl.load "vcl1" ./vcl.lU8d_9fm.so **** v1 2.9 vsl| 0 CLI - Wr 200 36 Loaded "./vcl.lU8d_9fm.so" as "vcl1" **** v1 2.9 vsl| 0 CLI - Rd vcl.use "vcl1" **** v1 2.9 vsl| 0 CLI - Wr 200 0 *** v1 2.9 CLI RX 200 *** v1 2.9 wait-running **** v1 2.9 CLI TX| status *** v1 2.9 debug| Child (11852) said Not running as root, no priv- sep\n *** v1 2.9 debug| Child (11852) said Child starts\n *** v1 2.9 debug| Child (11852) said Wrapped silo\n *** v1 2.9 debug| Child (11852) said Silo completely loaded\n *** v1 2.9 debug| Child (11852) said Dropped 0 segments to make free_reserve\n *** v1 2.9 debug| Child (11852) said Silo completely loaded\n *** v1 2.9 CLI RX 200 **** v1 2.9 CLI RX| Child in state running **** v1 2.9 CLI TX| debug.xid 999 **** v1 2.9 vsl| 0 CLI - Rd start **** v1 2.9 vsl| 0 CLI - Wr 200 0 *** v1 3.0 CLI RX 200 **** v1 3.0 CLI RX| XID is 999 **** v1 3.0 CLI TX| debug.listen_address **** v1 3.0 vsl| 0 CLI - Rd debug.xid 999 **** v1 3.0 vsl| 0 CLI - Wr 200 10 XID is 999 *** v1 3.0 CLI RX 200 **** v1 3.0 CLI RX| 127.0.0.1 41200\n ** v1 3.0 Listen on 127.0.0.1 41200 **** v1 3.0 macro def v1_addr=127.0.0.1 **** v1 3.0 macro def v1_port=41200 **** v1 3.0 macro def v1_sock=127.0.0.1 41200 *** top 3.0 varnish **** v1 3.0 CLI TX| ban.list **** v1 3.0 vsl| 0 CLI - Rd debug.listen_address **** v1 3.0 vsl| 0 CLI - Wr 200 16 127.0.0.1 41200 *** v1 3.0 CLI RX 200 **** v1 3.0 CLI RX| Present bans:\n **** v1 3.0 CLI RX| 1395058400.834320 0 C \n **** v1 3.0 CLI RX| 1395058399.661653 0 req.url == /test\n **** v1 3.0 CLI RX| 1395058399.621650 0 C \n **** v1 3.0 CLI RX| 1395058399.431171 1 C \n ** v1 3.0 CLI 200 *** top 3.0 client ** c1 3.0 Starting client ** c1 3.0 Waiting for client *** c1 3.0 Connect to 127.0.0.1 41200 *** c1 3.0 connected fd 10 from 127.0.0.1 45002 to 127.0.0.1 41200 *** c1 3.0 txreq **** c1 3.0 txreq| GET / HTTP/1.1\r\n **** c1 3.0 txreq| \r\n *** c1 3.0 rxresp **** c1 3.0 rxhdr| HTTP/1.1 200 Ok\r\n **** c1 3.0 rxhdr| x-foo: foo\r\n **** c1 3.0 rxhdr| Date: Mon, 17 Mar 2014 12:13:21 GMT\r\n **** c1 3.0 rxhdr| X-Varnish: 1001 1002\r\n **** c1 3.0 rxhdr| Age: 2\r\n **** c1 3.0 rxhdr| Via: 1.1 varnish\r\n **** c1 3.0 rxhdr| Content-Length: 0\r\n **** c1 3.0 rxhdr| Connection: keep-alive\r\n **** c1 3.0 rxhdr| Accept-Ranges: bytes\r\n **** c1 3.0 rxhdr| \r\n **** c1 3.0 http[ 0] | HTTP/1.1 **** c1 3.0 http[ 1] | 200 **** c1 3.0 http[ 2] | Ok **** c1 3.0 http[ 3] | x-foo: foo **** c1 3.0 http[ 4] | Date: Mon, 17 Mar 2014 12:13:21 GMT **** c1 3.0 http[ 5] | X-Varnish: 1001 1002 **** c1 3.0 http[ 6] | Age: 2 **** c1 3.0 http[ 7] | Via: 1.1 varnish **** c1 3.0 http[ 8] | Content-Length: 0 **** c1 3.0 http[ 9] | Connection: keep-alive **** c1 3.0 http[10] | Accept-Ranges: bytes **** c1 3.0 bodylen = 0 *** c1 3.0 expect **** c1 3.0 EXPECT resp.http.x-foo (foo) == "foo" match *** c1 3.0 closing fd 10 ** c1 3.0 Ending *** top 3.0 varnish **** v1 3.0 vsl| 0 CLI - Rd ban.list **** v1 3.0 vsl| 0 CLI - Wr 200 142 Present bans: 1395058400.834320 0 C 1395058399.661653 0 req.url == /test 1395058399.621650 0 C 1395058399.431171 1 C **** v1 3.0 vsl| 1000 Begin c sess 0 HTTP/1 **** v1 3.0 vsl| 1000 SessOpen c 127.0.0.1 45002 127.0.0.1:0 127.0.0.1 41200 1395058401.982032 13 **** v1 3.0 vsl| 1000 Link c req 1001 rxreq **** v1 3.0 vsl| 0 ExpKill - EXP_Rearm p=0x2b390c0008c0 E=1395058429.582860470 e=1395058429.582860470 f=0x1000 **** v1 3.0 vsl| 0 ExpKill - EXP_Inbox p=0x2b390c0008c0 e=1395058429.582860470 f=0x1410 **** v1 3.0 vsl| 0 ExpKill - EXP_When p=0x2b390c0008c0 e=1395058429.582860470 f=0x1410 **** v1 3.0 vsl| 1001 Begin c req 1000 rxreq **** v1 3.0 vsl| 1001 ReqStart c 127.0.0.1 45002 **** v1 3.0 vsl| 1001 ReqMethod c GET **** v1 3.0 vsl| 1001 ReqURL c / **** v1 3.0 vsl| 1001 ReqProtocol c HTTP/1.1 **** v1 3.0 vsl| 1001 VCL_call c RECV **** v1 3.0 vsl| 1001 ReqHeader c X-Forwarded-For: 127.0.0.1 **** v1 3.0 vsl| 1001 VCL_return c hash **** v1 3.0 vsl| 1001 VCL_call c HASH **** v1 3.0 vsl| 1001 VCL_return c lookup **** v1 3.0 vsl| 1001 Hit c 2147484650 **** v1 3.0 vsl| 1001 VCL_call c HIT **** v1 3.0 vsl| 1001 VCL_return c deliver **** v1 3.0 vsl| 1001 RespProtocol c HTTP/1.1 **** v1 3.0 vsl| 1001 RespStatus c 200 **** v1 3.0 vsl| 1001 RespResponse c Ok **** v1 3.0 vsl| 1001 RespHeader c x-foo: foo **** v1 3.0 vsl| 1001 RespHeader c Date: Mon, 17 Mar 2014 12:13:21 GMT **** v1 3.0 vsl| 1001 RespHeader c X-Varnish: 1001 1002 **** v1 3.0 vsl| 1001 RespHeader c Age: 2 **** v1 3.0 vsl| 1001 RespHeader c Via: 1.1 varnish **** v1 3.0 vsl| 1001 VCL_call c DELIVER **** v1 3.0 vsl| 1001 VCL_return c deliver **** v1 3.0 vsl| 1001 RespHeader c Content-Length: 0 **** v1 3.0 vsl| 1001 Debug c RES_MODE 2 **** v1 3.0 vsl| 1001 RespHeader c Connection: keep-alive **** v1 3.0 vsl| 1001 RespHeader c Accept-Ranges: bytes **** v1 3.0 vsl| 1001 Debug c XXX REF 2 **** v1 3.0 vsl| 1001 Length c 0 **** v1 3.0 vsl| 1001 ReqEnd c 1395058401.982092381 1395058401.982031584 -0.000237942 0.000177145 -0.000237942 **** v1 3.0 vsl| 1001 End c **** v1 3.0 vsl| 1000 SessClose c REM_CLOSE 0.001 1 0 0 0 1 0 **** v1 3.0 vsl| 1000 End c ** v1 3.3 as expected: bans_dups (1) == 1 *** top 3.3 varnish ---- v1 4.3 Not true: bans_completed (1) == 3 (3) * top 4.3 RESETTING after ../../../bin/varnishtest/tests/p00009.vtc ** s1 4.3 Waiting for server **** s1 4.3 macro undef s1_addr **** s1 4.3 macro undef s1_port **** s1 4.3 macro undef s1_sock **** v1 4.9 vsl| 0 CLI - Rd ping **** v1 4.9 vsl| 0 CLI - Wr 200 19 PONG 1395058403 1.0 ** v1 5.3 Wait **** v1 5.3 vsl| 0 CLI - EOF on CLI connection, worker stops ** v1 7.4 R 8447 Status: 0000 (u 0.144009 s 0.144009) * top 7.4 TEST ../../../bin/varnishtest/tests/p00009.vtc FAILED # top TEST ../../../bin/varnishtest/tests/p00009.vtc FAILED (7.427) exit=1 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 17 12:31:27 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 17 Mar 2014 12:31:27 -0000 Subject: [Varnish] #1451: p00009.vtc is fragile In-Reply-To: <046.a43cd06901bb6cec45f2384dcd13c80d@varnish-cache.org> References: <046.a43cd06901bb6cec45f2384dcd13c80d@varnish-cache.org> Message-ID: <061.d94fe787df80f92649f0dcc83c904ad9@varnish-cache.org> #1451: p00009.vtc is fragile -------------------------+-------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishtest | Version: trunk Severity: minor | Resolution: Keywords: | -------------------------+-------------------- Comment (by lkarsten): Ran the Jenkins job manually to verify, and on the second run all the test cases pass just fine. {{{ [..] PASS: tests/v00036.vtc PASS: tests/v00037.vtc ==================== All 358 tests passed ==================== }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 17 13:17:16 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 17 Mar 2014 13:17:16 -0000 Subject: [Varnish] #1452: Assert error in VRT_r_obj_status(), cache/cache_vrt_var.c Message-ID: <046.1a69a83a90437c6ccc4025ee568c14db@varnish-cache.org> #1452: Assert error in VRT_r_obj_status(), cache/cache_vrt_var.c ----------------------+--------------------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+--------------------------------- Converting synthetic/redirect code from 3.0 til 4.0, I forgot one instance and tried to read obj.status in vcl_error. This leads to an assert. {{{ if (obj.status == 790) { set resp.http.Content-Type = "text/plain; charset=utf-8"; set resp.status = 200; synthetic({"You are "} + client.ip); return (deliver); } }}} {{{ Last panic at: Mon, 17 Mar 2014 13:12:37 GMT Assert error in VRT_r_obj_status(), cache/cache_vrt_var.c line 117: Condition((ctx->http_obj) != NULL) not true. thread = (cache-worker) ident = Linux,3.11.0-18-generic,x86_64,-smalloc,-smalloc,-hcritbit,epoll Backtrace: 0x439586: pan_backtrace+0x19 0x439890: pan_ic+0x1e9 0x44c727: VRT_r_obj_status+0xb5 0x7f1b08207633: ./vcl.oeHHka5i.so(VGC_function_vcl_error+0x23) [0x7f1b08207633] 0x447b67: vcl_call_method+0x402 0x448ad7: VCL_error_method+0x125 0x43ca6f: cnt_error+0x370 0x43f595: CNT_Request+0x560 0x4328fa: HTTP1_Session+0x426 0x4424ca: ses_req_pool_task+0x166 req = 0x7f1ae0090a90 { sp = 0x7f1ad4001810, vxid = 1073741826, step = R_STP_ERROR, req_body = R_BODY_NONE, err_code = 790, err_reason = whoami, restarts = 0, esi_level = 0 sp = 0x7f1ad4001810 { fd = 11, vxid = 1, client = 77.40.251.100 48578, step = S_STP_WORKING, }, worker = 0x7f1af8fcfc30 { ws = 0x7f1af8fcfe30 { id = "wrk", {s,f,r,e} = {0x7f1af8fcf400,0x7f1af8fcf400,(nil),+2048}, }, VCL::method = ERROR, VCL::return = abandon, }, ws = 0x7f1ae0090c10 { id = "req", {s,f,r,e} = {0x7f1ae0092a68,+224,(nil),+57384}, }, http[req] = { ws = 0x7f1ae0090c10[req] "GET", "/whoami", "HTTP/1.1", "TE: deflate,gzip;q=0.3", "Connection: TE, close", "Host: hyse.org", "User-Agent: lwp-request/6.03 libwww-perl/6.05", }, http[resp] = { ws = 0x7f1ae0090c10[req] "HTTP/1.1", "790", "whoami", "Date: Mon, 17 Mar 2014 13:12:34 GMT", "Server: Varnish", "X-Varnish: 2", }, vcl = { srcname = { "input", "Default", }, }, }, }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 17 13:51:35 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 17 Mar 2014 13:51:35 -0000 Subject: [Varnish] #1449: Assert error in ban_check_object(), cache/cache_ban.c line 915 In-Reply-To: <046.7113ebd1ce10ac27acc0986067f77f64@varnish-cache.org> References: <046.7113ebd1ce10ac27acc0986067f77f64@varnish-cache.org> Message-ID: <061.f7b9cd0ff9f0591a5fed7395e9aea5b0@varnish-cache.org> #1449: Assert error in ban_check_object(), cache/cache_ban.c line 915 ----------------------+---------------------------------------- Reporter: lkarsten | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+---------------------------------------- Comment (by lkarsten): Fryer ran into a similar panic just now, with latest master/793d67a. {{{ Last panic at: Mon, 17 Mar 2014 12:35:18 GMT Assert error in ban_check_object(), cache/cache_ban.c line 915: Condition((oc->ban) != NULL) not true. thread = (cache-worker) ident = Linux,3.2.0-51-generic,x86_64,-smalloc,-smalloc,-hcritbit,epoll Backtrace: 0x439eda: pan_backtrace+0x19 0x43a1eb: pan_ic+0x1e9 0x416045: ban_check_object+0x1a5 0x416441: BAN_CheckObject+0x35 0x42a9b6: HSH_Lookup+0x734 0x43da84: cnt_lookup+0x227 0x43fe8e: CNT_Request+0x441 0x433225: HTTP1_Session+0x427 0x442f11: ses_req_pool_task+0x166 0x43bac8: Pool_Work_Thread+0x416 req = 0x7f6c00030970 { sp = 0x7f6c040019c0, vxid = 1075557359, step = R_STP_LOOKUP, req_body = R_BODY_NONE, restarts = 0, esi_level = 0 sp = 0x7f6c040019c0 { fd = 21, vxid = 1815534, client = 194.31.39.161 43240, step = S_STP_WORKING, }, worker = 0x7f6c739c2c70 { ws = 0x7f6c739c2e70 { id = "wrk", {s,f,r,e} = {0x7f6c739c2420,0x7f6c739c2420,(nil),+2048}, }, VCL::method = 0x0, VCL::return = deliver, }, ws = 0x7f6c00030af0 { id = "req", {s,f,r,e} = {0x7f6c00032948,+272,+57384,+57384}, }, http[req] = { ws = 0x7f6c00030af0[req] "GET", "/cacheabledata/set_imagehosting1/8/image9618.jpg", "HTTP/1.1", "Host: fryer1.varnish-software.com:6081", "Accept: */*", "Accept-Encoding: gzip", "User-Agent: Mozilla/5.0 (unknown-x86_64-linux-gnu) Siege/3.0.4", "Connection: close", "X-Forwarded-For: 194.31.39.161", }, vcl = { srcname = { "input", "Default", }, }, }, }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 17 13:51:42 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 17 Mar 2014 13:51:42 -0000 Subject: [Varnish] #1449: Assert error in ban_check_object(), cache/cache_ban.c line 915 In-Reply-To: <046.7113ebd1ce10ac27acc0986067f77f64@varnish-cache.org> References: <046.7113ebd1ce10ac27acc0986067f77f64@varnish-cache.org> Message-ID: <061.dd439e6eb3368a85c73ccd802c7dbfc0@varnish-cache.org> #1449: Assert error in ban_check_object(), cache/cache_ban.c line 915 ----------------------+---------------------------------------- Reporter: lkarsten | Owner: Poul-Henning Kamp Type: defect | Status: reopened Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+---------------------------------------- Changes (by lkarsten): * status: closed => reopened * resolution: fixed => -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 18 10:26:17 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 18 Mar 2014 10:26:17 -0000 Subject: [Varnish] #1453: Assert error in exp_inbox(), cache/cache_expire.c line 430 Message-ID: <046.9b9a21329f678cd8f9078c0c57250b30@varnish-cache.org> #1453: Assert error in exp_inbox(), cache/cache_expire.c line 430 ----------------------+--------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: unknown Severity: normal | Keywords: ----------------------+--------------------- fryer found this last night. (efe50681) {{{ Last panic at: Tue, 18 Mar 2014 01:33:27 GMT Assert error in exp_inbox(), cache/cache_expire.c line 430: Condition((oc->flags & (1<<1)) == 0) not true. thread = (cache-timeout) ident = Linux,3.2.0-51-generic,x86_64,-smalloc,-smalloc,-hcritbit,epoll Backtrace: 0x43a023: pan_backtrace+0x19 0x43a334: pan_ic+0x1e9 0x420fa4: exp_inbox+0x165 0x421d8a: exp_thread+0x24b 0x454b71: wrk_bgthread+0x103 0x7f158e400e9a: /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a) [0x7f158e400e9a] 0x7f158e12d3fd: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f158e12d3fd] }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 18 10:26:33 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 18 Mar 2014 10:26:33 -0000 Subject: [Varnish] #1453: Assert error in exp_inbox(), cache/cache_expire.c line 430 In-Reply-To: <046.9b9a21329f678cd8f9078c0c57250b30@varnish-cache.org> References: <046.9b9a21329f678cd8f9078c0c57250b30@varnish-cache.org> Message-ID: <061.ccd8790ed29bea1edb0a46afe42135fa@varnish-cache.org> #1453: Assert error in exp_inbox(), cache/cache_expire.c line 430 ----------------------+-------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Changes (by lkarsten): * version: unknown => trunk -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 18 10:31:15 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 18 Mar 2014 10:31:15 -0000 Subject: [Varnish] #1454: XFF is not handled in C Message-ID: <046.2060dad0d9d3c50788cb49f268e7db35@varnish-cache.org> #1454: XFF is not handled in C ----------------------+--------------------------------- Reporter: lkarsten | Owner: tfheen Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+--------------------------------- X-Forwarded-For should be handled in C before we reach VCL. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 18 10:33:51 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 18 Mar 2014 10:33:51 -0000 Subject: [Varnish] #1455: Connection: close is not set before vcl_pipe is run. Message-ID: <046.29864a2bd2236aa443567cfe1b3d6ebe@varnish-cache.org> #1455: Connection: close is not set before vcl_pipe is run. ----------------------+--------------------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+--------------------------------- Move this to C before vcl_pipe, as agreed on VDD2013Q4. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 18 10:34:33 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 18 Mar 2014 10:34:33 -0000 Subject: [Varnish] #1455: Connection: close is not set before vcl_pipe is run. In-Reply-To: <046.29864a2bd2236aa443567cfe1b3d6ebe@varnish-cache.org> References: <046.29864a2bd2236aa443567cfe1b3d6ebe@varnish-cache.org> Message-ID: <061.cdaef4fe5350cf46e5f834efbd65b55c@varnish-cache.org> #1455: Connection: close is not set before vcl_pipe is run. ----------------------+---------------------------------- Reporter: lkarsten | Owner: tfheen Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+---------------------------------- Changes (by lkarsten): * owner: => tfheen -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 18 10:48:48 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 18 Mar 2014 10:48:48 -0000 Subject: [Varnish] #1456: ReqAcct is not output during request handling Message-ID: <046.d3874a8b2442595487802963f9b68200@varnish-cache.org> #1456: ReqAcct is not output during request handling ----------------------+--------------------------------- Reporter: lkarsten | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+--------------------------------- As agreed on VDD2013Q4, we want byte counters for each record. SessClose outputs some counters, but they're currently zero or 1. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 18 10:49:13 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 18 Mar 2014 10:49:13 -0000 Subject: [Varnish] #1456: ReqAcct is not output during request handling In-Reply-To: <046.d3874a8b2442595487802963f9b68200@varnish-cache.org> References: <046.d3874a8b2442595487802963f9b68200@varnish-cache.org> Message-ID: <061.b952f3b60ed6f6eae5c0a1027b8a1d26@varnish-cache.org> #1456: ReqAcct is not output during request handling ----------------------+---------------------------------- Reporter: lkarsten | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+---------------------------------- Description changed by lkarsten: Old description: > As agreed on VDD2013Q4, we want byte counters for each record. > > SessClose outputs some counters, but they're currently zero or 1. New description: As agreed on VDD2013Q4, we want byte counters for each request. SessClose outputs some counters, but they're currently zero or 1. -- -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 18 11:18:11 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 18 Mar 2014 11:18:11 -0000 Subject: [Varnish] #1457: vcl.show should mention which include some piece of source is from Message-ID: <043.f14786107b6d266ced5da4fa3a4b15af@varnish-cache.org> #1457: vcl.show should mention which include some piece of source is from --------------------+--------------------- Reporter: slink | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: unknown Severity: normal | Keywords: --------------------+--------------------- from VDD13Q4 recap VDD13Q2 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 18 11:20:08 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 18 Mar 2014 11:20:08 -0000 Subject: [Varnish] #1457: vcl.show should expand includes (was: vcl.show should mention which include some piece of source is from) In-Reply-To: <043.f14786107b6d266ced5da4fa3a4b15af@varnish-cache.org> References: <043.f14786107b6d266ced5da4fa3a4b15af@varnish-cache.org> Message-ID: <058.1e91de5d0092bb4526e4ce43c7fe9261@varnish-cache.org> #1457: vcl.show should expand includes --------------------+---------------------- Reporter: slink | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: unknown Severity: normal | Resolution: Keywords: | --------------------+---------------------- -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 18 11:53:56 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 18 Mar 2014 11:53:56 -0000 Subject: [Varnish] #1455: Connection: close is not set before vcl_pipe is run. In-Reply-To: <046.29864a2bd2236aa443567cfe1b3d6ebe@varnish-cache.org> References: <046.29864a2bd2236aa443567cfe1b3d6ebe@varnish-cache.org> Message-ID: <061.e4c65a129e26e93a4c6cf7199ffe12d1@varnish-cache.org> #1455: Connection: close is not set before vcl_pipe is run. ----------------------+---------------------------------- Reporter: lkarsten | Owner: tfheen Type: defect | Status: closed Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+---------------------------------- Changes (by Tollef Fog Heen ): * status: new => closed * resolution: => fixed Comment: In [880c3c2a564aeeaad508dab136611973ca71d6aa]: {{{ #!CommitTicketReference repository="" revision="880c3c2a564aeeaad508dab136611973ca71d6aa" Set Connection: close before calling vcl_pipe It makes sense to default to setting Connection: close for vcl_pipe. Do this before calling vcl_pipe so it's overrideable. Fixes #1455 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 18 11:53:56 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 18 Mar 2014 11:53:56 -0000 Subject: [Varnish] #1454: XFF is not handled in C In-Reply-To: <046.2060dad0d9d3c50788cb49f268e7db35@varnish-cache.org> References: <046.2060dad0d9d3c50788cb49f268e7db35@varnish-cache.org> Message-ID: <061.3a94e068a339b11a727eda1eda4a0d1d@varnish-cache.org> #1454: XFF is not handled in C ----------------------+---------------------------------- Reporter: lkarsten | Owner: tfheen Type: defect | Status: closed Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+---------------------------------- Changes (by Tollef Fog Heen ): * status: new => closed * resolution: => fixed Comment: In [ae548683b8f91d0a92799f6c746b80773a4c9f05]: {{{ #!CommitTicketReference repository="" revision="ae548683b8f91d0a92799f6c746b80773a4c9f05" Move X-Forwarded-For handled into C code Remove adding of X-Forwarded-For from builtin.vcl and put it into the C code that runs before vcl_recv. This makes it more likely that it's properly set when the user VCL runs. Fixes: #1454 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 19 08:44:58 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 19 Mar 2014 08:44:58 -0000 Subject: [Varnish] #1458: Assert error in VBF_Fetch(), cache/cache_fetch.c line 863 Message-ID: <046.25afbe3c30abacc2e1fc42ff5cfc5956@varnish-cache.org> #1458: Assert error in VBF_Fetch(), cache/cache_fetch.c line 863 ----------------------+--------------------------------- Reporter: lkarsten | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: blocker | Keywords: ----------------------+--------------------------------- {{{ Last panic at: Wed, 19 Mar 2014 00:06:47 GMT Assert error in VBF_Fetch(), cache/cache_fetch.c line 863: Condition((bo->fetch_objcore->flags & (1<<1)) == 0) not true. thread = (cache-worker) ident = Linux,3.2.0-51-generic,x86_64,-smalloc,-smalloc,-hcritbit,epoll Backtrace: 0x439f27: pan_backtrace+0x19 0x43a238: pan_ic+0x1e9 0x425a19: VBF_Fetch+0x636 0x43e49d: cnt_miss+0x2a6 0x43fff5: CNT_Request+0x4b5 0x43319d: HTTP1_Session+0x427 0x443005: ses_req_pool_task+0x166 0x4432d0: ses_sess_pool_task+0x23b 0x44386f: SES_pool_accept_task+0x1f9 0x43bb18: Pool_Work_Thread+0x416 req = 0x7febb40409a0 { sp = 0x7febb8001150, vxid = 1073776715, step = R_STP_MISS, req_body = R_BODY_NONE, restarts = 0, esi_level = 0 sp = 0x7febb8001150 { fd = 20, vxid = 34890, client = 194.31.39.161 57114, step = S_STP_WORKING, }, worker = 0x7febece5bc70 { ws = 0x7febece5be70 { id = "wrk", {s,f,r,e} = {0x7febece5b420,0x7febece5b420,(nil),+2048}, }, VCL::method = 0x0, VCL::return = fetch, }, ws = 0x7febb4040b20 { id = "req", {s,f,r,e} = {0x7febb4042978,+256,(nil),+57384}, }, http[req] = { ws = 0x7febb4040b20[req] "GET", "/cacheabledata/set_imagehosting1/0/image340.jpg", "HTTP/1.1", "Host: fryer1.varnish-software.com:6081", "Accept: */*", "Accept-Encoding: gzip", "User-Agent: Mozilla/5.0 (unknown-x86_64-linux-gnu) Siege/3.0.4", "Connection: close", "X-Forwarded-For: 194.31.39.161", }, vcl = { srcname = { "input", "Default", }, }, }, busyobj = 0x7febc00008e0 { ws = 0x7febc00009a8 { id = "bo", {s,f,r,e} = {0x7febc00028a8,+33040,(nil),+57400}, }, is_do_stream is_is_gunzip bodystatus = 3 (length), }, ws = 0x7febc0000b28 { id = "obj", {s,f,r,e} = {0x7feb304890d8,+224,(nil),+224}, }, objcore (FETCH) = 0x7febc4a24620 { refcnt = 3 flags = 0x1002 objhead = 0x7febc4213970 } obj (FETCH) = 0x7feb30488f30 { vxid = 2147518540, http[obj] = { ws = 0x7febc0000b28[obj] "HTTP/1.1", "200", "OK", "Date: Wed, 19 Mar 2014 00:06:46 GMT", "Server: Apache/2.2.22 (Ubuntu)", "Last-Modified: Mon, 26 Aug 2013 14:08:44 GMT", "ETag: "820ccc-13eb8-4e4da4b4ce52b"", "Content-Type: image/jpeg", }, len = 81592, store = { 81592 { 00 00 80 5a fb 81 ec 41 00 00 80 39 f0 21 ee 41 |...Z...A...9.!.A| 00 00 40 e8 bd 8e e1 41 00 00 80 4d 25 65 e3 41 |.. at ....A...M%e.A| 00 00 40 56 4d 77 e0 41 00 00 60 f4 aa 98 e9 41 |.. at VMw.A..`....A| 00 00 c0 3b 8f 97 ec 41 00 00 40 7c 2d 5b d0 41 |...;...A..@|-[.A| [81528 more] }, }, }, } }}} 2014-03-19 00:48:22,143[fry] - DEBUG - HEAD is now at f89015a Add major version in Via header -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 19 09:18:10 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 19 Mar 2014 09:18:10 -0000 Subject: [Varnish] #1458: Assert error in VBF_Fetch(), cache/cache_fetch.c line 863 In-Reply-To: <046.25afbe3c30abacc2e1fc42ff5cfc5956@varnish-cache.org> References: <046.25afbe3c30abacc2e1fc42ff5cfc5956@varnish-cache.org> Message-ID: <061.b34ae84f9cec61d07a86073458f71ae0@varnish-cache.org> #1458: Assert error in VBF_Fetch(), cache/cache_fetch.c line 863 ----------------------+---------------------------------- Reporter: lkarsten | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: blocker | Resolution: Keywords: | ----------------------+---------------------------------- Comment (by martin): I believe this is due to the bo->state not being reset in VBO_GetBusyObj(). On reuse of busyobj an old state could because of that be set already on the busyobj, causing the waiting thread to get passed the VBO_WaitState() early. Martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 19 09:23:52 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 19 Mar 2014 09:23:52 -0000 Subject: [Varnish] #1458: Assert error in VBF_Fetch(), cache/cache_fetch.c line 863 In-Reply-To: <046.25afbe3c30abacc2e1fc42ff5cfc5956@varnish-cache.org> References: <046.25afbe3c30abacc2e1fc42ff5cfc5956@varnish-cache.org> Message-ID: <061.45d4c781e40ba18beb90574f29e78a09@varnish-cache.org> #1458: Assert error in VBF_Fetch(), cache/cache_fetch.c line 863 ----------------------+---------------------------------- Reporter: lkarsten | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: blocker | Resolution: fixed Keywords: | ----------------------+---------------------------------- Changes (by Martin Blix Grydeland ): * status: new => closed * resolution: => fixed Comment: In [0f90ee223daf97d4e6d83a78ae919a95e590bcca]: {{{ #!CommitTicketReference repository="" revision="0f90ee223daf97d4e6d83a78ae919a95e590bcca" Reset busyobj state to BOS_INVALID in VBO_GetBusyObj Fixes: #1458 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 19 15:17:43 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 19 Mar 2014 15:17:43 -0000 Subject: [Varnish] #1457: vcl.show should expand includes In-Reply-To: <043.f14786107b6d266ced5da4fa3a4b15af@varnish-cache.org> References: <043.f14786107b6d266ced5da4fa3a4b15af@varnish-cache.org> Message-ID: <058.06b98536ff2402799157629d4360eec2@varnish-cache.org> #1457: vcl.show should expand includes ----------------------+---------------------- Reporter: slink | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: unknown Severity: normal | Resolution: Keywords: | ----------------------+---------------------- Changes (by slink): * component: build => varnishd -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 20 09:32:15 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 20 Mar 2014 09:32:15 -0000 Subject: [Varnish] #1458: Assert error in VBF_Fetch(), cache/cache_fetch.c line 863 In-Reply-To: <046.25afbe3c30abacc2e1fc42ff5cfc5956@varnish-cache.org> References: <046.25afbe3c30abacc2e1fc42ff5cfc5956@varnish-cache.org> Message-ID: <061.5911fd62bff9d78b1fbb025c952f11b3@varnish-cache.org> #1458: Assert error in VBF_Fetch(), cache/cache_fetch.c line 863 ----------------------+---------------------------------- Reporter: lkarsten | Owner: phk Type: defect | Status: reopened Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: blocker | Resolution: Keywords: | ----------------------+---------------------------------- Changes (by martin): * status: closed => reopened * resolution: fixed => -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 20 11:46:33 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 20 Mar 2014 11:46:33 -0000 Subject: [Varnish] #1459: Undefined references in documentation Message-ID: <046.c258283d118d15bda2cfb8813f1d2132@varnish-cache.org> #1459: Undefined references in documentation ---------------------------+--------------------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: low | Milestone: Varnish 4.0 release Component: documentation | Version: trunk Severity: normal | Keywords: ---------------------------+--------------------------------- Documentation has a lot of undefined references and prints a lot of warnings when being built. {{{ lkarsten at immer:~/work/varnish-cache/doc/sphinx$ make html sphinx-build -b html -d build/doctrees -D latex_paper_size=a4 . build/html Making output directory... Running Sphinx v1.2.2 loading pickled environment... not yet created building [html]: targets for 102 source files that are out of date updating environment: 102 added, 0 changed, 0 removed reading sources... [100%] whats-new/upgrading /home/lkarsten/work/varnish-cache/doc/sphinx/installation/bugs.rst:86: WARNING: Definition list ends without a blank line; unexpected unindent. /home/lkarsten/work/varnish-cache/doc/sphinx/installation/install.rst:144: WARNING: Inline literal start-string without end-string. include/params.rst:511: WARNING: duplicate label ref_param_max_retries, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:532: WARNING: duplicate label ref_param_pcre_match_limit, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:393: WARNING: duplicate label ref_param_http_range_support, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:112: WARNING: duplicate label ref_param_cc_command, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:226: WARNING: duplicate label ref_param_default_grace, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:754: WARNING: duplicate label ref_param_tcp_keepalive_time, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:335: WARNING: duplicate label ref_param_gzip_buffer, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:1025: WARNING: duplicate label ref_param_vsl_space, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:478: WARNING: duplicate label ref_param_lru_interval, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:923: WARNING: duplicate label ref_param_timeout_linger, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:711: WARNING: duplicate label ref_param_sigsegv_handler, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:444: WARNING: duplicate label ref_param_idle_send_timeout, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:871: WARNING: duplicate label ref_param_thread_pools, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:357: WARNING: duplicate label ref_param_gzip_memlevel, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:912: WARNING: duplicate label ref_param_timeout_idle, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:490: WARNING: duplicate label ref_param_max_esi_depth, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:174: WARNING: duplicate label ref_param_critbit_cooloff, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:457: WARNING: duplicate label ref_param_listen_address, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:316: WARNING: duplicate label ref_param_first_byte_timeout, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:54: WARNING: duplicate label ref_param_ban_dups, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:1056: WARNING: duplicate label ref_param_workspace_backend, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:888: WARNING: duplicate label ref_param_thread_queue_limit, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:936: WARNING: duplicate label ref_param_timeout_req, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:380: WARNING: duplicate label ref_param_http_max_hdr, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:1078: WARNING: duplicate label ref_param_workspace_session, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:305: WARNING: duplicate label ref_param_fetch_maxchunksize, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:562: WARNING: duplicate label ref_param_pipe_timeout, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:782: WARNING: duplicate label ref_param_thread_pool_destroy_delay, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:7: WARNING: duplicate label ref_param_acceptor_sleep_decay, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:500: WARNING: duplicate label ref_param_max_restarts, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:766: WARNING: duplicate label ref_param_thread_pool_add_delay, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:964: WARNING: duplicate label ref_param_vcc_err_unref, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:63: WARNING: duplicate label ref_param_ban_lurker_age, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:93: WARNING: duplicate label ref_param_between_bytes_timeout, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:644: WARNING: duplicate label ref_param_prefer_ipv6, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:983: WARNING: duplicate label ref_param_vcl_dir, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:665: WARNING: duplicate label ref_param_send_timeout, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:1047: WARNING: duplicate label ref_param_waiter, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:999: WARNING: duplicate label ref_param_vsl_buffer, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:742: WARNING: duplicate label ref_param_tcp_keepalive_probes, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:154: WARNING: duplicate label ref_param_clock_skew, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:730: WARNING: duplicate label ref_param_tcp_keepalive_intvl, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:186: WARNING: duplicate label ref_param_debug, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:467: WARNING: duplicate label ref_param_listen_depth, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:626: WARNING: duplicate label ref_param_pool_vbo, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:701: WARNING: duplicate label ref_param_shortlived, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:121: WARNING: duplicate label ref_param_cli_buffer, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:368: WARNING: duplicate label ref_param_http_gzip_support, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:541: WARNING: duplicate label ref_param_pcre_match_limit_recursion, other instance in /home/lkarsten/work/varnish-cache/doc/sphinx/include/params.rst include/params.rst:45: WARNING: duplicate label ref_param_auto_restart, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:900: WARNING: duplicate label ref_param_thread_stats_rate, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:689: WARNING: duplicate label ref_param_shm_reclen, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:829: WARNING: duplicate label ref_param_thread_pool_min, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:412: WARNING: duplicate label ref_param_http_req_size, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:32: WARNING: duplicate label ref_param_acceptor_sleep_max, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:144: WARNING: duplicate label ref_param_cli_timeout, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:248: WARNING: duplicate label ref_param_default_ttl, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:293: WARNING: duplicate label ref_param_fetch_chunksize, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:82: WARNING: duplicate label ref_param_ban_lurker_sleep, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:1067: WARNING: duplicate label ref_param_workspace_client, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:237: WARNING: duplicate label ref_param_default_keep, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:721: WARNING: duplicate label ref_param_syslog_cli_traffic, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:103: WARNING: duplicate label ref_param_busyobj_worker_cache, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:955: WARNING: duplicate label ref_param_vcc_allow_inline_c, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:347: WARNING: duplicate label ref_param_gzip_level, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:164: WARNING: duplicate label ref_param_connect_timeout, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:73: WARNING: duplicate label ref_param_ban_lurker_batch, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:550: WARNING: duplicate label ref_param_ping_interval, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:590: WARNING: duplicate label ref_param_pool_sess, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:433: WARNING: duplicate label ref_param_http_resp_size, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:1036: WARNING: duplicate label ref_param_vsm_space, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:521: WARNING: duplicate label ref_param_nuke_limit, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:1012: WARNING: duplicate label ref_param_vsl_mask, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:814: WARNING: duplicate label ref_param_thread_pool_max, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:856: WARNING: duplicate label ref_param_thread_pool_timeout, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:946: WARNING: duplicate label ref_param_user, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:653: WARNING: duplicate label ref_param_rush_exponent, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:326: WARNING: duplicate label ref_param_group, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:973: WARNING: duplicate label ref_param_vcc_unsafe_path, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:678: WARNING: duplicate label ref_param_session_max, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:991: WARNING: duplicate label ref_param_vmod_dir, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:797: WARNING: duplicate label ref_param_thread_pool_fail_delay, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:423: WARNING: duplicate label ref_param_http_resp_hdr_len, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:844: WARNING: duplicate label ref_param_thread_pool_stack, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:259: WARNING: duplicate label ref_param_feature, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:1089: WARNING: duplicate label ref_param_workspace_thread, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:608: WARNING: duplicate label ref_param_pool_vbc, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:133: WARNING: duplicate label ref_param_cli_limit, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:402: WARNING: duplicate label ref_param_http_req_hdr_len, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst include/params.rst:19: WARNING: duplicate label ref_param_acceptor_sleep_incr, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/include/params.rst include/params.rst:572: WARNING: duplicate label ref_param_pool_req, other instance in /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst /home/lkarsten/work/varnish- cache/doc/sphinx/tutorial/introduction.rst.BACKUP.6207.rst:33: WARNING: Title underline too short. This behaviour and most other behaviour can be changed using policies ======= /home/lkarsten/work/varnish- cache/doc/sphinx/tutorial/introduction.rst.BACKUP.6207.rst:4: WARNING: duplicate label tutorial-intro, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/tutorial/introduction.rst /home/lkarsten/work/varnish- cache/doc/sphinx/tutorial/introduction.rst.BASE.6207.rst:4: WARNING: duplicate label tutorial-intro, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/tutorial/introduction.rst.BACKUP.6207.rst /home/lkarsten/work/varnish- cache/doc/sphinx/tutorial/introduction.rst.LOCAL.6207.rst:4: WARNING: duplicate label tutorial-intro, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/tutorial/introduction.rst.BASE.6207.rst /home/lkarsten/work/varnish- cache/doc/sphinx/tutorial/introduction.rst.REMOTE.6207.rst:4: WARNING: duplicate label tutorial-intro, other instance in /home/lkarsten/work /varnish-cache/doc/sphinx/tutorial/introduction.rst.LOCAL.6207.rst /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/command- line.rst:19: WARNING: Title underline too short. '-a' *listen_address* ^^^^^^^^^^^^^^^^^^^ /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/command- line.rst:45: WARNING: Title underline too short. '-f' *VCL-file* or '-b' *backend* ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/command- line.rst:45: WARNING: Title underline too short. '-f' *VCL-file* or '-b' *backend* ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/esi.rst:85: WARNING: Title underline too short. Doing ESI on JSON and other non-XML'ish content ---------------------------------------------- /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/esi.rst:85: WARNING: Title underline too short. Doing ESI on JSON and other non-XML'ish content ---------------------------------------------- /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/index.rst:35: WARNING: toctree contains reference to nonexisting document u'users- guide/orphans' /home/lkarsten/work/varnish-cache/doc/sphinx/users- guide/run_security.rst:171: WARNING: Definition list ends without a blank line; unexpected unindent. /home/lkarsten/work/varnish-cache/doc/sphinx/users- guide/troubleshooting.rst:95: WARNING: Block quote ends without a blank line; unexpected unindent. /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/vcl.rst:33: WARNING: toctree contains reference to nonexisting document u'users- guide/websockets' /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/vcl- backends.rst:217: WARNING: Definition list ends without a blank line; unexpected unindent. /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/vcl- syntax.rst:98: WARNING: Literal block expected; none found. /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/vcl- syntax.rst:100: ERROR: Unknown target name: "vcl". /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/vcl- variables.rst:3: WARNING: Title underline too short. Requests and responses as objects ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/vcl- variables.rst:32: WARNING: Definition list ends without a blank line; unexpected unindent. looking for now-outdated files... none found pickling environment... done checking consistency... /home/lkarsten/work/varnish- cache/doc/sphinx/include/params.rst:: WARNING: document isn't included in any toctree /home/lkarsten/work/varnish- cache/doc/sphinx/include/varnishhist_options.rst:: WARNING: document isn't included in any toctree /home/lkarsten/work/varnish- cache/doc/sphinx/include/varnishhist_synopsis.rst:: WARNING: document isn't included in any toctree /home/lkarsten/work/varnish- cache/doc/sphinx/include/varnishlog_options.rst:: WARNING: document isn't included in any toctree /home/lkarsten/work/varnish- cache/doc/sphinx/include/varnishlog_synopsis.rst:: WARNING: document isn't included in any toctree /home/lkarsten/work/varnish- cache/doc/sphinx/include/varnishncsa_options.rst:: WARNING: document isn't included in any toctree /home/lkarsten/work/varnish- cache/doc/sphinx/include/varnishncsa_synopsis.rst:: WARNING: document isn't included in any toctree /home/lkarsten/work/varnish- cache/doc/sphinx/include/varnishtop_options.rst:: WARNING: document isn't included in any toctree /home/lkarsten/work/varnish- cache/doc/sphinx/include/varnishtop_synopsis.rst:: WARNING: document isn't included in any toctree /home/lkarsten/work/varnish-cache/doc/sphinx/reference/vcl_var.rst:: WARNING: document isn't included in any toctree /home/lkarsten/work/varnish- cache/doc/sphinx/tutorial/introduction.rst.BACKUP.6207.rst:: WARNING: document isn't included in any toctree /home/lkarsten/work/varnish- cache/doc/sphinx/tutorial/introduction.rst.BASE.6207.rst:: WARNING: document isn't included in any toctree /home/lkarsten/work/varnish- cache/doc/sphinx/tutorial/introduction.rst.LOCAL.6207.rst:: WARNING: document isn't included in any toctree /home/lkarsten/work/varnish- cache/doc/sphinx/tutorial/introduction.rst.REMOTE.6207.rst:: WARNING: document isn't included in any toctree /home/lkarsten/work/varnish-cache/doc/sphinx/users- guide/devicedetection.rst:: WARNING: document isn't included in any toctree /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/vcl-intro.rst:: WARNING: document isn't included in any toctree done preparing documents... done writing output... [100%] whats-new/upgrading /home/lkarsten/work/varnish-cache/doc/sphinx/index.rst:25: WARNING: undefined label: users_guide_index (if the link has no caption the label must precede a section header) /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/operation- statistics.rst:27: WARNING: undefined label: ref-varnishtop (if the link has no caption the label must precede a section header) /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/operation- statistics.rst:41: WARNING: undefined label: ref-varnishhist (if the link has no caption the label must precede a section header) /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/operation- statistics.rst:57: WARNING: undefined label: ref-varnishstat (if the link has no caption the label must precede a section header) /home/lkarsten/work/varnish-cache/doc/sphinx/users-guide/vcl- syntax.rst:105: WARNING: undefined label: vcl-built-in-subs (if the link has no caption the label must precede a section header) writing additional files... genindex search copying static files... done copying extra files... done dumping search index... done dumping object inventory... done build succeeded, 133 warnings. Build finished. The HTML pages are in build/html. }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 24 10:25:30 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 24 Mar 2014 10:25:30 -0000 Subject: [Varnish] #1368: Assert error in object_cmp(), cache/cache_expire.c line 540 In-Reply-To: <046.3b0f279a2d861e83c5c8d5b0b9ae54b5@varnish-cache.org> References: <046.3b0f279a2d861e83c5c8d5b0b9ae54b5@varnish-cache.org> Message-ID: <061.c7c81ac641fa04906e359f30b6c5ea5d@varnish-cache.org> #1368: Assert error in object_cmp(), cache/cache_expire.c line 540 ----------------------+------------------------- Reporter: lkarsten | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: worksforme Keywords: | ----------------------+------------------------- Changes (by lkarsten): * status: new => closed * resolution: => worksforme Comment: I haven't seen this in the fryer runs in a long time now. Probably this has been fixed as a part of some other bugfix. Closing for now. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 24 11:01:13 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 24 Mar 2014 11:01:13 -0000 Subject: [Varnish] #1459: Undefined references in documentation In-Reply-To: <046.c258283d118d15bda2cfb8813f1d2132@varnish-cache.org> References: <046.c258283d118d15bda2cfb8813f1d2132@varnish-cache.org> Message-ID: <061.b188ca1ad6c97aa455c42487042bbab3@varnish-cache.org> #1459: Undefined references in documentation ---------------------------+---------------------------------- Reporter: lkarsten | Owner: lkarsten Type: defect | Status: new Priority: low | Milestone: Varnish 4.0 release Component: documentation | Version: trunk Severity: normal | Resolution: Keywords: | ---------------------------+---------------------------------- Changes (by lkarsten): * owner: => lkarsten -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 24 12:37:10 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 24 Mar 2014 12:37:10 -0000 Subject: [Varnish] #1452: Assert error in VRT_r_obj_status(), cache/cache_vrt_var.c In-Reply-To: <046.1a69a83a90437c6ccc4025ee568c14db@varnish-cache.org> References: <046.1a69a83a90437c6ccc4025ee568c14db@varnish-cache.org> Message-ID: <061.587d43283c55b789b0271da02071b2a5@varnish-cache.org> #1452: Assert error in VRT_r_obj_status(), cache/cache_vrt_var.c ----------------------+---------------------------------- Reporter: lkarsten | Owner: Type: defect | Status: closed Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+---------------------------------- Changes (by daghf): * status: new => closed * resolution: => fixed Comment: This was fixed in d260e9874bc89d550f89462f7ea237a672c0f265. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 24 14:12:45 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 24 Mar 2014 14:12:45 -0000 Subject: [Varnish] #1417: Panic on abandon in vcl_backend_response In-Reply-To: <043.208fe12b447118500afdc89eb66f6dad@varnish-cache.org> References: <043.208fe12b447118500afdc89eb66f6dad@varnish-cache.org> Message-ID: <058.7cd23c3153757b18fa403532c7ad0845@varnish-cache.org> #1417: Panic on abandon in vcl_backend_response ----------------------+---------------------------------- Reporter: fgsch | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+---------------------------------- Changes (by Dag Haavi Finstad ): * status: new => closed * resolution: => fixed Comment: In [32c8acbf89a0ce4f3a6fe1ed16b08ae7e9af7564]: {{{ #!CommitTicketReference repository="" revision="32c8acbf89a0ce4f3a6fe1ed16b08ae7e9af7564" Handle 'return (abandon);' in vcl_backend_response. Test case by: Federico G. Schwindt Fixes: #1417 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 24 20:43:39 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 24 Mar 2014 20:43:39 -0000 Subject: [Varnish] #1460: All entries in varnishhist is filed under 1e-6 (zero?) Message-ID: <046.28c206e39885419ea72e2c3f2c8551d6@varnish-cache.org> #1460: All entries in varnishhist is filed under 1e-6 (zero?) -------------------------+--------------------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0 release Component: varnishhist | Version: trunk Severity: normal | Keywords: -------------------------+--------------------------------- When running varnishhist, all the entries are filed in the 1e-6 bin of the histogram. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 25 10:02:38 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 25 Mar 2014 10:02:38 -0000 Subject: [Varnish] #1403: n_object becomes bogus every night In-Reply-To: <043.e8ea7fcf7ae28e33640a4bf2e3f04ab9@varnish-cache.org> References: <043.e8ea7fcf7ae28e33640a4bf2e3f04ab9@varnish-cache.org> Message-ID: <058.1a6d6e3bb5f5a126f431124aa3dab27c@varnish-cache.org> #1403: n_object becomes bogus every night ----------------------+---------------------------------- Reporter: scoof | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Varnish 4.0 release Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+---------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: Not seen for a long time according to scoof. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 25 10:47:35 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 25 Mar 2014 10:47:35 -0000 Subject: [Varnish] #1320: Varnish returns a 503 when being given a 302 by the webapp In-Reply-To: <042.e26368a7c676e3ed22ccad2cf3d7d4cd@varnish-cache.org> References: <042.e26368a7c676e3ed22ccad2cf3d7d4cd@varnish-cache.org> Message-ID: <057.b33ec9f3a186d3ca051d71fb78cf2c54@varnish-cache.org> #1320: Varnish returns a 503 when being given a 302 by the webapp --------------------+---------------------------------------- Reporter: Wilb | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: 3.0.3 Severity: normal | Resolution: fixed Keywords: | --------------------+---------------------------------------- Changes (by Poul-Henning Kamp ): * status: new => closed * owner: => Poul-Henning Kamp * resolution: => fixed Comment: In [ac21ca073d7a93268e9f7340519e2e9cc8db1d00]: {{{ #!CommitTicketReference repository="" revision="ac21ca073d7a93268e9f7340519e2e9cc8db1d00" If the backend sends "Content-Length: 0" and "Content_Encoding: gzip" it is buggy, work around it. If the backend sends chunked encoding we don't catch it and fail the transfer. Fixes: #1320 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 25 11:52:39 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 25 Mar 2014 11:52:39 -0000 Subject: [Varnish] #1461: Missing build dependency: ncurses devel Message-ID: <045.1fa8456432142e146bc39a8ea67285a5@varnish-cache.org> #1461: Missing build dependency: ncurses devel ---------------------------------+------------------------- Reporter: espebra | Type: enhancement Status: new | Priority: normal Milestone: Varnish 4.0 release | Component: build Version: trunk | Severity: trivial Keywords: | ---------------------------------+------------------------- If ncurses devel is not installed at the time of building Varnish, Varnish will build without varnishstat, varnishhist and varnishtop. A hard build dependency may avoid unnecessary troubleshooting. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 25 14:28:32 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 25 Mar 2014 14:28:32 -0000 Subject: [Varnish] #1450: Segfault in varnishstat with -l In-Reply-To: <046.cb082f0af3196092e65f34d669884e8d@varnish-cache.org> References: <046.cb082f0af3196092e65f34d669884e8d@varnish-cache.org> Message-ID: <061.25db3080f5c7520d609feabb13a24eca@varnish-cache.org> #1450: Segfault in varnishstat with -l -------------------------+--------------------- Reporter: lkarsten | Owner: martin Type: defect | Status: closed Priority: low | Milestone: Component: varnishstat | Version: trunk Severity: normal | Resolution: fixed Keywords: | -------------------------+--------------------- Changes (by Dag Haavi Finstad ): * status: new => closed * resolution: => fixed Comment: In [8a986ce96e1396edb80fdd538d2045ca2dd2d115]: {{{ #!CommitTicketReference repository="" revision="8a986ce96e1396edb80fdd538d2045ca2dd2d115" Fix 'varnishstat -l' segmentation fault. Fixes: #1450 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 26 13:28:01 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 26 Mar 2014 13:28:01 -0000 Subject: [Varnish] #1460: All entries in varnishhist is filed under 1e-6 (zero?) In-Reply-To: <046.28c206e39885419ea72e2c3f2c8551d6@varnish-cache.org> References: <046.28c206e39885419ea72e2c3f2c8551d6@varnish-cache.org> Message-ID: <061.730b13e978cb41da64f8cabffecce529@varnish-cache.org> #1460: All entries in varnishhist is filed under 1e-6 (zero?) -------------------------+---------------------------------- Reporter: lkarsten | Owner: daghf Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0 release Component: varnishhist | Version: trunk Severity: normal | Resolution: Keywords: | -------------------------+---------------------------------- Changes (by daghf): * owner: => daghf -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 26 14:51:51 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 26 Mar 2014 14:51:51 -0000 Subject: [Varnish] #1460: All entries in varnishhist is filed under 1e-6 (zero?) In-Reply-To: <046.28c206e39885419ea72e2c3f2c8551d6@varnish-cache.org> References: <046.28c206e39885419ea72e2c3f2c8551d6@varnish-cache.org> Message-ID: <061.674bde95c59624eeb6672a48cf15a0db@varnish-cache.org> #1460: All entries in varnishhist is filed under 1e-6 (zero?) -------------------------+---------------------------------- Reporter: lkarsten | Owner: daghf Type: defect | Status: closed Priority: normal | Milestone: Varnish 4.0 release Component: varnishhist | Version: trunk Severity: normal | Resolution: fixed Keywords: | -------------------------+---------------------------------- Changes (by Dag Haavi Finstad ): * status: new => closed * resolution: => fixed Comment: In [b40bd3dc159b3cf1efbb8eaa0521abd0645800a8]: {{{ #!CommitTicketReference repository="" revision="b40bd3dc159b3cf1efbb8eaa0521abd0645800a8" Update varnishhist to read ttfb from VSL_Timestamp record. Fixes: #1460 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 26 14:53:26 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 26 Mar 2014 14:53:26 -0000 Subject: [Varnish] #1462: ReqURL is emitted twice Message-ID: <043.4c15f0afe4e6c22dd922a9ce48ae670c@varnish-cache.org> #1462: ReqURL is emitted twice --------------------+----------------------------- Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP2 Component: build | Version: trunk Severity: normal | Keywords: --------------------+----------------------------- Before and after vcl_recv. Because of this, if url is changed in vcl_recv, varnishncsa will log the wrong URL. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 26 15:47:17 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 26 Mar 2014 15:47:17 -0000 Subject: [Varnish] #1405: Assert error in exp_inbox(), cache/cache_expire.c line 444 In-Reply-To: <043.e8bc6eb559047d8ef76c282eca47dbb2@varnish-cache.org> References: <043.e8bc6eb559047d8ef76c282eca47dbb2@varnish-cache.org> Message-ID: <058.ce4e12ebc801d80cb73a69682b0fe076@varnish-cache.org> #1405: Assert error in exp_inbox(), cache/cache_expire.c line 444 --------------------+---------------------- Reporter: scoof | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: unknown Severity: normal | Resolution: fixed Keywords: | --------------------+---------------------- Changes (by lkarsten): * status: new => closed * resolution: => fixed Comment: This has been resolved in a different commit. Scoof confirms that the issue is gone. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 27 09:59:26 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 27 Mar 2014 09:59:26 -0000 Subject: [Varnish] #1447: Panic message: Assert error in http_Write In-Reply-To: <046.4d292c524c5bcf6e4c46bbf1ff236ca0@varnish-cache.org> References: <046.4d292c524c5bcf6e4c46bbf1ff236ca0@varnish-cache.org> Message-ID: <061.814a499ef6a908b00b967b22af27b7b8@varnish-cache.org> #1447: Panic message: Assert error in http_Write -------------------------------------+---------------------- Reporter: scorillo | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 3.0.5 Severity: major | Resolution: invalid Keywords: panic assert http_write | -------------------------------------+---------------------- Changes (by daghf): * status: new => closed * resolution: => invalid Comment: Varnish is crashing with an assert because you are running out of workspace. To fix this, you should increase the session workspace available by increasing the sess_workspace parameter. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 27 09:59:57 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 27 Mar 2014 09:59:57 -0000 Subject: [Varnish] #1448: Segfault in jemalloc In-Reply-To: <046.4c03ddaddd5fbdf6a4f5e15b03fc8d18@varnish-cache.org> References: <046.4c03ddaddd5fbdf6a4f5e15b03fc8d18@varnish-cache.org> Message-ID: <061.f20b21ccc37c1102474a4611e9aa397d@varnish-cache.org> #1448: Segfault in jemalloc ----------------------+-------------------------------------------- Reporter: lkarsten | Owner: Lasse Karstensen Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 3.0.5 Severity: normal | Resolution: fixed Keywords: | ----------------------+-------------------------------------------- Comment (by mareks): Got the same crash again with these bits: Platform: Linux,2.6.39-200.24.1.el6uek.x86_64,x86_64,-smalloc,-smalloc,-hcritbit Linux,2.6.39-200.24.1.el6uek.x86_64,x86_64,-smalloc,-smalloc,-hcritbit varnish-3.0.5 revision 1a89b1f and stack trace: 2 Thread 0x7f7fd54ff700 (LWP 4815) 0x000000345fe0b98e in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 * 1 Thread 4807 arena_dalloc_small (ptr=0x7f7f740008f0) at jemalloc_linux.c:3687 (gdb) (gdb) thr a 1 bt Thread 1 (Thread 4807): #0 arena_dalloc_small (ptr=0x7f7f740008f0) at jemalloc_linux.c:3687 #1 arena_dalloc (ptr=0x7f7f740008f0) at jemalloc_linux.c:3939 #2 idalloc (ptr=0x7f7f740008f0) at jemalloc_linux.c:3957 #3 free (ptr=0x7f7f740008f0) at jemalloc_linux.c:5586 #4 0x000000345f211229 in _dl_deallocate_tls () from /lib64/ld- linux-x86-64.so.2 #5 0x000000345fe0675d in __free_stacks () from /lib64/libpthread.so.0 #6 0x000000345fe078ea in __free_tcb () from /lib64/libpthread.so.0 #7 0x000000345fe07b9d in start_thread () from /lib64/libpthread.so.0 #8 0x000000345f6e8b6d in clone () from /lib64/libc.so.6 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 27 14:18:38 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 27 Mar 2014 14:18:38 -0000 Subject: [Varnish] #1463: Assert in cnt_lookup(), cache/cache_req_fsm.c line 417 Message-ID: <046.fcde1d88ee5a91a1b85a42bd45352ba0@varnish-cache.org> #1463: Assert in cnt_lookup(), cache/cache_req_fsm.c line 417 ----------------------+------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+------------------- We tested current master (6dc740f00) in production, serving about 1400req/s. On a 2 hour run we saw this assert at the beginning. No asserts after the cache was warm. On a semi-related note, there was significant CPU usage (80-100% on 8 cores) when the cache was filling. Fell down to 300-450% when steady state was attained. {{{ Last panic at: Thu, 27 Mar 2014 12:01:27 GMT Assert error in cnt_lookup(), cache/cache_req_fsm.c line 417: Condition((oc->busyobj) == 0) not true. thread = (cache-worker) ident = Linux,2.6.32-431.5.1.el6.x86_64,x86_64,-smalloc,-smalloc,-hcritbit,epoll Backtrace: 0x4399d2: /usr/sbin/varnishd() [0x4399d2] 0x439ce2: /usr/sbin/varnishd() [0x439ce2] 0x43dc5f: /usr/sbin/varnishd() [0x43dc5f] 0x43fca8: /usr/sbin/varnishd(CNT_Request+0x441) [0x43fca8] 0x432be0: /usr/sbin/varnishd(HTTP1_Session+0x429) [0x432be0] 0x442c5d: /usr/sbin/varnishd() [0x442c5d] 0x442f28: /usr/sbin/varnishd() [0x442f28] 0x43b547: /usr/sbin/varnishd(Pool_Work_Thread+0x416) [0x43b547] 0x453f94: /usr/sbin/varnishd() [0x453f94] 0x4540bd: /usr/sbin/varnishd(WRK_thread+0x27) [0x4540bd] req = 0x7f3718caf910 { sp = 0x7f36e0452b70, vxid = 1079805327, step = R_STP_LOOKUP, req_body = R_BODY_NONE, restarts = 0, esi_level = 0 sp = 0x7f36e0452b70 { fd = 1158, vxid = 5573417, client = 85.166.x.x 62664, step = S_STP_WORKING, }, worker = 0x7f375c1dfc30 { ws = 0x7f375c1dfe30 { id = "wrk", {s,f,r,e} = {0x7f375c1df410,0x7f375c1df410,(nil),+2048}, }, VCL::method = 0x0, VCL::return = deliver, }, ws = 0x7f3718cafa98 { id = "req", {s,f,r,e} = {0x7f3718cb18f0,+520,(nil),+2088992}, }, http[req] = { ws = 0x7f3718cafa98[req] "GET", "XXX" "HTTP/1.1", "Accept: image/png, image/svg+xml, image/*;q=0.8, */*;q=0.5", "Referer: http://www.XXX/", "Accept-Language: nb-NO", "User-Agent: Mozilla/5.0 (Windows NT 6.1; Trident/7.0; rv:11.0) like Gecko", "Host: XXX", "DNT: 1", "Connection: Keep-Alive", "X-Forwarded-For: 85.166.xx.xx", "Accept-Encoding: gzip", "X-Debug-obj-ttl: -1.038", }, vcl = { srcname = { "input", "Default", "xx", "xx", "xx", "xx", }, }, busyobj = 0x7f36f80f0930 { ws = 0x7f36f80f09f8 { id = "bo", {s,f,r,e} = {0x7f36f80f28e0,+1432,(nil),+57424}, }, refcnt = 1 retries = 0 failed = 0 state = 2 is_do_stream is_is_gzip bodystatus = 3 (length), }, http[bereq] = { ws = 0x7f36f80f09f8[bo] "GET", "XXX", "HTTP/1.1", "Host: XXX", "Accept: image/webp,*/*;q=0.8", "User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.154 Safari/537.36", "Referer: http://www.YYYY", "Accept-Language: nb-NO,nb;q=0.8,no;q=0.6,nn;q=0.4,en- US;q=0.2,en;q=0.2", "X-Forwarded-For: 217.144.xx.xx", "Accept-Encoding: gzip", "X-Debug-obj-ttl: -1.005", "X-Varnish: 13797825", }, http[beresp] = { ws = 0x7f36f80f09f8[bo] "HTTP/1.1", "404", "Not Found", "X-Trace-App: xx", "Cache-Control: max-age=60, xxx", "Access-Control-Allow-Origin: *", "Content-Type: text/html; charset=iso-8859-1", "Server: Jetty(6.1.25)", "x-channel-maxage: 60", "X-Src-Webcache: xx", "Content-Encoding: gzip", "Content-Length: 95", "Accept-Ranges: bytes", "Date: Thu, 27 Mar 2014 12:01:26 GMT", "X-Varnish: 2835180224 2835179698", "Age: 5", "Via: 1.1 varnish", "Connection: keep-alive", "X-Trace-Cache: xxx", "X-Trace-CacheTMP: ", }, ws = 0x7f36f80f0b60 { id = "obj", {s,f,r,e} = {0x7f36b444d360,+728,(nil),+728}, }, objcore (FETCH) = 0x7f364da34060 { refcnt = 3 flags = 0x0 objhead = 0x7f3664236b40 } obj (FETCH) = 0x7f36b444d140 { vxid = 2161281473, http[obj] = { ws = 0x7f36f80f0b60[obj] "HTTP/1.1", "404", "Not Found", "X-Trace-App: xxx", "Cache-Control: max-age=60, xxx", "Access-Control-Allow-Origin: *", "Content-Type: text/html; charset=iso-8859-1", "Server: Jetty(6.1.25)", "x-channel-maxage: 60", "X-Src-Webcache: xx", "Content-Encoding: gzip", "Date: Thu, 27 Mar 2014 12:01:26 GMT", "X-Varnish: 2835180224 2835179698", "Via: 1.1 varnish", "X-Trace-Cache: xx", "X-Trace-CacheTMP: ", }, len = 0, store = { 0 { }, }, }, } obj (REQ) = 0x7f36b444d140 { vxid = 2161281473, http[obj] = { ws = 0x7f36f80f0b60[obj] "HTTP/1.1", "404", "Not Found", "X-Trace-App: xx", "Cache-Control: max-age=60, xx", "Access-Control-Allow-Origin: *", "Content-Type: text/html; charset=iso-8859-1", "Server: Jetty(6.1.25)", "x-channel-maxage: 60", "X-Src-Webcache: xx", "Content-Encoding: gzip", "Date: Thu, 27 Mar 2014 12:01:26 GMT", "X-Varnish: 2835180224 2835179698", "Via: 1.1 varnish", "X-Trace-Cache: xx", "X-Trace-CacheTMP: ", }, len = 0, store = { 0 { }, }, }, }, }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 27 14:55:11 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 27 Mar 2014 14:55:11 -0000 Subject: [Varnish] #1464: EL6 RPM packages are uninstallable Message-ID: <046.293d1117d044ad690864b0bf4e1b456a@varnish-cache.org> #1464: EL6 RPM packages are uninstallable -----------------------+------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: packaging | Version: trunk Severity: normal | Keywords: -----------------------+------------------- The RPM packages built from master for RHEL6 are uninstallable due to a dependency issue. {{{ [root at el6 ~]# LC_ALL=C yum localinstall varnish*rpm Loaded plugins: fastestmirror, presto Setting up Local Package Process Examining varnish-4.0.0-0.20131129tp2.el6.x86_64.rpm: varnish-4.0.0-0.20131129tp2.el6.x86_64 Marking varnish-4.0.0-0.20131129tp2.el6.x86_64.rpm to be installed Loading mirror speeds from cached hostfile * base: ftp.uninett.no * epel: ftp.uninett.no * extras: ftp.uninett.no * updates: ftp.uninett.no Examining varnish-debuginfo-4.0.0-0.20131129tp2.el6.x86_64.rpm: varnish- debuginfo-4.0.0-0.20131129tp2.el6.x86_64 Marking varnish-debuginfo-4.0.0-0.20131129tp2.el6.x86_64.rpm to be installed Examining varnish-libs-4.0.0-0.20131129tp2.el6.x86_64.rpm: varnish- libs-4.0.0-0.20131129tp2.el6.x86_64 Marking varnish-libs-4.0.0-0.20131129tp2.el6.x86_64.rpm to be installed Resolving Dependencies --> Running transaction check ---> Package varnish.x86_64 0:4.0.0-0.20131129tp2.el6 will be installed --> Processing Dependency: libvarnishapi.so.1(LIBVARNISHAPI_1.0)(64bit) for package: varnish-4.0.0-0.20131129tp2.el6.x86_64 --> Processing Dependency: libvarnishapi.so.1(LIBVARNISHAPI_1.1)(64bit) for package: varnish-4.0.0-0.20131129tp2.el6.x86_64 --> Processing Dependency: libvarnishapi.so.1(LIBVARNISHAPI_1.2)(64bit) for package: varnish-4.0.0-0.20131129tp2.el6.x86_64 --> Processing Dependency: libvarnishapi.so.1(LIBVARNISHAPI_1.3)(64bit) for package: varnish-4.0.0-0.20131129tp2.el6.x86_64 ---> Package varnish-debuginfo.x86_64 0:4.0.0-0.20131129tp2.el6 will be installed ---> Package varnish-libs.x86_64 0:4.0.0-0.20131129tp2.el6 will be installed --> Finished Dependency Resolution Error: Package: varnish-4.0.0-0.20131129tp2.el6.x86_64 (/varnish-4.0.0-0.20131129tp2.el6.x86_64) Requires: libvarnishapi.so.1(LIBVARNISHAPI_1.1)(64bit) Error: Package: varnish-4.0.0-0.20131129tp2.el6.x86_64 (/varnish-4.0.0-0.20131129tp2.el6.x86_64) Requires: libvarnishapi.so.1(LIBVARNISHAPI_1.2)(64bit) Error: Package: varnish-4.0.0-0.20131129tp2.el6.x86_64 (/varnish-4.0.0-0.20131129tp2.el6.x86_64) Requires: libvarnishapi.so.1(LIBVARNISHAPI_1.0)(64bit) Error: Package: varnish-4.0.0-0.20131129tp2.el6.x86_64 (/varnish-4.0.0-0.20131129tp2.el6.x86_64) Requires: libvarnishapi.so.1(LIBVARNISHAPI_1.3)(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root at el6 ~]# ^C [root at el6 ~]# ls -lh varnish*rpm -rw-r--r--. 1 root root 350K 2014-03-27 12:25 varnish-4.0.0-0.20131129tp2.el6.x86_64.rpm -rw-r--r--. 1 root root 77K 2014-03-27 12:25 varnish- debuginfo-4.0.0-0.20131129tp2.el6.x86_64.rpm -rw-r--r--. 1 root root 173K 2014-03-27 12:25 varnish- libs-4.0.0-0.20131129tp2.el6.x86_64.rpm [root at el6 ~]# }}} {{{ [root at el6 ~]# rpm -qp --requires varnish-4.0.0-0.20131129tp2.el6.x86_64.rpm varnish-libs = 4.0.0-0.20131129tp2.el6 logrotate ncurses pcre shadow-utils /sbin/chkconfig /usr/bin/uuidgen /sbin/chkconfig /sbin/service initscripts gcc /bin/sh /bin/sh /bin/sh /bin/sh rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 /bin/bash /bin/sh libc.so.6()(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3.2)(64bit) libc.so.6(GLIBC_2.3)(64bit) libdl.so.2()(64bit) libdl.so.2(GLIBC_2.2.5)(64bit) libedit.so.0()(64bit) libm.so.6()(64bit) libm.so.6(GLIBC_2.2.5)(64bit) libncurses.so.5()(64bit) libncursesw.so.5()(64bit) libnsl.so.1()(64bit) libpcre.so.0()(64bit) libpthread.so.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit) libpthread.so.0(GLIBC_2.3.2)(64bit) librt.so.1()(64bit) librt.so.1(GLIBC_2.2.5)(64bit) libtinfo.so.5()(64bit) libvarnishapi.so.1()(64bit) libvarnishapi.so.1(LIBVARNISHAPI_1.0)(64bit) libvarnishapi.so.1(LIBVARNISHAPI_1.1)(64bit) libvarnishapi.so.1(LIBVARNISHAPI_1.2)(64bit) libvarnishapi.so.1(LIBVARNISHAPI_1.3)(64bit) libvarnishcompat.so()(64bit) libvarnish.so()(64bit) libvcc.so()(64bit) libvgz.so()(64bit) rpmlib(PayloadIsXz) <= 5.2-1 [root at el6 ~]# }}} {{{ [root at el6 ~]# rpm -qp --provides varnish- libs-4.0.0-0.20131129tp2.el6.x86_64.rpm libvarnishapi.so.1 libc.so.6()(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.7)(64bit) libm.so.6()(64bit) libm.so.6(GLIBC_2.2.5)(64bit) libnsl.so.1()(64bit) libpcre.so.0()(64bit) libpthread.so.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit) librt.so.1()(64bit) librt.so.1(GLIBC_2.2.5)(64bit) varnishabi-4.0.0-tp2-6dc740f varnish-libs = 4.0.0-0.20131129tp2.el6 varnish-libs(x86-64) = 4.0.0-0.20131129tp2.el6 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 27 15:33:23 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 27 Mar 2014 15:33:23 -0000 Subject: [Varnish] #1464: EL6 RPM packages are uninstallable In-Reply-To: <046.293d1117d044ad690864b0bf4e1b456a@varnish-cache.org> References: <046.293d1117d044ad690864b0bf4e1b456a@varnish-cache.org> Message-ID: <061.5cec944320753703a199692874fc7c68@varnish-cache.org> #1464: EL6 RPM packages are uninstallable -----------------------+------------------------ Reporter: lkarsten | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: packaging | Version: trunk Severity: normal | Resolution: duplicate Keywords: | -----------------------+------------------------ Changes (by lkarsten): * status: new => closed * resolution: => duplicate Comment: This is a duplicate of #1445. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 27 17:13:35 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 27 Mar 2014 17:13:35 -0000 Subject: [Varnish] #1445: Missing provides in varnish rpm, varnish-4.0.0-tp2+2014-03-06, fedora 19 In-Reply-To: <044.6a2ead7fd03370bd700a92dffb4f5e2a@varnish-cache.org> References: <044.6a2ead7fd03370bd700a92dffb4f5e2a@varnish-cache.org> Message-ID: <059.41e823c0ef973a4fd328c67e4d0bb7e4@varnish-cache.org> #1445: Missing provides in varnish rpm, varnish-4.0.0-tp2+2014-03-06, fedora 19 -------------------------------------------------+------------------------- Reporter: ingvar | Owner: Type: defect | Status: closed Priority: normal | Milestone: Varnish Component: build | 4.0-TP2 Severity: normal | Version: unknown Keywords: rpm specfile redhat varnish-libs | Resolution: fixed provides | -------------------------------------------------+------------------------- Changes (by lkarsten): * status: new => closed * resolution: => fixed Comment: Merged in 6f4a02dd. Thanks. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 28 08:21:33 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 28 Mar 2014 08:21:33 -0000 Subject: [Varnish] #1465: Empty chunked response on storage failure Message-ID: <046.2a16722930c8a8f8903e2d31a85fb9eb@varnish-cache.org> #1465: Empty chunked response on storage failure ----------------------+------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+------------------- When Varnish is not able to get storage for a new object, it appears to send a 200 OK with Transfer-Encoding: chunked, but no body data. Expected result: Varnish resetting the TCP connection to indicate failure. What is happening: packet trace shows a well-formed HTTP header, then the connection is closed by the remote/Varnish with FIN+ACK, which my system happily responds FIN+ACK to. varnishd (varnish-4.0.0-tp2 revision 405aad9) From Wireshark's "follow TCP connection": {{{ GET / HTTP/1.1 TE: deflate,gzip;q=0.3 Connection: TE, close Host: hyse.org User-Agent: lwp-request/6.03 libwww-perl/6.05 HTTP/1.1 200 OK Server: nginx/1.4.1 (Ubuntu) Content-Type: text/html Last-Modified: Wed, 26 Feb 2014 10:16:05 GMT Date: Fri, 28 Mar 2014 07:24:58 GMT X-Varnish: 136268 Age: 0 Via: 1.1 varnish (v4) Transfer-Encoding: chunked Connection: close Accept-Ranges: bytes }}} varnishlog of the failing request: {{{ * << Session >> 136267 - Begin sess 0 HTTP/1 - SessOpen 84.215.144.99 41700 :80 91.227.249.12 80 1395991497.998688 15 - Link req 136268 rxreq - SessClose REM_CLOSE 0.030 1 0 0 1 1 0 - End ** << Request >> 136268 -- Begin req 136267 rxreq -- ReqStart 84.215.144.99 41700 -- ReqMethod GET -- ReqURL / -- ReqProtocol HTTP/1.1 -- ReqHeader TE: deflate,gzip;q=0.3 -- ReqHeader Connection: TE, close -- ReqHeader Host: hyse.org -- ReqHeader User-Agent: lwp-request/6.03 libwww-perl/6.05 -- ReqHeader X-Forwarded-For: 84.215.144.99 -- VCL_call RECV -- VCL_return hash -- VCL_call HASH -- VCL_return lookup -- Debug "XXXX MISS" -- VCL_call MISS -- VCL_return fetch -- Link bereq 136269 fetch -- RespProtocol HTTP/1.1 -- RespStatus 200 -- RespResponse OK -- RespHeader Server: nginx/1.4.1 (Ubuntu) -- RespHeader Date: Fri, 28 Mar 2014 07:24:58 GMT -- RespHeader Content-Type: text/html -- RespHeader Last-Modified: Wed, 26 Feb 2014 10:16:05 GMT -- RespHeader Content-Encoding: gzip -- RespUnset Date: Fri, 28 Mar 2014 07:24:58 GMT -- RespHeader Date: Fri, 28 Mar 2014 07:24:58 GMT -- RespHeader X-Varnish: 136268 -- RespHeader Age: 0 -- RespHeader Via: 1.1 varnish (v4) -- VCL_call DELIVER -- VCL_return deliver -- Debug "RES_MODE 48" -- RespUnset Content-Encoding: gzip -- RespHeader Transfer-Encoding: chunked -- RespHeader Connection: close -- RespHeader Accept-Ranges: bytes -- Gzip U D - 0 0 0 0 0 -- Debug "XXX REF 2" -- ReqEnd 1395991498.026633501 1395991497.998687983 -0.029036760 0.001091242 -0.029036760 -- End *** << BeReq >> 136269 --- Begin bereq 136268 fetch --- BereqMethod GET --- BereqURL / --- BereqProtocol HTTP/1.1 --- BereqHeader Host: hyse.org --- BereqHeader User-Agent: lwp-request/6.03 libwww-perl/6.05 --- BereqHeader X-Forwarded-For: 84.215.144.99 --- BereqHeader Accept-Encoding: gzip --- BereqHeader X-Varnish: 136269 --- VCL_call BACKEND_FETCH --- VCL_return fetch --- BackendOpen 18 default(127.0.0.1,,8085) 127.0.0.1 47270 --- Backend 18 default default(127.0.0.1,,8085) --- BerespProtocol HTTP/1.1 --- BerespStatus 200 --- BerespResponse OK --- BerespHeader Server: nginx/1.4.1 (Ubuntu) --- BerespHeader Date: Fri, 28 Mar 2014 07:24:58 GMT --- BerespHeader Content-Type: text/html --- BerespHeader Last-Modified: Wed, 26 Feb 2014 10:16:05 GMT --- BerespHeader Transfer-Encoding: chunked --- BerespHeader Connection: keep-alive --- BerespHeader Content-Encoding: gzip --- TTL RFC 20 -1 -1 1395991498 1395991498 1395991498 0 0 --- VCL_call BACKEND_RESPONSE --- TTL VCL 20 60 0 1395991498 --- TTL VCL 20 60 86400 1395991498 --- VCL_return deliver --- Storage malloc s0 --- ObjProtocol HTTP/1.1 --- ObjStatus 200 --- ObjResponse OK --- ObjHeader Server: nginx/1.4.1 (Ubuntu) --- ObjHeader Date: Fri, 28 Mar 2014 07:24:58 GMT --- ObjHeader Content-Type: text/html --- ObjHeader Last-Modified: Wed, 26 Feb 2014 10:16:05 GMT --- ObjHeader Content-Encoding: gzip --- Fetch_Body 2 chunked stream --- ExpKill LRU_Cand p=0x7ff3c400ce90 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff3c405d7c0 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff3c4030a50 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff3b8254ce0 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff3b8254d70 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff3b8254f00 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff3c03a7120 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff3c03a7440 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff3c0412ed0 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff3c04131f0 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff3b840e320 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff3b806d240 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff3b800b960 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff3b800bdb0 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff3c04183d0 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff3b80b8780 f=0x0 r=2 [ 560 lines of ExpKill removed ] --- ExpKill LRU_Cand p=0x7ff3c10439b0 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff2c40ffec0 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff2c4126ec0 f=0x0 r=2 --- ExpKill LRU_Cand p=0x7ff2b58a2920 f=0x0 r=7 --- ExpKill LRU_Cand p=0x7ff38c000e00 f=0x200 r=3 --- ExpKill LRU_Fail --- FetchError Could not get storage --- Gzip u F - 0 0 0 0 0 --- BackendClose 18 default(127.0.0.1,,8085) --- BereqEnd 1395991498.026790142 1395991498.028229713 0.000505485 0.000008513 0.000057440 0.000065953 --- End }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 28 09:11:02 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 28 Mar 2014 09:11:02 -0000 Subject: [Varnish] #1463: Assert in cnt_lookup(), cache/cache_req_fsm.c line 417 In-Reply-To: <046.fcde1d88ee5a91a1b85a42bd45352ba0@varnish-cache.org> References: <046.fcde1d88ee5a91a1b85a42bd45352ba0@varnish-cache.org> Message-ID: <061.f96d52f2dcf451fed5a1a7b54ed635fb@varnish-cache.org> #1463: Assert in cnt_lookup(), cache/cache_req_fsm.c line 417 ----------------------+--------------------- Reporter: lkarsten | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+--------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: Fixed, the assert looks at the wrong objcore -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 28 09:12:31 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 28 Mar 2014 09:12:31 -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.a5191a2c829a2344eb554357d9eb1cc6@varnish-cache.org> #1462: ReqURL is emitted twice --------------------+------------------------------ Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP2 Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+------------------------------ Comment (by phk): This is a consequence of our new "log all changes" policy. I'm not sure if varnishncsa should log the original or the adjusted URL. Somebody should make a decision and implement it. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 28 12:07:57 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 28 Mar 2014 12:07:57 -0000 Subject: [Varnish] #1466: struct req memory leak Message-ID: <044.405f83ccd9aea5f6bdeca16bd684d5a1@varnish-cache.org> #1466: struct req memory leak ----------------------+------------------- Reporter: martin | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+------------------- When waking a waitinglist, hsh_rush calls SES_ScheduleReq with the requests that needs to be woken. If SES_ScheduleReq can't queue the task (no worker available), it will loose the struct req on the floor. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 28 20:47:40 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 28 Mar 2014 20:47:40 -0000 Subject: [Varnish] #1448: Segfault in jemalloc In-Reply-To: <046.4c03ddaddd5fbdf6a4f5e15b03fc8d18@varnish-cache.org> References: <046.4c03ddaddd5fbdf6a4f5e15b03fc8d18@varnish-cache.org> Message-ID: <061.2e69d2544d4a3500884aeb7b664d1259@varnish-cache.org> #1448: Segfault in jemalloc ----------------------+-------------------------------------------- Reporter: lkarsten | Owner: Lasse Karstensen Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 3.0.5 Severity: normal | Resolution: fixed Keywords: | ----------------------+-------------------------------------------- Comment (by mareks): Usually happens around the time when worker threads are purged and default vcl is (re)loaded: {{{ 0 WorkThread - 0x7fdb9ebc9a90 end 0 CLI - Rd ping 0 CLI - Wr 200 19 PONG 1396044042 1.0 0 WorkThread - 0x7fdba300aa90 end 0 WorkThread - 0x7fdb9e3c8a90 end 0 CLI - Rd ping 0 CLI - Wr 200 19 PONG 1396044045 1.0 0 WorkThread - 0x7fdba41fba90 end 0 CLI - Rd vcl.load "boot" ./vcl.v8g0ve4i.so 0 WorkThread - 0x7fdba51fda90 start 0 WorkThread - 0x7fdba300aa90 start 0 WorkThread - 0x7fdba2809a90 start 0 WorkThread - 0x7fdba1807a90 start 0 WorkThread - 0x7fdba2008a90 start 0 WorkThread - 0x7fdba1006a90 start 0 WorkThread - 0x7fdba0004a90 start 0 WorkThread - 0x7fdb9f3caa90 start 0 WorkThread - 0x7fdba0805a90 start 0 WorkThread - 0x7fdb9ebc9a90 start 0 WorkThread - 0x7fdb9e3c8a90 start 0 WorkThread - 0x7fdb9dbc7a90 start 0 WorkThread - 0x7fdb9d3c6a90 start 0 CLI - Wr 200 36 Loaded "./vcl.v8g0ve4i.so" as "boot" }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 31 09:07:36 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 31 Mar 2014 09:07:36 -0000 Subject: [Varnish] #1467: Assert error in HSH_RefBusy(); Condition((bo)->magic == 0x23b95567) not true Message-ID: <046.fd6be300b168e3c4917df7bb5cf70b7d@varnish-cache.org> #1467: Assert error in HSH_RefBusy(); Condition((bo)->magic == 0x23b95567) not true ----------------------+------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+------------------- current master 8d3e492 ran into this assert: {{{ Last panic at: Mon, 31 Mar 2014 01:25:29 GMT Assert error in HSH_RefBusy(), cache/cache_hash.c line 737: Condition((bo)->magic == 0x23b95567) not true. thread = (cache-worker) ident = Linux,3.11.0-18-generic,x86_64,-smalloc,-smalloc,-hcritbit,epoll Backtrace: 0x439f23: pan_backtrace+0x19 0x43a22d: pan_ic+0x1e9 0x42c37b: HSH_RefBusy+0x199 0x4382ea: ObjIterBegin+0xd8 0x44120e: v1d_WriteDirObj+0x99 0x441b54: V1D_Deliver+0x800 0x43d13b: cnt_deliver+0x7ba 0x4404a1: CNT_Request+0x529 0x4330c0: HTTP1_Session+0x426 0x443352: ses_req_pool_task+0x166 req = 0x7f56480008e0 { sp = 0x7f564c001b70, vxid = 1073939965, step = R_STP_DELIVER, req_body = R_BODY_NONE, err_code = 404, err_reason = (null), restarts = 0, esi_level = 0 sp = 0x7f564c001b70 { fd = 15, vxid = 198140, client = 66.249.78.150 64324, step = S_STP_WORKING, }, worker = 0x7f5669728c30 { ws = 0x7f5669728e30 { id = "wrk", {s,f,r,e} = {0x7f5669728400,+80,+2048,+2048}, }, VCL::method = 0x0, VCL::return = deliver, }, ws = 0x7f5648000a68 { id = "req", {s,f,r,e} = {0x7f56480028c0,+400,(nil),+57376}, }, http[req] = { ws = 0x7f5648000a68[req] "GET", "/robots.txt", "HTTP/1.1", "Host: hyse.org", "Connection: Keep-alive", "Accept: text/plain", "Accept: text/html", "From: googlebot(at)googlebot.com", "User-Agent: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)", "X-Forwarded-For: 66.249.78.150", "Accept-Encoding: gzip", }, http[resp] = { ws = 0x7f5648000a68[req] "HTTP/1.1", "404", "Not Found", "Server: nginx/1.4.1 (Ubuntu)", "Content-Type: text/html", "Content-Encoding: gzip", "Date: Mon, 31 Mar 2014 01:25:27 GMT", "X-Varnish: 198141", "Age: 0", "Via: 1.1 varnish (v4)", "Transfer-Encoding: chunked", "Connection: keep-alive", }, vcl = { srcname = { "input", "Builtin", }, }, busyobj = 0x7f5654080a60 { ws = 0x7f5654080b28 { BAD_MAGIC(0x00000000) }, }, refcnt = 0 retries = 0 failed = 0 state = 0 bodystatus = 0 (none), }, }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 31 09:13:12 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 31 Mar 2014 09:13:12 -0000 Subject: [Varnish] #1467: Assert error in HSH_RefBusy(); Condition((bo)->magic == 0x23b95567) not true In-Reply-To: <046.fd6be300b168e3c4917df7bb5cf70b7d@varnish-cache.org> References: <046.fd6be300b168e3c4917df7bb5cf70b7d@varnish-cache.org> Message-ID: <061.00c23e89a9945fe530b59528d5dcde35@varnish-cache.org> #1467: Assert error in HSH_RefBusy(); Condition((bo)->magic == 0x23b95567) not true ----------------------+-------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Comment (by lkarsten): I've had three instances of this over the weekend, with trivial traffic levels. The two other panics: {{{ Mar 30 13:00:38 sierra kernel: [61393.719657] varnishd[2358]: segfault at 10 ip 00000000004399cc sp 00007f56696bbff0 error 4 in varnishd[400000+9e000] Mar 30 13:00:38 sierra varnishd[2125]: Child (2143) died signal=11 (core dumped) Mar 30 13:00:38 sierra varnishd[2125]: Child (2143) Panic message: Assert error in HSH_RefBusy(), cache/cache_hash.c line 737:#012 Condition((bo)->magic == 0x23b95567) not true.#012thread = (cache- worker)#012ident = Linux,3.11.0-18-generic,x86_64,-smalloc,-smalloc,-hcritbit,epoll#012Backtrace:#012 0x439f23: pan_backtrace+0x19#012 0x43a22d: pan_ic+0x1e9#012 0x42c37b: HSH_RefBusy+0x199#012 0x4382ea: ObjIterBegin+0xd8#012 0x44120e: v1d_WriteDirObj+0x99#012 0x441b54: V1D_Deliver+0x800#012 0x43d13b: cnt_deliver+0x7ba#012 0x4404a1: CNT_Request+0x529#012 0x4330c0: HTTP1_Session+0x426#012 0x443352: ses_req_pool_task+0x166#012req = 0x7f56480409a0 {#012 sp = 0x7f563c000a90, vxid = 1073906261, step = R_STP_DELIVER,#012 req_body = R_BODY_NONE,#012 err_code = 200, err_reason = (null),#012 restarts = 0, esi_level = 0#012 sp = 0x7f563c000a90 {#012 fd = 14, vxid = 164436,#012 client = 37.253.23.63 60534,#012 step = S_STP_WORKING,#012 },#012 worker = 0x7f56696bcc30 {#012 ws = 0x7f56696bce30 {#012 id = "wrk",#012 {s,f,r,e} = {0x7f56696bc400,+80,+2048,+2048},#012 },#012 VCL::method = 0x0,#012 VCL::return = deliver,#012 },#012 ws = 0x7f5648040b28 {#012 id = "req",#012 {s,f,r,e} = {0x7f5648042980,+320,(nil),+57376},#012 },#012 http[req] = {#012 ws = 0x7f5648040b28[req]#012 "GET",#012 "/djfriendly/djfriendly-nrkp3-2014-03-15__2200.mp3",#012 "HTTP/1.1",#012 "Host: hyse.org",#012 "Connection: Keep- Alive",#012 "User-Agent: Dalvik/1.6.0 (Linux; U; Android 4.4.2; SM-N9005 Build/KOT49H)",#012 "X-Forwarded-For: 37.253.23.63",#012 },#012 http[resp] = {#012 ws = 0x7f5648040b28[req]#012 "HTTP/1.1",#012 "200",#012 "OK",#012 "Server: nginx/1.4.1 (Ubuntu)",#012 "Content-Type: audio/mpeg",#012 "Last-Modified: Sat, 15 Mar 2014 23:00:05 GMT",#012 "ETag: "5324db75-a4e67e5"",#012 "Date: Sun, 30 Mar 2014 11:00:37 GMT",#012 "X-Varnish: 164437",#012 "Age: 0",#012 "Via: 1.1 varnish (v4)",#012 "Trans }}} {{{ Mar 31 03:25:27 sierra kernel: [113283.511087] varnishd[12023]: segfault at 10 ip 00000000004399cc sp 00007f5669727ff0 error 4 in varnishd[400000+9e000] Mar 31 03:25:28 sierra varnishd[2125]: Child (11817) not responding to CLI, killing it. Mar 31 03:25:29 sierra varnishd[2125]: Child (11817) died signal=11 (core dumped) Mar 31 03:25:29 sierra varnishd[2125]: Child (11817) Panic message: Assert error in HSH_RefBusy(), cache/cache_hash.c line 737:#012 Condition((bo)->magic == 0x23b95567) not true.#012thread = (cache- worker)#012ident = Linux,3.11.0-18-generic,x86_64,-smalloc,-smalloc,-hcritbit,epoll#012Backtrace:#012 0x439f23: pan_backtrace+0x19#012 0x43a22d: pan_ic+0x1e9#012 0x42c37b: HSH_RefBusy+0x199#012 0x4382ea: ObjIterBegin+0xd8#012 0x44120e: v1d_WriteDirObj+0x99#012 0x441b54: V1D_Deliver+0x800#012 0x43d13b: cnt_deliver+0x7ba#012 0x4404a1: CNT_Request+0x529#012 0x4330c0: HTTP1_Session+0x426#012 0x443352: ses_req_pool_task+0x166#012req = 0x7f56480008e0 {#012 sp = 0x7f564c001b70, vxid = 1073939965, step = R_STP_DELIVER,#012 req_body = R_BODY_NONE,#012 err_code = 404, err_reason = (null),#012 restarts = 0, esi_level = 0#012 sp = 0x7f564c001b70 {#012 fd = 15, vxid = 198140,#012 client = 66.249.78.150 64324,#012 step = S_STP_WORKING,#012 },#012 worker = 0x7f5669728c30 {#012 ws = 0x7f5669728e30 {#012 id = "wrk",#012 {s,f,r,e} = {0x7f5669728400,+80,+2048,+2048},#012 },#012 VCL::method = 0x0,#012 VCL::return = deliver,#012 },#012 ws = 0x7f5648000a68 {#012 id = "req",#012 {s,f,r,e} = {0x7f56480028c0,+400,(nil),+57376},#012 },#012 http[req] = {#012 ws = 0x7f5648000a68[req]#012 "GET",#012 "/robots.txt",#012 "HTTP/1.1",#012 "Host: hyse.org",#012 "Connection: Keep-alive",#012 "Accept: text/plain",#012 "Accept: text/html",#012 "From: googlebot(at)googlebot.com",#012 "User- Agent: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)",#012 "X-Forwarded-For: 66.249.78.150",#012 "Accept-Encoding: gzip",#012 },#012 http[resp] = {#012 ws = 0x7f5648000a68[req]#012 "HTTP/1.1",#012 "404",#012 "Not Found",#012 "Server: nginx/1.4.1 (Ubuntu)",#012 "Content-Type: text/html",#012 "Content-Encoding: gzip",#012 "Date: Mon, 31 Mar 2014 01:25:27 GMT",#012 "X-Varnish: 198141",#012 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Mar 31 12:58:07 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 31 Mar 2014 12:58:07 -0000 Subject: [Varnish] #1467: Assert error in HSH_RefBusy(); Condition((bo)->magic == 0x23b95567) not true In-Reply-To: <046.fd6be300b168e3c4917df7bb5cf70b7d@varnish-cache.org> References: <046.fd6be300b168e3c4917df7bb5cf70b7d@varnish-cache.org> Message-ID: <061.1e8b6c709d5938abf575b398081603fd@varnish-cache.org> #1467: Assert error in HSH_RefBusy(); Condition((bo)->magic == 0x23b95567) not true ----------------------+----------------------------------------------- Reporter: lkarsten | Owner: Martin Blix Grydeland Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------- Changes (by Martin Blix Grydeland ): * owner: => Martin Blix Grydeland * status: new => closed * resolution: => fixed Comment: In [20319dd6e73e2979948468f49ed11cb7a00a6156]: {{{ #!CommitTicketReference repository="" revision="20319dd6e73e2979948468f49ed11cb7a00a6156" Fix missing clearing of oc->busyobj on HSH_Fail. The oc's busyobj isn't cleared in HSH_Fail (like it is in HSH_Complete). This allows a thread to get a pointer to an already free'd busyobj. Fixes: #1467 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator