From varnish-bugs at projects.linpro.no Tue Mar 6 14:34:23 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 06 Mar 2007 14:34:23 -0000 Subject: [Varnish] #89: Cannot compile varnish on debian Message-ID: <077.85189331aa07a18def21ac0f90c18130@projects.linpro.no> #89: Cannot compile varnish on debian --------------------+------------------------------------------------------- Reporter: naro | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------------------------------------------- I'm tryng to compile varnish 1.0.3 or current svn trunk on debian stable. After running ./autogen.sh && ./configure && make there are compilation errors: {{{ In file included from clock_gettime.c:40: ../../include/compat/clock_gettime.h:37: error: syntax error before numeric constant }}} It is possible to compile plain varnish 1.0.3 without running autogen.sh, but varnishd does not work. {{{ CLI start child pid 19461 Assert error in ev_now(), mgt_event.c line 85: Condition(clock_gettime(CLOCK_MONOTONIC, &ts) == 0) not true. errno = 22 (Invalid argument) Aborted }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Mar 7 10:55:53 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 07 Mar 2007 10:55:53 -0000 Subject: [Varnish] #56: varnish respond with HTTP/1.1 when resquest was HTTP/1.0 with pass In-Reply-To: <077.0fbe03a2b8e275a2ef448779e7d9f4a5@projects.linpro.no> References: <077.0fbe03a2b8e275a2ef448779e7d9f4a5@projects.linpro.no> Message-ID: <086.348cd6fac792be80d8867dadfa10f0b1@projects.linpro.no> #56: varnish respond with HTTP/1.1 when resquest was HTTP/1.0 with pass ----------------------+----------------------------------------------------- Reporter: ced | Owner: phk Type: defect | Status: closed Priority: high | Milestone: Component: varnishd | Version: trunk Severity: major | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: This problem should now be fixed in trunk with the new handling of "pass" mode requests. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Mar 8 09:30:44 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 08 Mar 2007 09:30:44 -0000 Subject: [Varnish] #90: Update VCL documentation Message-ID: <077.f1c792df761644bf9dcbbb6c2e1d501b@projects.linpro.no> #90: Update VCL documentation ---------------------------+------------------------------------------------ Reporter: des | Owner: des Type: documentation | Status: new Priority: high | Milestone: Component: documentation | Version: trunk Severity: normal | Keywords: ---------------------------+------------------------------------------------ The {{{vcl(7)}}} man page needs to be updated to reflect Poul-Henning's rewrite of the backend code path and document the new VCL functions ({{{vcl_pass()}}} and {{{vcl_pipe()}}}). It also needs a better explanation of the {{{errror}}}, {{{lookup}}}, {{{pass}}}, {{{pipe}}} etc. keywords. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Mar 8 19:54:12 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 08 Mar 2007 19:54:12 -0000 Subject: [Varnish] #89: Cannot compile varnish on debian In-Reply-To: <077.85189331aa07a18def21ac0f90c18130@projects.linpro.no> References: <077.85189331aa07a18def21ac0f90c18130@projects.linpro.no> Message-ID: <086.c824fe06c0ce8f2daef87d0733673352@projects.linpro.no> #89: Cannot compile varnish on debian --------------------+------------------------------------------------------- Reporter: naro | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+------------------------------------------------------- Comment (by complexero): I had the same problem on Debian Sarge. Here is what you need to do to fix it. Install automake-1.9 http://packages.debian.org/stable/devel/automake1.9 Then in autogen.sh, change all occurences of the following: aclocal -> aclocal-1.9 automake -> automake-1.9 Then try running autogen.sh to see if that fixes your problems. Then you should be able to run ./configure or dpkg-buildpackage successfully. -- Ticket URL: Varnish The Varnish HTTP Accelerator From bahner at debian.org Fri Mar 9 10:03:37 2007 From: bahner at debian.org (Lars Bahner) Date: Fri, 9 Mar 2007 11:03:37 +0100 Subject: [Varnish] #89: Cannot compile varnish on debian In-Reply-To: <086.c824fe06c0ce8f2daef87d0733673352@projects.linpro.no> References: <077.85189331aa07a18def21ac0f90c18130@projects.linpro.no> <086.c824fe06c0ce8f2daef87d0733673352@projects.linpro.no> Message-ID: <20070309100334.GA24133@zen.bahner.com> On Thu, Mar 08, 2007 at 07:54:12PM -0000, Varnish wrote: > #89: Cannot compile varnish on debian > --------------------+------------------------------------------------------- > Reporter: naro | Owner: des > Type: defect | Status: new > Priority: normal | Milestone: > Component: build | Version: trunk > Severity: normal | Resolution: > Keywords: | > --------------------+------------------------------------------------------- > Comment (by complexero): > > I had the same problem on Debian Sarge. Here is what you need to do to fix > it. Install automake-1.9 > http://packages.debian.org/stable/devel/automake1.9 > > Then in autogen.sh, change all occurences of the following: > aclocal -> aclocal-1.9 > automake -> automake-1.9 For the record the debian package itself *does* depend on automake1.9 Kindly, Lars Bahner From varnish-bugs at projects.linpro.no Thu Mar 15 03:30:40 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 15 Mar 2007 03:30:40 -0000 Subject: [Varnish] #91: Crash - missing error handling code in mgt_vcc.c In-Reply-To: <077.e4ea37290d35c5d08bb1c9129a106993@projects.linpro.no> References: <077.e4ea37290d35c5d08bb1c9129a106993@projects.linpro.no> Message-ID: <086.8c42cf908e1c1e734eca14c28784f92b@projects.linpro.no> #91: Crash - missing error handling code in mgt_vcc.c --------------------------+------------------------------------------------- Reporter: esrever_otua | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: Severity: normal | Resolution: Keywords: | --------------------------+------------------------------------------------- Comment (by esrever_otua): Just realised that this is a perfect dup of #80. Close it here and I'll put a note on #80 instead :) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Mar 15 03:31:43 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 15 Mar 2007 03:31:43 -0000 Subject: [Varnish] #80: Missing errorhandler causes crash In-Reply-To: <077.e97396144de555b7e05f93bb17097cd6@projects.linpro.no> References: <077.e97396144de555b7e05f93bb17097cd6@projects.linpro.no> Message-ID: <086.bceebae3dab8f6dbe00d7a7de286ce7a@projects.linpro.no> #80: Missing errorhandler causes crash --------------------+------------------------------------------------------- Reporter: xingli | Owner: des Type: defect | Status: assigned Priority: high | Milestone: Varnish 1.1 Component: build | Version: 1.0 Severity: major | Resolution: Keywords: | --------------------+------------------------------------------------------- Comment (by esrever_otua): Got this error on a host that didn't experience any block errors, see #91. Will try the patch and see how it goes :) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Mar 21 13:18:55 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 21 Mar 2007 13:18:55 -0000 Subject: [Varnish] #92: VCL-check for purge prevents caching Message-ID: <077.2939a8964d3fa3409d2de4574ce75003@projects.linpro.no> #92: VCL-check for purge prevents caching ----------------------+----------------------------------------------------- Reporter: stonor | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: Severity: normal | Keywords: ----------------------+----------------------------------------------------- I don't know if this is a bug or my lack of vcl knowledge, so here we go: I want this behavior: When somebody hits -F5 in a browser, varnish will purge the current page from the cache. Firefox puts this in its request header when you do that: Cache-Control: no-cache So I inserted this piece of vcl: -- sub vcl_hit { if(req.http.Cache-Control == "no-cache") { set obj.ttl = 0s; error 200 "Hey, we got a purge"; } } -- At first glance that kind of works. When somebody hits -F5 the page gets purged and I get my custom error message. However suddenly the page is not served from the cache _at all_. That is unless I just hit F5, _then_ I get a cached page. Hitting F5 sends this request header in Firefox: Cache-Control: max-age=0 I don't send any caching headers on the backend if that matters, just relying on the default Varnish fallback to 120 sec. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 30 17:05:21 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 30 Mar 2007 17:05:21 -0000 Subject: [Varnish] #93: management interface crashes varnishd, coredump with signal 6 Message-ID: <077.496ce83a51a215c7d5a917f0bf6fcc7a@projects.linpro.no> #93: management interface crashes varnishd, coredump with signal 6 ----------------------+----------------------------------------------------- Reporter: kang | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: Severity: normal | Keywords: ----------------------+----------------------------------------------------- I'm running a 32-bit varnishd, I start varnishd with following command: {{{ varnishd -a my-ip-addr:80 -f /usr/local/etc/test.vcl -s file,/usr/V,2g -T 127.0.0.1:81 }}} after varnishd started {{{ telnet 127.0.0.1 81 then press Ctrl+C }}} varnishd will crash with signal 6 {{{ kang# strings varnishd.core | tail -50 Ready CLI ready 9 (( Y (l Y (X (file /usr/V size 214, ocks Assert error in mgt_cli_callback(), mgt_cli.c line 322: Condition(i <= cp->nbuf) not true. errno = 0 (Unknown error: 0) (void*)0 )> t child pid 44959 (rolling(2)... Child starts managed to mmap 2147479552 bytes of 2147479552 Ready CLI ready ] ( ( ] ( ( ] ( Y (lS (lS varnishd }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator