From varnish-bugs at varnish-cache.org Wed Jan 1 18:27:34 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 01 Jan 2014 18:27:34 -0000 Subject: [Varnish] #1401: Assert error in vbf_stp_startfetch(), cache/cache_fetch.c line 118 Message-ID: <046.47b9f956d56dbfe80790b785393898a5@varnish-cache.org> #1401: Assert error in vbf_stp_startfetch(), cache/cache_fetch.c line 118 -----------------------------+---------------------- Reporter: dmalinow | Type: defect Status: new | Priority: normal Milestone: Varnish 4.0-TP1 | Component: varnishd Version: trunk | Severity: normal Keywords: | -----------------------------+---------------------- After I add the option '''return (retry);''' in vcl_backend_response varnish crashed {{{#!python sub vcl_backend_response { ... return (retry); ... } }}} {{{#!python Panic message: Assert error in vbf_stp_startfetch(), cache/cache_fetch.c line 118: Condition((bo->should_close) == 0) not true. thread = (cache-worker) ident = Linux,2.6.32-431.1.2.0.1.el6.x86_64,x86_64,-sfile,-smalloc,-hcritbit,epoll Backtrace: 0x437a73: /usr/sbin/varnishd() [0x437a73] 0x437d83: /usr/sbin/varnishd() [0x437d83] 0x422052: /usr/sbin/varnishd() [0x422052] 0x42419e: /usr/sbin/varnishd() [0x42419e] 0x4394f7: /usr/sbin/varnishd(Pool_Work_Thread+0x416) [0x4394f7] 0x451fd4: /usr/sbin/varnishd() [0x451fd4] 0x4520fd: /usr/sbin/varnishd(WRK_thread+0x27) [0x4520fd] 0x7fcdf210f9d1: /lib64/libpthread.so.0(+0x79d1) [0x7fcdf210f9d1] 0x7fcdf1e5cb6d: /lib64/libc.so.6(clone+0x6d) [0x7fcdf1e5cb6d] busyobj = 0x7fcd840916f0 { ws = 0x7fcd84091790 { id = "bo", {s,f,r,e} = {0x7fcd840936b8,+608,(nil),+57400}, }, do_stream should_close bodystatus = 3 (length), }, http[bereq] = { ws = 0x7fcd84091790[bo] "GET", "/new.php", "HTTP/1.1", "Host: 168.192.1.36", "User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0", "Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8", "Accept-Language: pl,en-us;q=0.7,en;q=0.3", "Accept-Encoding: gzip, deflate", "x-up-calling-line-id: 48509000223", "X-Forwarded-For: 168.192.1.42", "X-Varnish: 3", "X-MALINA: PHPSESSID=9tvmc0k9s2v7ppstsfvb9gojf3", }, http[beresp] = { ws = 0x7fcd84091790[bo] "HTTP/1.1", "200", "OK", "Date: Wed, 01 Jan 2014 18:00:53 GMT", "Server: Apache/2.2.15 (CentOS) DAV/2 PHP/5.3.3", "X-Powered-By: PHP/5.3.3", "Set-Cookie: PHPSESSID=9tvmc0k9s2v7ppstsfvb9gojf3; path=/", "Expires: Thu, 19 Nov 1981 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 1 20:36:31 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 01 Jan 2014 20:36:31 -0000 Subject: [Varnish] #1402: Failed dependencies: libvarnishapi.so.1 Message-ID: <046.8f382fc03c0717150d85139dbc82a371@varnish-cache.org> #1402: Failed dependencies: libvarnishapi.so.1 -----------------------------+----------------------- Reporter: dmalinow | Type: defect Status: new | Priority: normal Milestone: Varnish 4.0-TP1 | Component: packaging Version: trunk | Severity: major Keywords: | -----------------------------+----------------------- {{{#!python rpm -Uvh ~/rpmbuild/RPMS/x86_64/varnish-4.0.0-0.20131129tp1.el6.x86_64.rpm error: Failed dependencies: libvarnishapi.so.1(LIBVARNISHAPI_1.0)(64bit) is needed by varnish-4.0.0-0.20131129tp1.el6.x86_64 libvarnishapi.so.1(LIBVARNISHAPI_1.1)(64bit) is needed by varnish-4.0.0-0.20131129tp1.el6.x86_64 libvarnishapi.so.1(LIBVARNISHAPI_1.2)(64bit) is needed by varnish-4.0.0-0.20131129tp1.el6.x86_64 libvarnishapi.so.1(LIBVARNISHAPI_1.3)(64bit) is needed by varnish-4.0.0-0.20131129tp1.el6.x86_64 }}} If you omit the dependencies, everything works ok. The issue is related to the lack of proper delivery of information by varnish-libs package. Stable package {{{#!python rpm -p ~/rpmbuild/RPMS/x86_64/varnish-libs-3.0.5-1.el6.x86_64.rpm -q --provides libvarnishapi.so.1()(64bit) libvarnishapi.so.1(LIBVARNISHAPI_1.0)(64bit) libvarnishapi.so.1(LIBVARNISHAPI_1.1)(64bit) varnish-libs = 3.0.5-1.el6 varnish-libs(x86-64) = 3.0.5-1.el6 }}} Trunk (4.0 tp1) package {{{#!python rpm -p ~/rpmbuild/RPMS/x86_64/varnish- libs-4.0.0-0.20131129tp1.el6.x86_64.rpm -q --provides 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-trunk-b9226c1 varnish-libs = 4.0.0-0.20131129tp1.el6 varnish-libs(x86-64) = 4.0.0-0.20131129tp1.el6 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 1 20:38:15 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 01 Jan 2014 20:38:15 -0000 Subject: [Varnish] #1402: Failed dependencies: libvarnishapi.so.1 In-Reply-To: <046.8f382fc03c0717150d85139dbc82a371@varnish-cache.org> References: <046.8f382fc03c0717150d85139dbc82a371@varnish-cache.org> Message-ID: <061.786075a1e1b504b9149bc94220210fc9@varnish-cache.org> #1402: Failed dependencies: libvarnishapi.so.1 -----------------------+------------------------------ Reporter: dmalinow | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP1 Component: packaging | Version: trunk Severity: major | Resolution: Keywords: | -----------------------+------------------------------ Comment (by dmalinow): workaround: {{{#!python rpm -Uvh --nodeps /home/atg/rpmbuild/RPMS/x86_64/varnish-4.0.0-0.20131129tp1.el6.x86_64.rpm }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 1 21:26:45 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 01 Jan 2014 21:26:45 -0000 Subject: [Varnish] #1402: Failed dependencies: libvarnishapi.so.1 In-Reply-To: <046.8f382fc03c0717150d85139dbc82a371@varnish-cache.org> References: <046.8f382fc03c0717150d85139dbc82a371@varnish-cache.org> Message-ID: <061.f5f5bdbb783158653828509e3d1b5d31@varnish-cache.org> #1402: Failed dependencies: libvarnishapi.so.1 -----------------------+------------------------------ Reporter: dmalinow | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP1 Component: packaging | Version: trunk Severity: major | Resolution: Keywords: | -----------------------+------------------------------ Comment (by dmalinow): Fixed with commit (proposal changes) 7797d10 on github. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 2 10:08:37 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 02 Jan 2014 10:08:37 -0000 Subject: [Varnish] #1398: Assert error in VRT_r_beresp_backend_name(), cache/cache_vrt_var.c In-Reply-To: <059.60efee19c4ef65c9297e7b5d100abaf4@varnish-cache.org> References: <059.60efee19c4ef65c9297e7b5d100abaf4@varnish-cache.org> Message-ID: <074.f9efa1ee9e0bda96ea01f5d2db329522@varnish-cache.org> #1398: Assert error in VRT_r_beresp_backend_name(), cache/cache_vrt_var.c -------------------------------------+------------------------------------- Reporter: varnish@? | Owner: Poul-Henning Kamp Type: defect | Priority: normal | Status: closed Component: varnishd | Milestone: Varnish 4.0-TP1 Severity: normal | Version: trunk Keywords: assert assertion | Resolution: fixed VRT_r_beresp_backend_name | -------------------------------------+------------------------------------- Changes (by Poul-Henning Kamp ): * owner: => Poul-Henning Kamp * status: new => closed * resolution: => fixed Comment: In [7f9a989f2178295d52a92e0be4f2ca2c15cd919b]: {{{ #!CommitTicketReference repository="" revision="7f9a989f2178295d52a92e0be4f2ca2c15cd919b" Fix NULL deref related to a backend we don't know any more. Fixes #1398 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 2 10:52:47 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 02 Jan 2014 10:52:47 -0000 Subject: [Varnish] #1399: Memory get freed while in use by another thread/object In-Reply-To: <059.1e289aaa7c9164a8a63898e6d8c12f43@varnish-cache.org> References: <059.1e289aaa7c9164a8a63898e6d8c12f43@varnish-cache.org> Message-ID: <074.b24da5381a340f0add15e56577b5cf21@varnish-cache.org> #1399: Memory get freed while in use by another thread/object -------------------------------------------------+------------------------- Reporter: varnish@? | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish Component: varnishd | 4.0-TP1 Severity: major | Version: trunk Keywords: memory get freed MPL_Free | Resolution: vbf_stp_fetchhdr | -------------------------------------------------+------------------------- Comment (by phk): Can you please capture the outout of varnishlog when you reproduce this ? Please set parameter "debug=+syncvsl" -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 2 12:12:21 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 02 Jan 2014 12:12:21 -0000 Subject: [Varnish] #1399: Memory get freed while in use by another thread/object In-Reply-To: <059.1e289aaa7c9164a8a63898e6d8c12f43@varnish-cache.org> References: <059.1e289aaa7c9164a8a63898e6d8c12f43@varnish-cache.org> Message-ID: <074.176c5d9e29c4f4375715251dee6d4c88@varnish-cache.org> #1399: Memory get freed while in use by another thread/object -------------------------------------------------+------------------------- Reporter: varnish@? | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish Component: varnishd | 4.0-TP1 Severity: major | Version: trunk Keywords: memory get freed MPL_Free | Resolution: vbf_stp_fetchhdr | -------------------------------------------------+------------------------- Comment (by varnish@?): Dear Mr. Kamp, I've attached thhe requested file. Best, Martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 2 12:28:54 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 02 Jan 2014 12:28:54 -0000 Subject: [Varnish] #1400: -S "" for varnishd is not working In-Reply-To: <044.9282743ec37c5826aad6cab27ca197aa@varnish-cache.org> References: <044.9282743ec37c5826aad6cab27ca197aa@varnish-cache.org> Message-ID: <059.732871780dec6a1d658ead4f097d1064@varnish-cache.org> #1400: -S "" for varnishd is not working ----------------------+---------------------- Reporter: quiver | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: invalid Keywords: | ----------------------+---------------------- Changes (by daghf): * status: new => closed * resolution: => invalid -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 2 16:03:45 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 02 Jan 2014 16:03:45 -0000 Subject: [Varnish] #1399: Memory get freed while in use by another thread/object In-Reply-To: <059.1e289aaa7c9164a8a63898e6d8c12f43@varnish-cache.org> References: <059.1e289aaa7c9164a8a63898e6d8c12f43@varnish-cache.org> Message-ID: <074.b462eea73cc812b0af0c91ce4548e830@varnish-cache.org> #1399: Memory get freed while in use by another thread/object -------------------------------------+------------------------------------- Reporter: varnish@? | Owner: Poul-Henning Kamp Type: defect | Priority: normal | Status: closed Component: varnishd | Milestone: Varnish 4.0-TP1 Severity: major | Version: trunk Keywords: memory get freed | Resolution: fixed MPL_Free vbf_stp_fetchhdr | -------------------------------------+------------------------------------- Changes (by Poul-Henning Kamp ): * status: new => closed * owner: => Poul-Henning Kamp * resolution: => fixed Comment: In [1cb047172faed3c38bc8d0cd0fad8af249a3302a]: {{{ #!CommitTicketReference repository="" revision="1cb047172faed3c38bc8d0cd0fad8af249a3302a" Make sure we have copied all we need from the req.* http structure for the bg-fetch, before we release the request to carry on. Fixes #1399 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 2 21:50:37 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 02 Jan 2014 21:50:37 -0000 Subject: [Varnish] #1403: n_object becomes bogus every night Message-ID: <043.e8ea7fcf7ae28e33640a4bf2e3f04ab9@varnish-cache.org> #1403: n_object becomes bogus every night ----------------------+----------------------------- Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP1 Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------- It looks looks like MAIN.n_object can drop below 0. Every night we see a pattern like this: 2014.Jan.02 01:31:10 18446744073709548169 2014.Jan.02 01:30:40 18446744073709549453 2014.Jan.02 01:30:10 18446744073709551430 2014.Jan.02 01:29:40 2686 2014.Jan.02 01:29:10 4897 2014.Jan.02 01:28:40 6441 This is corrected by us hitting #1397 and restarting, but the pattern repeats every night around the same time. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 3 09:31:51 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 03 Jan 2014 09:31:51 -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.f4663421f1819d6dcab823041ec99976@varnish-cache.org> #1403: n_object becomes bogus every night ----------------------+------------------------------ Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP1 Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+------------------------------ Description changed by phk: Old description: > It looks looks like MAIN.n_object can drop below 0. > Every night we see a pattern like this: > 2014.Jan.02 01:31:10 18446744073709548169 > 2014.Jan.02 01:30:40 18446744073709549453 > 2014.Jan.02 01:30:10 18446744073709551430 > 2014.Jan.02 01:29:40 2686 > 2014.Jan.02 01:29:10 4897 > 2014.Jan.02 01:28:40 6441 > > This is corrected by us hitting #1397 and restarting, but the pattern > repeats every night around the same time. New description: It looks looks like MAIN.n_object can drop below 0. Every night we see a pattern like this: {{{ 2014.Jan.02 01:31:10 18446744073709548169 2014.Jan.02 01:30:40 18446744073709549453 2014.Jan.02 01:30:10 18446744073709551430 2014.Jan.02 01:29:40 2686 2014.Jan.02 01:29:10 4897 2014.Jan.02 01:28:40 6441 }}} This is corrected by us hitting #1397 and restarting, but the pattern repeats every night around the same time. -- -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 3 10:19:57 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 03 Jan 2014 10:19:57 -0000 Subject: [Varnish] #1395: vcl_error is not called if fetch failed on vcl_backend_fetch In-Reply-To: <043.08951e6dbd6d7ac15da515243c6db095@varnish-cache.org> References: <043.08951e6dbd6d7ac15da515243c6db095@varnish-cache.org> Message-ID: <058.83507395198a47ccef7d6bf075d17567@varnish-cache.org> #1395: vcl_error is not called if fetch failed on vcl_backend_fetch ----------------------+---------------------------------------- Reporter: fgsch | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+---------------------------------------- Changes (by Poul-Henning Kamp ): * status: new => closed * owner: => Poul-Henning Kamp * resolution: => fixed Comment: In [f950e875c2f8d89c0903e3cff29fb11d5fc2858a]: {{{ #!CommitTicketReference repository="" revision="f950e875c2f8d89c0903e3cff29fb11d5fc2858a" This problem was already fixed. Fixes #1395 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 3 11:23:56 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 03 Jan 2014 11:23:56 -0000 Subject: [Varnish] #1086: VGZ_WrwGunzip loops forever if receiving junk data after end of gzip data In-Reply-To: <044.dedba8f13c20d02f02a39731a1edea7c@varnish-cache.org> References: <044.dedba8f13c20d02f02a39731a1edea7c@varnish-cache.org> Message-ID: <059.60053c11c5c2400363e51bab3c7f5f1a@varnish-cache.org> #1086: VGZ_WrwGunzip loops forever if receiving junk data after end of gzip data ----------------------+--------------------- Reporter: martin | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.2 Severity: normal | Resolution: Keywords: | ----------------------+--------------------- Comment (by phk): This seems still unfixed in 3.0.5 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 3 11:35:05 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 03 Jan 2014 11:35:05 -0000 Subject: [Varnish] #1340: Multiple backend requests per miss In-Reply-To: <046.428f3fe760f6bc854cf7d82980f4a006@varnish-cache.org> References: <046.428f3fe760f6bc854cf7d82980f4a006@varnish-cache.org> Message-ID: <061.82b3502b1bb9a6b14d6c119b38fd0e68@varnish-cache.org> #1340: Multiple backend requests per miss ----------------------+--------------------- Reporter: lkarsten | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+--------------------- Changes (by lkarsten): * status: new => closed * resolution: => fixed Comment: I'm not able to reproduce this any longer on master. Closing it. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 3 14:08:48 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 03 Jan 2014 14:08:48 -0000 Subject: [Varnish] #1086: VGZ_WrwGunzip loops forever if receiving junk data after end of gzip data In-Reply-To: <044.dedba8f13c20d02f02a39731a1edea7c@varnish-cache.org> References: <044.dedba8f13c20d02f02a39731a1edea7c@varnish-cache.org> Message-ID: <059.0616f0a4e7c9d94bc757249021534cbd@varnish-cache.org> #1086: VGZ_WrwGunzip loops forever if receiving junk data after end of gzip data ----------------------+--------------------- Reporter: martin | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.2 Severity: normal | Resolution: Keywords: | ----------------------+--------------------- Comment (by lkarsten): Went digging in this a bit today. The VGZ_END patch ignores the possibility that there are multiple gzip streams concatenated in an object. I wouldn't be surprised if there are backends that end up doing this, perhaps after getting a flush() or similar. This is speculation, but debugging partial/incomplete responses to non-gzip-clients sometime down the road sounds painful. I guess the main point is to avoid a spinning thread. If we stop after a VGZ_END, we'll get that but may serve incomplete objects. We can also make up some magic number of rounds this loop maximum should take before aborting, but that isn't very pretty. Another way might be to look into the next data chunk after VGZ_END and see if it is a gzip header (continue) or not (close connection). What is the correct behaviour here? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 3 14:20:28 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 03 Jan 2014 14:20:28 -0000 Subject: [Varnish] #1369: Spinning thread while esi+gzip fetch In-Reply-To: <046.a959baf0eee18a6849c8587f6527406f@varnish-cache.org> References: <046.a959baf0eee18a6849c8587f6527406f@varnish-cache.org> Message-ID: <061.ddb9962c5f8270faf665f565f0cdd2cb@varnish-cache.org> #1369: Spinning thread while esi+gzip fetch ----------------------+-------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.4 Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Comment (by lkarsten): I'll see what I can do. This looks sufficiently close to #1086 that I would expect it to be the same issue. The code in vfp_esi_bytes_gg() is very similar to VGZ_WrwGunzip(). -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 6 11:10:40 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 06 Jan 2014 11:10:40 -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.468042db17621712ca8dabbc3ec63b37@varnish-cache.org> #1403: n_object becomes bogus every night ----------------------+------------------------------ Reporter: scoof | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP1 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 Jan 6 11:27:52 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 06 Jan 2014 11:27:52 -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.5fbdf9c1e3a12ce0aed9a1422954a46b@varnish-cache.org> #1393: segfault in varnish tools (but varnish is running fine) -----------------------------+-------------------- Reporter: brandonwamboldt | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishlog | Version: 3.0.2 Severity: major | Resolution: Keywords: | -----------------------------+-------------------- Comment (by lkarsten): Is this the 12.04.3 LTS default Varnish packages? (dpkg -l output please) Are you using the correct libvarnishapi for the shm contents? What kind of request rates is this server seeing? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 6 13:20:09 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 06 Jan 2014 13:20:09 -0000 Subject: [Varnish] #1394: Add conf.d/*.vcl directive to config system In-Reply-To: <050.17c3b265f7939f94c7de9be81236efd9@varnish-cache.org> References: <050.17c3b265f7939f94c7de9be81236efd9@varnish-cache.org> Message-ID: <065.44419ed436d40f6a8995134851ddd6c5@varnish-cache.org> #1394: Add conf.d/*.vcl directive to config system --------------------------+---------------------- Reporter: michaelfavia | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: invalid Keywords: config | --------------------------+---------------------- Changes (by martin): * status: new => closed * resolution: => invalid Comment: Added a point about this on the Future Usability page, which is where we track feature requests: https://www.varnish- cache.org/trac/wiki/Future_Usability Closing ticket with invalid status as we don't track feature requests in tickets. Regards, Martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 6 16:35:08 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 06 Jan 2014 16:35:08 -0000 Subject: [Varnish] #1404: 4.0-tp1 sends Content-Length for HTTP 304 Message-ID: <043.5415171386cce0fd6898a44a394b220c@varnish-cache.org> #1404: 4.0-tp1 sends Content-Length for HTTP 304 ----------------------+----------------------------- Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP1 Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------- This seems to give rise to issues with some browsers, since they expect a body to follow. vtc will follow -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 6 17:27:55 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 06 Jan 2014 17:27:55 -0000 Subject: [Varnish] #1404: 4.0-tp1 sends Content-Length for HTTP 304 In-Reply-To: <043.5415171386cce0fd6898a44a394b220c@varnish-cache.org> References: <043.5415171386cce0fd6898a44a394b220c@varnish-cache.org> Message-ID: <058.9bdbccc1f13fc24fbd5a902aeeda1fec@varnish-cache.org> #1404: 4.0-tp1 sends Content-Length for HTTP 304 ----------------------+---------------------------------------- Reporter: scoof | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Varnish 4.0-TP1 Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+---------------------------------------- Changes (by Poul-Henning Kamp ): * status: new => closed * owner: => Poul-Henning Kamp * resolution: => fixed Comment: In [a5bf869f4fd5de53eb5e8c3084d5931154cc58d3]: {{{ #!CommitTicketReference repository="" revision="a5bf869f4fd5de53eb5e8c3084d5931154cc58d3" Don't send Content-Length on 304 responses. It seems that browser writers also have trouble figuring out that twisted logic in HTTP/1.1. Fixes: #1404 Spotted by: Scoof }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 6 18:52:58 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 06 Jan 2014 18:52:58 -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.aac8a6035e1033be1f26cc7190585021@varnish-cache.org> #1388: Length is 0 for most responses --------------------+------------------------------ Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP1 Component: build | Version: unknown Severity: normal | Resolution: Keywords: | --------------------+------------------------------ Comment (by scoof): This seems to be caused by SES_Charge being run after SLT_Length is logged in cache_req_fsm.c. Suggested fix: {{{ diff --git a/bin/varnishd/cache/cache_req_fsm.c b/bin/varnishd/cache/cache_req_fsm.c index d80c16f..b1d7416 100644 --- a/bin/varnishd/cache/cache_req_fsm.c +++ b/bin/varnishd/cache/cache_req_fsm.c @@ -865,6 +865,9 @@ CNT_Request(struct worker *wrk, struct req *req) CHECK_OBJ_ORNULL(wrk->nobjhead, OBJHEAD_MAGIC); } if (nxt == REQ_FSM_DONE) { + /* done == 2 was charged by cache_hash.c */ + SES_Charge(wrk, req); + /* XXX: Workaround for pipe */ if (req->sp->fd >= 0) { VSLb(req->vsl, SLT_Length, "%ju", @@ -883,9 +886,6 @@ CNT_Request(struct worker *wrk, struct req *req) STV_free(st); } - /* done == 2 was charged by cache_hash.c */ - SES_Charge(wrk, req); - /* * Nuke the VXID, cache_http1_fsm.c::http1_dissect() will * allocate a new one when necessary. }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 6 19:37:18 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 06 Jan 2014 19:37:18 -0000 Subject: [Varnish] #1397: Assert error in vbf_stp_condfetch(), cache/cache_fetch.c line 635: Condition(obj->len == al) not true. In-Reply-To: <043.061aecbbdcc366bcf2ba6b76f21fb1c5@varnish-cache.org> References: <043.061aecbbdcc366bcf2ba6b76f21fb1c5@varnish-cache.org> Message-ID: <058.a1ae10e5415dd712c7e15159fb1794e2@varnish-cache.org> #1397: Assert error in vbf_stp_condfetch(), cache/cache_fetch.c line 635: Condition(obj->len == al) not true. --------------------+---------------------- Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: unknown Severity: normal | Resolution: Keywords: | --------------------+---------------------- Comment (by scoof): I was able to reproduce on my laptop. 100M malloc, 1s TTL, 1d grace on all objects. I then fetch a 10M object, and then fill the cache with 20k objects until <10MB are left. I make sure that nuke_limit is sufficiently high, and fetch the 10M object again. This triggers this assert. syncvsl varnishlog, running 3d50d453ad6cd2b9d4da72d970b3051862757123 {{{ * << Request >> 68562 - Begin req 68561 - ReqMethod GET - ReqURL /10MB - ReqProtocol HTTP/1.1 - ReqHeader User-Agent: curl/7.30.0 - ReqHeader Host: localhost - ReqHeader Accept: */* - ReqStart 127.0.0.1 58823 - VCL_call RECV - VCL_return hash - VCL_call HASH - VCL_return lookup - Hit 2147483651 - VCL_call HIT - VCL_return deliver - Link bereq 68563 - VCL_call DELIVER - VCL_return deliver - Debug "RES_MODE 2%00" - RespProtocol HTTP/1.1 - RespStatus 200 - RespResponse OK - RespHeader Server: Apache/2.4.6 (Debian) - RespHeader Last-Modified: Mon, 24 Oct 2011 13:29:00 GMT - RespHeader ETag: "989680-4b00b67d84216" - RespHeader Date: Mon, 06 Jan 2014 19:32:32 GMT - RespHeader Content-Length: 10000000 - RespHeader Connection: keep-alive - RespHeader Accept-Ranges: bytes - Debug "XXX REF 3%00" - Length 0 - ReqEnd 1389036752.007915258 1389036752.005141497 -0.002975702 0.000201941 -0.002975702 - End * << Session >> 68561 - Begin sess - SessOpen 127.0.0.1 58823 :80 127.0.0.1 80 1389036752.005141 17 - Link req 68562 - SessClose REM_CLOSE 0.009 1 0 0 0 1 1 - End * << BeReq >> 68563 - Begin bereq 68562 - Debug "MKBEREQ -> STARTFETCH%00" - VCL_call BACKEND_FETCH - VCL_return fetch - Debug "STARTFETCH -> FETCHHDR%00" - BereqMethod GET - BereqURL /10MB - BereqProtocol HTTP/1.1 - BereqHeader User-Agent: curl/7.30.0 - BereqHeader Host: localhost - BereqHeader Accept: */* - BereqHeader X-Forwarded-For: 127.0.0.1 - BereqHeader Accept-Encoding: gzip - BereqHeader If-Modified-Since: Mon, 24 Oct 2011 13:29:00 GMT - BereqHeader X-Varnish: 68563 - Debug "XXX BOS: 0 -> 1%00" - BackendClose 21 default(127.0.0.1,,8081) toolate - BackendOpen 21 default(127.0.0.1,,8081) 127.0.0.1 44593 - Backend 21 default default(127.0.0.1,,8081) - BereqMethod GET - BereqURL /10MB - BereqProtocol HTTP/1.1 - BereqHeader User-Agent: curl/7.30.0 - BereqHeader Host: localhost - BereqHeader Accept: */* - BereqHeader X-Forwarded-For: 127.0.0.1 - BereqHeader Accept-Encoding: gzip - BereqHeader If-Modified-Since: Mon, 24 Oct 2011 13:29:00 GMT - BereqHeader X-Varnish: 68563 - BerespProtocol HTTP/1.1 - BerespStatus 304 - BerespResponse Not Modified - BerespHeader Date: Mon, 06 Jan 2014 19:32:32 GMT - BerespHeader Server: Apache/2.4.6 (Debian) - BerespHeader ETag: "989680-4b00b67d84216" - TTL RFC -1 -1 -1 1389036752 1389036752 1389036752 0 0 - VCL_call BACKEND_RESPONSE - TTL VCL 1 10 0 1389036752 0 - TTL VCL 1 86400 0 1389036752 0 - VCL_return deliver - Debug "FETCHHDR -> CONDFETCH%00" - Storage malloc s0 - ObjProtocol HTTP/1.1 - ObjStatus 200 - ObjResponse OK - ObjHeader Date: Mon, 06 Jan 2014 19:31:52 GMT - ObjHeader Server: Apache/2.4.6 (Debian) - ObjHeader Last-Modified: Mon, 24 Oct 2011 13:29:00 GMT - ObjHeader ETag: "989680-4b00b67d84216" - Debug "XXX BOS: 1 -> 2%00" - VSL flush - End synth }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 6 19:47:42 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 06 Jan 2014 19:47:42 -0000 Subject: [Varnish] #1397: Assert error in vbf_stp_condfetch(), cache/cache_fetch.c line 635: Condition(obj->len == al) not true. In-Reply-To: <043.061aecbbdcc366bcf2ba6b76f21fb1c5@varnish-cache.org> References: <043.061aecbbdcc366bcf2ba6b76f21fb1c5@varnish-cache.org> Message-ID: <058.d9c14916a9bbf09eda2754a65de8a51f@varnish-cache.org> #1397: Assert error in vbf_stp_condfetch(), cache/cache_fetch.c line 635: Condition(obj->len == al) not true. --------------------+---------------------- Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: unknown Severity: normal | Resolution: Keywords: | --------------------+---------------------- Comment (by scoof): varnishlog -g raw: {{{ 0 CLI - Rd ping 0 CLI - Wr 200 19 PONG 1389037608 1.0 360449 Begin c sess 360449 SessOpen c 127.0.0.1 39734 :80 127.0.0.1 80 1389037609.543531 16 360450 Begin c req 360449 360449 Link c req 360450 360450 ReqMethod c GET 360450 ReqURL c /10MB 360450 ReqProtocol c HTTP/1.1 360450 ReqHeader c User-Agent: curl/7.30.0 360450 ReqHeader c Host: localhost 360450 ReqHeader c Accept: */* 360450 ReqStart c 127.0.0.1 39734 360450 VCL_call c RECV 360450 VCL_return c hash 360450 VCL_call c HASH 360450 VCL_return c lookup 360450 Hit c 2147483651 360450 VCL_call c HIT 360450 VCL_return c deliver 360451 Begin b bereq 360450 360450 Link c bereq 360451 360451 Debug b "MKBEREQ -> STARTFETCH%00" 360451 VCL_call b BACKEND_FETCH 360451 VCL_return b fetch 360451 Debug b "STARTFETCH -> FETCHHDR%00" 360451 BereqMethod b GET 360451 BereqURL b /10MB 360451 BereqProtocol b HTTP/1.1 360451 BereqHeader b User-Agent: curl/7.30.0 360451 BereqHeader b Host: localhost 360451 BereqHeader b Accept: */* 360451 BereqHeader b X-Forwarded-For: 127.0.0.1 360451 BereqHeader b Accept-Encoding: gzip 360451 BereqHeader b If-Modified-Since: Mon, 24 Oct 2011 13:29:00 GMT 360451 BereqHeader b X-Varnish: 360451 360451 Debug b "XXX BOS: 0 -> 1%00" 360451 BackendOpen b 175 default(127.0.0.1,,8081) 127.0.0.1 53737 360451 Backend b 175 default default(127.0.0.1,,8081) 360451 BereqMethod b GET 360451 BereqURL b /10MB 360451 BereqProtocol b HTTP/1.1 360451 BereqHeader b User-Agent: curl/7.30.0 360451 BereqHeader b Host: localhost 360451 BereqHeader b Accept: */* 360451 BereqHeader b X-Forwarded-For: 127.0.0.1 360451 BereqHeader b Accept-Encoding: gzip 360451 BereqHeader b If-Modified-Since: Mon, 24 Oct 2011 13:29:00 GMT 360451 BereqHeader b X-Varnish: 360451 360450 VCL_call c DELIVER 360450 VCL_return c deliver 360450 Debug c "RES_MODE 2%00" 360450 RespProtocol c HTTP/1.1 360450 RespStatus c 200 360450 RespResponse c OK 360450 RespHeader c Server: Apache/2.4.6 (Debian) 360450 RespHeader c Last-Modified: Mon, 24 Oct 2011 13:29:00 GMT 360450 RespHeader c ETag: "989680-4b00b67d84216" 360450 RespHeader c Date: Mon, 06 Jan 2014 19:46:49 GMT 360450 RespHeader c Content-Length: 10000000 360450 RespHeader c Connection: keep-alive 360450 RespHeader c Accept-Ranges: bytes 360451 BerespProtocol b HTTP/1.1 360451 BerespStatus b 304 360451 BerespResponse b Not Modified 360451 BerespHeader b Date: Mon, 06 Jan 2014 19:46:49 GMT 360451 BerespHeader b Server: Apache/2.4.6 (Debian) 360451 BerespHeader b ETag: "989680-4b00b67d84216" 360451 TTL b RFC -1 -1 -1 1389037610 1389037610 1389037609 0 0 360451 VCL_call b BACKEND_RESPONSE 360451 TTL b VCL 1 10 0 1389037610 0 360451 TTL b VCL 1 86400 0 1389037610 0 360451 VCL_return b deliver 360451 Debug b "FETCHHDR -> CONDFETCH%00" 360451 Storage b malloc s0 360451 ObjProtocol b HTTP/1.1 360451 ObjStatus b 200 360451 ObjResponse b OK 360451 ObjHeader b Date: Mon, 06 Jan 2014 19:46:00 GMT 360451 ObjHeader b Server: Apache/2.4.6 (Debian) 360451 ObjHeader b Last-Modified: Mon, 24 Oct 2011 13:29:00 GMT 360451 ObjHeader b ETag: "989680-4b00b67d84216" 360451 Debug b "XXX BOS: 1 -> 2%00" 0 ExpKill - EXP_Inbox p=0x7fc5f8010400 e=0.000000000 f=0x1c10 0 ExpKill - EXP_When p=0x7fc5f8010400 e=1389124010.544181347 f=0x1c10 360450 Debug c "XXX REF 3%00" 360450 Length c 0 360450 ReqEnd c 1389037609.544181347 1389037609.543531418 -0.000818491 0.000168562 -0.000818491 360450 End c Log abandoned }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 6 20:46:04 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 06 Jan 2014 20:46:04 -0000 Subject: [Varnish] #1397: Assert error in vbf_stp_condfetch(), cache/cache_fetch.c line 635: Condition(obj->len == al) not true. In-Reply-To: <043.061aecbbdcc366bcf2ba6b76f21fb1c5@varnish-cache.org> References: <043.061aecbbdcc366bcf2ba6b76f21fb1c5@varnish-cache.org> Message-ID: <058.2ab677d70edb5074f52460dba6d5a7ae@varnish-cache.org> #1397: Assert error in vbf_stp_condfetch(), cache/cache_fetch.c line 635: Condition(obj->len == al) not true. --------------------+---------------------------------------- Reporter: scoof | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: unknown Severity: normal | Resolution: fixed Keywords: | --------------------+---------------------------------------- Changes (by Poul-Henning Kamp ): * owner: => Poul-Henning Kamp * status: new => closed * resolution: => fixed Comment: In [c0096f759b8af324d1253993fd76960ecbd2e399]: {{{ #!CommitTicketReference repository="" revision="c0096f759b8af324d1253993fd76960ecbd2e399" Lay #1397 to rest: It was something as trivial as a typo from my side, but staring at the wrong assert for hours on end did not reveal that. Many thanks to: scoof Fixes #1397 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 9 09:14:19 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 09 Jan 2014 09:14:19 -0000 Subject: [Varnish] #1405: Assert error in exp_inbox(), cache/cache_expire.c line 444 Message-ID: <043.e8bc6eb559047d8ef76c282eca47dbb2@varnish-cache.org> #1405: Assert error in exp_inbox(), cache/cache_expire.c line 444 --------------------+--------------------- Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: unknown Severity: normal | Keywords: --------------------+--------------------- Panic in 4.0, running c0096f759b8af324d1253993fd76960ecbd2e399 and some small local changes that should affect expiry. {{{ Last panic at: Thu, 09 Jan 2014 08:29:24 GMT Assert error in exp_inbox(), cache/cache_expire.c line 444: Condition(oc->timer_idx != BINHEAP_NOIDX) not true. thread = (cache-timeout) ident = Linux,2.6.32-5-amd64,x86_64,-smalloc,-smalloc,-hcritbit,epoll Backtrace: 0x439614: pan_backtrace+0x19 0x439924: pan_ic+0x1e8 0x421f53: exp_inbox+0x35d 0x422b27: exp_thread+0x232 0x453e1a: wrk_bgthread+0xde 0x7f9ba49548ba: /lib/libpthread.so.0(+0x68ba) [0x7f9ba49548ba] 0x7f9ba46bc02d: /lib/libc.so.6(clone+0x6d) [0x7f9ba46bc02d] }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 9 14:10:59 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 09 Jan 2014 14:10:59 -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.0cf67094fb960b8426a6ca0f7a7b867f@varnish-cache.org> #1405: Assert error in exp_inbox(), cache/cache_expire.c line 444 --------------------+---------------------- Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: unknown Severity: normal | Resolution: Keywords: | --------------------+---------------------- Comment (by scoof): Seemed to coincide with a growing amount of bans -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 10 16:30:14 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 10 Jan 2014 16:30:14 -0000 Subject: [Varnish] #1406: Setting a header to a falsy value than getting it returns true Message-ID: <053.67b679cfde5eb48e50df6e81d4e36d86@varnish-cache.org> #1406: Setting a header to a falsy value than getting it returns true -----------------------------+---------------------- Reporter: brandonwamboldt | Type: defect Status: new | Priority: high Milestone: | Component: varnishd Version: 3.0.4 | Severity: normal Keywords: | -----------------------------+---------------------- Simple test case: {{{ sub vcl_recv { C{ VRT_SetHdr(sp, HDR_REQ, "\020X-CUSTOM-HEADER:", 0, vrt_magic_string_end ); }C if (req.http.X-CUSTOM-HEADER) { std.log("-------------------------> TRUTHY"); } else { std.log("-------------------------> FALSY"); } } }}} This was NOT the behaviour in 3.0.2, but does occur in 3.0.4. I don't believe this change should be made at all, definitely not in a minor version release. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 13 11:14:23 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 13 Jan 2014 11:14:23 -0000 Subject: [Varnish] #1384: std.fileread does not refresh file changed on disk In-Reply-To: <046.0a9bee5969c34a18231e9ea106bcf425@varnish-cache.org> References: <046.0a9bee5969c34a18231e9ea106bcf425@varnish-cache.org> Message-ID: <061.07cba0d568fd2cbdd4f13d41fd33ffea@varnish-cache.org> #1384: std.fileread does not refresh file changed on disk --------------------------+-------------------- Reporter: rzuidhof | Owner: Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 3.0.5 Severity: major | Resolution: Keywords: std.fileread | --------------------------+-------------------- Comment (by lkarsten): This is the documented behavior[1], and is not considered a bug. If you want to improve this, feel free to submit a patch. It is surprisingly hard to get done properly. We don't keep feature requests in the bugtracker, I'm closing this now. 1: https://www.varnish-cache.org/docs/3.0/reference/vmod_std.html#fileread -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 13 11:14:33 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 13 Jan 2014 11:14:33 -0000 Subject: [Varnish] #1384: std.fileread does not refresh file changed on disk In-Reply-To: <046.0a9bee5969c34a18231e9ea106bcf425@varnish-cache.org> References: <046.0a9bee5969c34a18231e9ea106bcf425@varnish-cache.org> Message-ID: <061.494cf855b1e1717996ce93f4ab4e282b@varnish-cache.org> #1384: std.fileread does not refresh file changed on disk --------------------------+---------------------- Reporter: rzuidhof | Owner: Type: defect | Status: closed Priority: high | Milestone: Component: varnishd | Version: 3.0.5 Severity: major | Resolution: wontfix Keywords: std.fileread | --------------------------+---------------------- Changes (by lkarsten): * status: new => closed * resolution: => wontfix -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 13 11:16:30 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 13 Jan 2014 11:16:30 -0000 Subject: [Varnish] #1406: Setting a header to a falsy value than getting it returns true In-Reply-To: <053.67b679cfde5eb48e50df6e81d4e36d86@varnish-cache.org> References: <053.67b679cfde5eb48e50df6e81d4e36d86@varnish-cache.org> Message-ID: <068.506062e6e3ec07fb8a30815c68c220d0@varnish-cache.org> #1406: Setting a header to a falsy value than getting it returns true -----------------------------+-------------------- Reporter: brandonwamboldt | Owner: Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 3.0.4 Severity: normal | Resolution: Keywords: | -----------------------------+-------------------- Comment (by scoof): introduced by 26b450904c39eb2b056e42846bd11be2993866e9 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 13 22:04:14 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 13 Jan 2014 22:04:14 -0000 Subject: [Varnish] #1406: Setting a header to a falsy value than getting it returns true In-Reply-To: <053.67b679cfde5eb48e50df6e81d4e36d86@varnish-cache.org> References: <053.67b679cfde5eb48e50df6e81d4e36d86@varnish-cache.org> Message-ID: <068.bfa04040e2a748e77889271b9505e39b@varnish-cache.org> #1406: Setting a header to a falsy value than getting it returns true -----------------------------+-------------------- Reporter: brandonwamboldt | Owner: Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 3.0.4 Severity: normal | Resolution: Keywords: | -----------------------------+-------------------- Comment (by phk): -trunk seems not to be affected by this, but I added a test-case, just in case. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 14 10:10:21 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 14 Jan 2014 10:10:21 -0000 Subject: [Varnish] #1380: esi:request_headers support In-Reply-To: <050.7ad8956688b36fbc07042bef02c0ea41@varnish-cache.org> References: <050.7ad8956688b36fbc07042bef02c0ea41@varnish-cache.org> Message-ID: <065.cea57dea49f45024e621fc17761d0084@varnish-cache.org> #1380: esi:request_headers support ---------------------------+------------------------------ Reporter: lorenzololli | Owner: Type: documentation | Status: closed Priority: lowest | Milestone: Varnish 3.0 dev Component: documentation | Version: 3.0.4 Severity: normal | Resolution: invalid Keywords: ESI | ---------------------------+------------------------------ Changes (by phk): * status: new => closed * resolution: => invalid Comment: Apologies for the late response. No, varnish does not support esi:request_headers at this time, and it is not obvious that there is a big requirement for it, given that the esi:include transactions run through the VCL as separate requests, where you can modify the headers to your preference. If you have a usecase where that is not enough, by all means explain it to us, but please add it to one of the wiki's future_* pages, as that is where we keep change requests. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 14 15:55:23 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 14 Jan 2014 15:55:23 -0000 Subject: [Varnish] #1407: Varnishd loses the ability to write to shared memory if you try to start it twice Message-ID: <053.90c213397c3b87bfe5b4975288bb67b4@varnish-cache.org> #1407: Varnishd loses the ability to write to shared memory if you try to start it twice -----------------------------+---------------------- Reporter: brandonwamboldt | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: 3.0.3 | Severity: normal Keywords: | -----------------------------+---------------------- If you start Varnish, and then try to start it again using the varnishd command directly, it will take over the shared memory file from the running varnishd process, then exit as it fails to bind ports. This leaves the original process unable to write to shared memory. It does throw a warning, "WARNING: Taking over SHMFILE marked as owned by running process (pid=29585)", but I feel like this could be handled better. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 15 22:11:39 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 15 Jan 2014 22:11:39 -0000 Subject: [Varnish] #1319: Daemon Package should depend on exact library version In-Reply-To: <041.3d5142236d5cf8faf1c871b7383e5964@varnish-cache.org> References: <041.3d5142236d5cf8faf1c871b7383e5964@varnish-cache.org> Message-ID: <056.b0f3e5043f4d7516971ec69dbfb03859@varnish-cache.org> #1319: Daemon Package should depend on exact library version -----------------------+-------------------- Reporter: tex | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: packaging | Version: 3.0.4 Severity: normal | Resolution: Keywords: | -----------------------+-------------------- Comment (by lkarsten): I was under the impression that this was fixed, but recent feedback (and me finding this bug report still open) it seems like we need to have another go at it. Bump. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 15 22:12:00 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 15 Jan 2014 22:12:00 -0000 Subject: [Varnish] #1319: Daemon Package should depend on exact library version In-Reply-To: <041.3d5142236d5cf8faf1c871b7383e5964@varnish-cache.org> References: <041.3d5142236d5cf8faf1c871b7383e5964@varnish-cache.org> Message-ID: <056.bb853a36cb0bec866dfaeb7339358f3d@varnish-cache.org> #1319: Daemon Package should depend on exact library version -----------------------+----------------------- Reporter: tex | Owner: lkarsten Type: defect | Status: new Priority: normal | Milestone: Component: packaging | Version: 3.0.4 Severity: normal | Resolution: Keywords: | -----------------------+----------------------- Changes (by lkarsten): * owner: => lkarsten -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 15 22:51:14 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 15 Jan 2014 22:51:14 -0000 Subject: [Varnish] #1319: Daemon Package should depend on exact library version In-Reply-To: <041.3d5142236d5cf8faf1c871b7383e5964@varnish-cache.org> References: <041.3d5142236d5cf8faf1c871b7383e5964@varnish-cache.org> Message-ID: <056.7f1cfc131566e963c7532a9b3385c46c@varnish-cache.org> #1319: Daemon Package should depend on exact library version -----------------------+----------------------- Reporter: tex | Owner: lkarsten Type: defect | Status: new Priority: normal | Milestone: Component: packaging | Version: 3.0.4 Severity: normal | Resolution: Keywords: | -----------------------+----------------------- Comment (by mattrobenolt): For information, this is what is coming from your apt repo currently with the following in my sources.list {{{ deb http://repo.varnish-cache.org/ubuntu precise varnish-3.0 deb http://repo.varnish-cache.org/ubuntu precise varnish-4.0 }}} {{{ $ apt-cache show varnish Package: varnish Source: varnish (4.0.0~~tp1-1) Version: 4.0.0~~tp1-1~precise Installed-Size: 1297 Maintainer: Varnish Package Maintainers Architecture: amd64 Replaces: libvarnishapi1 (<< 3.0.0-5) Depends: libc6 (>= 2.14), libedit2 (>= 2.11-20080614-1), libncurses5 (>= 5.5-5~), libpcre3 (>= 8.10), libtinfo5, libvarnishapi1, gcc (>= 3.3), libc6-dev | libc6.1-dev | libc-dev, adduser Suggests: varnish-doc Description-en: state of the art, high-performance web accelerator Varnish Cache is a state of the art web accelerator written with performance and flexibility in mind. . Varnish Cache stores web pages in memory so web servers don't have to create the same web page over and over again. Varnish serves pages much faster than any application server; giving the website a significant speed up. . Some of the features include: * A modern design * VCL - a very flexible configuration language * Load balancing with health checking of backends * Partial support for ESI - Edge Side Includes * URL rewriting * Graceful handling of "dead" backends Homepage: http://varnish-cache.org/ Section: varnish-4.0/web Priority: optional Filename: pool/varnish-4.0/v/varnish/varnish_4.0.0~~tp1-1~precise_amd64.deb Size: 555014 MD5sum: f7a2a8ffce111496985de7e52ebafb06 SHA1: 49554ad40c7e9c8e26a6a9154d3487f5bc808f9a SHA256: e4b0b43d3c0c5fab930e5fe306c12e242e055f7f6253c873baef52815416d00f Package: varnish Source: varnish (3.0.5-1) Version: 3.0.5-1~precise Installed-Size: 1282 Maintainer: Varnish Package Maintainers Architecture: amd64 Replaces: libvarnishapi1 (<< 3.0.0-5) Provides: varnishabi-3.0.5-1a89b1f Depends: libc6 (>= 2.14), libedit2 (>= 2.11-20080614-1), libncurses5 (>= 5.5-5~), libpcre3 (>= 8.10), libtinfo5, libvarnishapi1, gcc (>= 3.3), libc6-dev | libc6.1-dev | libc-dev, adduser Suggests: varnish-doc Description-en: state of the art, high-performance web accelerator Varnish Cache is a state of the art web accelerator written with performance and flexibility in mind. . Varnish Cache stores web pages in memory so web servers don't have to create the same web page over and over again. Varnish serves pages much faster than any application server; giving the website a significant speed up. . Some of the features include: * A modern design * VCL - a very flexible configuration language * Load balancing with health checking of backends * Partial support for ESI - Edge Side Includes * URL rewriting * Graceful handling of "dead" backends Homepage: http://varnish-cache.org/ Section: web Priority: optional Filename: pool/varnish-3.0/v/varnish/varnish_3.0.5-1~precise_amd64.deb Size: 538894 MD5sum: 1511c0d785f55f5cb4dc6414d9ee2021 SHA1: 0a6850c246e0859f1a08c6d2291f1eb8341c73f5 SHA256: 876265ca9260156e1e27e0af6f6f2373ce855a0e7ad262f0ae64bf67ae7dfa3f Package: varnish Source: varnish (3.0.4-1) Version: 3.0.4-1~precise Installed-Size: 1282 Maintainer: Varnish Package Maintainers Architecture: amd64 Replaces: libvarnishapi1 (<< 3.0.0-5) Depends: libc6 (>= 2.14), libedit2 (>= 2.11-20080614-1), libncurses5 (>= 5.5-5~), libpcre3 (>= 8.10), libtinfo5, libvarnishapi1, gcc (>= 3.3), libc6-dev | libc6.1-dev | libc-dev, adduser Suggests: varnish-doc Description-en: state of the art, high-performance web accelerator Varnish Cache is a state of the art web accelerator written with performance and flexibility in mind. . Varnish Cache stores web pages in memory so web servers don't have to create the same web page over and over again. Varnish serves pages much faster than any application server; giving the website a significant speed up. . Some of the features include: * A modern design * VCL - a very flexible configuration language * Load balancing with health checking of backends * Partial support for ESI - Edge Side Includes * URL rewriting * Graceful handling of "dead" backends Homepage: http://varnish-cache.org/ Section: web Priority: optional Filename: pool/varnish-3.0/v/varnish/varnish_3.0.4-1~precise_amd64.deb Size: 537934 MD5sum: ca30c3555559a132a9bd388ccc478a52 SHA1: 6c81cc096190f9e4a2058fd93b2a51c57f1d5ac8 SHA256: b8905d166917e029baf56852f269543266e005ded0e017cd36e7c74216f1cd46 Package: varnish Priority: optional Section: web Installed-Size: 1276 Maintainer: Varnish Package Maintainers Architecture: amd64 Version: 3.0.3-1~precise Replaces: libvarnishapi1 (<< 3.0.0-5) Depends: libc6 (>= 2.14), libedit2 (>= 2.11-20080614-1), libncurses5 (>= 5.5-5~), libpcre3 (>= 8.10), libtinfo5, libvarnishapi1, gcc (>= 3.3), libc6-dev | libc6.1-dev | libc-dev, adduser Suggests: varnish-doc Filename: precise/disqus/varnish_3.0.3-1~precise_amd64.deb Size: 534824 MD5sum: 84a774dbe22602c382cd43088b78255a SHA1: a1e80f23414b47d08ec63ad9ab15037fde6e2915 SHA256: 8c5cef7fda2a64994619696cdb145c84abc8d9080df90de68e549f613d71430d SHA512: 9cfccc221f73cb3d234ad5282a0b77738d493168936787e53caf74244f81c8ddcafaaa2598ca145c612723931b088d60ea5a5bab11d0ead855c0649cda906e11 Description-en: state of the art, high-performance web accelerator Varnish Cache is a state of the art web accelerator written with performance and flexibility in mind. . Varnish Cache stores web pages in memory so web servers don't have to create the same web page over and over again. Varnish serves pages much faster than any application server; giving the website a significant speed up. . Some of the features include: * A modern design * VCL - a very flexible configuration language * Load balancing with health checking of backends * Partial support for ESI - Edge Side Includes * URL rewriting * Graceful handling of "dead" backends Homepage: http://varnish-cache.org/ Package: varnish Priority: extra Section: default Installed-Size: 5773 Maintainer: Architecture: amd64 Version: 3.0.2-0disqus0-1 Depends: libedit2, libncurses5, libpcre3, libtinfo5, adduser Filename: precise/disqus/varnish_3.0.2-0disqus0-1_amd64.deb Size: 2058396 MD5sum: 7cebe12133f84d1ce354953255419fdc SHA1: 9871a62b4cb498b1af223002a2b4dc642826334e SHA256: cb29fce0070e6b4b21675809a23a2b3f4e403a0626c431b8e5c6c3f6f4b76050 SHA512: 9eccb8bb11c271096bb14df5583ce2662ccfa9924ba7a6883a4538df73ed636e920a37b9c6a4f002d6f763a351dc5eac9998210dc70df23a147a5bc9920a34d9 Description: state of the art, high-performance web accelerator License: unknown Vendor: vagrant at precise.vagrant.disqus.net Homepage: https://www.varnish-cache.org/ Package: varnish Priority: optional Section: universe/web Installed-Size: 1258 Maintainer: Ubuntu Developers Original-Maintainer: Varnish Package Maintainers Architecture: amd64 Version: 3.0.2-1ubuntu0.1 Replaces: libvarnishapi1 (<< 3.0.0-5) Depends: libc6 (>= 2.14), libedit2 (>= 2.11-20080614-1), libncurses5 (>= 5.5-5~), libpcre3 (>= 8.10), libtinfo5, libvarnishapi1 (>= 3.0.0), gcc (>= 3.3), libc6-dev | libc6.1-dev | libc-dev, adduser Suggests: varnish-doc Filename: pool/universe/v/varnish/varnish_3.0.2-1ubuntu0.1_amd64.deb Size: 521100 MD5sum: 42a8b11a1e47052510f6786359dec5de SHA1: 89de05e5b2dec580abcbd02024b72535d0bddc25 SHA256: 9129b91b72b88e7ba8cd0bd7e0b778fccecffcb437bb9abf843ce0bf3282e6fc Description-en: state of the art, high-performance web accelerator Varnish Cache is a state of the art web accelerator written with performance and flexibility in mind. . Varnish Cache stores web pages in memory so web servers don't have to create the same web page over and over again. Varnish serves pages much faster than any application server; giving the website a significant speed up. . Some of the features include: * A modern design * VCL - a very flexible configuration language * Load balancing with health checking of backends * Partial support for ESI - Edge Side Includes * URL rewriting * Graceful handling of "dead" backends Homepage: http://varnish-cache.org/ Description-md5: ebbadfc1a0485abd58ba563250510a25 Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Package: varnish Priority: optional Section: universe/web Installed-Size: 1257 Maintainer: Ubuntu Developers Original-Maintainer: Varnish Package Maintainers Architecture: amd64 Version: 3.0.2-1 Replaces: libvarnishapi1 (<< 3.0.0-5) Depends: libc6 (>= 2.4), libedit2 (>= 2.11-20080614-1), libncurses5 (>= 5.5-5~), libpcre3 (>= 8.10), libtinfo5, libvarnishapi1 (>= 3.0.0), gcc (>= 3.3), libc6-dev | libc6.1-dev | libc-dev, adduser Suggests: varnish-doc Filename: pool/universe/v/varnish/varnish_3.0.2-1_amd64.deb Size: 519252 MD5sum: 6cb6e9fb2683b32aa836121a96ed60e9 SHA1: 5176c601f133b71269cd5a66bf92a9e5b4afdbb3 SHA256: 41c27dbc6c6e6bd0637e9d70461873450ec8b07dfb94f842999ab884dbdbbf36 Description-en: state of the art, high-performance web accelerator Varnish Cache is a state of the art web accelerator written with performance and flexibility in mind. . Varnish Cache stores web pages in memory so web servers don't have to create the same web page over and over again. Varnish serves pages much faster than any application server; giving the website a significant speed up. . Some of the features include: * A modern design * VCL - a very flexible configuration language * Load balancing with health checking of backends * Partial support for ESI - Edge Side Includes * URL rewriting * Graceful handling of "dead" backends Homepage: http://varnish-cache.org/ Description-md5: ebbadfc1a0485abd58ba563250510a25 Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 16 16:36:57 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 16 Jan 2014 16:36:57 -0000 Subject: [Varnish] #1408: idle_send_timeout not valid in an included vcl file Message-ID: <049.77d63141d9bdb0a1635d67399b99efa7@varnish-cache.org> #1408: idle_send_timeout not valid in an included vcl file -------------------------------+---------------------- Reporter: raymondjiii | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: 3.0.5 | Severity: normal Keywords: idle_send_timeout | -------------------------------+---------------------- I generate a backend director round-robin vcl file that I include in my main vcl file. For the backends I am trying to set idle_send_timeout but it apparently is not valid despite it being in the varnishd manpage. EXAMPLE director round-robin file I use: backend gamesfeinternal00000 { .host = "10.74.65.38"; .port = "80"; .between_bytes_timeout = 90s; .connect_timeout = 10s; .first_byte_timeout = 90s; .idle_send_timeout = 90s; .probe = { .url = "/server-status?auto"; .interval = 60s; .timeout = 60s; .window = 5; .threshold = 3; } } director localhosts round-robin { { .backend = gamesfeinternal00000; } } $ varnishd -C -f default.vcl Message from VCC-compiler: Unknown field: 'idle_send_timeout' at ('/etc/varnish/nyt-varnish-loadbalancer.vcl' Line 7 Pos 4) .idle_send_timeout = 90s; ---#################------- backend gamesfeinternal00000 { In backend specification starting at: ('/etc/varnish/nyt-varnish-loadbalancer.vcl' Line 1 Pos 1) backend gamesfeinternal00000 { #######----------------------- Running VCC-compiler failed, exit 1 VCL compilation failed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 17 10:58:29 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 17 Jan 2014 10:58:29 -0000 Subject: [Varnish] #1401: Assert error in vbf_stp_startfetch(), cache/cache_fetch.c line 118 In-Reply-To: <046.47b9f956d56dbfe80790b785393898a5@varnish-cache.org> References: <046.47b9f956d56dbfe80790b785393898a5@varnish-cache.org> Message-ID: <061.fc257671a56dd46daca063ee267283ec@varnish-cache.org> #1401: Assert error in vbf_stp_startfetch(), cache/cache_fetch.c line 118 ----------------------+---------------------------------------- Reporter: dmalinow | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Varnish 4.0-TP1 Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+---------------------------------------- Changes (by Poul-Henning Kamp ): * status: new => closed * owner: => Poul-Henning Kamp * resolution: => fixed Comment: In [fe85c10c5d2c85a3f8efcfc41d4f57c539cae2d9]: {{{ #!CommitTicketReference repository="" revision="fe85c10c5d2c85a3f8efcfc41d4f57c539cae2d9" Handle the case where too many retries are attempted, by returning a 503 reply. Fixes #1401 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sat Jan 18 14:18:37 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sat, 18 Jan 2014 14:18:37 -0000 Subject: [Varnish] #1409: Gain Strong Muscles Message-ID: <048.a05cc54e786770862a62424ad184e044@varnish-cache.org> #1409: Gain Strong Muscles ---------------------------+-------------------- Reporter: OlgaFSmith | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: unknown | Severity: normal Keywords: xtreme antler | ---------------------------+-------------------- I just finished that yesterday and 16 tells got snow 0 for yes as I just want to get away personal you know what if way here now trouble years think probably the same her head out now. Mohit rights waiting years for each acre well as you know just happened 3 heat right way here we don?t have enough surplus calorie anyway is that life so sometimes I fall into that category where all have surpluses calories for a couple weeks and you know up being a surplus mandate go back down backup collective arose still anyway that is why so Universal Nutrition real Kings okay this is the cookies cream flavour it was really good I got to tell you it's gonna be alright. it?s okay so it was a win-win for me I'll way is okay we are you know it's away here the prices 5774 a body feeling of comfort and held back get about 31 servings and cost me about ten dollars shipping so that sixty-seven dollars but if we divide 31 servings with which to base prices before shipping we come out with dollar eighty-six per serving 614 calories about how many calories is hoops her they were serving back not too bad right a breakdown of the marriage and scours 614 10 grams sugar I like that too much sugar as compared to some other way. for more info please visit the page below. [http://www.xtremeantleraustralia.com/] -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sat Jan 18 14:21:12 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sat, 18 Jan 2014 14:21:12 -0000 Subject: [Varnish] #1410: Weight Loss With Supplement Message-ID: <046.85de076f722ef2bb75b42c7864d6f346@varnish-cache.org> #1410: Weight Loss With Supplement ----------------------+-------------------- Reporter: ruthmire | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: unknown | Severity: normal Keywords: | ----------------------+-------------------- So I don't I D E any pasta no race no potatoes nothing Alma no bread none of that mama and I did that because have poly cystic ovarian syndrome that is disease where you have issues with your insulin resistance in your endocrine system is just so much fun con but yeah. I just makes you fatter and harder to its way and it makes all those crabs just store in the faces really awesome it's great for people who want to lose weight fun disease that I like to have con so I have that and it's great and coming up cards has really helped do I think that low crab diets are good for you know. I don't think they're good for the long term doing they can be beneficial for short-term weight loss yeah they have been super beneficial to me I feel really good too like super good for dinners I was have like I would boil up about her for like awake or a bell pepper http://www.zencleansedetoxify.com/ -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sat Jan 18 15:03:43 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sat, 18 Jan 2014 15:03:43 -0000 Subject: [Varnish] #1411: Weight Loss Formula Message-ID: <046.5533d6e4d868b0858b40f1d2ae4b10b2@varnish-cache.org> #1411: Weight Loss Formula ----------------------+-------------------- Reporter: ruthmire | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: unknown | Severity: normal Keywords: | ----------------------+-------------------- Take you're supposed to take that twenty to thirty minutes before and here your meals and like I said I just find take all of them in the morning in the same time just get it done with and I would like to point out though that this is not this is not what has made me lose way it just helps me continua their weight loss and b just because there were a couple weeks and I didn't even have a and I still lives just as much weight. I don't know how effective it's bending bring coffee is really in right now for a way burning fat so maybe I'm just burning fat from it unmanned renal swish my dentist put mean which also helps with cortical levels but just because and then you know exercising like crazy. It's just been helping more fatigue symptoms unpacked sweating even are that's what I?d taken on morning with my wife have so you're on my room just because I'm making this little blonde laminate via on logging throughout the day to show you exactly what I'm doing Myron seeming Microgram looking like right now diet and exercise lies this is three months in a few days since this happened http://www.zencleansedetoxify.com/ -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sat Jan 18 15:03:58 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sat, 18 Jan 2014 15:03:58 -0000 Subject: [Varnish] #1412: Here Are Ten Best Tips For Weight Loss Message-ID: <050.3fcd2c7438db6c1c7be0196d3c7daad4@varnish-cache.org> #1412: Here Are Ten Best Tips For Weight Loss -------------------------------+-------------------- Reporter: Jasenbarbera | Type: task Status: new | Priority: normal Milestone: After Varnish 2.1 | Component: build Version: 1.1.1 | Severity: normal Keywords: Supra Cleanse 350 | -------------------------------+-------------------- Husky watermelon Gnash edges help me so much that meant that justice system it just is just a Danish help me soul marts and its quest is delicious with it I 87 week crackers some turkey pepperoni S&T its next we have some popcorn into pieces so a Kiwi I love popcorn you can inspect power plant to be very high in parts so you really have to watch it because his easy to see eat to me leave turkey burger as love turkey burgers and guides an before a story he held the I will never die like a turkey burger & Noble now will test okay services the turkey burger him some watermelon mass AV excellent next to waterman is grapes and nuzzles grapes and so here weave some grapes and we have some wheat crackers wasn't turkey pepperoni in cheats are known by pepperoni with cheese and crackers and then is so good Nana nasty Lance item that I want to show you guys Israel with once love will tell year and what to do is just a mi you can use ground beef or turkey meat and you will pay roads here eat comes in keen east chase and think to Mayo's game green peppers I'm not 100 percent surgeon Baghdad?s so that poor you want to bet. If you are more to be labeled roll tale so you know exactly what it issue and you can play Amy can achieve want to play in it like and cream cheese or Velveeta MBA you were I'm decal which it sits at isn't there it can also do and this is now weakness and though this test and made peace with turkey meat and it?s or whole grain for the most part they use next guidance how with eats at dinner so this is so how many with some barber chichi keen in some grapes nets we have some sleep trust in I made peace with some wheat wing when the I'm not mistaking and we have some we tolls then I just put like a little brother morning and sprinkled some Curly parent wants in making some homemade quiet brain are sold either be your why and how r may be sharper stance if you would like to see her maybe out that the link below you can click on any you can check out that tutorial I'm not 100 percent sure about this meal because I didn't act could get but I think this is Brett beams with sausages in some I mean and the corn bread it was May with Eve. http://www.supracleanse350facts.org/ -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 20 11:15:16 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 20 Jan 2014 11:15:16 -0000 Subject: [Varnish] #1408: idle_send_timeout not valid in an included vcl file In-Reply-To: <049.77d63141d9bdb0a1635d67399b99efa7@varnish-cache.org> References: <049.77d63141d9bdb0a1635d67399b99efa7@varnish-cache.org> Message-ID: <064.fdf6cf011b8bb242ac91177fac1b37ff@varnish-cache.org> #1408: idle_send_timeout not valid in an included vcl file -------------------------------+-------------------- Reporter: raymondjiii | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.5 Severity: normal | Resolution: Keywords: idle_send_timeout | -------------------------------+-------------------- Comment (by tfheen): idle_send_timeout is a varnishd parameter, not a backend parameter. Where did you see docs that lead you to believe idle_send_timeout is valid as a backend parameter? I'd like to get that fixed. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 20 11:22:24 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 20 Jan 2014 11:22:24 -0000 Subject: [Varnish] #1407: Varnishd loses the ability to write to shared memory if you try to start it twice In-Reply-To: <053.90c213397c3b87bfe5b4975288bb67b4@varnish-cache.org> References: <053.90c213397c3b87bfe5b4975288bb67b4@varnish-cache.org> Message-ID: <068.04d5e2cc7f0bb914dc5f9c1c14858a71@varnish-cache.org> #1407: Varnishd loses the ability to write to shared memory if you try to start it twice -----------------------------+----------------------- Reporter: brandonwamboldt | Owner: lkarsten Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Resolution: Keywords: | -----------------------------+----------------------- Changes (by lkarsten): * owner: => lkarsten -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 20 11:22:33 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 20 Jan 2014 11:22:33 -0000 Subject: [Varnish] #1319: Daemon Package should depend on exact library version In-Reply-To: <041.3d5142236d5cf8faf1c871b7383e5964@varnish-cache.org> References: <041.3d5142236d5cf8faf1c871b7383e5964@varnish-cache.org> Message-ID: <056.c25496c585ed419cb43fbc50155c99b1@varnish-cache.org> #1319: Daemon Package should depend on exact library version -----------------------+----------------------- Reporter: tex | Owner: lkarsten Type: defect | Status: closed Priority: normal | Milestone: Component: packaging | Version: 3.0.4 Severity: normal | Resolution: fixed Keywords: | -----------------------+----------------------- Changes (by tfheen): * status: new => closed * resolution: => fixed Comment: I've added a variant on this which will go into the next version. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 20 11:23:54 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 20 Jan 2014 11:23:54 -0000 Subject: [Varnish] #1407: Varnishd loses the ability to write to shared memory if you try to start it twice In-Reply-To: <053.90c213397c3b87bfe5b4975288bb67b4@varnish-cache.org> References: <053.90c213397c3b87bfe5b4975288bb67b4@varnish-cache.org> Message-ID: <068.d9c89c645de6ecebf61f1cdc7db0e353@varnish-cache.org> #1407: Varnishd loses the ability to write to shared memory if you try to start it twice -----------------------------+----------------------- Reporter: brandonwamboldt | Owner: lkarsten Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Resolution: Keywords: | -----------------------------+----------------------- Comment (by lkarsten): Note to self: Verify for 3.0.5/master. Possible new check: stat the shm file and if it is older than cli_timeout then take it, otherwise don't. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 20 11:42:54 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 20 Jan 2014 11:42:54 -0000 Subject: [Varnish] #1413: Wrong default.vcl in 4.0tp1 packages Message-ID: <043.1d61dbc2a264f2f647367c80072f7a6f@varnish-cache.org> #1413: Wrong default.vcl in 4.0tp1 packages -----------------------+----------------------------- Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP1 Component: packaging | Version: trunk Severity: normal | Keywords: -----------------------+----------------------------- Seems like there's a 3.0 default.vcl left in the source tree, and that's the one that ends up in the .deb -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 20 12:05:00 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 20 Jan 2014 12:05:00 -0000 Subject: [Varnish] #1413: Wrong default.vcl in 4.0tp1 packages In-Reply-To: <043.1d61dbc2a264f2f647367c80072f7a6f@varnish-cache.org> References: <043.1d61dbc2a264f2f647367c80072f7a6f@varnish-cache.org> Message-ID: <058.af80fb9b73c81a32b4cbc4d1ed54dab8@varnish-cache.org> #1413: Wrong default.vcl in 4.0tp1 packages -----------------------+------------------------------ Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP1 Component: packaging | Version: trunk Severity: normal | Resolution: Keywords: | -----------------------+------------------------------ Comment (by christianjul): Installing 4.0-TP1 on Ubuntu Raring with Precise packages from http://repo .varnish-cache.org/ubuntu/dists/precise/, there seems be a non-4.0 compatible default vcl shipped, making varnish fail at installation. See attachment. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 22 14:13:54 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 22 Jan 2014 14:13:54 -0000 Subject: [Varnish] #1413: Wrong default.vcl in 4.0tp1 packages In-Reply-To: <043.1d61dbc2a264f2f647367c80072f7a6f@varnish-cache.org> References: <043.1d61dbc2a264f2f647367c80072f7a6f@varnish-cache.org> Message-ID: <058.a0a2bf315102aa179b9e2dfd227e0152@varnish-cache.org> #1413: Wrong default.vcl in 4.0tp1 packages -----------------------+-------------------------------------------- Reporter: scoof | Owner: Lasse Karstensen Type: defect | Status: closed Priority: normal | Milestone: Varnish 4.0-TP1 Component: packaging | Version: trunk Severity: normal | Resolution: fixed Keywords: | -----------------------+-------------------------------------------- Changes (by Lasse Karstensen ): * owner: => Lasse Karstensen * status: new => closed * resolution: => fixed Comment: In [d617d9f8d8244843cd9f48e9bd1da04c0b796119]: {{{ #!CommitTicketReference repository="" revision="d617d9f8d8244843cd9f48e9bd1da04c0b796119" Add VCL 4.0 marker in default.vcl. Fixes: #1413 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 22 14:18:28 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 22 Jan 2014 14:18:28 -0000 Subject: [Varnish] #1372: Consistent crashes with seg fault error 4 in libc-2.12.so In-Reply-To: <045.a0d66f4881fdf144e127f5a22a64caca@varnish-cache.org> References: <045.a0d66f4881fdf144e127f5a22a64caca@varnish-cache.org> Message-ID: <060.79deff73f0505f0ac4d82dd870a55583@varnish-cache.org> #1372: Consistent crashes with seg fault error 4 in libc-2.12.so ----------------------+------------------------------ Reporter: tomypro | Owner: Type: defect | Status: new Priority: highest | Milestone: Varnish 3.0 dev Component: varnishd | Version: 3.0.4 Severity: blocker | Resolution: Keywords: | ----------------------+------------------------------ Comment (by tomypro): This issue still remains but I am having issues running a 'bt full' on what I hope is the core dump. When varnish crashes I am able to locate .so files in /usr/local/var/varnish/ e.g. vcl.thT77xZc.so Are these the core dump files I should be working with? Trying to run gdb /usr/local/sbin/varnishd /usr/local/var/varnish/instant0962.localdomain/vcl.4A7lChR_.so give me the error "/usr/local/var/varnish/instant0962.localdomain/vcl.4A7lChR_.so" is not a core dump: File format not recognized Any help is appreciated. /T -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 23 12:50:03 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 23 Jan 2014 12:50:03 -0000 Subject: [Varnish] #1414: r01391.vtc is unstable Message-ID: <046.d5a045f162e52112b625f28f45c5fb5b@varnish-cache.org> #1414: r01391.vtc is unstable -------------------------+------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishtest | Version: trunk Severity: normal | Keywords: -------------------------+------------------- This test case fails intermittently on RHEL5 servers. Seems to pass on all other platforms we build it on. I'm moving the test case into tests.disabled/ for now so we have a working tree for 4.0.0-tp2 release. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 24 17:43:18 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 24 Jan 2014 17:43:18 -0000 Subject: [Varnish] #1415: [PATCH]: Debian init script - Verify the VCL before restart Message-ID: <043.e3ff6a6de3d3f34370e3a3c2911903a8@varnish-cache.org> #1415: [PATCH]: Debian init script - Verify the VCL before restart ---------------------+------------------------- Reporter: idl0r | Type: enhancement Status: new | Priority: normal Milestone: | Component: packaging Version: unknown | Severity: normal Keywords: | ---------------------+------------------------- Taken from http://www.mail-archive.com/varnish-dev at varnish- cache.org/msg01264.html "I enhanced the Debian init script a bit. It now verifies the config prior restarting (or actually stopping) the current running varnish process. I couldn't find the Debian stuff in the Varnish Git repository so if there is a other location for it please let me know. The patch is against the current Varnish version (3.0.4) of repo.varnish-cache.org." -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 24 23:27:10 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 24 Jan 2014 23:27:10 -0000 Subject: [Varnish] #1416: Panic on abandon in vcl_backend_response Message-ID: <043.ba17f45f1ad62a35fd07f5fcdcade067@varnish-cache.org> #1416: Panic on abandon in vcl_backend_response -------------------+---------------------- Reporter: fgsch | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: trunk | Severity: normal Keywords: | -------------------+---------------------- See attached test. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 24 23:36:43 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 24 Jan 2014 23:36:43 -0000 Subject: [Varnish] #1417: Panic on abandon in vcl_backend_response Message-ID: <043.208fe12b447118500afdc89eb66f6dad@varnish-cache.org> #1417: Panic on abandon in vcl_backend_response -------------------+---------------------- Reporter: fgsch | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: trunk | Severity: normal Keywords: | -------------------+---------------------- *** v1 0.8 debug| Child (29331) died signal=6 (core dumped)\n *** v1 0.8 debug| Child (29331) Panic message: Assert error in vbf_stp_fetchhdr(), cache/cache_fetch.c line 277:\n *** v1 0.8 debug| Condition(wrk->handling == VCL_RET_DELIVER) not true.\n See attached test. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 24 23:51:59 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 24 Jan 2014 23:51:59 -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.c8a3bcc3147ac175f9fec2a8342b3e48@varnish-cache.org> #1417: Panic on abandon in vcl_backend_response ----------------------+------------------------------ Reporter: fgsch | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP2 Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+------------------------------ Changes (by fgsch): * milestone: => Varnish 4.0-TP2 Old description: > *** v1 0.8 debug| Child (29331) died signal=6 (core dumped)\n > *** v1 0.8 debug| Child (29331) Panic message: Assert error in > vbf_stp_fetchhdr(), cache/cache_fetch.c line 277:\n > *** v1 0.8 debug| Condition(wrk->handling == VCL_RET_DELIVER) not > true.\n > > See attached test. New description: {{{ *** v1 0.8 debug| Child (29331) died signal=6 (core dumped)\n *** v1 0.8 debug| Child (29331) Panic message: Assert error in vbf_stp_fetchhdr(), cache/cache_fetch.c line 277:\n *** v1 0.8 debug| Condition(wrk->handling == VCL_RET_DELIVER) not true.\n }}} See attached test. -- -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Jan 24 23:52:46 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 24 Jan 2014 23:52:46 -0000 Subject: [Varnish] #1416: Panic on abandon in vcl_backend_response In-Reply-To: <043.ba17f45f1ad62a35fd07f5fcdcade067@varnish-cache.org> References: <043.ba17f45f1ad62a35fd07f5fcdcade067@varnish-cache.org> Message-ID: <058.0700f73ce28aa49c357267ae3fa67830@varnish-cache.org> #1416: Panic on abandon in vcl_backend_response ----------------------+------------------------ Reporter: fgsch | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: duplicate Keywords: | ----------------------+------------------------ Changes (by fgsch): * status: new => closed * resolution: => duplicate -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 27 11:07:55 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 27 Jan 2014 11:07:55 -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.493c5a82d1e52b7ede23f0de0e23d9a3@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-TP2 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 Jan 27 11:21:29 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 27 Jan 2014 11:21:29 -0000 Subject: [Varnish] #1372: Consistent crashes with seg fault error 4 in libc-2.12.so In-Reply-To: <045.a0d66f4881fdf144e127f5a22a64caca@varnish-cache.org> References: <045.a0d66f4881fdf144e127f5a22a64caca@varnish-cache.org> Message-ID: <060.74c278424c123fd254695fa0db6ee07c@varnish-cache.org> #1372: Consistent crashes with seg fault error 4 in libc-2.12.so ----------------------+------------------------------ Reporter: tomypro | Owner: Type: defect | Status: new Priority: highest | Milestone: Varnish 3.0 dev Component: varnishd | Version: 3.0.4 Severity: blocker | Resolution: Keywords: | ----------------------+------------------------------ Comment (by lkarsten): Hi. We'd like to dig into this, but it is hard without further information. The .so file you're referring to is the compiled VCL version. We need the plaintext one. Here are some more info on how to extract the details we need: https://www.varnish-cache.org/trac/wiki/DebuggingVarnish Can you also define what a "smaller equiped cloud server" is? What kind of virtualisation method is being used? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Jan 27 11:53:39 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 27 Jan 2014 11:53:39 -0000 Subject: [Varnish] #1086: VGZ_WrwGunzip loops forever if receiving junk data after end of gzip data In-Reply-To: <044.dedba8f13c20d02f02a39731a1edea7c@varnish-cache.org> References: <044.dedba8f13c20d02f02a39731a1edea7c@varnish-cache.org> Message-ID: <059.eecf78b31146db804fa16c75e27b5b4b@varnish-cache.org> #1086: VGZ_WrwGunzip loops forever if receiving junk data after end of gzip data ----------------------+--------------------- Reporter: martin | Owner: martin Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 3.0.2 Severity: normal | Resolution: fixed Keywords: | ----------------------+--------------------- Changes (by Lasse Karstensen ): * status: new => closed * resolution: => fixed Comment: In [4ae3ffc3ab7cd358fa626caf3a9fab55f3bda22d]: {{{ #!CommitTicketReference repository="" revision="4ae3ffc3ab7cd358fa626caf3a9fab55f3bda22d" Stop handling after gzip object end. Junk after gzip body end would lead to a spinning thread. Fixes: #1086 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Jan 28 15:30:34 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 28 Jan 2014 15:30:34 -0000 Subject: [Varnish] #1418: Makefile race for vcc_if.h Message-ID: <046.944204b95cd6cb7cd4d6a036e18ceb8a@varnish-cache.org> #1418: Makefile race for vcc_if.h ----------------------+------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: minor | Keywords: ----------------------+------------------- In current master, when building in parallel, the first attempt is halted because libvmod_debug/vcc_if.h isn't ready yet. Re-running make after it fails resumes compilation. {{{ CC libvgz_la-uncompr.lo CC libvgz_la-zutil.lo CCLD libvgz.la make[3]: Leaving directory `/home/lkarsten/varnish-4.0.0-tp2/lib/libvgz' Making all in libvmod_debug make[3]: Entering directory `/home/lkarsten/varnish-4.0.0-tp2/lib/libvmod_debug' python2 ../../lib/libvcc/vmodtool.py ../../lib/libvmod_debug/vmod.vcc python2 ../../lib/libvcc/vmodtool.py ../../lib/libvmod_debug/vmod.vcc CC vmod_debug_obj.lo vmod_debug_obj.c:36:20: error: vcc_if.h: No such file or directory make[3]: *** [vmod_debug_obj.lo] Error 1 make[3]: *** Waiting for unfinished jobs.... Warning: $Init description is not included in .rst: Warning: $Init description is not included in .rst: ('\t', '') ('\t', 'Call this whenever a VCL is loaded which imports this vmod.') ('\t', '') ('\t', '') ('\t', 'Call this whenever a VCL is loaded which imports this vmod.') ('\t', '') make[3]: Leaving directory `/home/lkarsten/varnish-4.0.0-tp2/lib/libvmod_debug' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/lkarsten/varnish-4.0.0-tp2/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/lkarsten/varnish-4.0.0-tp2' make: *** [all] Error 2 }}} (output says 4.0.0-tp2, but it is master from jenkins tarball due to non- working autoconf on el5) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 29 08:17:48 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 29 Jan 2014 08:17:48 -0000 Subject: [Varnish] #1419: Assert error in oc_getobj(), cache/cache.h line 457: Condition((oc->flags & (1<<1)) == 0) not true. Message-ID: <043.ddb6ed54aaa7cab2451d4380877d355e@varnish-cache.org> #1419: Assert error in oc_getobj(), cache/cache.h line 457: Condition((oc->flags & (1<<1)) == 0) not true. ----------------------+----------------------------- Reporter: scoof | Owner: Type: defect | Status: new Priority: normal | Milestone: Varnish 4.0-TP2 Component: varnishd | Version: unknown Severity: normal | Keywords: ----------------------+----------------------------- Running bb710b14b5362d5b109fa95351fae853c807334b and my SES_Charge patch {{{ Last panic at: Wed, 29 Jan 2014 08:00:50 GMT Assert error in oc_getobj(), cache/cache.h line 457: Condition((oc->flags & (1<<1)) == 0) not true. thread = (ban-lurker) ident = Linux,2.6.32-5-amd64,x86_64,-smalloc,-smalloc,-hcritbit,epoll Backtrace: 0x4396f0: pan_backtrace+0x19 0x439a00: pan_ic+0x1e8 0x41477a: oc_getobj+0xba 0x417ad5: ban_lurker_test_ban+0x121 0x417f81: ban_lurker_work+0x299 0x418022: ban_lurker+0x68 0x453fe2: wrk_bgthread+0xde 0x7fe889f2d8ba: /lib/libpthread.so.0(+0x68ba) [0x7fe889f2d8ba] 0x7fe889c9502d: /lib/libc.so.6(clone+0x6d) [0x7fe889c9502d] }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 29 11:19:04 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 29 Jan 2014 11:19:04 -0000 Subject: [Varnish] #1419: Assert error in oc_getobj(), cache/cache.h line 457: Condition((oc->flags & (1<<1)) == 0) not true. In-Reply-To: <043.ddb6ed54aaa7cab2451d4380877d355e@varnish-cache.org> References: <043.ddb6ed54aaa7cab2451d4380877d355e@varnish-cache.org> Message-ID: <058.2de4b3c351f40c39f970dbde99f7d13a@varnish-cache.org> #1419: Assert error in oc_getobj(), cache/cache.h line 457: Condition((oc->flags & (1<<1)) == 0) not true. ----------------------+---------------------------------------- Reporter: scoof | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Varnish 4.0-TP2 Component: varnishd | Version: unknown Severity: normal | Resolution: fixed Keywords: | ----------------------+---------------------------------------- Changes (by Poul-Henning Kamp ): * owner: => Poul-Henning Kamp * status: new => closed * resolution: => fixed Comment: In [4067f504827b349ee61d481b5218b1e1b09afed1]: {{{ #!CommitTicketReference repository="" revision="4067f504827b349ee61d481b5218b1e1b09afed1" Don't put objcores on the ban list until they go non-BUSY. Fixes #1419 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 29 11:27:39 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 29 Jan 2014 11:27:39 -0000 Subject: [Varnish] #1420: Ban/Fetch race Message-ID: <041.b95ccb65dcdc701e3d0812123d5cc95f@varnish-cache.org> #1420: Ban/Fetch race ----------------------+------------------- Reporter: phk | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+------------------- There exists a race between fetch and bans today: Fetch starts, but takes long time. Ban is entered which applies to fetch Once we get the headers from the backend, we currently do not check if any bans were entered between the fetch starting and now, which might apply. What to do in that case is also slightly icky. Turning the fetch into a pass has been proposed as a least-evil handling. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 29 13:26:05 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 29 Jan 2014 13:26:05 -0000 Subject: [Varnish] #1421: BEST CREAM EVER FOR AGE EFFECT Message-ID: <049.f389a0de9439744e4c76eef88ba2f42c@varnish-cache.org> #1421: BEST CREAM EVER FOR AGE EFFECT -------------------------+-------------------- Reporter: LeeannaWood | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: unknown | Severity: normal Keywords: | -------------------------+-------------------- power to maintain your face left weekly [Miracle Phytoceramides] facial exercises are a great way for men and women toehold and reverse the signs of aging in as little as 30 games you could look a decade younger without any surgery amaze your friends and family with your and youth it only takes a few minutes a week click on the link on the video description section below to start looking younger now everybody this is Annie information makeup time to come today in the show you how to do eighty conjuring facial missiles this will. Happen if you think you thinkmickey you and radiant face massage is extremely beneficial to in the blood circulation cell it will bring blood and oxygen in underneath it eat so many things to be done it will self in mind done it will help the money in the toxins and produce collagen be sure to wash your face and moisturize before you begin put on some relaxation music a place like pressured never but I felt. [http://miraclephytoceramidesfacts.com] -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Jan 29 21:52:03 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 29 Jan 2014 21:52:03 -0000 Subject: [Varnish] #1422: varnishd keeps getting a SIGINT Message-ID: <049.bfe295782aa14e08240053a6e8dcb920@varnish-cache.org> #1422: varnishd keeps getting a SIGINT -------------------------+---------------------- Reporter: raymondjiii | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: unknown | Severity: normal Keywords: | -------------------------+---------------------- Looking at /var/log/messages Jan 20 11:43:12 ip-10-124-15-198 varnishd[32482]: Manager got SIGINT Jan 20 11:43:13 ip-10-124-15-198 varnishd[32592]: Platform: Linux,2.6.32-71.29.1.el6.x86_64,x86_64,-sfile,-smalloc,-hcritbit Jan 20 11:43:13 ip-10-124-15-198 varnishd[32592]: child (32596) Started Jan 20 11:43:13 ip-10-124-15-198 varnishd[32592]: Child (32596) said Child starts Jan 20 11:43:13 ip-10-124-15-198 varnishd[32592]: Child (32596) said SMF.s0 mmap'ed 9663676416 bytes of 9663676416 This seems to happen at random. Here is varnishd running: root 3610 1 0 09:36 ? 00:00:00 /usr/sbin/varnishd -P /var/run/varnish.pid -a :80 -f /etc/varnish/default.vcl -T 10.124.15.198:6082 -t 2400 -w 1,1000,120 -p shm_reclen=1024 -p http_req_hdr_len=17408 -p idle_send_timeout=30 -u varnish -g varnish -S /etc/varnish/secret -s file,/var/lib/varnish/varnish_storage.bin,9G varnish 3614 3610 0 09:36 ? 00:00:37 /usr/sbin/varnishd -P /var/run/varnish.pid -a :80 -f /etc/varnish/default.vcl -T 10.124.15.198:6082 -t 2400 -w 1,1000,120 -p shm_reclen=1024 -p http_req_hdr_len=17408 -p idle_send_timeout=30 -u varnish -g varnish -S /etc/varnish/secret -s file,/var/lib/varnish/varnish_storage.bin,9G Is there anything I can look at to see why varnishd is constantly being SIGINT'd ? None of my filesystems are anywhere near full: -rw------- 1 root root 9663676416 Jan 29 16:50 varnish_storage.bin /tmp is fine -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 30 07:36:45 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 30 Jan 2014 07:36:45 -0000 Subject: [Varnish] #1422: varnishd keeps getting a SIGINT In-Reply-To: <049.bfe295782aa14e08240053a6e8dcb920@varnish-cache.org> References: <049.bfe295782aa14e08240053a6e8dcb920@varnish-cache.org> Message-ID: <064.3fe48a3036483cfdd44635ccee71c0dd@varnish-cache.org> #1422: varnishd keeps getting a SIGINT -------------------------+---------------------- Reporter: raymondjiii | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: unknown Severity: normal | Resolution: Keywords: | -------------------------+---------------------- Description changed by tfheen: Old description: > Looking at /var/log/messages > > Jan 20 11:43:12 ip-10-124-15-198 varnishd[32482]: Manager got SIGINT > Jan 20 11:43:13 ip-10-124-15-198 varnishd[32592]: Platform: > Linux,2.6.32-71.29.1.el6.x86_64,x86_64,-sfile,-smalloc,-hcritbit > Jan 20 11:43:13 ip-10-124-15-198 varnishd[32592]: child (32596) Started > Jan 20 11:43:13 ip-10-124-15-198 varnishd[32592]: Child (32596) said > Child starts > Jan 20 11:43:13 ip-10-124-15-198 varnishd[32592]: Child (32596) said > SMF.s0 mmap'ed 9663676416 bytes of 9663676416 > > This seems to happen at random. > > Here is varnishd running: > > root 3610 1 0 09:36 ? 00:00:00 /usr/sbin/varnishd -P > /var/run/varnish.pid -a :80 -f /etc/varnish/default.vcl -T > 10.124.15.198:6082 -t 2400 -w 1,1000,120 -p shm_reclen=1024 -p > http_req_hdr_len=17408 -p idle_send_timeout=30 -u varnish -g varnish -S > /etc/varnish/secret -s file,/var/lib/varnish/varnish_storage.bin,9G > varnish 3614 3610 0 09:36 ? 00:00:37 /usr/sbin/varnishd -P > /var/run/varnish.pid -a :80 -f /etc/varnish/default.vcl -T > 10.124.15.198:6082 -t 2400 -w 1,1000,120 -p shm_reclen=1024 -p > http_req_hdr_len=17408 -p idle_send_timeout=30 -u varnish -g varnish -S > /etc/varnish/secret -s file,/var/lib/varnish/varnish_storage.bin,9G > > Is there anything I can look at to see why varnishd is constantly being > SIGINT'd ? > > None of my filesystems are anywhere near full: > > -rw------- 1 root root 9663676416 Jan 29 16:50 varnish_storage.bin > > /tmp is fine New description: Looking at /var/log/messages {{{ Jan 20 11:43:12 ip-10-124-15-198 varnishd[32482]: Manager got SIGINT Jan 20 11:43:13 ip-10-124-15-198 varnishd[32592]: Platform: Linux,2.6.32-71.29.1.el6.x86_64,x86_64,-sfile,-smalloc,-hcritbit Jan 20 11:43:13 ip-10-124-15-198 varnishd[32592]: child (32596) Started Jan 20 11:43:13 ip-10-124-15-198 varnishd[32592]: Child (32596) said Child starts Jan 20 11:43:13 ip-10-124-15-198 varnishd[32592]: Child (32596) said SMF.s0 mmap'ed 9663676416 bytes of 9663676416 }}} This seems to happen at random. Here is varnishd running: {{{ root 3610 1 0 09:36 ? 00:00:00 /usr/sbin/varnishd -P /var/run/varnish.pid -a :80 -f /etc/varnish/default.vcl -T 10.124.15.198:6082 -t 2400 -w 1,1000,120 -p shm_reclen=1024 -p http_req_hdr_len=17408 -p idle_send_timeout=30 -u varnish -g varnish -S /etc/varnish/secret -s file,/var/lib/varnish/varnish_storage.bin,9G varnish 3614 3610 0 09:36 ? 00:00:37 /usr/sbin/varnishd -P /var/run/varnish.pid -a :80 -f /etc/varnish/default.vcl -T 10.124.15.198:6082 -t 2400 -w 1,1000,120 -p shm_reclen=1024 -p http_req_hdr_len=17408 -p idle_send_timeout=30 -u varnish -g varnish -S /etc/varnish/secret -s file,/var/lib/varnish/varnish_storage.bin,9G }}} Is there anything I can look at to see why varnishd is constantly being SIGINT'd ? None of my filesystems are anywhere near full: -rw------- 1 root root 9663676416 Jan 29 16:50 varnish_storage.bin /tmp is fine -- -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 30 07:39:58 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 30 Jan 2014 07:39:58 -0000 Subject: [Varnish] #1422: varnishd keeps getting a SIGINT In-Reply-To: <049.bfe295782aa14e08240053a6e8dcb920@varnish-cache.org> References: <049.bfe295782aa14e08240053a6e8dcb920@varnish-cache.org> Message-ID: <064.d745d47a11516154f73212a8a7c749f4@varnish-cache.org> #1422: varnishd keeps getting a SIGINT -------------------------+---------------------- Reporter: raymondjiii | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: unknown Severity: normal | Resolution: Keywords: | -------------------------+---------------------- Comment (by tfheen): If it just randomly happens, I don't really know what could be causing it. It's certainly not Varnish itself. Check dmesg for any hints about you hitting the OOM killer, also check other log files for clues. If none of that helps, I'd write a systemtap script to log sender and receiver of all signals and use that to track it down. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 30 10:43:58 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 30 Jan 2014 10:43:58 -0000 Subject: [Varnish] #1418: Makefile race for vcc_if.h In-Reply-To: <046.944204b95cd6cb7cd4d6a036e18ceb8a@varnish-cache.org> References: <046.944204b95cd6cb7cd4d6a036e18ceb8a@varnish-cache.org> Message-ID: <061.ce15b0f31586421837549a449b1b3e31@varnish-cache.org> #1418: Makefile race for vcc_if.h ----------------------+------------------------------------------ Reporter: lkarsten | Owner: Dag Haavi Finstad Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: minor | Resolution: fixed Keywords: | ----------------------+------------------------------------------ Changes (by Dag Haavi Finstad ): * owner: => Dag Haavi Finstad * status: new => closed * resolution: => fixed Comment: In [d43af818662a8c5cf3330c850f42c79b62b07baf]: {{{ #!CommitTicketReference repository="" revision="d43af818662a8c5cf3330c850f42c79b62b07baf" Fix missing dependency in libvmod_debug makefile. Fixes: #1418 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Jan 30 12:50:25 2014 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 30 Jan 2014 12:50:25 -0000 Subject: [Varnish] #1423: Make Your Body Slim Message-ID: <052.7265850bce90505c22ecb9668f5b6ebd@varnish-cache.org> #1423: Make Your Body Slim ----------------------------+-------------------- Reporter: doriscarpenter | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: unknown | Severity: normal Keywords: | ----------------------------+-------------------- That would fantastic we've got one more month are call without mama nice I got my first let?s all make they're going to want right lacks not like35 rights left yeah not its rights good do it again I alright do that work again we got it here treat got sidetracked right left really complex now mother alright I get march right that was great the left caviar hoping to take some time you're going to love it here we go call soup 3 and four can't are chapped right back I'm not that girl going to do. Make sure you show your back and your plot really go for poem 3 you believe that public sex top you three loll get there you go market cap alright I think we've got back I cannot & Co all the way back to the top I alright the whole thing DE [http://zymbiotixcleansefacts.com/ zmybiotix Cleanse] Paul 3 seem I get 5gb cap track now to get back opened it up out here we go okay get that means that I guess can't write shot Cuban hogtie sweat trust struck at top take it up the ass kidnapped and not take it back now good drop in overall truck drop. yet good take 3 day and re: I cant out 10 let now by really bad again good well a bath right here hell by yeah mom both shine have started out with yeah great job however detailed it we're going to go back to top and you hope to get few times tell right I'm going to add margin between feeling like irk I'll forget everything you?ve got asthmatic here me outbreak track I yeah nothing got hat think sup together great yeah with this track with strut their stuff have time to come up there. http://zymbiotixcleansefacts.com/ -- Ticket URL: Varnish The Varnish HTTP Accelerator