From varnish-bugs at varnish-cache.org Fri Feb 1 17:18:31 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 01 Feb 2013 17:18:31 -0000 Subject: [Varnish] #1259: Backend naming bug Message-ID: <041.62bb8cd4d5352e5c2ad3ec33c21be152@varnish-cache.org> #1259: Backend naming bug -------------------+-------------------- Reporter: urg | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: trunk | Severity: normal Keywords: | -------------------+-------------------- Any backend that starts with if causes the following error: Message from VCC-compiler: Expected ID got 'if' (program line 331), at ('/etc/varnish/servers-pre-verify.vcl' Line 1 Pos 9) backend ifa -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:00:04 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:00:04 -0000 Subject: [Varnish] #957: Bug in varnishstat related to the -f option In-Reply-To: <045.f672148c0581799d40cc68509dc3b9da@varnish-cache.org> References: <045.f672148c0581799d40cc68509dc3b9da@varnish-cache.org> Message-ID: <060.b42617d813d67e8c7a511eac225f1f17@varnish-cache.org> #957: Bug in varnishstat related to the -f option -------------------------+--------------------- Reporter: leed25d | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: varnishstat | Version: 3.0.0 Severity: major | Resolution: Keywords: | -------------------------+--------------------- Changes (by martin): * owner: tfheen => martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:00:28 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:00:28 -0000 Subject: [Varnish] #937: missing files in varnish-libs-devel rpm package In-Reply-To: <043.9bed421a56403203c823b6e9dcc79ebf@varnish-cache.org> References: <043.9bed421a56403203c823b6e9dcc79ebf@varnish-cache.org> Message-ID: <058.ff026c642fafa07b5697da78867064e6@varnish-cache.org> #937: missing files in varnish-libs-devel rpm package -----------------------+------------------------------ Reporter: fr3nd | Owner: tfheen Type: defect | Status: new Priority: normal | Milestone: Varnish 3.0 dev Component: packaging | Version: trunk Severity: normal | Resolution: Keywords: rpm vmod | -----------------------+------------------------------ Changes (by tfheen): * owner: kristian => tfheen -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:07:47 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:07:47 -0000 Subject: [Varnish] #1018: Man vcl missing director options In-Reply-To: <043.0ef8568f105acbda1448ea0094a04325@varnish-cache.org> References: <043.0ef8568f105acbda1448ea0094a04325@varnish-cache.org> Message-ID: <058.8525e0cdebdd9471ea4fe2a4e1847d22@varnish-cache.org> #1018: Man vcl missing director options ---------------------------+---------------------- Reporter: scoof | Owner: drwilco Type: documentation | Status: new Priority: lowest | Milestone: Component: documentation | Version: trunk Severity: trivial | Resolution: Keywords: | ---------------------------+---------------------- Changes (by drwilco): * owner: scoof => drwilco -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:10:13 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:10:13 -0000 Subject: [Varnish] #1163: .saintmode_threshold with ESI In-Reply-To: <045.5eb39dca6fe96b66a032aa3d10aa6903@varnish-cache.org> References: <045.5eb39dca6fe96b66a032aa3d10aa6903@varnish-cache.org> Message-ID: <060.6ebd2a48553510efe0bf28dd47b55b7a@varnish-cache.org> #1163: .saintmode_threshold with ESI ----------------------------+----------------------- Reporter: fenidik | Owner: lkarsten Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: 3.0.2 Severity: normal | Resolution: Keywords: esi, saintmode | ----------------------------+----------------------- Comment (by lkarsten): This was discussed this during the 2013Q1 developer day, and nobody is really sure what is going on. Is it a fetch error because the ESI components can't be loaded, or due to something else? This is a fairly old ticket, is this still a problem? Please provide more information, varnishstat and parameter list. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:16:47 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:16:47 -0000 Subject: [Varnish] #1178: Varnish should add Vary: Accept-Encoding when compressing content In-Reply-To: <043.f8e3add5fe2d9de34f59397c4cedbe58@varnish-cache.org> References: <043.f8e3add5fe2d9de34f59397c4cedbe58@varnish-cache.org> Message-ID: <058.4322eefece66629879e3146ff0149141@varnish-cache.org> #1178: Varnish should add Vary: Accept-Encoding when compressing content --------------------+------------------------ Reporter: scoof | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: duplicate Keywords: | --------------------+------------------------ Changes (by slink): * status: new => closed * resolution: => duplicate Comment: Yes, we need to do this and we will when we get to #940 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:20:33 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:20:33 -0000 Subject: [Varnish] #940: For gzip and un-gzip: Change ETags and add Vary (was: ETag for gzip'd variant identical to ETag of ungzipped variant.) In-Reply-To: <043.d3f0122c5f2e8a8e1ed36783de6aff0a@varnish-cache.org> References: <043.d3f0122c5f2e8a8e1ed36783de6aff0a@varnish-cache.org> Message-ID: <058.57022d203eb1bcfe59c8d8faf3c92d14@varnish-cache.org> #940: For gzip and un-gzip: Change ETags and add Vary ----------------------+-------------------- Reporter: david | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: build | Version: 3.0.0 Severity: critical | Resolution: Keywords: | ----------------------+-------------------- Changes (by slink): * owner: martin => phk Comment: We have made the decision documented in [wiki:Etags]: * Remove `Etag` on way out for un-gzip * Make `Etag` `W/"eak"` on way out for gzip * Add `Vary: Accept-Encoding` for gzip -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:21:49 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:21:49 -0000 Subject: [Varnish] #1167: 3.0.3rc1 Compile Error on Solaris 10 with gcc 4.3.3 In-Reply-To: <044.677261b72c12472e07a7cff6c933fe66@varnish-cache.org> References: <044.677261b72c12472e07a7cff6c933fe66@varnish-cache.org> Message-ID: <059.289fc92f11cad51d2e984eda14bbf408@varnish-cache.org> #1167: 3.0.3rc1 Compile Error on Solaris 10 with gcc 4.3.3 --------------------------+--------------------- Reporter: Dommas | Owner: thfeen Type: defect | Status: new Priority: normal | Milestone: Component: port:solaris | Version: 3.0.3 Severity: normal | Resolution: Keywords: | --------------------------+--------------------- Changes (by slink): * owner: slink => thfeen Comment: giving to tollef for merge -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:28:17 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:28:17 -0000 Subject: [Varnish] #1166: Varnishadm throws an assert In-Reply-To: <051.5814c781387d31eb173c4ed622e0ca4c@varnish-cache.org> References: <051.5814c781387d31eb173c4ed622e0ca4c@varnish-cache.org> Message-ID: <066.b21d291893381a6f2f9e9f3094a57aad@varnish-cache.org> #1166: Varnishadm throws an assert ------------------------+--------------------- Reporter: rj@? | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: varnishadm | Version: 3.0.2 Severity: normal | Resolution: Keywords: varnishadm | ------------------------+--------------------- Comment (by lkarsten): I'm able to reproduce this with 3.0.3. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:29:01 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:29:01 -0000 Subject: [Varnish] #1219: degraded speed with persistent storage In-Reply-To: <047.d33cc554f18272c8c3e85a89b7fa6dd4@varnish-cache.org> References: <047.d33cc554f18272c8c3e85a89b7fa6dd4@varnish-cache.org> Message-ID: <062.653bf6ceb8f6b49c2b5b516d68d74589@varnish-cache.org> #1219: degraded speed with persistent storage -----------------------+--------------------- Reporter: stavrinov | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Resolution: Keywords: | -----------------------+--------------------- Comment (by martin): Could you please check with the current 3.0-plus and see if there is still a major slow down on persistence? There are large works on both streaming and persistence there. Regards, Martin Blix Grydeland -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:30:29 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:30:29 -0000 Subject: [Varnish] #1207: varnishd child segfaults when using dns director In-Reply-To: <046.cbd6b84dea250737a025adc3c0105555@varnish-cache.org> References: <046.cbd6b84dea250737a025adc3c0105555@varnish-cache.org> Message-ID: <061.6ac174c522e97974430e83b9d623260e@varnish-cache.org> #1207: varnishd child segfaults when using dns director --------------------------+---------------------- Reporter: econnell | Owner: drwilco Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.2 Severity: normal | Resolution: Keywords: dns director | --------------------------+---------------------- Changes (by drwilco): * owner: kristian => drwilco -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:30:31 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:30:31 -0000 Subject: [Varnish] #1198: Make check takes much longer after we started to sync the shmem file In-Reply-To: <044.9aa3d0a3e8fb7c21731fdfe1e38a61ff@varnish-cache.org> References: <044.9aa3d0a3e8fb7c21731fdfe1e38a61ff@varnish-cache.org> Message-ID: <059.6d7da11562c809b91b5051c1c88df446@varnish-cache.org> #1198: Make check takes much longer after we started to sync the shmem file --------------------+-------------------- Reporter: martin | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+-------------------- Comment (by Poul-Henning Kamp ): In [8a2fdce41f76c161a130c722d63cbdafddf6337c]: {{{ #!CommitTicketReference repository="" revision="8a2fdce41f76c161a130c722d63cbdafddf6337c" Only msync() on OS's without coherent buf/vm (aka: OpenBSD) Fixes #1198 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:30:33 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:30:33 -0000 Subject: [Varnish] #1198: Make check takes much longer after we started to sync the shmem file In-Reply-To: <044.9aa3d0a3e8fb7c21731fdfe1e38a61ff@varnish-cache.org> References: <044.9aa3d0a3e8fb7c21731fdfe1e38a61ff@varnish-cache.org> Message-ID: <059.858d5035a10782d051b7d126c836e622@varnish-cache.org> #1198: Make check takes much longer after we started to sync the shmem file --------------------+--------------------- Reporter: martin | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+--------------------- Changes (by Poul-Henning Kamp ): * status: new => closed * resolution: => fixed Comment: (In [8a2fdce41f76c161a130c722d63cbdafddf6337c]) Only msync() on OS's without coherent buf/vm (aka: OpenBSD) Fixes #1198 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:31:22 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:31:22 -0000 Subject: [Varnish] #1003: Fix libedit (libreadline) support for FreeBSD In-Reply-To: <044.97ea0cb79c8172ef6b88dc23843a837c@varnish-cache.org> References: <044.97ea0cb79c8172ef6b88dc23843a837c@varnish-cache.org> Message-ID: <059.8b2a003f737104315da3042b6d709a69@varnish-cache.org> #1003: Fix libedit (libreadline) support for FreeBSD -------------------------+----------------------- Reporter: anders | Owner: tfheen Type: enhancement | Status: reopened Priority: normal | Milestone: Component: build | Version: 3.0.1 Severity: normal | Resolution: Keywords: | -------------------------+----------------------- Comment (by bz): I'll try to track this down with anders and solve it for FreeBSD and the ports as well. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:33:36 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:33:36 -0000 Subject: [Varnish] #1166: Varnishadm throws an assert In-Reply-To: <051.5814c781387d31eb173c4ed622e0ca4c@varnish-cache.org> References: <051.5814c781387d31eb173c4ed622e0ca4c@varnish-cache.org> Message-ID: <066.0e815967b36caac38d7b66c9e315e58f@varnish-cache.org> #1166: Varnishadm throws an assert ------------------------+--------------------- Reporter: rj@? | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: varnishadm | Version: 3.0.2 Severity: normal | Resolution: Keywords: varnishadm | ------------------------+--------------------- Comment (by Tollef Fog Heen ): In [683cc929be04d8693e005eb298bc0c9d5eb13f7d]: {{{ #!CommitTicketReference repository="" revision="683cc929be04d8693e005eb298bc0c9d5eb13f7d" varnishadm: Handle EINTR from poll poll can return EINTR, so we need to handle that. Fixes: #1166 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:33:38 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:33:38 -0000 Subject: [Varnish] #1166: Varnishadm throws an assert In-Reply-To: <051.5814c781387d31eb173c4ed622e0ca4c@varnish-cache.org> References: <051.5814c781387d31eb173c4ed622e0ca4c@varnish-cache.org> Message-ID: <066.bf62f87a08e395f83f44190dc29bed5e@varnish-cache.org> #1166: Varnishadm throws an assert ------------------------+--------------------- Reporter: rj@? | Owner: martin Type: defect | Status: closed Priority: normal | Milestone: Component: varnishadm | Version: 3.0.2 Severity: normal | Resolution: fixed Keywords: varnishadm | ------------------------+--------------------- Changes (by Tollef Fog Heen ): * status: new => closed * resolution: => fixed Comment: (In [683cc929be04d8693e005eb298bc0c9d5eb13f7d]) varnishadm: Handle EINTR from poll poll can return EINTR, so we need to handle that. Fixes: #1166 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:39:22 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:39:22 -0000 Subject: [Varnish] #1224: Long backend name asserts the varnishd child In-Reply-To: <046.c4f71086627c182e1c792186110e4c5e@varnish-cache.org> References: <046.c4f71086627c182e1c792186110e4c5e@varnish-cache.org> Message-ID: <061.54ea2930327064819fa5ed57c3c0ab30@varnish-cache.org> #1224: Long backend name asserts the varnishd child ----------------------+-------------------- Reporter: lkarsten | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: 3.0.3 Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Comment (by lkarsten): Todo: needs to be backported into 3.0.3. Tollef does that. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:39:42 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:39:42 -0000 Subject: [Varnish] #1224: Long backend name asserts the varnishd child In-Reply-To: <046.c4f71086627c182e1c792186110e4c5e@varnish-cache.org> References: <046.c4f71086627c182e1c792186110e4c5e@varnish-cache.org> Message-ID: <061.a1b675fcc96f054c60246cdf328e2626@varnish-cache.org> #1224: Long backend name asserts the varnishd child ----------------------+--------------------- Reporter: lkarsten | Owner: tfheen Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: 3.0.3 Severity: normal | Resolution: Keywords: | ----------------------+--------------------- Changes (by lkarsten): * owner: => tfheen -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:43:33 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:43:33 -0000 Subject: [Varnish] #1235: Frequent Varnish crashes - Size of Varnish cache never grows In-Reply-To: <048.31522a660c9c9b92f418dc9cbf9c8028@varnish-cache.org> References: <048.31522a660c9c9b92f418dc9cbf9c8028@varnish-cache.org> Message-ID: <063.2591d979f1beb01e1456b3cc7ecb5e2b@varnish-cache.org> #1235: Frequent Varnish crashes - Size of Varnish cache never grows ------------------------+------------------------- Reporter: msallen333 | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 3.0.2 Severity: normal | Resolution: worksforme Keywords: crash | ------------------------+------------------------- Changes (by martin): * status: new => closed * resolution: => worksforme Comment: Closing - lack of response. Regards, Martin Blix Grydeland -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:51:10 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:51:10 -0000 Subject: [Varnish] #1247: yum installation error "[Errno -1] Header is not complete." In-Reply-To: <044.e3db3b22021d9bf26d4bc79f8b887423@varnish-cache.org> References: <044.e3db3b22021d9bf26d4bc79f8b887423@varnish-cache.org> Message-ID: <059.0db55b5112780dcfb8262f1828ec501e@varnish-cache.org> #1247: yum installation error "[Errno -1] Header is not complete." --------------------+--------------------- Reporter: Damien | Owner: tfheen Type: defect | Status: new Priority: high | Milestone: Component: build | Version: trunk Severity: major | Resolution: Keywords: | --------------------+--------------------- Comment (by tfheen): Does wget-ing the file and installing by hand locally work for you? Can you please provide information about your IPs? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 11:57:05 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 11:57:05 -0000 Subject: [Varnish] #1124: Document Cache-Control private/no-cache behaviour In-Reply-To: <046.efd3b140d66579698a8653ee733c7d45@varnish-cache.org> References: <046.efd3b140d66579698a8653ee733c7d45@varnish-cache.org> Message-ID: <061.af39db92eacf7ab98d781efa2567b81f@varnish-cache.org> #1124: Document Cache-Control private/no-cache behaviour ---------------------------+-------------------- Reporter: timbunce | Owner: slink Type: documentation | Status: new Priority: normal | Milestone: Component: documentation | Version: 3.0.2 Severity: normal | Resolution: Keywords: | ---------------------------+-------------------- Changes (by drwilco): * owner: => slink -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 13:51:00 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 13:51:00 -0000 Subject: [Varnish] #1071: Varnishlog -m includes NOISE In-Reply-To: <046.9c810e03f23c7c76d4cf7a124260e531@varnish-cache.org> References: <046.9c810e03f23c7c76d4cf7a124260e531@varnish-cache.org> Message-ID: <061.e28be3c1aebc80fd9f3a7f2d8bb11a49@varnish-cache.org> #1071: Varnishlog -m includes NOISE ------------------------+--------------------- Reporter: kristian | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: varnishlog | Version: 3.0.2 Severity: normal | Resolution: Keywords: | ------------------------+--------------------- Comment (by Tollef Fog Heen ): In [78936f6460cb8d6dc61d93d828f51c42018e411f]: {{{ #!CommitTicketReference repository="" revision="78936f6460cb8d6dc61d93d828f51c42018e411f" varnishlog: if -m given, but no -c and -b, assume both If we don't add -c and -b in there, varnishlog will print all transactions that aren't associated with a session. That is likely to not be what the user wants. Fixes: #1071 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 13:51:03 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 13:51:03 -0000 Subject: [Varnish] #1071: Varnishlog -m includes NOISE In-Reply-To: <046.9c810e03f23c7c76d4cf7a124260e531@varnish-cache.org> References: <046.9c810e03f23c7c76d4cf7a124260e531@varnish-cache.org> Message-ID: <061.d0d9107dc026d3a7042377cd3ba360b3@varnish-cache.org> #1071: Varnishlog -m includes NOISE ------------------------+--------------------- Reporter: kristian | Owner: martin Type: defect | Status: closed Priority: normal | Milestone: Component: varnishlog | Version: 3.0.2 Severity: normal | Resolution: fixed Keywords: | ------------------------+--------------------- Changes (by Tollef Fog Heen ): * status: new => closed * resolution: => fixed Comment: (In [78936f6460cb8d6dc61d93d828f51c42018e411f]) varnishlog: if -m given, but no -c and -b, assume both If we don't add -c and -b in there, varnishlog will print all transactions that aren't associated with a session. That is likely to not be what the user wants. Fixes: #1071 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 14:18:31 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 14:18:31 -0000 Subject: [Varnish] #1130: varnishncsa -d makes it exit(0) after processing old entries In-Reply-To: <040.07815af94e0e42afed90f4fadb228259@varnish-cache.org> References: <040.07815af94e0e42afed90f4fadb228259@varnish-cache.org> Message-ID: <055.e539a0584f18dbdd34005f191715ff5b@varnish-cache.org> #1130: varnishncsa -d makes it exit(0) after processing old entries -------------------------+--------------------- Reporter: bz | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: varnishncsa | Version: 3.0.2 Severity: normal | Resolution: Keywords: | -------------------------+--------------------- Changes (by martin): * owner: daghf => martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 14:22:50 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 14:22:50 -0000 Subject: [Varnish] #1130: varnishncsa -d makes it exit(0) after processing old entries In-Reply-To: <040.07815af94e0e42afed90f4fadb228259@varnish-cache.org> References: <040.07815af94e0e42afed90f4fadb228259@varnish-cache.org> Message-ID: <055.695ae77231c3498f9f69e8f9e78e3f2b@varnish-cache.org> #1130: varnishncsa -d makes it exit(0) after processing old entries -------------------------+--------------------- Reporter: bz | Owner: martin Type: defect | Status: new Priority: normal | Milestone: Component: varnishncsa | Version: 3.0.2 Severity: normal | Resolution: Keywords: | -------------------------+--------------------- Comment (by bz): Private notes to not forget things mentioned: - split buffers (multiple segments). Could dynamically re-adjust. - API changes + allow "blocking" varnishd if readers can't keep up? - multiple knobs: + for dump and exit, and + dump and continue (after-the-facts debugging vs. startup). Whatever will go into the new varnish logging API changes etc. for 4 as discussed at VDD13Q1. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 4 20:21:49 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 04 Feb 2013 20:21:49 -0000 Subject: [Varnish] #1247: yum installation error "[Errno -1] Header is not complete." In-Reply-To: <044.e3db3b22021d9bf26d4bc79f8b887423@varnish-cache.org> References: <044.e3db3b22021d9bf26d4bc79f8b887423@varnish-cache.org> Message-ID: <059.16a029b0d01410d8629233bae6d17169@varnish-cache.org> #1247: yum installation error "[Errno -1] Header is not complete." --------------------+--------------------- Reporter: Damien | Owner: tfheen Type: defect | Status: new Priority: high | Milestone: Component: build | Version: trunk Severity: major | Resolution: Keywords: | --------------------+--------------------- Comment (by Saud): No I just try by (yum). What do you mean by information about my IP? which information you need? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Feb 5 09:02:57 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 05 Feb 2013 09:02:57 -0000 Subject: [Varnish] #1260: Varnishd restart unknown error Child (7727) not responding to CLI, killing it. Message-ID: <046.a8abfdc75ce2620288d10f750724d478@varnish-cache.org> #1260: Varnishd restart unknown error Child (7727) not responding to CLI, killing it. -----------------------------------------------+-------------------- Reporter: hieubkav | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: trunk | Severity: normal Keywords: not responding to CLI, killing it | -----------------------------------------------+-------------------- We are using an Varnish Instant for Caching Video Streaming. Varnish 3.0.3 Default settting compiled from source, Centos 6.3 X64 , Kernel 2.6.32-279.19.1.el6.x86_64 #1 SMP Varnishd process is sometimes restarted with some error in syslog Feb 1 21:52:20 server10 varnishd[4195]: Child (7727) not responding to CLI, killing it. Feb 1 21:52:24 server10 varnishd[4195]: Child (7727) not responding to CLI, killing it. Feb 1 21:52:24 server10 varnishd[4195]: Child (7727) not responding to CLI, killing it. I attached the log files Please help me check what wrong in my server! -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Feb 5 09:49:01 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 05 Feb 2013 09:49:01 -0000 Subject: [Varnish] #1247: yum installation error "[Errno -1] Header is not complete." In-Reply-To: <044.e3db3b22021d9bf26d4bc79f8b887423@varnish-cache.org> References: <044.e3db3b22021d9bf26d4bc79f8b887423@varnish-cache.org> Message-ID: <059.48e40544c6a05a4bdccefe74f8fd3620@varnish-cache.org> #1247: yum installation error "[Errno -1] Header is not complete." --------------------+--------------------- Reporter: Damien | Owner: tfheen Type: defect | Status: new Priority: high | Milestone: Component: build | Version: trunk Severity: major | Resolution: Keywords: | --------------------+--------------------- Comment (by lkarsten): One of the things that needs to be ruled out is if this is a network issue. Downloading it with another client, and trying to install it manually with rpm will tell us this. Please also provide a traceroute towards repo.varnish-cache.org with a timestamp (run /bin/date) , so we can try to correlate your requests with our logs. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Feb 5 12:03:56 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 05 Feb 2013 12:03:56 -0000 Subject: [Varnish] #1261: Free'd waitinglist structs don't decrement the n_waitinglist counter Message-ID: <044.30867011781ba85c1e479ed53caf3d07@varnish-cache.org> #1261: Free'd waitinglist structs don't decrement the n_waitinglist counter ----------------------+------------------- Reporter: martin | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Keywords: ----------------------+------------------- The n_waitinglist counter isn't decremented when waitinglists are free'd. See attached test case. -Martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Feb 5 12:18:38 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 05 Feb 2013 12:18:38 -0000 Subject: [Varnish] #1261: Free'd waitinglist structs don't decrement the n_waitinglist counter In-Reply-To: <044.30867011781ba85c1e479ed53caf3d07@varnish-cache.org> References: <044.30867011781ba85c1e479ed53caf3d07@varnish-cache.org> Message-ID: <059.01affbf1e093d96d9f9610b7311eae24@varnish-cache.org> #1261: Free'd waitinglist structs don't decrement the n_waitinglist counter ----------------------+-------------------- Reporter: martin | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Description changed by martin: Old description: > The n_waitinglist counter isn't decremented when waitinglists are free'd. > > See attached test case. > > -Martin New description: The n_waitinglist counter isn't decremented when waitinglists are free'd. See attached test case. Note: This was fixed in master, so ticket is against 3.0 only. -Martin -- -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Feb 5 12:26:32 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 05 Feb 2013 12:26:32 -0000 Subject: [Varnish] #1261: Free'd waitinglist structs don't decrement the n_waitinglist counter In-Reply-To: <044.30867011781ba85c1e479ed53caf3d07@varnish-cache.org> References: <044.30867011781ba85c1e479ed53caf3d07@varnish-cache.org> Message-ID: <059.59cb7af1e79b47c4bc5338bbd12fdd8a@varnish-cache.org> #1261: Free'd waitinglist structs don't decrement the n_waitinglist counter ----------------------+--------------------- Reporter: martin | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 3.0.3 Severity: normal | Resolution: fixed Keywords: | ----------------------+--------------------- Changes (by martin): * status: new => closed * resolution: => fixed Comment: Fixed by 6990271f0b6aadb0c51d776a504294d9134b4238 Closing Martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Feb 6 13:40:44 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 06 Feb 2013 13:40:44 -0000 Subject: [Varnish] #1247: yum installation error "[Errno -1] Header is not complete." In-Reply-To: <044.e3db3b22021d9bf26d4bc79f8b887423@varnish-cache.org> References: <044.e3db3b22021d9bf26d4bc79f8b887423@varnish-cache.org> Message-ID: <059.20aa6c3373082c08bc45e151dde09be8@varnish-cache.org> #1247: yum installation error "[Errno -1] Header is not complete." --------------------+--------------------- Reporter: Damien | Owner: tfheen Type: defect | Status: new Priority: high | Milestone: Component: build | Version: trunk Severity: major | Resolution: Keywords: | --------------------+--------------------- Comment (by Damien): Bonjour, Mon ip de sortie est 90.85 .8.1 I also, try : #rpm --nosignature -i varnish-3.0.3-1.el5.centos.x86_64.rpm error: Failed dependencies: libvarnishapi.so.1()(64bit) is needed by varnish-3.0.3-1.el5.centos.x86_64 libvarnishapi.so.1(LIBVARNISHAPI_1.0)(64bit) is needed by varnish-3.0.3-1.el5.centos.x86_64 varnish-libs = 3.0.3-1.el5.centos is needed by varnish-3.0.3-1.el5.centos.x86_64 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Feb 7 09:38:42 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 07 Feb 2013 09:38:42 -0000 Subject: [Varnish] #1262: raw values are not updating when using varnishstat -1, while varnishstat continues to work Message-ID: <042.69ee90ee822d61989104b3ac3fdfc0ed@varnish-cache.org> #1262: raw values are not updating when using varnishstat -1, while varnishstat continues to work --------------------+------------------- Reporter: yves | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: 3.0.3 Severity: normal | Keywords: --------------------+------------------- i start by saying that this is hard to reproduce. but here are the description. varnishd was running and was built from src, 3.0.3 tag with the following command, varnishd -a :6080 -T :6081 -S myownsecretfile -f myown.vcl now varnishtat was running in a terminal overnight and that continued to provide updated numbers, while running varnishstat -1 did not yield any updated numbers the day after. double checking against the uptime value confirmed that varnishstat -1 was unable to report any increments of the uptime. a restart of varnishd helped. note that only 1 varnishd command was issued and no other varnishd command was called. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 11 11:34:01 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Feb 2013 11:34:01 -0000 Subject: [Varnish] #1260: Varnishd restart unknown error Child (7727) not responding to CLI, killing it. In-Reply-To: <046.a8abfdc75ce2620288d10f750724d478@varnish-cache.org> References: <046.a8abfdc75ce2620288d10f750724d478@varnish-cache.org> Message-ID: <061.c78a789ecaed8265c42b67ae1d2a72ae@varnish-cache.org> #1260: Varnishd restart unknown error Child (7727) not responding to CLI, killing it. -----------------------------------------------+------------------------- Reporter: hieubkav | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: worksforme Keywords: not responding to CLI, killing it | -----------------------------------------------+------------------------- Changes (by martin): * status: new => closed * resolution: => worksforme Comment: Hi, It looks like you are hitting a race condition that is present in current Varnish with regard to the persistent storage. There has been improbevements made to the persistent storage backend that is not yet part of main Varnish, but lives in another tree. I suggest you try to use the -plus Varnish until the next major release, where this issue has been fixed. You can find RPMs at http://jenkins.varnish-software.com/job/varnish-3.0.3 -plus-rpm-el6-x86_64/ Regards, Martin Blix Grydeland -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 11 11:49:29 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Feb 2013 11:49:29 -0000 Subject: [Varnish] #1124: Document Cache-Control private/no-cache behaviour In-Reply-To: <046.efd3b140d66579698a8653ee733c7d45@varnish-cache.org> References: <046.efd3b140d66579698a8653ee733c7d45@varnish-cache.org> Message-ID: <061.22a3a339760874a7dcee5a1d6eca9678@varnish-cache.org> #1124: Document Cache-Control private/no-cache behaviour ---------------------------+--------------------- Reporter: timbunce | Owner: slink Type: documentation | Status: closed Priority: normal | Milestone: Component: documentation | Version: 3.0.2 Severity: normal | Resolution: fixed Keywords: | ---------------------------+--------------------- Changes (by tfheen): * status: new => closed * resolution: => fixed Comment: Fixed in 81006eafd6 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 11 11:51:43 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Feb 2013 11:51:43 -0000 Subject: [Varnish] #1257: Varnish restarting it self, large cache. In-Reply-To: <051.4eb1f47d3c10c74deb792ffa3ee19c81@varnish-cache.org> References: <051.4eb1f47d3c10c74deb792ffa3ee19c81@varnish-cache.org> Message-ID: <066.4fbab324233900e42f4f1728dced672c@varnish-cache.org> #1257: Varnish restarting it self, large cache. ---------------------------+-------------------- Reporter: anders-bazoom | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: 3.0.3 Severity: major | Resolution: Keywords: | ---------------------------+-------------------- Comment (by lkarsten): Thanks for reporting this. We need some more information. Can you please supply the VCL and startup parameters used? Also, you were running with identical setup without problems when using malloc before? This being a vm, what kind of hypervisor is it and what kind of storage system is underneath? Are you running Varnish built from source or from packages? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 11 12:43:33 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Feb 2013 12:43:33 -0000 Subject: [Varnish] #1259: Backend naming bug In-Reply-To: <041.62bb8cd4d5352e5c2ad3ec33c21be152@varnish-cache.org> References: <041.62bb8cd4d5352e5c2ad3ec33c21be152@varnish-cache.org> Message-ID: <056.5dd17d618ea5fca40193cbeefdad2a1b@varnish-cache.org> #1259: Backend naming bug --------------------+-------------------- Reporter: urg | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+-------------------- Comment (by Poul-Henning Kamp ): In [45af9764189ec55f0626a44ff64df7bef5d87d41]: {{{ #!CommitTicketReference repository="" revision="45af9764189ec55f0626a44ff64df7bef5d87d41" Discontinue words as fixed tokens ('if', 'else' etc) and use ID's instead. Fixes #1259 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 11 12:43:34 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Feb 2013 12:43:34 -0000 Subject: [Varnish] #1259: Backend naming bug In-Reply-To: <041.62bb8cd4d5352e5c2ad3ec33c21be152@varnish-cache.org> References: <041.62bb8cd4d5352e5c2ad3ec33c21be152@varnish-cache.org> Message-ID: <056.371ca6013c45e0e564ddde92b6b52fa2@varnish-cache.org> #1259: Backend naming bug --------------------+--------------------- Reporter: urg | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+--------------------- Changes (by Poul-Henning Kamp ): * status: new => closed * resolution: => fixed Comment: (In [45af9764189ec55f0626a44ff64df7bef5d87d41]) Discontinue words as fixed tokens ('if', 'else' etc) and use ID's instead. Fixes #1259 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 11 13:11:55 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 11 Feb 2013 13:11:55 -0000 Subject: [Varnish] #1257: Varnish restarting it self, large cache. In-Reply-To: <051.4eb1f47d3c10c74deb792ffa3ee19c81@varnish-cache.org> References: <051.4eb1f47d3c10c74deb792ffa3ee19c81@varnish-cache.org> Message-ID: <066.c7a7cc6b3097e5208a6066dbfd905ca3@varnish-cache.org> #1257: Varnish restarting it self, large cache. ---------------------------+-------------------- Reporter: anders-bazoom | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: 3.0.3 Severity: major | Resolution: Keywords: | ---------------------------+-------------------- Comment (by anders-bazoom): Here's the startup options {{{ DAEMON_OPTS="-a :80 \ -T localhost:6082 \ -f /etc/varnish/default.vcl \ -S /etc/varnish/secret \ -s file,/var/lib/varnish/varnish_storage.bin,650G \ -p nuke_limit=3000" }}} And here's the default.vcl {{{ backend bil { .host = "billeder2.bilgalleri.dk"; .port = "80"; .connect_timeout = 5s; } sub vcl_recv { if(req.http.host == "bilbilleder.invio.dk" || req.http.host == "bilbilleder2.invio.dk" || req.http.host == "bil.webgallerier.dk" || req.http.host == "bil2.webgallerier.dk"){ set req.backend = bil; set req.http.host = "billeder2.bilgalleri.dk"; } } sub vcl_fetch { if(beresp.status == 404){ set beresp.ttl = 0s; } } }}} The same VM is now running with malloc,10G - and has been running stable since I created this ticket. The VM has 2x1TB in Raid1, filesystem is ext4. And the hypervisor im not sure about, I've seen hints at it being Parallels, but on the providers site there is mention of VMWare. So I've sent them a mail - and will report back here when I have the answer. I installed varnish using the varnish package repository. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Feb 12 15:14:09 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 12 Feb 2013 15:14:09 -0000 Subject: [Varnish] #1263: Varnish Crash Message-ID: <043.4fecdbacf5db6c2385e7c0167e5aff67@varnish-cache.org> #1263: Varnish Crash -------------------+---------------------- Reporter: comur | Type: defect Status: new | Priority: high Milestone: | Component: varnishd Version: 3.0.2 | Severity: major Keywords: crash | -------------------+---------------------- Hello, We have a crash when we try to do a return(restart) after a Purge (see attached vcl file). It happened during our varnish formation with Zenika (Dridi Boukelmoune). The process crashes at line 81 return(restart); Dridi will add the test file. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Feb 12 15:29:46 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 12 Feb 2013 15:29:46 -0000 Subject: [Varnish] #1263: Varnish Crash In-Reply-To: <043.4fecdbacf5db6c2385e7c0167e5aff67@varnish-cache.org> References: <043.4fecdbacf5db6c2385e7c0167e5aff67@varnish-cache.org> Message-ID: <058.951c3c3a40979eb06362d5835d95167c@varnish-cache.org> #1263: Varnish Crash ----------------------+-------------------- Reporter: comur | Owner: Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 3.0.2 Severity: major | Resolution: Keywords: crash | ----------------------+-------------------- Comment (by Dridi): We are using Varnish 3.0.2 on an Ubuntu 12.10 server for the training. It is packaged as ''varnish-3.0.2-2''. {{{ uname -a Linux formateur 3.5.0-22-generic #34-Ubuntu SMP Thu Jan 8 21:47:00 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux }}} Test case attached to the issue. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Feb 12 23:31:24 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 12 Feb 2013 23:31:24 -0000 Subject: [Varnish] #1263: Varnish Crash In-Reply-To: <043.4fecdbacf5db6c2385e7c0167e5aff67@varnish-cache.org> References: <043.4fecdbacf5db6c2385e7c0167e5aff67@varnish-cache.org> Message-ID: <058.78c21a7e8707de58df3cfbee4e7e92ba@varnish-cache.org> #1263: Varnish Crash ----------------------+-------------------- Reporter: comur | Owner: Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 3.0.2 Severity: major | Resolution: Keywords: crash | ----------------------+-------------------- Comment (by Dridi): Same crash on my Fedora 18 VM (32bits though). {{{ $ uname -a Linux localhost.localdomain 3.7.6-201.fc18.i686 #1 SMP Mon Feb 4 16:15:01 UTC 2013 i686 i686 i386 GNU/Linux $ rpm -qa 'varnish*' varnish-libs-3.0.3-3.fc18.i686 varnish-3.0.3-3.fc18.i686 varnish-docs-3.0.3-3.fc18.i686 varnish-libs-devel-3.0.3-3.fc18.i686 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Feb 13 10:00:25 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 13 Feb 2013 10:00:25 -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.14cbb510333a24e9dbdf38d7bd798c06@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 dstuart): Hi, Is there any update on this. Regards, Dave -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Feb 13 15:24:48 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 13 Feb 2013 15:24:48 -0000 Subject: [Varnish] #1264: [PATCH] Add varnishlog -t for plain text logging Message-ID: <046.bfc5e2cd040f2bbf6ceddc00f85cfcd3@varnish-cache.org> #1264: [PATCH] Add varnishlog -t for plain text logging ----------------------+------------------------- Reporter: lkundrak | Type: enhancement Status: new | Priority: normal Milestone: | Component: varnishlog Version: trunk | Severity: normal Keywords: | ----------------------+------------------------- See attached patch & documentation change for explanation. Thank you! -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Feb 15 13:00:21 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 15 Feb 2013 13:00:21 -0000 Subject: [Varnish] #1265: Randomly getting 503 errors while using Varnish with Apache Message-ID: <053.ec20d9f905bc8ee3198ace78366822af@varnish-cache.org> #1265: Randomly getting 503 errors while using Varnish with Apache -----------------------------+---------------------- Reporter: abhishekjain203 | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: 3.0.3 | Severity: normal Keywords: | -----------------------------+---------------------- Hi, We are using Pound, Varnish with Apache on our server and we occasionally get 503 errors on some of the pages. Below is the Varnish log: 201 SessionOpen c 66.87.117.80 39422 208.113.240.79:80 201 ReqStart c 66.87.117.80 39422 1459793886 201 RxRequest c GET 201 RxURL c /templates/ja_elastica/css/typo.css 201 RxProtocol c HTTP/1.1 201 RxHeader c Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8, text/css, image/*, application/javascript, application/vbscript, */* 201 RxHeader c x-wap-profile: http://device.sprintpcs.com/Samsung/SPH-L710/LJ7.rdf 201 RxHeader c User-Agent: Mozilla/5.0 (Linux; U; Android 4.1.1; en- us; SPH-L710 Build/JRO03L) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30 201 RxHeader c Accept-Encoding: gzip,deflate 201 RxHeader c Accept-Language: en-US 201 RxHeader c Accept-Charset: utf-8, iso-8859-1, utf-16, *;q=0.7 201 RxHeader c Cookie: 2fda71d172c9d46b6d4c8e631064f5e0=xom9uHeaplOMwN3EF5N7Z3; ja_elastica_tpl=ja_elastica; __utma=112986586.416097245.1360781530.1360781530.1360826480.2; __utmc=112986586; __utmz=112986586.1360781530.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); _ 201 RxHeader c Host: www.organicfacts.net 201 RxHeader c Cache-Control: max-age=43200 201 RxHeader c Connection: keep-alive 201 VCL_call c recv pass 201 VCL_call c hash 201 Hash c /templates/ja_elastica/css/typo.css 201 Hash c www.organicfacts.net 201 VCL_return c hash 201 VCL_call c pass pass 201 Backend c 203 default default 201 TTL c 1459793886 RFC -1 -1 -1 1360926637 0 1360926637 0 0 201 VCL_call c fetch 201 TTL c 1459793886 VCL 120 -1 -1 1360926637 -0 201 VCL_return c hit_for_pass 201 ObjProtocol c HTTP/1.1 201 ObjResponse c Service Temporarily Unavailable 201 ObjHeader c Date: Fri, 15 Feb 2013 11:10:37 GMT 201 ObjHeader c Server: Apache 201 ObjHeader c Vary: Accept-Encoding 201 ObjHeader c Content-Encoding: gzip 201 ObjHeader c Content-Length: 236 201 ObjHeader c Content-Type: text/html; charset=iso-8859-1 201 Gzip c u F - 236 323 80 80 1823 201 VCL_call c deliver deliver 201 TxProtocol c HTTP/1.1 201 TxStatus c 503 201 TxResponse c Service Temporarily Unavailable 201 TxHeader c Server: Apache 201 TxHeader c Vary: Accept-Encoding 201 TxHeader c Content-Encoding: gzip 201 TxHeader c Content-Type: text/html; charset=iso-8859-1 201 TxHeader c Content-Length: 236 201 TxHeader c Accept-Ranges: bytes 201 TxHeader c Date: Fri, 15 Feb 2013 11:10:37 GMT 201 TxHeader c X-Varnish: 1459793886 201 TxHeader c Age: 0 201 TxHeader c Via: 1.1 varnish 201 TxHeader c Connection: keep-alive 201 Length c 236 201 ReqEnd c 1459793886 1360926637.034808159 1360926637.036862135 0.000040293 0.002015114 0.000038862 Below are the parameters that we are passing while running varnish: varnishd -f /etc/varnish/default.vcl -s malloc,2.5G -T 127.0.0.1:2000 -a 208.113.241.84:80,208.113.240.79:80,127.0.0.3:80 -p thread_pool_max=1500 -p thread_pools=4 -p listen_depth=2048 -p lru_interval=1800 -h classic,169313 -p first_byte_timeout=600 -p sess_timeout=600 -p sess_workspace=131072 -p connect_timeout=600 -p max_restarts=6 -p vcl_trace=on And this is our vcl config: backend default { .host = "127.0.0.2"; .port = "80"; .connect_timeout = 600s; .first_byte_timeout = 600s; .between_bytes_timeout = 600s; } backend mydomain{ .host = "127.0.0.4"; .port = "80"; .connect_timeout = 600s; .first_byte_timeout = 600s; .between_bytes_timeout = 600s; } sub vcl_recv { # choose a backend depending on domain if (req.http.host ~ "www.villcart.com") { set req.backend = mydomain; }else{ set req.backend = default; } } As there is no error in both the varnish log and apache log, we are not able to figure out where the problem is. Could you please help us out? Regards, Abhishek -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Feb 15 13:36:12 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 15 Feb 2013 13:36:12 -0000 Subject: [Varnish] #1266: Truncated bans get a length of 0 Message-ID: <044.7874955a03b5bb8de98aaa5aa09dfcbd@varnish-cache.org> #1266: Truncated bans get a length of 0 ----------------------+------------------- Reporter: martin | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+------------------- Truncated bans get a length of 0 instead of the length of the header. Applies only to trunk. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Feb 15 14:15:14 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 15 Feb 2013 14:15:14 -0000 Subject: [Varnish] #1266: Truncated bans get a length of 0 In-Reply-To: <044.7874955a03b5bb8de98aaa5aa09dfcbd@varnish-cache.org> References: <044.7874955a03b5bb8de98aaa5aa09dfcbd@varnish-cache.org> Message-ID: <059.5796ff9f38365427287e61a65df348b5@varnish-cache.org> #1266: Truncated bans get a length of 0 ----------------------+--------------------- Reporter: martin | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+--------------------- Changes (by martin): * status: new => closed * resolution: => fixed Comment: Fixed by bf36a1c58be5b8fe651e1ec6cf586feb6a671fb2 Closing Martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Feb 15 14:16:06 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 15 Feb 2013 14:16:06 -0000 Subject: [Varnish] #1252: varnish retries fetch from unresponsive backend indefinitely, leading to FD exhaustion In-Reply-To: <046.de7f99d95026561fe7f4357f355a3091@varnish-cache.org> References: <046.de7f99d95026561fe7f4357f355a3091@varnish-cache.org> Message-ID: <061.9d71c9b00f041fd91c5c69eb21554272@varnish-cache.org> #1252: varnish retries fetch from unresponsive backend indefinitely, leading to FD exhaustion ----------------------+--------------------- Reporter: askalski | Owner: martin Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+--------------------- Changes (by martin): * status: new => closed * resolution: => fixed Comment: Fixed by f6c4379a856987be89d4eb0b5ffe4fb0ba9cd242 Closing Martin -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Feb 15 15:04:49 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 15 Feb 2013 15:04:49 -0000 Subject: [Varnish] #1267: Setup stack side through sysconfig varnish configuration Message-ID: <054.c672f506174fbd32b2a1f8b9713528f1@varnish-cache.org> #1267: Setup stack side through sysconfig varnish configuration ------------------------------+------------------------- Reporter: andrii.grytsenko | Type: enhancement Status: new | Priority: normal Milestone: Varnish 3.0 dev | Component: packaging Version: 3.0.3 | Severity: normal Keywords: | ------------------------------+------------------------- Since more and more people are hitting this issue: https://www.varnish-cache.org/docs/trunk/installation/platformnotes.html and also some are require stack size adjustment. It would be really nice of you if you add the possibility to setup stack side through sysconfig varnish configuration. Please add to varnish init.d script: {{{ ulimit -s ${STACK:-10240} }}} and to sysconfig: {{{ STACK=10240 }}} Thank you! -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 18 13:43:13 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 18 Feb 2013 13:43:13 -0000 Subject: [Varnish] #1167: 3.0.3rc1 Compile Error on Solaris 10 with gcc 4.3.3 In-Reply-To: <044.677261b72c12472e07a7cff6c933fe66@varnish-cache.org> References: <044.677261b72c12472e07a7cff6c933fe66@varnish-cache.org> Message-ID: <059.1e6c55729d5bb87e9036e102655157d7@varnish-cache.org> #1167: 3.0.3rc1 Compile Error on Solaris 10 with gcc 4.3.3 --------------------------+--------------------- Reporter: Dommas | Owner: tfheen Type: defect | Status: new Priority: normal | Milestone: Component: port:solaris | Version: 3.0.3 Severity: normal | Resolution: Keywords: | --------------------------+--------------------- Changes (by lkarsten): * owner: thfeen => tfheen -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Feb 19 15:30:27 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 19 Feb 2013 15:30:27 -0000 Subject: [Varnish] #1268: 'shortlived' does not consider grace/keep Message-ID: <043.b6f261f0eca41d964db078b4b18d6e88@varnish-cache.org> #1268: 'shortlived' does not consider grace/keep --------------------+------------------- Reporter: daghf | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------- Grace/keep is not taken into account when considering if an object should be put in transient storage. See attached test case. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Feb 20 10:07:47 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 20 Feb 2013 10:07:47 -0000 Subject: [Varnish] #1262: raw values are not updating when using varnishstat -1, while varnishstat continues to work In-Reply-To: <042.69ee90ee822d61989104b3ac3fdfc0ed@varnish-cache.org> References: <042.69ee90ee822d61989104b3ac3fdfc0ed@varnish-cache.org> Message-ID: <057.d22934de7b4416c1a67eefc658666529@varnish-cache.org> #1262: raw values are not updating when using varnishstat -1, while varnishstat continues to work --------------------+-------------------- Reporter: yves | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: 3.0.3 Severity: normal | Resolution: Keywords: | --------------------+-------------------- Comment (by tfheen): My theory is that something like the following happened: - Varnish is running - Another varnishd with the same working directory and listening port is attempted to start. This leads to it unlinking the shm file, then failing the startup (since the ports are already in use) - varnishstat is already running and so has the shmfile open. Ditto for the running varnishd. - varnishstat -1 opens the newly created shmfile which there's no Varnish touching, hence not updating. This will at least cause the behaviour seen, but there might of course be other bugs in there too. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Feb 20 10:18:50 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 20 Feb 2013 10:18:50 -0000 Subject: [Varnish] #1258: Failure to build due to aclocal macros In-Reply-To: <043.6ea237116f12d12a49b1dd4812cb0105@varnish-cache.org> References: <043.6ea237116f12d12a49b1dd4812cb0105@varnish-cache.org> Message-ID: <058.ebdd4e5692554d434292fd376469e392@varnish-cache.org> #1258: Failure to build due to aclocal macros --------------------+-------------------- Reporter: richo | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+-------------------- Comment (by Tollef Fog Heen ): In [3be4a80b7893807953ce067159d3bfab059f3bd1]: {{{ #!CommitTicketReference repository="" revision="3be4a80b7893807953ce067159d3bfab059f3bd1" Change AM_CONFIG_HEADER to AC_CONFIG_HEADERS Fixes #1258 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Feb 20 10:18:52 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 20 Feb 2013 10:18:52 -0000 Subject: [Varnish] #1258: Failure to build due to aclocal macros In-Reply-To: <043.6ea237116f12d12a49b1dd4812cb0105@varnish-cache.org> References: <043.6ea237116f12d12a49b1dd4812cb0105@varnish-cache.org> Message-ID: <058.c8e8f7aaf082c8165d20b8616b74eefb@varnish-cache.org> #1258: Failure to build due to aclocal macros --------------------+--------------------- Reporter: richo | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+--------------------- Changes (by Tollef Fog Heen ): * status: new => closed * resolution: => fixed Comment: (In [3be4a80b7893807953ce067159d3bfab059f3bd1]) Change AM_CONFIG_HEADER to AC_CONFIG_HEADERS Fixes #1258 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Feb 22 12:01:14 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 22 Feb 2013 12:01:14 -0000 Subject: [Varnish] #1222: std.collect() doesn't work on resp.http (e.g. in vcl_deliver) In-Reply-To: <042.c9461de71037fad1dbccd1350fff076f@varnish-cache.org> References: <042.c9461de71037fad1dbccd1350fff076f@varnish-cache.org> Message-ID: <057.04499e8f72ba1bd0614151d62e92d7e9@varnish-cache.org> #1222: std.collect() doesn't work on resp.http (e.g. in vcl_deliver) --------------------+-------------------- Reporter: mark | Owner: daghf Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: 3.0.3 Severity: normal | Resolution: Keywords: | --------------------+-------------------- Comment (by Tollef Fog Heen ): In [6a9302c986762616288b612f261aa2d066bdc57c]: {{{ #!CommitTicketReference repository="" revision="6a9302c986762616288b612f261aa2d066bdc57c" Make std.collect() also work for resp.http and bereq.http. Fixes: #1222 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Feb 22 12:01:19 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 22 Feb 2013 12:01:19 -0000 Subject: [Varnish] #1222: std.collect() doesn't work on resp.http (e.g. in vcl_deliver) In-Reply-To: <042.c9461de71037fad1dbccd1350fff076f@varnish-cache.org> References: <042.c9461de71037fad1dbccd1350fff076f@varnish-cache.org> Message-ID: <057.e86e21c0d10e3ce168d644eb05522fd5@varnish-cache.org> #1222: std.collect() doesn't work on resp.http (e.g. in vcl_deliver) --------------------+--------------------- Reporter: mark | Owner: daghf Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: 3.0.3 Severity: normal | Resolution: fixed Keywords: | --------------------+--------------------- Changes (by Tollef Fog Heen ): * status: new => closed * resolution: => fixed Comment: (In [6a9302c986762616288b612f261aa2d066bdc57c]) Make std.collect() also work for resp.http and bereq.http. Fixes: #1222 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Sun Feb 24 11:14:14 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Sun, 24 Feb 2013 11:14:14 -0000 Subject: [Varnish] #1269: varnishncsa does not show pipe'ed requests Message-ID: <047.74c03b61e1ee686de1e8904dfd87ef9a@varnish-cache.org> #1269: varnishncsa does not show pipe'ed requests -----------------------+------------------------- Reporter: prymitive | Type: defect Status: new | Priority: low Milestone: | Component: varnishncsa Version: 3.0.3 | Severity: minor Keywords: | -----------------------+------------------------- I'm using varnishncsa (3.0.3) for creating hourly traffic stats for each of my app behind it and I've noticed that logs are missing all pipe'ed requests. Man page doesn't have any information about this, it only says: {{{ Varnish:hitmiss Whether the request was a cache hit or miss. Pipe and pass are considered misses. Varnish:handling How the request was handled, whether it was a cache hit, miss, pass, pipe or error. }}} So above docs are little confusing. I've found that those requests are simply ignored due to https://www .varnish-cache.org/trac/browser/bin/varnishncsa/varnishncsa.c#L524 Would anything break if we would allow to log those requests event without the status code? I think that adding new switch to varnishncsa that would enable such logs and information that resulting logs will miss some information would be enough. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Mon Feb 25 09:54:03 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Mon, 25 Feb 2013 09:54:03 -0000 Subject: [Varnish] #1257: Varnish restarting it self, large cache. In-Reply-To: <051.4eb1f47d3c10c74deb792ffa3ee19c81@varnish-cache.org> References: <051.4eb1f47d3c10c74deb792ffa3ee19c81@varnish-cache.org> Message-ID: <066.3fe4e566169683fde01a4c1a43ceac00@varnish-cache.org> #1257: Varnish restarting it self, large cache. ---------------------------+-------------------- Reporter: anders-bazoom | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: 3.0.3 Severity: major | Resolution: Keywords: | ---------------------------+-------------------- Comment (by anders-bazoom): Hi again, sorry for the late followup. I've gotten a response from the host. They are using Parallels Bare Metal [http://www.parallels.com/products/server/baremetal/sp/] -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Feb 26 12:06:54 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 26 Feb 2013 12:06:54 -0000 Subject: [Varnish] #1270: Any way to detect/distinguish ESI requests? Message-ID: <046.c9b37f3467e6d6c2b4aa0b0321021a52@varnish-cache.org> #1270: Any way to detect/distinguish ESI requests? ----------------------+------------------------- Reporter: whocares | Type: enhancement Status: new | Priority: normal Milestone: | Component: varnishd Version: 3.0.3 | Severity: normal Keywords: | ----------------------+------------------------- While playing with ESI I found that there seems to be no way to make Varnish distinguish between internal ESI and normal (= coming from a user) requests in vcl_recv(). What I'm trying to do is to add a special header and probably other stuff in a way like this: {{{ if (req.isesi) { set req.http.X-Esi = ""; } }}} to any ESI requests so that the snippet to be included can actually make sure it was called through ESI processing and not directly by a user. I tried looking in the docs and also tried modifying the req.http. Headers for the ESI enabled pages in vcl_recv() as well as vcl_fetch() in the hope that the ESI requests would copy the headers from the original request but no luck there. Maybe I've done something wrong there but in any case I'd think that being able to detect ESI requests directly would be a much cleaner approach. -Stefan -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Feb 27 00:58:12 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 27 Feb 2013 00:58:12 -0000 Subject: [Varnish] #1271: Seemingly valid backend identifier causes VCL compilation failure Message-ID: <047.3982ac01e45fc54535f9749a5675b32a@varnish-cache.org> #1271: Seemingly valid backend identifier causes VCL compilation failure -----------------------+---------------------- Reporter: aaronlevy | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: 3.0.2 | Severity: normal Keywords: | -----------------------+---------------------- Setting a backend identifier to "storage[0-9]+" causes the VCL compilation to fail with unhelpful message. Example: {{{ backend storage1 { .host = "127.0.0.1"; .port = "8080" } }}} Results in: {{{ Assert error in vcc_Stv_Wildcard(), vcc_storage.c line 115: Condition((t->e - t->b) > strlen(PFX)) not true. errno = 9 (Bad file descriptor) Running VCC-compiler failed, signal 6, core dumped VCL compilation failed }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Feb 27 01:04:35 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 27 Feb 2013 01:04:35 -0000 Subject: [Varnish] #1271: Seemingly valid backend identifier causes VCL compilation failure In-Reply-To: <047.3982ac01e45fc54535f9749a5675b32a@varnish-cache.org> References: <047.3982ac01e45fc54535f9749a5675b32a@varnish-cache.org> Message-ID: <062.ab617d1cbc509dc36082527c31364403@varnish-cache.org> #1271: Seemingly valid backend identifier causes VCL compilation failure -----------------------+-------------------- Reporter: aaronlevy | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.2 Severity: normal | Resolution: Keywords: | -----------------------+-------------------- Comment (by aaronlevy): Actually, anything that starts with "storage" will fail. So "storagefoo" no good either. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Feb 27 07:46:30 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 27 Feb 2013 07:46:30 -0000 Subject: [Varnish] #1271: Seemingly valid backend identifier causes VCL compilation failure In-Reply-To: <047.3982ac01e45fc54535f9749a5675b32a@varnish-cache.org> References: <047.3982ac01e45fc54535f9749a5675b32a@varnish-cache.org> Message-ID: <062.eafd4b3aadd1ad1c6c25bd68aeb74e57@varnish-cache.org> #1271: Seemingly valid backend identifier causes VCL compilation failure -----------------------+-------------------- Reporter: aaronlevy | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 3.0.2 Severity: normal | Resolution: Keywords: | -----------------------+-------------------- Comment (by daghf): This is #1164. Closing as duplicate. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Feb 27 07:46:39 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 27 Feb 2013 07:46:39 -0000 Subject: [Varnish] #1271: Seemingly valid backend identifier causes VCL compilation failure In-Reply-To: <047.3982ac01e45fc54535f9749a5675b32a@varnish-cache.org> References: <047.3982ac01e45fc54535f9749a5675b32a@varnish-cache.org> Message-ID: <062.efca8e4d5a60c55c230e883f636d944e@varnish-cache.org> #1271: Seemingly valid backend identifier causes VCL compilation failure -----------------------+------------------------ Reporter: aaronlevy | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 3.0.2 Severity: normal | Resolution: duplicate Keywords: | -----------------------+------------------------ Changes (by daghf): * status: new => closed * resolution: => duplicate -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Feb 27 09:59:25 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 27 Feb 2013 09:59:25 -0000 Subject: [Varnish] #1003: Fix libedit (libreadline) support for FreeBSD In-Reply-To: <044.97ea0cb79c8172ef6b88dc23843a837c@varnish-cache.org> References: <044.97ea0cb79c8172ef6b88dc23843a837c@varnish-cache.org> Message-ID: <059.926c665b7cb59f3502bb62f1604b2ae2@varnish-cache.org> #1003: Fix libedit (libreadline) support for FreeBSD -------------------------+----------------------- Reporter: anders | Owner: tfheen Type: enhancement | Status: reopened Priority: normal | Milestone: Component: build | Version: 3.0.1 Severity: normal | Resolution: Keywords: | -------------------------+----------------------- Comment (by tfheen): Can you see if this compiles correctly for you if you just uninstall the libedit port? It seems like that fixes it for me at least. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Feb 28 16:04:07 2013 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 28 Feb 2013 16:04:07 -0000 Subject: [Varnish] #1272: duplicate Content-Length headers with pass and stream Message-ID: <045.e87497923f5222571a8b67f55be7787e@varnish-cache.org> #1272: duplicate Content-Length headers with pass and stream -----------------------------------+---------------------- Reporter: ehocdet | Type: defect Status: new | Priority: normal Milestone: | Component: varnishd Version: 3.0.3 | Severity: normal Keywords: stream Content-Length | -----------------------------------+---------------------- In 3.0.3, i see a lot of duplicate Content-Length headers with this setup: sub vcl_recv { return (pass); } sub vcl_fetch { set beresp.do_stream = true; } RES_StreamStart() add the second -- Ticket URL: Varnish The Varnish HTTP Accelerator