From varnish-bugs at projects.linpro.no Wed Aug 1 08:22:18 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 01 Aug 2007 08:22:18 -0000 Subject: [Varnish] #129: POST request with pipe method not fully working in trunk In-Reply-To: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> References: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> Message-ID: <060.029d4c19070a56856f2ea726b6a2528f@projects.linpro.no> #129: POST request with pipe method not fully working in trunk ----------------------+----------------------------------------------------- Reporter: jpulz | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by teddy): Tcpdump attached to ticket. This contains the packets between varnish and backend from the start of the POST to the last response. Hopes this gets you started. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 2 09:39:48 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 02 Aug 2007 09:39:48 -0000 Subject: [Varnish] #135: default.vcl out of sync Message-ID: <052.c196e75db5c13b3f37ec0b3a55dd4ad7@projects.linpro.no> #135: default.vcl out of sync ---------------------------+------------------------------------------------ Reporter: anders | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: documentation | Version: 1.1 Severity: normal | Keywords: default.vcl ---------------------------+------------------------------------------------ The default.vcl installed as a part of Varnish 1.1, is out of sync with the actual default VCL in mgt_vcc.c. For example, default.vcl mentions using resp.http.Set-Cookie in vcl_fetch, but this is not valid: vcl.load run1 /usr/local/etc/varnish.vcl 106 190 Variable 'resp.http.Set-Cookie' not accessible in method 'vcl_fetch'. At: (/usr/local/etc/varnish.vcl Line 75 Pos 13) if (resp.http.Set-Cookie) { ------------####################--- In mgt_vcc.c, obj.http.Set-Cookie is used, which works. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 2 14:20:38 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 02 Aug 2007 14:20:38 -0000 Subject: [Varnish] #136: Setting vcl_trace to on in cli doesn't work Message-ID: <050.57043b1f9ca27fd83007e501737a32cf@projects.linpro.no> #136: Setting vcl_trace to on in cli doesn't work --------------------+------------------------------------------------------- Reporter: jesw | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------------------------------------------- You have to set vcl_trace during startup, setting it to "on" in the cli doesn't enables tracing anymore -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 2 16:45:30 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 02 Aug 2007 16:45:30 -0000 Subject: [Varnish] #137: regsub in vcl_hash fails Message-ID: <049.b7e5cd54775072421075abd03ef71e0d@projects.linpro.no> #137: regsub in vcl_hash fails --------------------+------------------------------------------------------- Reporter: phk | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------------------------------------------- {{{ CLI ready >> Child said (2, 44030): <> Child said (2, 44030): <r == NULL) not true. errno = 0 (Unknown error: 0) >> Cache child died pid=44030 status=0x86 Clean child Child cleaned start child pid 44031 Child said (2, 44031): <> }}} for vcl code: {{{ sub vcl_recv { lookup; } sub vcl_hash { if (req.http.cookie) { set req.hash += regsub( req.http.cookie, ".*=(.*)", "$1"); } } }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 3 07:40:41 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 03 Aug 2007 07:40:41 -0000 Subject: [Varnish] #138: [PATCH] varish-1.1 does not link on uclibc due to missing -lm linker flag Message-ID: <051.024a6368b13ea39bac4f748574f63896@projects.linpro.no> #138: [PATCH] varish-1.1 does not link on uclibc due to missing -lm linker flag --------------------+------------------------------------------------------- Reporter: ncopa | Owner: des Type: defect | Status: new Priority: normal | Milestone: Varnish 1.1.1 Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------------------------------------------- Hi, when I try to compile varnish-1.1 with uclibc (x86) I get the following error: {{{ ... i386-gentoo-linux-uclibc-gcc -include config.h -march=i386 -Os -pipe -fomit-frame-pointer -o .libs/varnishd varnishd-cache_acceptor.o varnishd- cache_acceptor_epoll.o varnishd-cache_acceptor_poll.o varnishd- cache_acceptor_kqueue.o varnishd-cache_backend.o varnishd-cache_ban.o varnishd-cache_center.o varnishd-cache_cli.o varnishd-cache_expire.o varnishd-cache_fetch.o varnishd-cache_hash.o varnishd-cache_http.o varnishd-cache_lru.o varnishd-cache_main.o varnishd-cache_pool.o varnishd- cache_pipe.o varnishd-cache_response.o varnishd-cache_session.o varnishd- cache_synthetic.o varnishd-cache_vary.o varnishd-cache_vcl.o varnishd- cache_vrt.o varnishd-cache_vrt_acl.o varnishd-cache_vrt_re.o varnishd- cache_ws.o varnishd-hash_simple_list.o varnishd-hash_classic.o varnishd- instance.o varnishd-mgt_child.o varnishd-mgt_cli.o varnishd-mgt_event.o varnishd-mgt_param.o varnishd-mgt_vcc.o varnishd-rfc2616.o varnishd- shmlog.o varnishd-stevedore.o varnishd-storage_file.o varnishd- storage_malloc.o varnishd-tcp.o varnishd-varnishd.o -Wl,--export-dynamic ../../lib/libvarnish/.libs/libvarnish.so ../../lib/libcompat/libcompat.a ../../lib/libvcl/.libs/libvcl.so -ldl -lpthread varnishd-cache_pool.o: In function `wrk_do_one': cache_pool.c:(.text+0x6de): undefined reference to `__isnan' varnishd-cache_pool.o: In function `wrk_thread': cache_pool.c:(.text+0x9ff): undefined reference to `__isnan' collect2: ld returned 1 exit status make[3]: *** [varnishd] Error 1 make[3]: Leaving directory `/var/tmp/portage/www- servers/varnish-1.1/work/varnish-1.1/bin/varnishd' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/www- servers/varnish-1.1/work/varnish-1.1/bin' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/www- servers/varnish-1.1/work/varnish-1.1' make: *** [all] Error 2 }}} The problem is that -lm should be added to the linker flags. This is a common misstake since glibc does not require -lm. I would not be surprised if you get the same linker error on *bsd. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 3 07:45:25 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 03 Aug 2007 07:45:25 -0000 Subject: [Varnish] #138: [PATCH] varish-1.1 does not link on uclibc due to missing -lm linker flag In-Reply-To: <051.024a6368b13ea39bac4f748574f63896@projects.linpro.no> References: <051.024a6368b13ea39bac4f748574f63896@projects.linpro.no> Message-ID: <060.fc5459bb52d85f4bcb53a7ed59e8a5ca@projects.linpro.no> #138: [PATCH] varish-1.1 does not link on uclibc due to missing -lm linker flag --------------------+------------------------------------------------------- Reporter: ncopa | Owner: des Type: defect | Status: new Priority: normal | Milestone: Varnish 1.1.1 Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+------------------------------------------------------- Comment (by ncopa): Also reported here: https://bugs.gentoo.org/show_bug.cgi?id=187570 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 3 07:54:11 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 03 Aug 2007 07:54:11 -0000 Subject: [Varnish] #138: [PATCH] varish-1.1 does not link on uclibc due to missing -lm linker flag In-Reply-To: <051.024a6368b13ea39bac4f748574f63896@projects.linpro.no> References: <051.024a6368b13ea39bac4f748574f63896@projects.linpro.no> Message-ID: <060.54007b8a7c0d4e8bd7b1416c6744e669@projects.linpro.no> #138: [PATCH] varish-1.1 does not link on uclibc due to missing -lm linker flag --------------------+------------------------------------------------------- Reporter: ncopa | Owner: des Type: defect | Status: new Priority: normal | Milestone: Varnish 1.1.1 Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+------------------------------------------------------- Comment (by ncopa): Please look at the "original format" of the patch. The trac-view of the patch only displays the diff for the first file while it contains diff's for multiple files. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 3 10:08:32 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 03 Aug 2007 10:08:32 -0000 Subject: [Varnish] #139: Varnish 1.1 dies with assert error in cnt_done upon PURGE Message-ID: <052.0fac94fc8efc8893c8fc4cd5fb3fba3c@projects.linpro.no> #139: Varnish 1.1 dies with assert error in cnt_done upon PURGE ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Keywords: varnishd core dump cnt_done ----------------------+----------------------------------------------------- I am running Varnish 1.1 (from ports, with patches by des committed july 25th) in FreeBSD 6.2-RELEASE/amd64, on Intel hardware. When sending a PURGE like this to Varnish: PURGE /lov-og-rett/article1917942.ece HTTP/1.0 Host: e24.no Connection: close Varnishd dies like this: Child said (2, 13158): <bereq) == 0) not true. errno = 2 (No such file or directory) >> Cache child died pid=13158 status=0x6 In my messages log: Aug 3 13:58:57 aicache8 kernel: pid 13543 (varnishd), uid 65534: exited on signal 6 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 3 10:35:17 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 03 Aug 2007 10:35:17 -0000 Subject: [Varnish] #139: Varnish 1.1 dies with assert error in cnt_done upon PURGE In-Reply-To: <052.0fac94fc8efc8893c8fc4cd5fb3fba3c@projects.linpro.no> References: <052.0fac94fc8efc8893c8fc4cd5fb3fba3c@projects.linpro.no> Message-ID: <061.11e12f91a0b41d78e96f4cfd41cbdd17@projects.linpro.no> #139: Varnish 1.1 dies with assert error in cnt_done upon PURGE -----------------------------------------+---------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump cnt_done | -----------------------------------------+---------------------------------- Comment (by anders): I guess I should note, that my VCL for relevant parts looks like this: backend foo { set backend.host = "80.91.1.1"; set backend.port = "80"; } backend bob { set backend.host = "80.91.1.2"; set backend.port = "80"; } backend foobar { set backend.host = "80.91.1.3"; set backend.port = "80"; } backend bar { set backend.host = "80.91.1.4"; set backend.port = "80"; } acl mypurge { "80.91.1.5"; } sub vcl_recv { if (req.http.host ~ "^(foo.aftenposten.no|bar.aftenposten.no|baz.aftenposten.no)$") { set req.backend = foo; } elsif (req.http.host ~ "^(bob.aftenposten.no)$") { set req.backend = bob; } elsif (req.http.host ~ "^(foobar.aftenposten.no|barbar.aftenposten.no|bazbaz.aftenposten.no)$") { set req.backend = foobar; } elsif (req.http.host ~ "^(www.bar.no|bar.no|www.baz.no|baz.no)$") { set req.backend = bar; } else { error 403 "Access denied. Contact cacheadmin at aftenposten.no if you have problems."; } if (req.request == "GET" || req.request == "HEAD") { if (req.http.Expect || req.http.Authenticate || req.http.Cookie) { pass; } else { lookup; } } elsif (req.request == "PURGE") { if (client.ip ~ mypurge) { lookup; } else { error 405 "Not allowed."; } } else { pass; } } -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 3 20:42:59 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 03 Aug 2007 20:42:59 -0000 Subject: [Varnish] #140: varnishd doesn't start without 'nogroup' even when using -g Message-ID: <052.26925e3b3d237c55ff035162aa6a002f@projects.linpro.no> #140: varnishd doesn't start without 'nogroup' even when using -g ----------------------+----------------------------------------------------- Reporter: andrew | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: minor | Keywords: ----------------------+----------------------------------------------------- varnishd won't start without the group 'nogroup' existing, even when you specify -g on the commandline. this is my command line: /usr/local/sbin/varnishd -a :80 -f /etc/varnish/default.vcl -T 127.0.0.1:6082 -t 120 -w 1,1000,120 -s file,/c01/varnish/varnish_storage.bin,40% -u varnish -g varnish -n /var/varnish -P /var/run/varnish.pid and when i didn't have 'nogroup' in /etc/group, it gave me an error stating so. when i added 'nogroup' to /etc/group, it started up with user varnish and group varnish. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sat Aug 4 22:56:38 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sat, 04 Aug 2007 22:56:38 -0000 Subject: [Varnish] #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash Message-ID: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Keywords: varnishd core dump VRT_l_req_hash ----------------------+----------------------------------------------------- I am running Varnish 1.1 (from ports, with patches by des committed july 25th) in FreeBSD 6.2-RELEASE/amd64, on Intel hardware. Varnishd in my test-production died with this error message: Child said (2, 97261): <hash_e + l + 1 <= sp->http->ws->e) not true. errno = 0 (Unknown error: 0) >> Cache child died pid=97261 status=0x6 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sat Aug 4 23:08:59 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sat, 04 Aug 2007 23:08:59 -0000 Subject: [Varnish] #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash In-Reply-To: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> References: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> Message-ID: <061.6338a6dd5ed962a56eb9973bec06cb0a@projects.linpro.no> #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash -----------------------------------------------+---------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump VRT_l_req_hash | -----------------------------------------------+---------------------------- Comment (by anders): I should note, that I am using varnishd with a broad (20 GB sm_balloc) data set here, and that my graphs shows upto 1.43 million hashes/objects. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Aug 5 19:27:13 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 05 Aug 2007 19:27:13 -0000 Subject: [Varnish] #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash In-Reply-To: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> References: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> Message-ID: <061.b449997adf38feeefc5816a419e36fc1@projects.linpro.no> #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash -----------------------------------------------+---------------------------- Reporter: anders | Owner: phk Type: defect | Status: closed Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Resolution: duplicate Keywords: varnishd core dump VRT_l_req_hash | -----------------------------------------------+---------------------------- Changes (by phk): * status: new => closed * resolution: => duplicate Comment: I have become aware that vcl_hash may not allow very much action that needs memory, in particular regsub(). You didn't include your VCL code (please always do) in the ticket, so I'm not 100% sure this is what is happening here, but I suspect this is a duplicate of the problem in ticket 137, and will mark this ticket as such. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Aug 5 19:37:16 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 05 Aug 2007 19:37:16 -0000 Subject: [Varnish] #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash In-Reply-To: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> References: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> Message-ID: <061.60393ea3569a460ddfbc26226d7ef3c1@projects.linpro.no> #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash -----------------------------------------------+---------------------------- Reporter: anders | Owner: phk Type: defect | Status: reopened Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump VRT_l_req_hash | -----------------------------------------------+---------------------------- Changes (by anders): * status: closed => reopened * resolution: duplicate => Comment: I do not have vcl_hash defined at all. This is my VCL code: backend default { set backend.host = "192.168.0.3"; set backend.port = "80"; } acl purge { "192.168.0.4"/32; } sub vcl_recv { if ((req.http.host ~ "^(cache.finn.no|finn.no|www.finn.no)$") || (req.http.host == "banner.finn.no" && req.url ~ "^/(jsp2|finn/gojsp|daily|board|auximg/papirfly|finn/cacheable|crossdomain.xml)")) { if (req.request == "GET" || req.request == "HEAD") { lookup; } elsif (req.request == "PURGE") { if (!client.ip ~ purge) { error 405 "Not allowed."; } lookup; } else { pipe; } } else { error 403 "Access denied. Contact cacheadmin at finn.no if you have problems."; } } sub vcl_miss { if (req.request == "PURGE") { error 404 "Not in cache."; } else { fetch; } } sub vcl_hit { if (req.request == "PURGE") { set obj.ttl = 0s; error 200 "Purged."; } else { deliver; } } sub vcl_fetch { if (obj.ttl < 86400s) { set obj.ttl = 604800s; } if (obj.http.Cookie) { remove obj.http.Cookie; } if (obj.http.Set-Cookie) { remove obj.http.Set-Cookie; } insert; } -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Aug 5 19:38:39 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 05 Aug 2007 19:38:39 -0000 Subject: [Varnish] #136: Setting vcl_trace to on in cli doesn't work In-Reply-To: <050.57043b1f9ca27fd83007e501737a32cf@projects.linpro.no> References: <050.57043b1f9ca27fd83007e501737a32cf@projects.linpro.no> Message-ID: <059.7c829e35d11df8ed85a910bbda64c934@projects.linpro.no> #136: Setting vcl_trace to on in cli doesn't work --------------------+------------------------------------------------------- Reporter: jesw | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: Fixed in change 1795. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Aug 5 19:39:06 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 05 Aug 2007 19:39:06 -0000 Subject: [Varnish] #132: Varnish 1.1 dies with assert error in SES_Delete In-Reply-To: <052.fe8cf8964ac10aa02472af7aa5d37aad@projects.linpro.no> References: <052.fe8cf8964ac10aa02472af7aa5d37aad@projects.linpro.no> Message-ID: <061.a2ac1a2b3a7072e050ca5ba92793d417@projects.linpro.no> #132: Varnish 1.1 dies with assert error in SES_Delete ----------------------------------+----------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: core dump SES_Delete | ----------------------------------+----------------------------------------- Comment (by anders): VCL code used is: backend default { set backend.host = "192.168.0.3"; set backend.port = "80"; } acl purge { "192.168.0.4"/32; } sub vcl_recv { if ((req.http.host ~ "^(cache.finn.no|finn.no|www.finn.no)$") || (req.http.host == "banner.finn.no" && req.url ~ "^/(jsp2|finn/gojsp|daily|board|auximg/papirfly|finn/cacheable|crossdomain.xml)")) { if (req.request == "GET" || req.request == "HEAD") { lookup; } elsif (req.request == "PURGE") { if (!client.ip ~ purge) { error 405 "Not allowed."; } lookup; } else { pipe; } } else { error 403 "Access denied. Contact cacheadmin at finn.no if you have problems."; } } sub vcl_miss { if (req.request == "PURGE") { error 404 "Not in cache."; } else { fetch; } } sub vcl_hit { if (req.request == "PURGE") { set obj.ttl = 0s; error 200 "Purged."; } else { deliver; } } sub vcl_fetch { if (obj.ttl < 86400s) { set obj.ttl = 604800s; } if (obj.http.Cookie) { remove obj.http.Cookie; } if (obj.http.Set-Cookie) { remove obj.http.Set-Cookie; } insert; } -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Aug 5 19:41:11 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 05 Aug 2007 19:41:11 -0000 Subject: [Varnish] #139: Varnish 1.1 dies with assert error in cnt_done upon PURGE In-Reply-To: <052.0fac94fc8efc8893c8fc4cd5fb3fba3c@projects.linpro.no> References: <052.0fac94fc8efc8893c8fc4cd5fb3fba3c@projects.linpro.no> Message-ID: <061.da1b7175fd2a005a017b683d496c818a@projects.linpro.no> #139: Varnish 1.1 dies with assert error in cnt_done upon PURGE -----------------------------------------+---------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump cnt_done | -----------------------------------------+---------------------------------- Comment (by anders): The rest of my VCL, not posted before, is: sub vcl_miss { if (req.request == "PURGE") { error 404 "Not in cache."; } else { fetch; } } sub vcl_hit { if (req.request == "PURGE") { set obj.ttl = 0s; error 200 "Purged."; } else { deliver; } } That's all. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Aug 5 20:18:11 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 05 Aug 2007 20:18:11 -0000 Subject: [Varnish] #140: varnishd doesn't start without 'nogroup' even when using -g In-Reply-To: <052.26925e3b3d237c55ff035162aa6a002f@projects.linpro.no> References: <052.26925e3b3d237c55ff035162aa6a002f@projects.linpro.no> Message-ID: <061.7a5628ff80708a9d2b75e50bb95a7e2e@projects.linpro.no> #140: varnishd doesn't start without 'nogroup' even when using -g ----------------------+----------------------------------------------------- Reporter: andrew | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: minor | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: fixed. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Aug 5 20:26:33 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 05 Aug 2007 20:26:33 -0000 Subject: [Varnish] #138: [PATCH] varish-1.1 does not link on uclibc due to missing -lm linker flag In-Reply-To: <051.024a6368b13ea39bac4f748574f63896@projects.linpro.no> References: <051.024a6368b13ea39bac4f748574f63896@projects.linpro.no> Message-ID: <060.fbf181b5914d2579851c839c185564e1@projects.linpro.no> #138: [PATCH] varish-1.1 does not link on uclibc due to missing -lm linker flag --------------------+------------------------------------------------------- Reporter: ncopa | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Varnish 1.1.1 Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: Fixed in trunk. Thanks for the patch. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Aug 5 20:34:55 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 05 Aug 2007 20:34:55 -0000 Subject: [Varnish] #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash In-Reply-To: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> References: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> Message-ID: <061.54ae7e79b63585b3b6867b70799db172@projects.linpro.no> #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash -----------------------------------------------+---------------------------- Reporter: anders | Owner: phk Type: defect | Status: reopened Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump VRT_l_req_hash | -----------------------------------------------+---------------------------- Comment (by phk): You're right, this is not the same as 137. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Aug 5 20:39:10 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 05 Aug 2007 20:39:10 -0000 Subject: [Varnish] #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash In-Reply-To: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> References: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> Message-ID: <061.0d0185eb1afec9ac65ada41fae34c41a@projects.linpro.no> #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash -----------------------------------------------+---------------------------- Reporter: anders | Owner: phk Type: defect | Status: reopened Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump VRT_l_req_hash | -----------------------------------------------+---------------------------- Comment (by anders): Per request from phk, I have set http_workspace to 16K instead of the default value 8K. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Aug 5 20:58:21 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 05 Aug 2007 20:58:21 -0000 Subject: [Varnish] #112: VCL needs an invalidation API In-Reply-To: <049.2762bb85b91c7448842c959f8ef9ba87@projects.linpro.no> References: <049.2762bb85b91c7448842c959f8ef9ba87@projects.linpro.no> Message-ID: <058.f6cb539ed0aa0fb598d313384134e62c@projects.linpro.no> #112: VCL needs an invalidation API -------------------------+-------------------------------------------------- Reporter: des | Owner: des Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: This seems to have been completed. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Aug 5 21:08:14 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 05 Aug 2007 21:08:14 -0000 Subject: [Varnish] #19: HTTP purge In-Reply-To: <049.8f39fc8f66a2142171f0ae9fa5886ddc@projects.linpro.no> References: <049.8f39fc8f66a2142171f0ae9fa5886ddc@projects.linpro.no> Message-ID: <058.e1bde1b11abe9c6d2afc4a5cbce66282@projects.linpro.no> #19: HTTP purge -------------------------+-------------------------------------------------- Reporter: des | Owner: phk Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: duplicate Keywords: | -------------------------+-------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => duplicate Comment: This has been implemented in the meantime. 112 was a duplicate of this. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 6 08:17:48 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 06 Aug 2007 08:17:48 -0000 Subject: [Varnish] #142: Varnishd core dumps because of segmentation violation Message-ID: <052.f72cc7589f3a3102380b0e8593362636@projects.linpro.no> #142: Varnishd core dumps because of segmentation violation ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Keywords: varnishd core dump sig 11 ----------------------+----------------------------------------------------- I am running Varnish 1.1 (from ports, with patches by des committed july 25th) in FreeBSD 6.2-RELEASE/amd64, on Intel hardware. I am using varnishd with a broad (20 GB sm_balloc) data set here, and that my graphs shows upto 1.43 million hashes/objects. Now and then, varnishd dies with sig11: Aug 6 04:46:27 cache10 kernel: pid 99461 (varnishd), uid 0: exited on signal 11 (core dumped) Backtrace, with what phk asked for so far: root at cache10:~# gdb -c /usr/local/varnish/cache10.finn.no/varnishd_2007-08-06_10- -01-44.core -s /usr/local/sbin/varnishd GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Core was generated by `varnishd'. Program terminated with signal 11, Segmentation fault. #0 0x0000000800a4e550 in ?? () (gdb) bt #0 0x0000000800a4e550 in ?? () #1 0x00000030013a590e in ?? () #2 0x00007ffff2390ad0 in ?? () #3 0x0000000001b4d008 in ?? () #4 0x00007ffff2390a00 in ?? () #5 0x0000000000416cc8 in VCL_recv_method (sp=0x1b4d008) at vcl_returns.h:37 Previous frame identical to this frame (corrupt stack?) (gdb) info threads 13 process 100145 0x0000000800a1a63c in ?? () 12 process 100045 0x0000000800a4b7fc in ?? () 11 process 100069 0x0000000800a4b7fc in ?? () 10 process 100079 0x0000000800a4b7fc in ?? () 9 process 100110 0x0000000800a2b0fc in ?? () 8 process 100111 0x0000000800a1a63c in ?? () 7 process 100130 0x0000000800a64f2c in ?? () 6 process 100178 0x0000000800a64f2c in ?? () 5 process 100133 0x0000000800a64f2c in ?? () 4 process 100159 0x0000000800a64f2c in ?? () 3 process 100161 0x0000000800a64f2c in ?? () 2 process 100115 0x0000000800a64f2c in ?? () * 1 process 100127 0x0000000800a4e550 in ?? () (gdb) thread 1 [Switching to thread 1 (process 100127)]#0 0x0000000800a4e550 in ?? () (gdb) bt #0 0x0000000800a4e550 in ?? () #1 0x00000030013a590e in ?? () #2 0x00007ffff2390ad0 in ?? () #3 0x0000000001b4d008 in ?? () #4 0x00007ffff2390a00 in ?? () #5 0x0000000000416cc8 in VCL_recv_method (sp=0x1b4d008) at vcl_returns.h:37 Previous frame identical to this frame (corrupt stack?) (gdb) thread 9 [Switching to thread 9 (process 100110)]#0 0x0000000800a2b0fc in ?? () (gdb) bt #0 0x0000000800a2b0fc in ?? () #1 0x0000000000408163 in vca_kqueue_main (arg=0x0) at cache_acceptor_kqueue.c:143 #2 0x000000080088655b in ?? () #3 0x0000000000000000 in ?? () #4 0x0000000000000000 in ?? () #5 0x000000000053be00 in ?? () #6 0x0000000000000000 in ?? () #7 0x000000000053b000 in ?? () #8 0x0000000000000000 in ?? () Cannot access memory at address 0x7fffff5fc000 My VCL: backend default { set backend.host = "192.168.0.3"; set backend.port = "80"; } acl purge { "192.168.0.4"/32; } sub vcl_recv { if ((req.http.host ~ "^(cache.finn.no|finn.no|www.finn.no)$") || (req.http.host == "banner.finn.no" && req.url ~ "^/(jsp2|finn/gojsp|daily|board|auximg/papirfly|finn/cacheable|crossdomain.xml)")) { if (req.request == "GET" || req.request == "HEAD") { lookup; } elsif (req.request == "PURGE") { if (!client.ip ~ purge) { error 405 "Not allowed."; } lookup; } else { pipe; } } else { error 403 "Access denied. Contact cacheadmin at finn.no if you have problems."; } } sub vcl_miss { if (req.request == "PURGE") { error 404 "Not in cache."; } else { fetch; } } sub vcl_hit { if (req.request == "PURGE") { set obj.ttl = 0s; error 200 "Purged."; } else { deliver; } } sub vcl_fetch { if (obj.ttl < 86400s) { set obj.ttl = 604800s; } if (obj.http.Cookie) { remove obj.http.Cookie; } if (obj.http.Set-Cookie) { remove obj.http.Set-Cookie; } insert; } -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 6 08:24:40 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 06 Aug 2007 08:24:40 -0000 Subject: [Varnish] #142: Varnishd core dumps because of segmentation violation In-Reply-To: <052.f72cc7589f3a3102380b0e8593362636@projects.linpro.no> References: <052.f72cc7589f3a3102380b0e8593362636@projects.linpro.no> Message-ID: <061.f1ec65d4cdde49bb99a095d583a15dae@projects.linpro.no> #142: Varnishd core dumps because of segmentation violation ---------------------------------------+------------------------------------ Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump sig 11 | ---------------------------------------+------------------------------------ Old description: > I am running Varnish 1.1 (from ports, with patches by des committed july > 25th) in FreeBSD 6.2-RELEASE/amd64, on Intel hardware. I am using > varnishd with a broad (20 GB sm_balloc) data set here, and that my graphs > shows upto 1.43 million hashes/objects. > > Now and then, varnishd dies with sig11: > > Aug 6 04:46:27 cache10 kernel: pid 99461 (varnishd), uid 0: exited on > signal 11 (core dumped) > > Backtrace, with what phk asked for so far: > > root at cache10:~# gdb -c > /usr/local/varnish/cache10.finn.no/varnishd_2007-08-06_10- > -01-44.core -s /usr/local/sbin/varnishd > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "amd64-marcel-freebsd"... > Core was generated by `varnishd'. > Program terminated with signal 11, Segmentation fault. > #0 0x0000000800a4e550 in ?? () > (gdb) bt > #0 0x0000000800a4e550 in ?? () > #1 0x00000030013a590e in ?? () > #2 0x00007ffff2390ad0 in ?? () > #3 0x0000000001b4d008 in ?? () > #4 0x00007ffff2390a00 in ?? () > #5 0x0000000000416cc8 in VCL_recv_method (sp=0x1b4d008) at > vcl_returns.h:37 > Previous frame identical to this frame (corrupt stack?) > (gdb) info threads > 13 process 100145 0x0000000800a1a63c in ?? () > 12 process 100045 0x0000000800a4b7fc in ?? () > 11 process 100069 0x0000000800a4b7fc in ?? () > 10 process 100079 0x0000000800a4b7fc in ?? () > 9 process 100110 0x0000000800a2b0fc in ?? () > 8 process 100111 0x0000000800a1a63c in ?? () > 7 process 100130 0x0000000800a64f2c in ?? () > 6 process 100178 0x0000000800a64f2c in ?? () > 5 process 100133 0x0000000800a64f2c in ?? () > 4 process 100159 0x0000000800a64f2c in ?? () > 3 process 100161 0x0000000800a64f2c in ?? () > 2 process 100115 0x0000000800a64f2c in ?? () > * 1 process 100127 0x0000000800a4e550 in ?? () > (gdb) thread 1 > [Switching to thread 1 (process 100127)]#0 0x0000000800a4e550 in ?? () > (gdb) bt > #0 0x0000000800a4e550 in ?? () > #1 0x00000030013a590e in ?? () > #2 0x00007ffff2390ad0 in ?? () > #3 0x0000000001b4d008 in ?? () > #4 0x00007ffff2390a00 in ?? () > #5 0x0000000000416cc8 in VCL_recv_method (sp=0x1b4d008) at > vcl_returns.h:37 > Previous frame identical to this frame (corrupt stack?) > (gdb) thread 9 > [Switching to thread 9 (process 100110)]#0 0x0000000800a2b0fc in ?? () > (gdb) bt > #0 0x0000000800a2b0fc in ?? () > #1 0x0000000000408163 in vca_kqueue_main (arg=0x0) > at cache_acceptor_kqueue.c:143 > #2 0x000000080088655b in ?? () > #3 0x0000000000000000 in ?? () > #4 0x0000000000000000 in ?? () > #5 0x000000000053be00 in ?? () > #6 0x0000000000000000 in ?? () > #7 0x000000000053b000 in ?? () > #8 0x0000000000000000 in ?? () > Cannot access memory at address 0x7fffff5fc000 > > My VCL: > > backend default { > set backend.host = "192.168.0.3"; > set backend.port = "80"; > } > acl purge { > "192.168.0.4"/32; > } > sub vcl_recv { > if ((req.http.host ~ "^(cache.finn.no|finn.no|www.finn.no)$") || > (req.http.host == "banner.finn.no" && req.url ~ > "^/(jsp2|finn/gojsp|daily|board|auximg/papirfly|finn/cacheable|crossdomain.xml)")) > { > if (req.request == "GET" || req.request == "HEAD") { > lookup; > } elsif (req.request == "PURGE") { > if (!client.ip ~ purge) { > error 405 "Not allowed."; > } > lookup; > } else { > pipe; > } > } else { > error 403 "Access denied. Contact cacheadmin at finn.no if > you have problems."; > } > } > sub vcl_miss { > if (req.request == "PURGE") { > error 404 "Not in cache."; > } else { > fetch; > } > } > sub vcl_hit { > if (req.request == "PURGE") { > set obj.ttl = 0s; > error 200 "Purged."; > } else { > deliver; > } > } > sub vcl_fetch { > if (obj.ttl < 86400s) { > set obj.ttl = 604800s; > } > if (obj.http.Cookie) { > remove obj.http.Cookie; > } > if (obj.http.Set-Cookie) { > remove obj.http.Set-Cookie; > } > insert; > } New description: I am running Varnish 1.1 (from ports, with patches by des committed july 25th) in FreeBSD 6.2-RELEASE/amd64, on Intel hardware. I am using varnishd with a broad (20 GB sm_balloc) data set here, and that my graphs shows upto 1.43 million hashes/objects. Now and then, varnishd dies with sig11: Aug 6 04:46:27 cache10 kernel: pid 99461 (varnishd), uid 0: exited on signal 11 (core dumped) Backtrace, with what phk asked for so far: {{{ root at cache10:~# gdb -c /usr/local/varnish/cache10.finn.no/varnishd_2007-08-06_10- -01-44.core -s /usr/local/sbin/varnishd GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Core was generated by `varnishd'. Program terminated with signal 11, Segmentation fault. #0 0x0000000800a4e550 in ?? () (gdb) bt #0 0x0000000800a4e550 in ?? () #1 0x00000030013a590e in ?? () #2 0x00007ffff2390ad0 in ?? () #3 0x0000000001b4d008 in ?? () #4 0x00007ffff2390a00 in ?? () #5 0x0000000000416cc8 in VCL_recv_method (sp=0x1b4d008) at vcl_returns.h:37 Previous frame identical to this frame (corrupt stack?) (gdb) info threads 13 process 100145 0x0000000800a1a63c in ?? () 12 process 100045 0x0000000800a4b7fc in ?? () 11 process 100069 0x0000000800a4b7fc in ?? () 10 process 100079 0x0000000800a4b7fc in ?? () 9 process 100110 0x0000000800a2b0fc in ?? () 8 process 100111 0x0000000800a1a63c in ?? () 7 process 100130 0x0000000800a64f2c in ?? () 6 process 100178 0x0000000800a64f2c in ?? () 5 process 100133 0x0000000800a64f2c in ?? () 4 process 100159 0x0000000800a64f2c in ?? () 3 process 100161 0x0000000800a64f2c in ?? () 2 process 100115 0x0000000800a64f2c in ?? () * 1 process 100127 0x0000000800a4e550 in ?? () (gdb) thread 1 [Switching to thread 1 (process 100127)]#0 0x0000000800a4e550 in ?? () (gdb) bt #0 0x0000000800a4e550 in ?? () #1 0x00000030013a590e in ?? () #2 0x00007ffff2390ad0 in ?? () #3 0x0000000001b4d008 in ?? () #4 0x00007ffff2390a00 in ?? () #5 0x0000000000416cc8 in VCL_recv_method (sp=0x1b4d008) at vcl_returns.h:37 Previous frame identical to this frame (corrupt stack?) (gdb) thread 9 [Switching to thread 9 (process 100110)]#0 0x0000000800a2b0fc in ?? () (gdb) bt #0 0x0000000800a2b0fc in ?? () #1 0x0000000000408163 in vca_kqueue_main (arg=0x0) at cache_acceptor_kqueue.c:143 #2 0x000000080088655b in ?? () #3 0x0000000000000000 in ?? () #4 0x0000000000000000 in ?? () #5 0x000000000053be00 in ?? () #6 0x0000000000000000 in ?? () #7 0x000000000053b000 in ?? () #8 0x0000000000000000 in ?? () Cannot access memory at address 0x7fffff5fc000 My VCL: backend default { set backend.host = "192.168.0.3"; set backend.port = "80"; } acl purge { "192.168.0.4"/32; } sub vcl_recv { if ((req.http.host ~ "^(cache.finn.no|finn.no|www.finn.no)$") || (req.http.host == "banner.finn.no" && req.url ~ "^/(jsp2|finn/gojsp|daily|board|auximg/papirfly|finn/cacheable|crossdomain.xml)")) { if (req.request == "GET" || req.request == "HEAD") { lookup; } elsif (req.request == "PURGE") { if (!client.ip ~ purge) { error 405 "Not allowed."; } lookup; } else { pipe; } } else { error 403 "Access denied. Contact cacheadmin at finn.no if you have problems."; } } sub vcl_miss { if (req.request == "PURGE") { error 404 "Not in cache."; } else { fetch; } } sub vcl_hit { if (req.request == "PURGE") { set obj.ttl = 0s; error 200 "Purged."; } else { deliver; } } sub vcl_fetch { if (obj.ttl < 86400s) { set obj.ttl = 604800s; } if (obj.http.Cookie) { remove obj.http.Cookie; } if (obj.http.Set-Cookie) { remove obj.http.Set-Cookie; } insert; } }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 6 08:38:21 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 06 Aug 2007 08:38:21 -0000 Subject: [Varnish] #142: Varnishd core dumps because of segmentation violation In-Reply-To: <052.f72cc7589f3a3102380b0e8593362636@projects.linpro.no> References: <052.f72cc7589f3a3102380b0e8593362636@projects.linpro.no> Message-ID: <061.5688ace3d2d19cc1b997625b12a2bfff@projects.linpro.no> #142: Varnishd core dumps because of segmentation violation ---------------------------------------+------------------------------------ Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump sig 11 | ---------------------------------------+------------------------------------ Comment (by anders): More data that phk asked for: {{{ (gdb) thread 1 [Switching to thread 1 (process 100127)]#4 0x00007ffff2390a00 in ?? () (gdb) up #5 0x0000000000416cc8 in VCL_recv_method (sp=0x1b4d008) at vcl_returns.h:37 37 vcl_returns.h: No such file or directory. in vcl_returns.h (gdb) up Previous frame identical to this frame (corrupt stack?) (gdb) print *sp $1 = {magic = 741317722, fd = 16, id = 16, xid = 1091137680, wrk = 0x7ffff2390ad0, sockaddrlen = 16, mysockaddrlen = 128, sockaddr = 0x1b4d408, mysockaddr = 0x1b4d488, addr = "85.25.129.95", '\0' , port = "3307", '\0' , srcaddr = 0x3a81c900, doclose = 0x4294a3
, http = 0x1b4d178, t_open = 1186368359.4365292, t_req = 1186368359.5116947, t_resp = nan(0x8000000000000), t_end = nan(0x8000000000000), step = STP_RECV, handling = 0, wantbody = 0 '\0', err_code = 0, err_reason = 0x0, list = {tqe_next = 0x0, tqe_prev = 0x0}, backend = 0xaf4d00, bereq = 0x0, obj = 0x0, vcl = 0x30014a7920, mem = 0x1b4d000, workreq = {list = {tqe_next = 0x0, tqe_prev = 0x0}, sess = 0x1b4d008}, acct = {first = 1186368359.4365292, sess = 0, req = 0, pipe = 0, pass = 0, fetch = 0, hdrbytes = 0, bodybytes = 0}, hash_b = 0x0, hash_e = 0x0} }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 6 09:32:21 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 06 Aug 2007 09:32:21 -0000 Subject: [Varnish] #137: regsub in vcl_hash fails In-Reply-To: <049.b7e5cd54775072421075abd03ef71e0d@projects.linpro.no> References: <049.b7e5cd54775072421075abd03ef71e0d@projects.linpro.no> Message-ID: <058.5db0c00b81c6385c6af6f12cc24c2e1e@projects.linpro.no> #137: regsub in vcl_hash fails --------------------+------------------------------------------------------- Reporter: phk | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: This is now fixed in trunk by using a scatter-gather strategy for the hash-string instead of (pointlessly) assembling it all on the workspace. Don't know what I was thinking when I did that... -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 6 10:12:07 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 06 Aug 2007 10:12:07 -0000 Subject: [Varnish] #142: Varnishd core dumps because of segmentation violation In-Reply-To: <052.f72cc7589f3a3102380b0e8593362636@projects.linpro.no> References: <052.f72cc7589f3a3102380b0e8593362636@projects.linpro.no> Message-ID: <061.25cbfc842f779cc5d70682b5573643a9@projects.linpro.no> #142: Varnishd core dumps because of segmentation violation ---------------------------------------+------------------------------------ Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump sig 11 | ---------------------------------------+------------------------------------ Comment (by anders): I am running varnishd with these parameters: -d -d -u root -g wheel -p http_workspace=16384 -p listen_depth=4096 -p srcaddr_hash=20480 -p default_ttl=604800 -T localhost:8080 -f /usr/local/etc/varnish.vcl -s file,/data/varnish.dat,171798691840 -P /var/run/varnishd.pid -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 6 10:12:22 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 06 Aug 2007 10:12:22 -0000 Subject: [Varnish] #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash In-Reply-To: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> References: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> Message-ID: <061.d88701c957e956c179e27c86f4d8ba61@projects.linpro.no> #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash -----------------------------------------------+---------------------------- Reporter: anders | Owner: phk Type: defect | Status: reopened Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump VRT_l_req_hash | -----------------------------------------------+---------------------------- Comment (by anders): I am running varnishd with these parameters: -d -d -u root -g wheel -p http_workspace=16384 -p listen_depth=4096 -p srcaddr_hash=20480 -p default_ttl=604800 -T localhost:8080 -f /usr/local/etc/varnish.vcl -s file,/data/varnish.dat,171798691840 -P /var/run/varnishd.pid -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 6 10:13:24 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 06 Aug 2007 10:13:24 -0000 Subject: [Varnish] #132: Varnish 1.1 dies with assert error in SES_Delete In-Reply-To: <052.fe8cf8964ac10aa02472af7aa5d37aad@projects.linpro.no> References: <052.fe8cf8964ac10aa02472af7aa5d37aad@projects.linpro.no> Message-ID: <061.dfc56674dba92b17605d945b6a669234@projects.linpro.no> #132: Varnish 1.1 dies with assert error in SES_Delete ----------------------------------+----------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: core dump SES_Delete | ----------------------------------+----------------------------------------- Comment (by anders): I was running varnishd with these parameters when the propblem occured last time: -d -d -p listen_depth=4096 -p srcaddr_hash=20480 -p default_ttl=604800 -T localhost:8080 -f /usr/local/etc/varnish.vcl -s file,/data/varnish.dat,171798691840 -P /var/run/varnishd.pid I've added -p http_workspace=16384 later on, but I don't know if that affects anything. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 6 11:08:46 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 06 Aug 2007 11:08:46 -0000 Subject: [Varnish] #139: Varnish 1.1 dies with assert error in cnt_done upon PURGE In-Reply-To: <052.0fac94fc8efc8893c8fc4cd5fb3fba3c@projects.linpro.no> References: <052.0fac94fc8efc8893c8fc4cd5fb3fba3c@projects.linpro.no> Message-ID: <061.e3339c635ccd5dd8f7b2ea371640246a@projects.linpro.no> #139: Varnish 1.1 dies with assert error in cnt_done upon PURGE -----------------------------------------+---------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump cnt_done | -----------------------------------------+---------------------------------- Comment (by anders): I am running varnishd with these parameters: -d -d -p listen_depth=4096 -p srcaddr_hash=20480 -p default_ttl=604800 -T localhost:8080 -f /usr/local/etc/varnish.vcl -s file,/data/varnish.dat ,42949672960 -P /var/run/varnishd.pid -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 7 06:56:14 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 07 Aug 2007 06:56:14 -0000 Subject: [Varnish] #139: Varnish 1.1 dies with assert error in cnt_done upon PURGE In-Reply-To: <052.0fac94fc8efc8893c8fc4cd5fb3fba3c@projects.linpro.no> References: <052.0fac94fc8efc8893c8fc4cd5fb3fba3c@projects.linpro.no> Message-ID: <061.04e6d161d1fa68c8038fb7c3d47596f8@projects.linpro.no> #139: Varnish 1.1 dies with assert error in cnt_done upon PURGE -----------------------------------------+---------------------------------- Reporter: anders | Owner: phk Type: defect | Status: closed Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Resolution: fixed Keywords: varnishd core dump cnt_done | -----------------------------------------+---------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: Fixed in commit 1807. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 7 08:51:16 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 07 Aug 2007 08:51:16 -0000 Subject: [Varnish] #143: Bogus message when loading a new VCL Message-ID: <052.3353517d4976f703850e8c2c3b1ef36e@projects.linpro.no> #143: Bogus message when loading a new VCL ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: low | Milestone: Component: varnishd | Version: 1.1 Severity: minor | Keywords: varnishd VCL vcl.load ----------------------+----------------------------------------------------- I am running varnishd with -d -d. Then, I connect to the management interface using telnet, and issue a command to load a new VCL: {{{ Connected to localhost. Escape character is '^]'. vcl.list 200 30 0 boot * 3 run1 vcl.load run2 /usr/local/etc/varnish.vcl 200 0 }}} On the console where I started varnishd (with -d -d), I then see an error message: >LI LI Varnish The Varnish HTTP Accelerator From anders at fupp.net Sun Aug 5 19:35:20 2007 From: anders at fupp.net (Anders Nordby) Date: Sun, 5 Aug 2007 21:35:20 +0200 Subject: [Varnish] #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash In-Reply-To: <061.b449997adf38feeefc5816a419e36fc1@projects.linpro.no> References: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> <061.b449997adf38feeefc5816a419e36fc1@projects.linpro.no> Message-ID: <20070805193520.GA40930@fupp.net> Hi, I have not defined vcl_hash at all. Please re-open this ticket. Attached is my VCL code. On Sun, Aug 05, 2007 at 07:27:13PM -0000, Varnish wrote: > #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash > -----------------------------------------------+---------------------------- > Reporter: anders | Owner: phk > Type: defect | Status: closed > Priority: high | Milestone: > Component: varnishd | Version: 1.1 > Severity: major | Resolution: duplicate > Keywords: varnishd core dump VRT_l_req_hash | > -----------------------------------------------+---------------------------- > Changes (by phk): > > * status: new => closed > * resolution: => duplicate > > Comment: > > I have become aware that vcl_hash may not allow very much action that > needs memory, in particular regsub(). > > You didn't include your VCL code (please always do) in the ticket, so I'm > not 100% sure this is what is happening here, but I suspect this is a > duplicate of the problem in ticket 137, and will mark this ticket as such. > > -- > Ticket URL: > Varnish > The Varnish HTTP Accelerator -- Anders. -------------- next part -------------- backend default { set backend.host = "192.168.0.3"; set backend.port = "80"; } acl purge { "192.168.0.4"/32; } sub vcl_recv { if ((req.http.host ~ "^(cache.finn.no|finn.no|www.finn.no)$") || (req.http.host == "banner.finn.no" && req.url ~ "^/(jsp2|finn/gojsp|daily|board|auximg/papirfly|finn/cacheable|crossdomain.xml)")) { if (req.request == "GET" || req.request == "HEAD") { lookup; } elsif (req.request == "PURGE") { if (!client.ip ~ purge) { error 405 "Not allowed."; } lookup; } else { pipe; } } else { error 403 "Access denied. Contact cacheadmin at finn.no if you have problems."; } } sub vcl_miss { if (req.request == "PURGE") { error 404 "Not in cache."; } else { fetch; } } sub vcl_hit { if (req.request == "PURGE") { set obj.ttl = 0s; error 200 "Purged."; } else { deliver; } } sub vcl_fetch { if (obj.ttl < 86400s) { set obj.ttl = 604800s; } if (obj.http.Cookie) { remove obj.http.Cookie; } if (obj.http.Set-Cookie) { remove obj.http.Set-Cookie; } insert; } From anders at fupp.net Sun Aug 5 19:38:20 2007 From: anders at fupp.net (Anders Nordby) Date: Sun, 5 Aug 2007 21:38:20 +0200 Subject: [Varnish] #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash In-Reply-To: <20070805193520.GA40930@fupp.net> References: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> <061.b449997adf38feeefc5816a419e36fc1@projects.linpro.no> <20070805193520.GA40930@fupp.net> Message-ID: <20070805193820.GA41184@fupp.net> Hi, On Sun, Aug 05, 2007 at 09:35:20PM +0200, Anders Nordby wrote: > I have not defined vcl_hash at all. Please re-open this ticket. > > Attached is my VCL code. Found out how to re-open. By logging in. :-) Well. I added my VCL code in the ticket. Bye, -- Anders. From varnish-bugs at projects.linpro.no Tue Aug 7 10:30:38 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 07 Aug 2007 10:30:38 -0000 Subject: [Varnish] #144: Varnishd core dumps because of bus error Message-ID: <052.869b9c75015371cffe23335fba6d1ce5@projects.linpro.no> #144: Varnishd core dumps because of bus error ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Keywords: varnishd core dump sig 10 ----------------------+----------------------------------------------------- I am running Varnish 1.1 (from ports, with patches by des committed july 25th) in FreeBSD 6.2-RELEASE/amd64, on Intel hardware. I am using varnishd with a broad (20 GB sm_balloc) data set here, and that my graphs shows upto 1.43 million hashes/objects. Per phk's request, I have set some malloc parameters: lrwxr-xr-x 1 root wheel 2 Aug 7 08:57 malloc.conf -> AJ Varnish crashed signal 10: Aug 7 12:01:21 cache10 kernel: pid 57690 (varnishd), uid 0: exited on signal 10 (core dumped) On the console: Child not responding to ping (..) Cache child died pid=57690 status=0x8a My VCL: {{{ backend default { set backend.host = "192.168.0.3"; set backend.port = "80"; } acl purge { "192.168.0.4"/32; } sub vcl_recv { if ((req.http.host ~ "^(cache.finn.no|finn.no|www.finn.no)$") || (req.http.host == "banner.finn.no" && req.url ~ "^/(jsp2|finn/gojsp|daily|board|auximg/papirfly|finn/cacheable|crossdomain.xml)")) { if (req.request == "GET" || req.request == "HEAD") { lookup; } elsif (req.request == "PURGE") { if (!client.ip ~ purge) { error 405 "Not allowed."; } lookup; } else { pipe; } } else { error 403 "Access denied. Contact cacheadmin at finn.no if you have problems."; } } sub vcl_miss { if (req.request == "PURGE") { error 404 "Not in cache."; } else { fetch; } } sub vcl_hit { if (req.request == "PURGE") { set obj.ttl = 0s; error 200 "Purged."; } else { deliver; } } sub vcl_fetch { if (obj.ttl < 86400s) { set obj.ttl = 604800s; } if (obj.http.Cookie) { remove obj.http.Cookie; } if (obj.http.Set-Cookie) { remove obj.http.Set-Cookie; } insert; } }}} Back-trace of the core-dump: {{{ root at cache10:/usr/local/varnish/cache10.finn.no# gdb -c varnishd_2007-08-07_12-00-01.core -s /usr/local/sbin/varnishd GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Core was generated by `varnishd'. Program terminated with signal 10, Bus error. #0 0x0000000000408850 in vbe_sock_conn (ai=0xd0d0d0d0d0d0d0d0) at cache_backend.c:158 158 s = socket(ai->ai_family, ai->ai_socktype, ai->ai_protocol); (gdb) bt #0 0x0000000000408850 in vbe_sock_conn (ai=0xd0d0d0d0d0d0d0d0) at cache_backend.c:158 #1 0x00000000004088fc in vbe_conn_try (bp=0xaf4d00, pai=0x7ffff8bc4868) at cache_backend.c:176 #2 0x0000000000408ad4 in vbe_connect (sp=0x38de008, bp=0xaf4d00) at cache_backend.c:224 #3 0x0000000000408ef3 in vbe_nextfd (sp=0x38de008) at cache_backend.c:295 #4 0x0000000000409132 in VBE_GetFd (sp=0x38de008) at cache_backend.c:332 #5 0x000000000040c700 in Fetch (sp=0x38de008) at cache_fetch.c:278 #6 0x0000000000409e34 in cnt_fetch (sp=0x38de008) at cache_center.c:290 #7 0x000000000040addd in CNT_Session (sp=0x38de008) at steps.h:40 #8 0x00000000004124b8 in wrk_do_one (w=0x7ffff8bc4ad0) at cache_pool.c:193 #9 0x00000000004129b3 in wrk_thread (priv=0x856300) at cache_pool.c:247 #10 0x000000080088655b in ?? () #11 0x0000000000000000 in ?? () #12 0x00007ffff3199fd8 in ?? () #13 0x0000000039bbb800 in ?? () #14 0x0000000000000000 in ?? () #15 0x000000000053be00 in ?? () #16 0x00007ffff89c7000 in ?? () Cannot access memory at address 0x7ffff8bc7000 }}} Varnish is compiled with -g (CFLAGS= -g), and not stripped (STRIP=). -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 7 10:40:32 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 07 Aug 2007 10:40:32 -0000 Subject: [Varnish] #144: Race in backend socket address replacement. In-Reply-To: <052.869b9c75015371cffe23335fba6d1ce5@projects.linpro.no> References: <052.869b9c75015371cffe23335fba6d1ce5@projects.linpro.no> Message-ID: <061.48c1c9ae8556b1e29cfeb6d9f96217e7@projects.linpro.no> #144: Race in backend socket address replacement. ---------------------------------------+------------------------------------ Reporter: anders | Owner: phk Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: 1.1 Severity: normal | Resolution: Keywords: varnishd core dump sig 10 | ---------------------------------------+------------------------------------ Changes (by phk): * priority: high => normal * status: new => assigned * severity: major => normal * summary: Varnishd core dumps because of bus error => Race in backend socket address replacement. Comment: there is a race in the backend code where failure to connect to the backend will trigger a new socket address lookup (DNS or numeric). However, other threads may be using the old address still. I have minimized the race so that undefined data is not present at any time, and that reduces the propability and changes the failure mode to access to free'ed memory. The right solution needs a bit of thinking, but it is something along the lines of caching the socket address in the vbe at a point where we have the lock anyway, and then do the replacement (but not the actual lookup!) under lock. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 7 13:20:41 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 07 Aug 2007 13:20:41 -0000 Subject: [Varnish] #145: Issues whild loading VCL code on the fly Message-ID: <052.cbf0da58c87c745a45933c736d50eec2@projects.linpro.no> #145: Issues whild loading VCL code on the fly ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.1 Severity: normal | Keywords: varnishd load VCL ----------------------+----------------------------------------------------- After loading VCL code with a couple of different config names, including doing that with errors in the config, it happens that you can not really discard a configuration which is not in use anymore. {{{ Connected to localhost. Escape character is '^]'. vcl.list 200 15 * 38 boot vcl.load run1 /usr/local/etc/varnish.vcl 106 102 Expected action, 'if' or '}' (/usr/local/etc/varnish.vcl Line 54 Pos 1) sub vcl_miss { ###----------- vcl.list 200 15 * 38 boot vcl.load run1 /usr/local/etc/varnish.vcl 200 0 vcl.list 200 30 * 38 boot 0 run1 vcl.use run1 200 0 vcl.load run2 /usr/local/etc/varnish.vcl 106 102 Expected action, 'if' or '}' (/usr/local/etc/varnish.vcl Line 54 Pos 1) sub vcl_miss { ###----------- vcl.list 200 30 23 boot * 15 run1 vcl.load run2 /usr/local/etc/varnish.vcl 200 0 vcl.list 200 45 8 boot * 30 run1 0 run2 vcl.discard run2 200 0 vcl.load run2 /usr/local/etc/varnish.vcl 200 0 vcl.use run2 200 0 vcl.discard run1 200 0 vcl.load run1 /usr/local/etc/varnish.vcl 106 28 Config 'run1' already loaded vcl.list 200 45 0 boot 1 run1 * 50 run2 vcl.discard run1 106 34 No configuration named run1 known. }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 7 14:08:34 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 07 Aug 2007 14:08:34 -0000 Subject: [Varnish] #132: Varnish 1.1 dies with assert error in SES_Delete In-Reply-To: <052.fe8cf8964ac10aa02472af7aa5d37aad@projects.linpro.no> References: <052.fe8cf8964ac10aa02472af7aa5d37aad@projects.linpro.no> Message-ID: <061.2c0b0bbdf8c7f7042cad47ffcff0fa08@projects.linpro.no> #132: Varnish 1.1 dies with assert error in SES_Delete ----------------------------------+----------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: core dump SES_Delete | ----------------------------------+----------------------------------------- Comment (by anders): Finally I got a dump from this bug. But the backtrace does not show much: {{{ # gdb -c varnishd_2007-08-07_13-45-00.core -s /usr/local/sbin/varnishd GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Core was generated by `varnishd'. Program terminated with signal 6, Aborted. #0 0x00000008009e30dc in ?? () (gdb) bt #0 0x00000008009e30dc in ?? () #1 0x000000080088401c in ?? () #2 0x00007fffff5faeac in ?? () #3 0x0000000800a6216d in ?? () #4 0x0000000000000000 in ?? () #5 0xffffffdf000186f5 in ?? () #6 0xffffffffffffffff in ?? () #7 0x00000000ffffffff in ?? () #8 0x000000000053be10 in ?? () #9 0x000000000053be00 in ?? () #10 0x000000000053be10 in ?? () #11 0x0000000800663b49 in ?? () #12 0x0000000000000000 in ?? () #13 0x0000000800b998a0 in ?? () #14 0x000000000042a272 in __func__.4 () Cannot access memory at address 0x42a240 }}} I will share a link to the actual core dump to des/phk in private. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 7 14:39:13 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 07 Aug 2007 14:39:13 -0000 Subject: [Varnish] #146: vcl(7) needs better description of obj.cacheable Message-ID: <052.54a04a091a986c2d2ff0800a707725b7@projects.linpro.no> #146: vcl(7) needs better description of obj.cacheable ---------------------------+------------------------------------------------ Reporter: anders | Owner: des Type: documentation | Status: new Priority: normal | Milestone: Component: documentation | Version: trunk Severity: normal | Keywords: vcl man page ---------------------------+------------------------------------------------ The vcl(7) man page says: obj.cacheable True if the object is cacheable. What is required for an object to be determined cacheable? A better, exact description should be written there. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 7 17:21:28 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 07 Aug 2007 17:21:28 -0000 Subject: [Varnish] #144: Race in backend socket address replacement. In-Reply-To: <052.869b9c75015371cffe23335fba6d1ce5@projects.linpro.no> References: <052.869b9c75015371cffe23335fba6d1ce5@projects.linpro.no> Message-ID: <061.7dcfd4df44bee7a7d845599f4b48f6b5@projects.linpro.no> #144: Race in backend socket address replacement. ---------------------------------------+------------------------------------ Reporter: anders | Owner: phk Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: 1.1 Severity: normal | Resolution: Keywords: varnishd core dump sig 10 | ---------------------------------------+------------------------------------ Comment (by anders): I applied commit 1809 (http://anders.fupp.net/patch-varnish-sigbus-r1809). PHK said it should help, but instead I get sigbus more often now: {{{ Aug 7 18:03:07 cache10 kernel: pid 27495 (varnishd), uid 0: exited on signal 10 (core dumped) Aug 7 18:04:25 cache10 kernel: pid 27714 (varnishd), uid 0: exited on signal 10 (core dumped) Aug 7 18:05:44 cache10 kernel: pid 27747 (varnishd), uid 0: exited on signal 10 (core dumped) Aug 7 18:07:03 cache10 kernel: pid 27751 (varnishd), uid 0: exited on signal 10 (core dumped) Aug 7 18:08:20 cache10 kernel: pid 27758 (varnishd), uid 0: exited on signal 10 (core dumped) Aug 7 18:09:38 cache10 kernel: pid 28003 (varnishd), uid 0: exited on signal 10 (core dumped) Aug 7 18:10:53 cache10 kernel: pid 28010 (varnishd), uid 0: exited on signal 10 (core dumped) Aug 7 18:12:09 cache10 kernel: pid 28050 (varnishd), uid 0: exited on signal 10 (core dumped) Aug 7 18:13:28 cache10 kernel: pid 28064 (varnishd), uid 0: exited on signal 10 (core dumped) Aug 7 18:14:47 cache10 kernel: pid 28317 (varnishd), uid 0: exited on signal 10 (core dumped) Aug 7 18:16:03 cache10 kernel: pid 28318 (varnishd), uid 0: exited on signal 10 (core dumped) Aug 7 18:17:20 cache10 kernel: pid 28328 (varnishd), uid 0: exited on signal 10 (core dumped) Aug 7 18:18:36 cache10 kernel: pid 28355 (varnishd), uid 0: exited on signal 10 (core dumped) Aug 7 18:19:55 cache10 kernel: pid 28580 (varnishd), uid 0: exited on signal 10 (core dumped) Aug 7 18:21:11 cache10 kernel: pid 28607 (varnishd), uid 0: exited on signal 10 (core dumped) }}} Did a backtrace on one of the new core-dumps, and got: {{{ Program terminated with signal 10, Bus error. #0 0x0000000000408840 in vbe_sock_conn (ai=0xd0d0d0d0d0d0d0d0) at cache_backend.c:161 161 cache_backend.c: No such file or directory. in cache_backend.c (gdb) bt #0 0x0000000000408840 in vbe_sock_conn (ai=0xd0d0d0d0d0d0d0d0) at cache_backend.c:161 #1 0x00000000004088ec in vbe_conn_try (bp=0xaf4d00, pai=0x7ffffa7d2868) at cache_backend.c:179 #2 0x0000000000408ac4 in vbe_connect (sp=0xc1a008, bp=0xaf4d00) at cache_backend.c:227 #3 0x0000000000408ee3 in vbe_nextfd (sp=0xc1a008) at cache_backend.c:298 #4 0x0000000000409122 in VBE_GetFd (sp=0xc1a008) at cache_backend.c:335 #5 0x000000000040c700 in Fetch (sp=0xc1a008) at cache_fetch.c:278 #6 0x0000000000409e24 in cnt_fetch (sp=0xc1a008) at cache_center.c:290 #7 0x000000000040addd in CNT_Session (sp=0xc1a008) at steps.h:40 #8 0x00000000004124b8 in wrk_do_one (w=0x7ffffa7d2ad0) at cache_pool.c:193 #9 0x0000000000412814 in wrk_thread (priv=0x856300) at cache_pool.c:234 #10 0x000000080088655b in ?? () #11 0x0000000000000000 in ?? () #12 0x0000000000000000 in ?? () #13 0x0000000000bd2e00 in ?? () #14 0x0000000000000000 in ?? () #15 0x0000000000af7000 in ?? () #16 0x0000000000000000 in ?? () Cannot access memory at address 0x7ffffa7d5000 (gdb) }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Aug 8 08:49:27 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 08 Aug 2007 08:49:27 -0000 Subject: [Varnish] #143: Bogus message when loading a new VCL In-Reply-To: <052.3353517d4976f703850e8c2c3b1ef36e@projects.linpro.no> References: <052.3353517d4976f703850e8c2c3b1ef36e@projects.linpro.no> Message-ID: <061.285fefc9f1a2164c6ce0103767833e2a@projects.linpro.no> #143: Bogus message when loading a new VCL -----------------------------------+---------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: closed Priority: low | Milestone: Component: varnishd | Version: 1.1 Severity: minor | Resolution: fixed Keywords: varnishd VCL vcl.load | -----------------------------------+---------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: Fixed in 1810. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:16:15 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:16:15 -0000 Subject: [Varnish] #130: Build of varnishhist, varnishstat and varnishtop fails with gcc 4.2.0 In-Reply-To: <048.0b7218bd5544d76ac492b1489dbef2b3@projects.linpro.no> References: <048.0b7218bd5544d76ac492b1489dbef2b3@projects.linpro.no> Message-ID: <057.0adc2e37b3551f0c3c4db12072b68918@projects.linpro.no> #130: Build of varnishhist, varnishstat and varnishtop fails with gcc 4.2.0 -------------------------+-------------------------------------------------- Reporter: cs | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Varnish 1.1.1 Component: varnishhist | Version: 1.1 Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by des): * status: assigned => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:16:27 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:16:27 -0000 Subject: [Varnish] #131: Target 'install-data-local' in Makefile.in doesn't honor any $DESTDIR In-Reply-To: <048.e4e080fad0630b81653aec71dbdba105@projects.linpro.no> References: <048.e4e080fad0630b81653aec71dbdba105@projects.linpro.no> Message-ID: <057.751bf88a1565836fb022c2008f622910@projects.linpro.no> #131: Target 'install-data-local' in Makefile.in doesn't honor any $DESTDIR --------------------+------------------------------------------------------- Reporter: cs | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Varnish 1.1.1 Component: build | Version: 1.1 Severity: normal | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by des): * status: assigned => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:17:18 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:17:18 -0000 Subject: [Varnish] #135: default.vcl out of sync In-Reply-To: <052.c196e75db5c13b3f37ec0b3a55dd4ad7@projects.linpro.no> References: <052.c196e75db5c13b3f37ec0b3a55dd4ad7@projects.linpro.no> Message-ID: <061.de71ce6881a5b0011eb97fb730807403@projects.linpro.no> #135: default.vcl out of sync ---------------------------+------------------------------------------------ Reporter: anders | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: documentation | Version: 1.1 Severity: normal | Resolution: fixed Keywords: default.vcl | ---------------------------+------------------------------------------------ Changes (by des): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:17:44 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:17:44 -0000 Subject: [Varnish] #145: Issues whild loading VCL code on the fly In-Reply-To: <052.cbf0da58c87c745a45933c736d50eec2@projects.linpro.no> References: <052.cbf0da58c87c745a45933c736d50eec2@projects.linpro.no> Message-ID: <061.e0e90d636a4d7374b1d9623d4f2e9528@projects.linpro.no> #145: Issues whild loading VCL code on the fly -------------------------------+-------------------------------------------- Reporter: anders | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: 1.1 Severity: normal | Resolution: Keywords: varnishd load VCL | -------------------------------+-------------------------------------------- Changes (by des): * owner: phk => des * status: new => assigned -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:19:14 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:19:14 -0000 Subject: [Varnish] #109: Backend did not respond. Guru Meditation: In-Reply-To: <056.6ca93e87d93a2a3947ee0f5c3c336ef0@projects.linpro.no> References: <056.6ca93e87d93a2a3947ee0f5c3c336ef0@projects.linpro.no> Message-ID: <065.6d38fda185f6c6e1535db6caad1e9907@projects.linpro.no> #109: Backend did not respond. Guru Meditation: ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: phk Type: task | Status: closed Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: 1.0.4 Severity: normal | Resolution: invalid Keywords: | ------------------------+--------------------------------------------------- Changes (by des): * status: new => closed * resolution: => invalid Comment: The ticket system is for bugs. Use the mailing lists for support questions. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:20:32 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:20:32 -0000 Subject: [Varnish] #129: POST request with pipe method not fully working in trunk In-Reply-To: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> References: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> Message-ID: <060.d7bbc562f7d8d7fb40d0d207e6e69db6@projects.linpro.no> #129: POST request with pipe method not fully working in trunk ----------------------+----------------------------------------------------- Reporter: jpulz | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * version: trunk => 1.1 * severity: normal => major * milestone: => Varnish 1.1.1 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:21:32 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:21:32 -0000 Subject: [Varnish] #50: Needs curses to successfull compile In-Reply-To: <052.c54bb15239ce42ff95bedd59d1d56c96@projects.linpro.no> References: <052.c54bb15239ce42ff95bedd59d1d56c96@projects.linpro.no> Message-ID: <061.921c3aca25c638d0f4504b9959fc252c@projects.linpro.no> #50: Needs curses to successfull compile ---------------------+------------------------------------------------------ Reporter: airmax | Owner: des Type: defect | Status: closed Priority: lowest | Milestone: Component: build | Version: 1.0 Severity: trivial | Resolution: fixed Keywords: | ---------------------+------------------------------------------------------ Changes (by des): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:21:44 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:21:44 -0000 Subject: [Varnish] #96: Varnishstat core-dumps if temp-file does not exist In-Reply-To: <061.583ed9306a620c47df1c385eecb804bd@projects.linpro.no> References: <061.583ed9306a620c47df1c385eecb804bd@projects.linpro.no> Message-ID: <070.db2cf6b8e289bae09be985b52ad4fc92@projects.linpro.no> #96: Varnishstat core-dumps if temp-file does not exist -----------------------------+---------------------------------------------- Reporter: anders at fupp.net | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishstat | Version: 1.0 Severity: normal | Resolution: fixed Keywords: | -----------------------------+---------------------------------------------- Changes (by des): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:23:02 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:23:02 -0000 Subject: [Varnish] #85: High number of "worker threads not created" and "overflowed work requests" In-Reply-To: <051.435325394d2dbeeb4c75c0a351e2820b@projects.linpro.no> References: <051.435325394d2dbeeb4c75c0a351e2820b@projects.linpro.no> Message-ID: <060.fe103584c93f2a143fdf4fa50540e4a7@projects.linpro.no> #85: High number of "worker threads not created" and "overflowed work requests" ----------------------+----------------------------------------------------- Reporter: Thias | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 1.0 Severity: normal | Resolution: wontfix Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: new => closed * resolution: => wontfix -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:26:34 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:26:34 -0000 Subject: [Varnish] #107: Varnish 1.0.4 RPM for RHEL 4 has broken init.d script In-Reply-To: <055.e90ca9c6b10a7688d0f4061bc41da518@projects.linpro.no> References: <055.e90ca9c6b10a7688d0f4061bc41da518@projects.linpro.no> Message-ID: <064.0f9eeca0da7a28c8685a06cebe4d9f21@projects.linpro.no> #107: Varnish 1.0.4 RPM for RHEL 4 has broken init.d script -----------------------+---------------------------------------------------- Reporter: dstoliker | Owner: ingvar Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | -----------------------+---------------------------------------------------- Changes (by des): * status: new => closed * resolution: => fixed Comment: The patch was committed in r1477, although the commit message doesn't mention it. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:26:52 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:26:52 -0000 Subject: [Varnish] #108: varnish start didnt work In-Reply-To: <056.838996d189003c2dd5e919631172bfcc@projects.linpro.no> References: <056.838996d189003c2dd5e919631172bfcc@projects.linpro.no> Message-ID: <065.28efaad88a7d041b8ec2d041602fe9ca@projects.linpro.no> #108: varnish start didnt work ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Varnish 1.0.4 Component: packaging | Version: 1.0.4 Severity: normal | Resolution: duplicate Keywords: | ------------------------+--------------------------------------------------- Changes (by des): * status: new => closed * resolution: => duplicate -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:27:19 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:27:19 -0000 Subject: [Varnish] #117: Mac OS X: Running varnishd results in Assert error in mgt_CallCc(), mgt_vcc.c line 222 In-Reply-To: <048.aa559d5bd4edda6a4d13bc3d880bcb57@projects.linpro.no> References: <048.aa559d5bd4edda6a4d13bc3d880bcb57@projects.linpro.no> Message-ID: <057.c207c1f96a86369ab407be7c2aae7552@projects.linpro.no> #117: Mac OS X: Running varnishd results in Assert error in mgt_CallCc(), mgt_vcc.c line 222 ----------------------+----------------------------------------------------- Reporter: oh | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: 1.0.4 Severity: normal | Resolution: Keywords: mac os x | ----------------------+----------------------------------------------------- Changes (by des): * owner: phk => des * status: new => assigned -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:27:24 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:27:24 -0000 Subject: [Varnish] #117: Mac OS X: Running varnishd results in Assert error in mgt_CallCc(), mgt_vcc.c line 222 In-Reply-To: <048.aa559d5bd4edda6a4d13bc3d880bcb57@projects.linpro.no> References: <048.aa559d5bd4edda6a4d13bc3d880bcb57@projects.linpro.no> Message-ID: <057.1ea50982abf238a4e311bc1efac4ee8a@projects.linpro.no> #117: Mac OS X: Running varnishd results in Assert error in mgt_CallCc(), mgt_vcc.c line 222 ----------------------+----------------------------------------------------- Reporter: oh | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.0.4 Severity: normal | Resolution: Keywords: mac os x | ----------------------+----------------------------------------------------- Changes (by des): * milestone: => Varnish 1.1.1 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:27:37 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:27:37 -0000 Subject: [Varnish] #59: need a small admin utility In-Reply-To: <051.904388fce4369cf2310fdd263b1953aa@projects.linpro.no> References: <051.904388fce4369cf2310fdd263b1953aa@projects.linpro.no> Message-ID: <060.6be2960a442b93ccc158376cc91e6faf@projects.linpro.no> #59: need a small admin utility ----------------------+----------------------------------------------------- Reporter: perbu | Owner: phk Type: defect | Status: closed Priority: low | Milestone: Component: varnishd | Version: Severity: minor | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:28:20 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:28:20 -0000 Subject: [Varnish] #95: Log entries mixed up with -o In-Reply-To: <052.abb41c208e73e9bb9ad4bfab7cec914b@projects.linpro.no> References: <052.abb41c208e73e9bb9ad4bfab7cec914b@projects.linpro.no> Message-ID: <061.b4d90e25539e45fb6debfd648a4e9d16@projects.linpro.no> #95: Log entries mixed up with -o ------------------------+--------------------------------------------------- Reporter: anders | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: varnishlog | Version: Severity: normal | Resolution: fixed Keywords: | ------------------------+--------------------------------------------------- Changes (by des): * status: assigned => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:42:08 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:42:08 -0000 Subject: [Varnish] #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash In-Reply-To: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> References: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> Message-ID: <061.8087264a5900a35c4d0891911d240906@projects.linpro.no> #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash -----------------------------------------------+---------------------------- Reporter: anders | Owner: phk Type: defect | Status: reopened Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump VRT_l_req_hash | -----------------------------------------------+---------------------------- Comment (by des): Anders, can you confirm that r1805 fixes this? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 13:42:41 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 13:42:41 -0000 Subject: [Varnish] #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash In-Reply-To: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> References: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> Message-ID: <061.682b5626fba28bc04786e32f8fe42afc@projects.linpro.no> #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash -----------------------------------------------+---------------------------- Reporter: anders | Owner: phk Type: defect | Status: reopened Priority: high | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump VRT_l_req_hash | -----------------------------------------------+---------------------------- Changes (by des): * milestone: => Varnish 1.1.1 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 14:09:15 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 14:09:15 -0000 Subject: [Varnish] #17: NCSA-style logger In-Reply-To: <049.bec763feba541c844f27e6c027664417@projects.linpro.no> References: <049.bec763feba541c844f27e6c027664417@projects.linpro.no> Message-ID: <058.7a594d087c8ab6544c851de875fbc527@projects.linpro.no> #17: NCSA-style logger -------------------------+-------------------------------------------------- Reporter: des | Owner: ab Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishlog | Version: trunk Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by des): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 14:09:33 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 14:09:33 -0000 Subject: [Varnish] #90: Update VCL documentation In-Reply-To: <049.a13066ae7aef9a6f6d9a38703f7c9406@projects.linpro.no> References: <049.a13066ae7aef9a6f6d9a38703f7c9406@projects.linpro.no> Message-ID: <058.6cc16c26aea28a3bb214d17b4d4044c1@projects.linpro.no> #90: Update VCL documentation ---------------------------+------------------------------------------------ Reporter: des | Owner: des Type: documentation | Status: closed Priority: high | Milestone: Component: documentation | Version: trunk Severity: normal | Resolution: fixed Keywords: | ---------------------------+------------------------------------------------ Changes (by des): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 14:10:07 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 14:10:07 -0000 Subject: [Varnish] #55: varnish stops responding with apache keepalive On In-Reply-To: <049.210f15126f587d48d25888bbf845f087@projects.linpro.no> References: <049.210f15126f587d48d25888bbf845f087@projects.linpro.no> Message-ID: <058.74d631e7a86a64185828ea779f687ecb@projects.linpro.no> #55: varnish stops responding with apache keepalive On -----------------------+---------------------------------------------------- Reporter: ced | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: major | Resolution: Keywords: Keepalive | -----------------------+---------------------------------------------------- Changes (by des): * owner: phk => des * status: new => assigned Comment: This is believed to have been fixed, but needs testing. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 14:10:38 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 14:10:38 -0000 Subject: [Varnish] #10: (regression-)testing In-Reply-To: <049.6dab28c6db4b78182c7231c0398c5b30@projects.linpro.no> References: <049.6dab28c6db4b78182c7231c0398c5b30@projects.linpro.no> Message-ID: <058.28cdc37630de36e1143c4b669c288721@projects.linpro.no> #10: (regression-)testing ----------------------+----------------------------------------------------- Reporter: des | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 14:11:24 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 14:11:24 -0000 Subject: [Varnish] #16: top clients viewer In-Reply-To: <049.435bd406576792c306b1dfe4d7ef1249@projects.linpro.no> References: <049.435bd406576792c306b1dfe4d7ef1249@projects.linpro.no> Message-ID: <058.3d66fec938def5ab85aee9dfb2ca1607@projects.linpro.no> #16: top clients viewer -------------------------+-------------------------------------------------- Reporter: des | Owner: phk Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishlog | Version: trunk Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by des): * status: new => closed * resolution: => fixed Comment: {{{varnishtop(1)}}} can do this. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 14:11:55 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 14:11:55 -0000 Subject: [Varnish] #18: Improved varnishstat In-Reply-To: <049.4e8af1a7f13ff2a63ac582073a754c74@projects.linpro.no> References: <049.4e8af1a7f13ff2a63ac582073a754c74@projects.linpro.no> Message-ID: <058.c09a26108400685859846f3374dcc6b2@projects.linpro.no> #18: Improved varnishstat -------------------------+-------------------------------------------------- Reporter: des | Owner: phk Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishstat | Version: trunk Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by des): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 14:29:48 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 14:29:48 -0000 Subject: [Varnish] #27: make workspace tweakable In-Reply-To: <049.ec5fda2dd7fd99c9c870e9b86d6d46ee@projects.linpro.no> References: <049.ec5fda2dd7fd99c9c870e9b86d6d46ee@projects.linpro.no> Message-ID: <058.164e106ca8304cc0747bd0e43fcfe5d0@projects.linpro.no> #27: make workspace tweakable -------------------------+-------------------------------------------------- Reporter: phk | Owner: phk Type: enhancement | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by des): Can this be closed? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 14:36:36 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 14:36:36 -0000 Subject: [Varnish] #35: Support for external error documents In-Reply-To: <049.f5a4682a77c16d18dc89350f88936431@projects.linpro.no> References: <049.f5a4682a77c16d18dc89350f88936431@projects.linpro.no> Message-ID: <058.ca5b50b051f21a876ee591cad8136eb1@projects.linpro.no> #35: Support for external error documents -------------------------+-------------------------------------------------- Reporter: des | Owner: des Type: enhancement | Status: assigned Priority: normal | Milestone: Varnish 2.0 Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by des): * owner: phk => des * status: new => assigned -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 14:37:19 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 14:37:19 -0000 Subject: [Varnish] #40: AC_REPLACE_FUNCS In-Reply-To: <049.104462c0cfcef141bb4b7b6cfec0a9e9@projects.linpro.no> References: <049.104462c0cfcef141bb4b7b6cfec0a9e9@projects.linpro.no> Message-ID: <058.b6f7739ee5522aed0216ef62332d1acc@projects.linpro.no> #40: AC_REPLACE_FUNCS -------------------------+-------------------------------------------------- Reporter: des | Owner: des Type: enhancement | Status: closed Priority: normal | Milestone: Varnish 2.0 Component: build | Version: trunk Severity: normal | Resolution: wontfix Keywords: | -------------------------+-------------------------------------------------- Changes (by des): * status: new => closed * resolution: => wontfix -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 14:39:59 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 14:39:59 -0000 Subject: [Varnish] #64: Overflow in varnishstat In-Reply-To: <058.6d128666aadcee84f53059da3db9a891@projects.linpro.no> References: <058.6d128666aadcee84f53059da3db9a891@projects.linpro.no> Message-ID: <067.2abb737af7148ee006b8f8f68243c63b@projects.linpro.no> #64: Overflow in varnishstat --------------------------+------------------------------------------------- Reporter: ay at linpro.no | Owner: phk Type: task | Status: new Priority: normal | Milestone: Component: varnishstat | Version: trunk Severity: normal | Resolution: Keywords: overflow | --------------------------+------------------------------------------------- Comment (by des): Does this still occur with newer versions? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 14:42:18 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 14:42:18 -0000 Subject: [Varnish] #79: force nocache of objects In-Reply-To: <049.a3518e85c26a520766a361db8b671e92@projects.linpro.no> References: <049.a3518e85c26a520766a361db8b671e92@projects.linpro.no> Message-ID: <058.ed532f2e87f684d783efc3cb99dbc679@projects.linpro.no> #79: force nocache of objects ----------------------+----------------------------------------------------- Reporter: hmn | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: assigned => closed * resolution: => fixed Comment: You can simply check {{{obj.http.cache-control}}} in {{{vcl_fetch}}} and go to {{{pass}}} if it matches {{{"no-cache"}}}. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 14:43:22 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 14:43:22 -0000 Subject: [Varnish] #89: Cannot compile varnish on debian In-Reply-To: <050.16e0b8c9719396937acfbb04b757c94b@projects.linpro.no> References: <050.16e0b8c9719396937acfbb04b757c94b@projects.linpro.no> Message-ID: <059.121e68892203758aafd8c5c1a2a10953@projects.linpro.no> #89: Cannot compile varnish on debian --------------------+------------------------------------------------------- Reporter: naro | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: wontfix Keywords: | --------------------+------------------------------------------------------- Changes (by des): * status: new => closed * resolution: => wontfix Comment: {{{autogen.sh}}} will issue a warning if it detects that {{{automake}}} is older than 1.9. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 14:59:47 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 14:59:47 -0000 Subject: [Varnish] #76: vcl(7) still need some work In-Reply-To: <051.de7505c84171842c264ec2a1296d0a2d@projects.linpro.no> References: <051.de7505c84171842c264ec2a1296d0a2d@projects.linpro.no> Message-ID: <060.397c4575a09c4ee70d3933062c228706@projects.linpro.no> #76: vcl(7) still need some work ---------------------------+------------------------------------------------ Reporter: perbu | Owner: des Type: documentation | Status: closed Priority: normal | Milestone: Component: documentation | Version: trunk Severity: normal | Resolution: fixed Keywords: | ---------------------------+------------------------------------------------ Changes (by des): * status: new => closed * resolution: => fixed Comment: All of these are now documented in {{{vcl(7)}}}. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 15:03:43 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 15:03:43 -0000 Subject: [Varnish] #101: Arithmetic error in storage file auto-sizing In-Reply-To: <049.df4b37603cc8c1b5e9a7a87d4109d898@projects.linpro.no> References: <049.df4b37603cc8c1b5e9a7a87d4109d898@projects.linpro.no> Message-ID: <058.d0faf17e7a9512d97869d4ca213ccafb@projects.linpro.no> #101: Arithmetic error in storage file auto-sizing ----------------------+----------------------------------------------------- Reporter: des | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: new => closed * resolution: => fixed Comment: Fixed in r1794. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 15:05:06 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 15:05:06 -0000 Subject: [Varnish] #102: RES_WriteObj() does not send body for POST In-Reply-To: <049.0f1cd63b229c27c45e4086d98e976838@projects.linpro.no> References: <049.0f1cd63b229c27c45e4086d98e976838@projects.linpro.no> Message-ID: <058.7d9862fc283d58df24887ab0b68956ea@projects.linpro.no> #102: RES_WriteObj() does not send body for POST ----------------------+----------------------------------------------------- Reporter: des | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * owner: DES => des * status: new => assigned Comment: Fixed for now, but {{{sp->wantbody}}} should be controllable from VCL. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 15:12:00 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 15:12:00 -0000 Subject: [Varnish] #146: vcl(7) needs better description of obj.cacheable In-Reply-To: <052.54a04a091a986c2d2ff0800a707725b7@projects.linpro.no> References: <052.54a04a091a986c2d2ff0800a707725b7@projects.linpro.no> Message-ID: <061.f3a2dbc54702ec030caf107c10c27e85@projects.linpro.no> #146: vcl(7) needs better description of obj.cacheable ---------------------------+------------------------------------------------ Reporter: anders | Owner: des Type: documentation | Status: closed Priority: normal | Milestone: Component: documentation | Version: trunk Severity: normal | Resolution: duplicate Keywords: vcl man page | ---------------------------+------------------------------------------------ Changes (by des): * status: new => closed * resolution: => duplicate Comment: Duplicate of #76. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 15:14:02 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 15:14:02 -0000 Subject: [Varnish] #29: VCL unload/discard leaks In-Reply-To: <049.a87c2081704d3c7c50b84bc2034e194e@projects.linpro.no> References: <049.a87c2081704d3c7c50b84bc2034e194e@projects.linpro.no> Message-ID: <058.87043e202b2a7a57b3913edae8a344cf@projects.linpro.no> #29: VCL unload/discard leaks ----------------------+----------------------------------------------------- Reporter: phk | Owner: phk Type: defect | Status: new Priority: low | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by des): I believe this has been fixed? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 17:32:41 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 17:32:41 -0000 Subject: [Varnish] #125: exit, quit command in telnet interface. In-Reply-To: <051.9cead11972a3e74d718d7abf4c4982f0@projects.linpro.no> References: <051.9cead11972a3e74d718d7abf4c4982f0@projects.linpro.no> Message-ID: <060.a7233f9260b4a0fe064527557f777197@projects.linpro.no> #125: exit, quit command in telnet interface. -------------------------+-------------------------------------------------- Reporter: tiamo | Owner: phk Type: enhancement | Status: closed Priority: lowest | Milestone: Component: varnishd | Version: trunk Severity: trivial | Resolution: wontfix Keywords: | -------------------------+-------------------------------------------------- Changes (by des): * status: new => closed * resolution: => wontfix Comment: Just close the connection. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 22:19:37 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 22:19:37 -0000 Subject: [Varnish] #147: compile errors Message-ID: <052.102b59a6eb9e355baa0a69351355078d@projects.linpro.no> #147: compile errors --------------------+------------------------------------------------------- Reporter: MrDigi | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: 1.1 Severity: normal | Keywords: --------------------+------------------------------------------------------- Under gcc 2.95 (I know its old but it can't be wrong that it compiles there, too :) no variable declaration in the "middle" of the code is allowed: --- vanish11old/bin/varnishadm/varnishadm.c Fri Jul 20 13:30:04 2007 +++ varnish-1.1/bin/varnishadm/varnishadm.c Thu Aug 9 23:37:22 2007 @@ -51,6 +51,7 @@ struct vss_addr **ta; char *addr, *port; int i, n; + int sock; long status, bytes; char *answer = NULL; char buf[13]; @@ -65,7 +66,7 @@ exit(2); } - int sock = VSS_connect(ta[0]); + sock = VSS_connect(ta[0]); for (i = 0; i < n; ++i) { free(ta[i]); --- vanish11old/bin/varnishd/storage_file.c Fri Jul 20 13:30:04 2007 +++ varnish-1.1/bin/varnishd/storage_file.c Thu Aug 9 23:45:08 2007 @@ -122,12 +122,14 @@ int i, explicit; off_t o; struct stat st; +#if defined(HAVE_SYS_MOUNT_H) || defined(HAVE_SYS_VFS_H) + struct statfs fsst; +#endif AN(sc); AZ(fstat(sc->fd, &st)); #if defined(HAVE_SYS_MOUNT_H) || defined(HAVE_SYS_VFS_H) - struct statfs fsst; AZ(fstatfs(sc->fd, &fsst)); #endif -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 9 23:26:36 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 09 Aug 2007 23:26:36 -0000 Subject: [Varnish] #148: -p user has no effect Message-ID: <053.b78d8d7dbca38cf53f966618bde7d18d@projects.linpro.no> #148: -p user has no effect ----------------------+----------------------------------------------------- Reporter: wichert | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.1 Severity: normal | Keywords: ----------------------+----------------------------------------------------- If I run this command: {{{ # varnishd -p user=nobody ... Error: Set Default for user = nobody Set Default for group = nogroup Unknown group }}} This is strange since the group for nobody is actually nobody on this system and does exist: {{{ # id nobody uid=99(nobody) gid=99(nobody) groups=99(nobody) }}} Explicitly passing in a group also has no effect: {{{ varnishd -p user=nobody -p group=nobody ... Error: Set Default for user = nobody Set Default for group = nogroup Unknown group }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 10 07:43:56 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 10 Aug 2007 07:43:56 -0000 Subject: [Varnish] #147: compile errors In-Reply-To: <052.102b59a6eb9e355baa0a69351355078d@projects.linpro.no> References: <052.102b59a6eb9e355baa0a69351355078d@projects.linpro.no> Message-ID: <061.b19151807ce0919f34dfb897801a0075@projects.linpro.no> #147: compile errors --------------------+------------------------------------------------------- Reporter: MrDigi | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Varnish 1.1.1 Component: build | Version: 1.1 Severity: normal | Resolution: Keywords: | --------------------+------------------------------------------------------- Changes (by des): * status: new => assigned * milestone: => Varnish 1.1.1 Comment: I don't normally bother with support for obsolete platforms, but this costs us nothing. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 10 14:39:47 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 10 Aug 2007 14:39:47 -0000 Subject: [Varnish] #129: POST request with pipe method not fully working in trunk In-Reply-To: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> References: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> Message-ID: <060.a7472260a7a5f1d587ecff281ba351fa@projects.linpro.no> #129: POST request with pipe method not fully working in trunk ----------------------+----------------------------------------------------- Reporter: jpulz | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by runa): Same thing happening here: 192.168.0.145 is my desktop 12 SessionOpen c 192.168.0.145 43634 ...stays there for 40 seconds or so... 12 SessionClose c pipe 12 ReqStart c 192.168.0.145 43634 353174938 12 RxRequest c POST 12 RxURL c /admin/login 12 RxProtocol c HTTP/1.1 12 RxHeader c Host: g6.local 12 RxHeader c User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.6) Gecko/20061201 Firefox/2.0.0.6 (Ubuntu-feisty) 12 RxHeader c Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 12 RxHeader c Accept-Language: en-us,en;q=0.5 12 RxHeader c Accept-Encoding: gzip,deflate 12 RxHeader c Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 12 RxHeader c Keep-Alive: 300 12 RxHeader c Connection: keep-alive 12 RxHeader c Referer: http://g6.local/admin/login 12 RxHeader c Cookie: PHPSESSID=b733860ba263afba028cd9ad32af0b49 12 RxHeader c Content-Type: application/x-www-form-urlencoded 12 RxHeader c Content-Length: 21 12 VCL_call c recv 12 VCL_return c pipe 12 VCL_call c pipe 12 VCL_return c pipe 12 Backend c 15 default 12 ReqEnd c 353174938 1186756485.901399374 1186756545.900139093 0.005095720 0.005486488 59.993253231 12 StatSess c 192.168.0.145 43634 nan 1 1 1 0 0 0 0 -- Ticket URL: Varnish The Varnish HTTP Accelerator From MAILER-DAEMON at projects.linpro.no Sun Aug 12 09:37:24 2007 From: MAILER-DAEMON at projects.linpro.no (Mail Delivery System) Date: Sun, 12 Aug 2007 11:37:24 +0200 (CEST) Subject: Undelivered Mail Returned to Sender Message-ID: <20070812093724.AC8281EC37C@projects.linpro.no> This is the mail system at host projects.linpro.no. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system : Host or domain name not found. Name service error for name=fup.net type=MX: Host not found, try again -------------- next part -------------- An embedded message was scrubbed... From: "Varnish" Subject: [Varnish] #143: Bogus message when loading a new VCL Date: Tue, 07 Aug 2007 08:51:16 -0000 Size: 2831 URL: From varnish-bugs at projects.linpro.no Mon Aug 13 07:38:57 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 07:38:57 -0000 Subject: [Varnish] #149: Can't Purge Message-ID: <053.5404c9d765f9edcccb61ed8a96c5809c@projects.linpro.no> #149: Can't Purge ----------------------+----------------------------------------------------- Reporter: greenad | Owner: phk Type: defect | Status: new Priority: high | Milestone: Varnish 1.0.4 Component: varnishd | Version: 1.0.4 Severity: major | Keywords: ----------------------+----------------------------------------------------- Hi, this is how I start varnishd: -a 0.0.0.0:8080 -f /etc/varnish/default.net.vcl -t 120s -s file,/var/lib/varnish/varnish_storage.bin,1g The caching works but I cant purge any files (VCL config is attached). #varnishncsa .... 127.0.0.1 - - [13/Aug/2007:09:34:20 +0200] "GET http://localhost:8080/users/7238558.jpg HTTP/1.0" 200 1657 "-" "Wget/1.10.2" ... telnet localhost 8080 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. PURGE http://localhost:8080/users/7238558.jpg HTTP/1.0 HTTP/1.1 404 Not Found Date: Mon, 13 Aug 2007 07:35:08 GMT Server: Varnish Connection: close Content-Type: text/html; charset=iso-8859-1 404 Not Found

Error 404 Not Found

Not in cache.

Guru Meditation:

XID: 385643636

Varnish Connection closed by foreign host. root at ubuntu60664m:/tmp# however the file is cached wget --server-response http://localhost:8080/users/7238558.jpg --09:35:00-- http://localhost:8080/users/7238558.jpg => `7238558.jpg.8' Resolving localhost... 127.0.0.1 Connecting to localhost|127.0.0.1|:8080... connected. HTTP request sent, awaiting response... HTTP/1.1 200 OK Expires: Thu, 16 Aug 2007 07:33:17 GMT Content-Type: image/jpeg Date: Mon, 13 Aug 2007 07:33:17 GMT Server: image_server Content-Length: 1657 X-Varnish: 385643448 385641021 Age: 103 Via: 1.1 varnish Length: 1,657 (1.6K) [image/jpeg] 100%[=====================================================================================================================>] 1,657 --.--K/s varnishd -V varnishd (varnish-1.0.4) Copyright (c) 2006 Linpro AS / Verdens Gang AS I cant use 1.1 since for some reason I never get a cache_miss ... it always return he same file (the first file it served after the varnishd restart). -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 07:52:25 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 07:52:25 -0000 Subject: [Varnish] #149: Can't Purge In-Reply-To: <053.5404c9d765f9edcccb61ed8a96c5809c@projects.linpro.no> References: <053.5404c9d765f9edcccb61ed8a96c5809c@projects.linpro.no> Message-ID: <062.b0df7ca3f201df040caf3f9c960d5567@projects.linpro.no> #149: Can't Purge ----------------------+----------------------------------------------------- Reporter: greenad | Owner: phk Type: defect | Status: closed Priority: high | Milestone: Varnish 1.0.4 Component: varnishd | Version: 1.0.4 Severity: major | Resolution: worksforme Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => worksforme Old description: > Hi, > > this is how I start varnishd: > > -a 0.0.0.0:8080 -f /etc/varnish/default.net.vcl -t 120s -s > file,/var/lib/varnish/varnish_storage.bin,1g > > The caching works but I cant purge any files (VCL config is attached). > > #varnishncsa > .... > 127.0.0.1 - - [13/Aug/2007:09:34:20 +0200] "GET > http://localhost:8080/users/7238558.jpg HTTP/1.0" 200 1657 "-" > "Wget/1.10.2" > ... > > > telnet localhost 8080 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > PURGE http://localhost:8080/users/7238558.jpg HTTP/1.0 > HTTP/1.1 404 Not Found > Date: Mon, 13 Aug 2007 07:35:08 GMT > Server: Varnish > Connection: close > Content-Type: text/html; charset=iso-8859-1 > > > > > 404 Not Found > > >

Error 404 Not Found

>

Not in cache.

>

Guru Meditation:

>

XID: 385643636

> Varnish > > > Connection closed by foreign host. > root at ubuntu60664m:/tmp# > > > however the file is cached > > wget --server-response http://localhost:8080/users/7238558.jpg > --09:35:00-- http://localhost:8080/users/7238558.jpg > => `7238558.jpg.8' > Resolving localhost... 127.0.0.1 > Connecting to localhost|127.0.0.1|:8080... connected. > HTTP request sent, awaiting response... > HTTP/1.1 200 OK > Expires: Thu, 16 Aug 2007 07:33:17 GMT > Content-Type: image/jpeg > Date: Mon, 13 Aug 2007 07:33:17 GMT > Server: image_server > Content-Length: 1657 > X-Varnish: 385643448 385641021 > Age: 103 > Via: 1.1 varnish > Length: 1,657 (1.6K) [image/jpeg] > > 100%[=====================================================================================================================>] > 1,657 --.--K/s > > > varnishd -V > varnishd (varnish-1.0.4) > Copyright (c) 2006 Linpro AS / Verdens Gang AS > > > I cant use 1.1 since for some reason I never get a cache_miss ... it > always return he same file (the first file it served after the varnishd > restart). New description: Hi, this is how I start varnishd: -a 0.0.0.0:8080 -f /etc/varnish/default.net.vcl -t 120s -s file,/var/lib/varnish/varnish_storage.bin,1g The caching works but I cant purge any files (VCL config is attached). {{{ #varnishncsa .... 127.0.0.1 - - [13/Aug/2007:09:34:20 +0200] "GET http://localhost:8080/users/7238558.jpg HTTP/1.0" 200 1657 "-" "Wget/1.10.2" ... telnet localhost 8080 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. PURGE http://localhost:8080/users/7238558.jpg HTTP/1.0 HTTP/1.1 404 Not Found Date: Mon, 13 Aug 2007 07:35:08 GMT Server: Varnish Connection: close Content-Type: text/html; charset=iso-8859-1 404 Not Found

Error 404 Not Found

Not in cache.

Guru Meditation:

XID: 385643636

Varnish Connection closed by foreign host. root at ubuntu60664m:/tmp# however the file is cached wget --server-response http://localhost:8080/users/7238558.jpg --09:35:00-- http://localhost:8080/users/7238558.jpg => `7238558.jpg.8' Resolving localhost... 127.0.0.1 Connecting to localhost|127.0.0.1|:8080... connected. HTTP request sent, awaiting response... HTTP/1.1 200 OK Expires: Thu, 16 Aug 2007 07:33:17 GMT Content-Type: image/jpeg Date: Mon, 13 Aug 2007 07:33:17 GMT Server: image_server Content-Length: 1657 X-Varnish: 385643448 385641021 Age: 103 Via: 1.1 varnish Length: 1,657 (1.6K) [image/jpeg] 100%[=====================================================================================================================>] 1,657 --.--K/s }}} varnishd -V varnishd (varnish-1.0.4) Copyright (c) 2006 Linpro AS / Verdens Gang AS I cant use 1.1 since for some reason I never get a cache_miss ... it always return he same file (the first file it served after the varnishd restart). Comment: You should not put the host part in the PURGE command, try this instead: {{{ PURGE /users/7238558.jpg }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 08:33:55 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 08:33:55 -0000 Subject: [Varnish] #149: Can't Purge In-Reply-To: <053.5404c9d765f9edcccb61ed8a96c5809c@projects.linpro.no> References: <053.5404c9d765f9edcccb61ed8a96c5809c@projects.linpro.no> Message-ID: <062.55f9476a2b9e949a2dc0c3a7851f04a0@projects.linpro.no> #149: Can't Purge ----------------------+----------------------------------------------------- Reporter: greenad | Owner: phk Type: defect | Status: reopened Priority: high | Milestone: Varnish 1.0.4 Component: varnishd | Version: 1.0.4 Severity: major | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by greenad): * status: closed => reopened * resolution: worksforme => Comment: I just tried that but it still says 404 :( root at ubuntu60664m:/tmp# telnet localhost 8080 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. '''PURGE /users/7238558.jpg HTTP/1.0 ''' HTTP/1.1 404 Not Found Date: Mon, 13 Aug 2007 08:32:24 GMT Server: Varnish Connection: close Content-Type: text/html; charset=iso-8859-1 404 Not Found

Error 404 Not Found

Not in cache.

Guru Meditation:

XID: 817904682

Varnish Connection closed by foreign host. root at ubuntu60664m:/tmp# telnet localhost 8080 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. PURGE /users/7238558.jpg HTTP/1.1 400 Bad Request Date: Mon, 13 Aug 2007 08:32:30 GMT Server: Varnish Connection: close Content-Type: text/html; charset=iso-8859-1 400 Bad Request

Error 400 Bad Request

Bad Request

Guru Meditation:

XID: 817904827

Varnish Connection closed by foreign host. root at ubuntu60664m:/tmp# -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 08:41:15 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 08:41:15 -0000 Subject: [Varnish] #149: Can't Purge In-Reply-To: <053.5404c9d765f9edcccb61ed8a96c5809c@projects.linpro.no> References: <053.5404c9d765f9edcccb61ed8a96c5809c@projects.linpro.no> Message-ID: <062.402fef407e7ceb1ddd2a2321fe2f2615@projects.linpro.no> #149: Can't Purge ----------------------+----------------------------------------------------- Reporter: greenad | Owner: phk Type: defect | Status: reopened Priority: lowest | Milestone: Varnish 1.0.4 Component: varnishd | Version: 1.0.4 Severity: minor | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * priority: high => lowest * severity: major => minor Comment: I see no evidence that Varnish doesn't do what it should do in this case, but will leave the ticket on lowest priority to give you a chance to prove otherwise. Be aware that with the PURGE implementation you use, you have to specify the URL exactly as it appears in the cache or you will get the behaviour you see here. I suggest you study the varnishlog output closely to see what goes wrong. Poul-Henning -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 08:45:17 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 08:45:17 -0000 Subject: [Varnish] #148: -p user has no effect In-Reply-To: <053.b78d8d7dbca38cf53f966618bde7d18d@projects.linpro.no> References: <053.b78d8d7dbca38cf53f966618bde7d18d@projects.linpro.no> Message-ID: <062.75f7dda4b59f99db6a6f3ce0f2fe1c0a@projects.linpro.no> #148: -p user has no effect ----------------------+----------------------------------------------------- Reporter: wichert | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 1.1 Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: This has since been fixed. The trouble is that "nobody" and "nogroup" is hardcoded in Varnish so before it ever gets to your -p argument, it fails trying to set the default values. I modified the code in -trunk a few days ago to not fail on the default values, but instead use a sensible fall-back strategy. -- Ticket URL: Varnish The Varnish HTTP Accelerator From MAILER-DAEMON at projects.linpro.no Mon Aug 13 09:14:06 2007 From: MAILER-DAEMON at projects.linpro.no (Mail Delivery System) Date: Mon, 13 Aug 2007 11:14:06 +0200 (CEST) Subject: Undelivered Mail Returned to Sender Message-ID: <20070813091406.699E11EC2B1@projects.linpro.no> This is the mail system at host projects.linpro.no. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system : Host or domain name not found. Name service error for name=fup.net type=MX: Host not found, try again -------------- next part -------------- An embedded message was scrubbed... From: "Varnish" Subject: Re: [Varnish] #143: Bogus message when loading a new VCL Date: Wed, 08 Aug 2007 08:49:27 -0000 Size: 2378 URL: From varnish-bugs at projects.linpro.no Mon Aug 13 09:18:10 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 09:18:10 -0000 Subject: [Varnish] #149: Can't Purge In-Reply-To: <053.5404c9d765f9edcccb61ed8a96c5809c@projects.linpro.no> References: <053.5404c9d765f9edcccb61ed8a96c5809c@projects.linpro.no> Message-ID: <062.3a147aaf6643daa1e7c58fa7cc54b0ab@projects.linpro.no> #149: Can't Purge ----------------------+----------------------------------------------------- Reporter: greenad | Owner: phk Type: defect | Status: reopened Priority: lowest | Milestone: Varnish 1.0.4 Component: varnishd | Version: 1.0.4 Severity: minor | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by greenad): Thanks for your fast reply. This time I tried - /thumbs/7238558.jpg wget --server-response http://localhost:8080/thumbs/7238558.jpg brings me this in varnishlog {{{ 11 SessionClose c Connection: close 11 StatSess c 10.10.23.46 55307 0 1 1 0 0 0 248 2796 11 SessionOpen c 10.10.23.46 55313 11 ReqStart c 10.10.23.46 55313 1701172779 11 RxRequest c GET 11 RxURL c /thumbs/9817923.jpg 11 RxProtocol c HTTP/1.0 11 RxHeader c Host: mogile 11 RxHeader c Connection: close 11 VCL_call c recv 11 VCL_return c lookup 11 VCL_call c hash 11 VCL_return c hash 11 Hit c 1701077913 11 VCL_call c hit 11 VCL_return c deliver 11 Length c 3797 11 TxProtocol c HTTP/1.1 11 TxStatus c 200 11 TxResponse c OK 11 TxHeader c Expires: Thu, 16 Aug 2007 08:04:15 GMT 11 TxHeader c Content-Type: image/jpeg 11 TxHeader c Date: Mon, 13 Aug 2007 08:04:15 GMT 11 TxHeader c Server: image_server 11 TxHeader c Content-Length: 3797 11 TxHeader c X-Varnish: 1701172779 1701077913 11 TxHeader c Age: 3517 11 TxHeader c Via: 1.1 varnish 11 TxHeader c Connection: close 11 ReqEnd c 1701172779 1186995772.802979000 1186995772.802999000 0.000014000 0.000006000 0.000014000 0 StatAddr 10.10.23.46 0 3967 106977 106977 0 0 44009 25892324 1491312716 11 SessionClose c Connection: close 11 StatSess c 10.10.23.46 55313 0 1 1 0 0 0 248 3797 12 ReqStart c 127.0.0.1 49985 1701172775 12 RxRequest c GET 12 RxURL c /thumbs/7238558.jpg 12 RxProtocol c HTTP/1.0 12 RxHeader c User-Agent: Wget/1.10.2 12 RxHeader c Accept: */* 12 RxHeader c Host: localhost:8080 12 RxHeader c Connection: Keep-Alive 12 VCL_call c recv 12 VCL_return c lookup 12 VCL_call c hash 12 VCL_return c hash 12 VCL_call c miss 12 VCL_return c fetch 17 BackendXID 1701172775 12 Backend c 17 default 17 TxRequest GET 17 TxURL /thumbs/7238558.jpg 17 TxProtocol HTTP/1.1 17 TxHeader User-Agent: Wget/1.10.2 17 TxHeader Accept: */* 17 TxHeader Host: localhost:8080 17 TxHeader X-Varnish: 1701172775 17 TxHeader X-Forwarded-for: 127.0.0.1 17 RxProtocol HTTP/1.1 17 RxStatus 200 17 RxResponse OK 17 RxHeader Expires: Thu, 16 Aug 2007 09:02:52 GMT 17 RxHeader Content-Type: image/jpeg 17 RxHeader Content-Length: 1657 17 RxHeader Date: Mon, 13 Aug 2007 09:02:52 GMT 17 RxHeader Server: image_server 12 ObjProtocol c HTTP/1.1 12 ObjStatus c 200 12 ObjResponse c OK 12 ObjHeader c Expires: Thu, 16 Aug 2007 09:02:52 GMT 12 ObjHeader c Content-Type: image/jpeg 12 ObjHeader c Date: Mon, 13 Aug 2007 09:02:52 GMT 12 ObjHeader c Server: image_server 12 ObjHeader c Content-Length: 1657 17 BackendReuse default 12 TTL c 1701172775 RFC 259200 1186995772 1186995772 1187254972 0 0 12 VCL_call c fetch 12 VCL_return c insert 12 Length c 1657 12 TxProtocol c HTTP/1.1 12 TxStatus c 200 12 TxResponse c OK 12 TxHeader c Expires: Thu, 16 Aug 2007 09:02:52 GMT 12 TxHeader c Content-Type: image/jpeg 12 TxHeader c Date: Mon, 13 Aug 2007 09:02:52 GMT 12 TxHeader c Server: image_server 12 TxHeader c Content-Length: 1657 12 TxHeader c X-Varnish: 1701172775 12 TxHeader c Age: 0 12 TxHeader c Via: 1.1 varnish 12 ReqEnd c 1701172775 1186995772.730346000 1186995772.807852000 0.000095000 0.077485000 0.000021000 0 StatAddr 127.0.0.1 0 3951 67 67 0 0 2 15430 12266767 12 HttpError c Received nothing 12 SessionClose c no request 12 StatSess c 127.0.0.1 49985 0 1 1 0 0 1 215 1657 11 SessionOpen c 10.10.23.46 55322 12 SessionOpen c 10.10.23.46 55345 12 ReqStart c 10.10.23.46 55345 1701172781 12 RxRequest c GET 12 RxURL c /thumbs/1417983.jpg 12 RxProtocol c HTTP/1.0 12 RxHeader c Host: mogile 12 RxHeader c Connection: close 12 VCL_call c recv 12 VCL_return c lookup 12 VCL_call c hash 12 VCL_return c hash 12 Hit c 1701077986 12 VCL_call c hit 12 VCL_return c deliver 12 Length c 2371 12 TxProtocol c HTTP/1.1 12 TxStatus c 200 12 TxResponse c OK 12 TxHeader c Expires: Thu, 16 Aug 2007 08:04:17 GMT 12 TxHeader c Content-Type: image/jpeg 12 TxHeader c Date: Mon, 13 Aug 2007 08:04:17 GMT 12 TxHeader c Server: image_server 12 TxHeader c Content-Length: 2371 12 TxHeader c X-Varnish: 1701172781 1701077986 12 TxHeader c Age: 3515 12 TxHeader c Via: 1.1 varnish 12 TxHeader c Connection: close 12 ReqEnd c 1701172781 1186995772.846569000 1186995772.846619000 0.002383000 0.000019000 0.000031000 0 StatAddr 10.10.23.46 0 3967 106978 106978 0 0 44009 25892572 1491315087 12 SessionClose c Connection: close 12 StatSess c 10.10.23.46 55345 0 1 1 0 0 0 248 2371 12 SessionOpen c 10.10.23.46 55348 13 SessionOpen c 10.10.23.46 55358 13 ReqStart c 10.10.23.46 55358 1701172783 }}} {{{ root at ubuntu60664m:/tmp# telnet localhost 8080 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. PURGE http://localhost:8080/thumbs/7238558.jpg HTTP/1.1 HTTP/1.1 404 Not Found Date: Mon, 13 Aug 2007 09:06:02 GMT Server: Varnish Connection: close Content-Type: text/html; charset=iso-8859-1 404 Not Found

Error 404 Not Found

Not in cache.

Guru Meditation:

XID: 1701177511

Varnish Connection closed by foreign host. root at ubuntu60664m:/tmp# }}} results in this log messages {{{ 12 SessionClose c Connection: close 12 StatSess c 10.10.23.46 45497 0 1 1 0 0 0 248 2150 11 VCL_acl c MATCH purge "127.0.0.1" 11 SessionClose c Not in cache. 11 ReqStart c 127.0.0.1 52982 1701177511 11 RxRequest c PURGE 11 RxURL c http://localhost:8080/thumbs/7238558.jpg 11 RxProtocol c HTTP/1.1 11 VCL_call c recv 11 VCL_return c lookup 11 VCL_call c hash 11 VCL_return c hash 11 VCL_call c miss 0 Debug "VCL_error(404, Not in cache.)" 11 VCL_return c error 11 TxStatus c 404 11 TxProtocol c HTTP/1.1 11 TxResponse c Not Found 11 ReqEnd c 1701177511 1186995962.226952000 1186995962.227023000 1.916852000 0.000014000 0.000057000 0 StatAddr 127.0.0.1 0 4141 72 72 0 0 2 16826 13010107 11 StatSess c 127.0.0.1 52982 2 1 1 0 0 0 472 0 11 SessionOpen c 10.10.23.46 45504 11 ReqStart c 10.10.23.46 45504 1701177512 }}} and finally this call {{{ telnet localhost 8080 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. PURGE /thumbs/7238558.jpg HTTP/1.1 HTTP/1.1 404 Not Found Date: Mon, 13 Aug 2007 09:06:31 GMT Server: Varnish Connection: close Content-Type: text/html; charset=iso-8859-1 404 Not Found

Error 404 Not Found

Not in cache.

Guru Meditation:

XID: 1701178248

Varnish Connection closed by foreign host. }}} results in this {{{ 0 StatAddr 10.10.23.46 0 4214 113159 113159 0 0 45798 27400262 1584580150 17 SessionClose c Connection: close 17 StatSess c 10.10.23.46 64445 0 1 1 0 0 0 248 2550 11 VCL_acl c MATCH purge "127.0.0.1" 11 SessionClose c Not in cache. 11 ReqStart c 127.0.0.1 53801 1701178972 11 RxRequest c PURGE 11 RxURL c /thumbs/7238558.jpg 11 RxProtocol c HTTP/1.1 11 VCL_call c recv 11 VCL_return c lookup 11 VCL_call c hash 11 VCL_return c hash 11 VCL_call c miss 0 Debug "VCL_error(404, Not in cache.)" 11 VCL_return c error 11 TxStatus c 404 11 TxProtocol c HTTP/1.1 11 TxResponse c Not Found 11 ReqEnd c 1701178972 1186996019.737754000 1186996019.737835000 0.598959000 0.000017000 0.000064000 0 StatAddr 127.0.0.1 0 4198 78 76 0 0 2 18470 13011764 11 StatSess c 127.0.0.1 53801 0 1 1 0 0 0 472 0 11 SessionOpen c 10.10.23.46 64454 11 ReqStart c 10.10.23.46 64454 1701178973 11 RxRequest c GET }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 10:10:47 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 10:10:47 -0000 Subject: [Varnish] #143: Bogus message when loading a new VCL In-Reply-To: <052.3353517d4976f703850e8c2c3b1ef36e@projects.linpro.no> References: <052.3353517d4976f703850e8c2c3b1ef36e@projects.linpro.no> Message-ID: <061.6bc10b2ba309da1d5b5fcb0d5f44e254@projects.linpro.no> #143: Bogus message when loading a new VCL -----------------------------------+---------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: closed Priority: low | Milestone: Component: varnishd | Version: 1.1 Severity: minor | Resolution: fixed Keywords: varnishd VCL vcl.load | -----------------------------------+---------------------------------------- Changes (by des): * cc: anders at fup.net (removed) * cc: anders at fupp.net (added) -- Ticket URL: Varnish The Varnish HTTP Accelerator From phk at phk.freebsd.dk Mon Aug 13 10:19:04 2007 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Mon, 13 Aug 2007 10:19:04 +0000 Subject: [Varnish] #149: Can't Purge In-Reply-To: Your message of "Mon, 13 Aug 2007 09:18:10 GMT." <062.3a147aaf6643daa1e7c58fa7cc54b0ab@projects.linpro.no> Message-ID: <93902.1187000344@critter.freebsd.dk> In message <062.3a147aaf6643daa1e7c58fa7cc54b0ab at projects.linpro.no>, "Varnish" writes: Now I see your trouble. > 11 RxRequest c GET > 11 RxURL c /thumbs/9817923.jpg > 11 RxProtocol c HTTP/1.0 > 11 RxHeader c Host: mogile Here you have a host header. > 11 RxRequest c PURGE > 11 RxURL c /thumbs/7238558.jpg > 11 RxProtocol c HTTP/1.1 And here you have none. Your PURGE must produce the same hash as the GET to find the same object. Try this: PURGE /thumbs/7238558.jpg /HTTP/1.0 Hosts: mogile -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk at FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From varnish-bugs at projects.linpro.no Mon Aug 13 11:07:16 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 11:07:16 -0000 Subject: [Varnish] #149: Can't Purge In-Reply-To: <053.5404c9d765f9edcccb61ed8a96c5809c@projects.linpro.no> References: <053.5404c9d765f9edcccb61ed8a96c5809c@projects.linpro.no> Message-ID: <062.8c172545b76b90c3d78344cadf76a037@projects.linpro.no> #149: Can't Purge ----------------------+----------------------------------------------------- Reporter: greenad | Owner: phk Type: defect | Status: reopened Priority: lowest | Milestone: Varnish 1.0.4 Component: varnishd | Version: 1.0.4 Severity: minor | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by greenad): solved it - the Host: was missing -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 13:55:08 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 13:55:08 -0000 Subject: [Varnish] #149: Can't Purge In-Reply-To: <053.5404c9d765f9edcccb61ed8a96c5809c@projects.linpro.no> References: <053.5404c9d765f9edcccb61ed8a96c5809c@projects.linpro.no> Message-ID: <062.21e7b7ad2620f09104aa920135a0c53a@projects.linpro.no> #149: Can't Purge ----------------------+----------------------------------------------------- Reporter: greenad | Owner: phk Type: defect | Status: closed Priority: lowest | Milestone: Varnish 1.0.4 Component: varnishd | Version: 1.0.4 Severity: minor | Resolution: worksforme Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: reopened => closed * resolution: => worksforme -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 19:21:23 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 19:21:23 -0000 Subject: [Varnish] #129: POST request with pipe method not fully working in trunk In-Reply-To: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> References: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> Message-ID: <060.fbfaae1887db0dd74f8ff5d7ec93fd3d@projects.linpro.no> #129: POST request with pipe method not fully working in trunk ----------------------+----------------------------------------------------- Reporter: jpulz | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: major | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: assigned => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 19:32:25 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 19:32:25 -0000 Subject: [Varnish] #147: compile errors In-Reply-To: <052.102b59a6eb9e355baa0a69351355078d@projects.linpro.no> References: <052.102b59a6eb9e355baa0a69351355078d@projects.linpro.no> Message-ID: <061.5c97f59e87a7a7b3f966fd18b3577827@projects.linpro.no> #147: compile errors --------------------+------------------------------------------------------- Reporter: MrDigi | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Varnish 1.1.1 Component: build | Version: 1.1 Severity: normal | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by des): * status: assigned => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 19:32:58 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 19:32:58 -0000 Subject: [Varnish] #144: Race in backend socket address replacement. In-Reply-To: <052.869b9c75015371cffe23335fba6d1ce5@projects.linpro.no> References: <052.869b9c75015371cffe23335fba6d1ce5@projects.linpro.no> Message-ID: <061.33b787554b35cb464a84054bf6644877@projects.linpro.no> #144: Race in backend socket address replacement. ---------------------------------------+------------------------------------ Reporter: anders | Owner: phk Type: defect | Status: assigned Priority: high | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump sig 10 | ---------------------------------------+------------------------------------ Changes (by des): * priority: normal => high * severity: normal => major * milestone: => Varnish 1.1.1 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 19:35:24 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 19:35:24 -0000 Subject: [Varnish] #68: Uptime in varnishstat -1 In-Reply-To: <048.98a3a6782d6f223ad2295fea101b26ef@projects.linpro.no> References: <048.98a3a6782d6f223ad2295fea101b26ef@projects.linpro.no> Message-ID: <057.f563b906e703f3b41cc13abe5edae3ef@projects.linpro.no> #68: Uptime in varnishstat -1 -------------------------+-------------------------------------------------- Reporter: ay | Owner: des Type: enhancement | Status: assigned Priority: normal | Milestone: Varnish 2.0 Component: varnishstat | Version: trunk Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by des): * owner: phk => des * status: new => assigned * version: => trunk * milestone: => Varnish 2.0 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 19:35:52 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 19:35:52 -0000 Subject: [Varnish] #73: Regression test syntax In-Reply-To: <049.7d69e176b10a32e964c7f5c98b4cf9ba@projects.linpro.no> References: <049.7d69e176b10a32e964c7f5c98b4cf9ba@projects.linpro.no> Message-ID: <058.e4622ea85a62287cce768d9dc882e01c@projects.linpro.no> #73: Regression test syntax --------------------+------------------------------------------------------- Reporter: phk | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: Severity: normal | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by des): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 19:36:25 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 19:36:25 -0000 Subject: [Varnish] #83: varnishd dos via telnet interface + listing of root password hash In-Reply-To: <063.22aaab6c731ef786292277d80d099bd8@projects.linpro.no> References: <063.22aaab6c731ef786292277d80d099bd8@projects.linpro.no> Message-ID: <072.a035f4ef7cc34fa28c58e570153abfdb@projects.linpro.no> #83: varnishd dos via telnet interface + listing of root password hash -------------------------------+-------------------------------------------- Reporter: kokanin at gmail.com | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: Severity: major | Resolution: wontfix Keywords: | -------------------------------+-------------------------------------------- Changes (by des): * status: new => closed * resolution: => wontfix -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 19:36:48 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 19:36:48 -0000 Subject: [Varnish] #33: Marketing Fodder: 18 syscalls per request In-Reply-To: <049.da802f9cf0be0d152621df5ed72a2b6e@projects.linpro.no> References: <049.da802f9cf0be0d152621df5ed72a2b6e@projects.linpro.no> Message-ID: <058.09ed58d5be116b70aa9f978d32d819de@projects.linpro.no> #33: Marketing Fodder: 18 syscalls per request ---------------------------+------------------------------------------------ Reporter: phk | Owner: des Type: documentation | Status: closed Priority: normal | Milestone: Component: documentation | Version: Severity: normal | Resolution: fixed Keywords: | ---------------------------+------------------------------------------------ Changes (by des): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 19:39:17 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 19:39:17 -0000 Subject: [Varnish] #44: DOC input: ReqEnd shmem record In-Reply-To: <049.218b66495d3acd2165b0035c91ca056c@projects.linpro.no> References: <049.218b66495d3acd2165b0035c91ca056c@projects.linpro.no> Message-ID: <058.efddf5e4c5641469e0d394eea5ee7ff1@projects.linpro.no> #44: DOC input: ReqEnd shmem record ---------------------------+------------------------------------------------ Reporter: phk | Owner: des Type: documentation | Status: closed Priority: normal | Milestone: Component: documentation | Version: Severity: normal | Resolution: fixed Keywords: | ---------------------------+------------------------------------------------ Changes (by des): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 19:39:35 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 19:39:35 -0000 Subject: [Varnish] #48: varnishd vanishes In-Reply-To: <051.d91f69eee84ed67344c36a89a8ddf269@projects.linpro.no> References: <051.d91f69eee84ed67344c36a89a8ddf269@projects.linpro.no> Message-ID: <060.99118e42c57fcb3151a9487fc57a103a@projects.linpro.no> #48: varnishd vanishes ----------------------+----------------------------------------------------- Reporter: perbu | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: assigned => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 19:40:40 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 19:40:40 -0000 Subject: [Varnish] #63: Overflow in varnishstat In-Reply-To: <048.ca21be17e3e9f37970369b71da7f62d1@projects.linpro.no> References: <048.ca21be17e3e9f37970369b71da7f62d1@projects.linpro.no> Message-ID: <057.fd65a8bfbce56c1ecb71c784a8a88249@projects.linpro.no> #63: Overflow in varnishstat ----------------------+----------------------------------------------------- Reporter: ay | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: Severity: normal | Resolution: duplicate Keywords: overflow | ----------------------+----------------------------------------------------- Changes (by des): * status: new => closed * resolution: => duplicate Old description: > We have a varnish (svn as of 2006-11-01). Varnishstat sometimes displays > the following. > > 00:00:21 > Hitrate ratio: 10 100 172 > Hitrate avg: 0.6604 0.7549 0.7820 > > 172 1.98 8.19 Client connections accepted > 548 2.97 26.10 Client requests received > 369 0.99 17.57 Cache hits > 10 0.99 0.48 Cache hits for pass > 168 0.99 8.00 Cache misses > 179 1.98 8.52 Backend connections initiated > 166 5.94 7.90 Backend connections recycles > 0 0.00 0.00 Backend connections unused > 56 0.00 2.67 N struct srcaddr > 17 -4.95 0.81 N active struct srcaddr > 39 0.00 1.86 N struct sess_mem > 26 -5.94 1.24 N struct sess > 175 1.98 8.33 N struct object > 175 1.98 8.33 N struct objecthead > 165 2.97 7.86 N struct smf > 2 0.00 0.10 N small free smf > 2 0.00 0.10 N large free smf > 13 0.00 0.62 N struct vbe_conn > 16 0.00 0.76 N worker threads > 16 0.00 0.76 N worker threads created > 0 0.00 0.00 N worker threads not created > 0 0.00 0.00 N worker threads limited > 0 0.00 0.00 N queued work requests > 16 0.00 0.76 N overflowed work requests > 0 0.00 0.00 N dropped work requests > 0 0.00 0.00 N expired objects > 0 0.00 0.00 N objects on deathrow > 0 0.00 0.00 HTTP header overflows > 152 1.98 7.24 Objects sent with sendfile > 200 1.98 9.52 Objects sent with write > 12961350068190840473 -5431088062805240832.00 -261209238358033856.00 Total > Sessions > 12961349728888425753 -5431088398748528640.00 -261209254515291712.00 Total > Requests > 12961349728888426744 -5431088398748527616.00 -261209254515291648.00 Total > pipe > 12961349728888425316 -5431088398748528640.00 -261209254515291744.00 Total > pass > 12961350703846000415 -5431087433443130368.00 -261209208088740544.00 Total > fetch > 12961349728888564487 -5431088398748525568.00 -261209254515285088.00 Total > header bytes > > 10715740 831115.60 510273.33 Total body bytes > 37 1.98 1.76 Session Closed > 0 0.00 0.00 Session Pipeline > 0 0.00 0.00 Session Read Ahead > 501 5.94 23.86 Session herd > 23144 475.25 1102.10 SHM records > 1125 31.68 53.57 SHM writes > 0 0.00 0.00 SHM MTX contention > > That looks like an integer overflow > > Runing CentOS release 4.4 on Xen 3.0 New description: We have a varnish (svn as of 2006-11-01). Varnishstat sometimes displays the following. {{{ 00:00:21 Hitrate ratio: 10 100 172 Hitrate avg: 0.6604 0.7549 0.7820 172 1.98 8.19 Client connections accepted 548 2.97 26.10 Client requests received 369 0.99 17.57 Cache hits 10 0.99 0.48 Cache hits for pass 168 0.99 8.00 Cache misses 179 1.98 8.52 Backend connections initiated 166 5.94 7.90 Backend connections recycles 0 0.00 0.00 Backend connections unused 56 0.00 2.67 N struct srcaddr 17 -4.95 0.81 N active struct srcaddr 39 0.00 1.86 N struct sess_mem 26 -5.94 1.24 N struct sess 175 1.98 8.33 N struct object 175 1.98 8.33 N struct objecthead 165 2.97 7.86 N struct smf 2 0.00 0.10 N small free smf 2 0.00 0.10 N large free smf 13 0.00 0.62 N struct vbe_conn 16 0.00 0.76 N worker threads 16 0.00 0.76 N worker threads created 0 0.00 0.00 N worker threads not created 0 0.00 0.00 N worker threads limited 0 0.00 0.00 N queued work requests 16 0.00 0.76 N overflowed work requests 0 0.00 0.00 N dropped work requests 0 0.00 0.00 N expired objects 0 0.00 0.00 N objects on deathrow 0 0.00 0.00 HTTP header overflows 152 1.98 7.24 Objects sent with sendfile 200 1.98 9.52 Objects sent with write 12961350068190840473 -5431088062805240832.00 -261209238358033856.00 Total Sessions 12961349728888425753 -5431088398748528640.00 -261209254515291712.00 Total Requests 12961349728888426744 -5431088398748527616.00 -261209254515291648.00 Total pipe 12961349728888425316 -5431088398748528640.00 -261209254515291744.00 Total pass 12961350703846000415 -5431087433443130368.00 -261209208088740544.00 Total fetch 12961349728888564487 -5431088398748525568.00 -261209254515285088.00 Total header bytes 10715740 831115.60 510273.33 Total body bytes 37 1.98 1.76 Session Closed 0 0.00 0.00 Session Pipeline 0 0.00 0.00 Session Read Ahead 501 5.94 23.86 Session herd 23144 475.25 1102.10 SHM records 1125 31.68 53.57 SHM writes 0 0.00 0.00 SHM MTX contention }}} That looks like an integer overflow Runing CentOS release 4.4 on Xen 3.0 Comment: Duplicate of #54. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 19:41:20 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 19:41:20 -0000 Subject: [Varnish] #65: Unbuffered loggin/Logging of spawning of children. In-Reply-To: <048.23a954e89d8c27c0671592470964914d@projects.linpro.no> References: <048.23a954e89d8c27c0671592470964914d@projects.linpro.no> Message-ID: <057.6b6183f09b144c3849beb0fb89f28825@projects.linpro.no> #65: Unbuffered loggin/Logging of spawning of children. -------------------------+-------------------------------------------------- Reporter: ay | Owner: des Type: enhancement | Status: assigned Priority: normal | Milestone: Varnish 2.0 Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by des): * version: => trunk * component: build => varnishd * milestone: => Varnish 2.0 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 19:42:10 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 19:42:10 -0000 Subject: [Varnish] #91: Crash - missing error handling code in mgt_vcc.c In-Reply-To: <058.45d2fd8c242fc87ce649f10d1cb0054f@projects.linpro.no> References: <058.45d2fd8c242fc87ce649f10d1cb0054f@projects.linpro.no> Message-ID: <067.221db0fe1dd46e4639a73b9b845ff318@projects.linpro.no> #91: Crash - missing error handling code in mgt_vcc.c --------------------------+------------------------------------------------- Reporter: esrever_otua | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: Severity: normal | Resolution: duplicate Keywords: | --------------------------+------------------------------------------------- Changes (by des): * status: new => closed * resolution: => duplicate -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 19:42:28 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 19:42:28 -0000 Subject: [Varnish] #91: Crash - missing error handling code in mgt_vcc.c In-Reply-To: <058.45d2fd8c242fc87ce649f10d1cb0054f@projects.linpro.no> References: <058.45d2fd8c242fc87ce649f10d1cb0054f@projects.linpro.no> Message-ID: <067.a4d062b34ac46994e069dadec196c9f4@projects.linpro.no> #91: Crash - missing error handling code in mgt_vcc.c --------------------------+------------------------------------------------- Reporter: esrever_otua | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 1.0.3 Severity: normal | Resolution: duplicate Keywords: | --------------------------+------------------------------------------------- Changes (by des): * version: => 1.0.3 * component: build => varnishd -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 19:45:00 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 19:45:00 -0000 Subject: [Varnish] #93: management interface crashes varnishd, coredump with signal 6 In-Reply-To: <050.3957960800ecbd874f5958db83bf051e@projects.linpro.no> References: <050.3957960800ecbd874f5958db83bf051e@projects.linpro.no> Message-ID: <059.98179e2351c8ee8f8c75625e05d10060@projects.linpro.no> #93: management interface crashes varnishd, coredump with signal 6 ----------------------+----------------------------------------------------- Reporter: kang | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: 1.0.3 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * owner: phk => des * status: new => assigned * version: => 1.0.3 Comment: Does this still occur with more recent versions? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 19:46:55 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 19:46:55 -0000 Subject: [Varnish] #99: returning pass from vcl_hit crashes the child In-Reply-To: <060.bc6d7510b64f29dc7608b3e7810cf372@projects.linpro.no> References: <060.bc6d7510b64f29dc7608b3e7810cf372@projects.linpro.no> Message-ID: <069.ac39795b9d9b642cfdc77caf8267f8a6@projects.linpro.no> #99: returning pass from vcl_hit crashes the child ----------------------------+----------------------------------------------- Reporter: denis at zeno.org | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: 1.0.3 Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by des): * status: new => assigned * version: => 1.0.3 * component: build => varnishd Comment: Does this still occur with more recent versions? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 19:47:48 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 19:47:48 -0000 Subject: [Varnish] #104: varnishncsa assertion fails sometimes In-Reply-To: <055.b2f86f700ad9117f39ea76f3dd2e454e@projects.linpro.no> References: <055.b2f86f700ad9117f39ea76f3dd2e454e@projects.linpro.no> Message-ID: <064.8550f306b11b96538a3ff31b50fea3e0@projects.linpro.no> #104: varnishncsa assertion fails sometimes -------------------------+-------------------------------------------------- Reporter: dirkgomez | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishncsa | Version: 1.0.3 Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by des): * status: new => assigned * version: => 1.0.3 Comment: Does this still occur with more recent versions? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 13 21:13:18 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 13 Aug 2007 21:13:18 -0000 Subject: [Varnish] #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash In-Reply-To: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> References: <052.111cd3af54dbcf458ccc9a8b8fb759f6@projects.linpro.no> Message-ID: <061.7a20651d9e236a5d5b7e60e22c7a94c5@projects.linpro.no> #141: Varnish 1.1 dies with missing errorhandling code in VRT_l_req_hash -----------------------------------------------+---------------------------- Reporter: anders | Owner: phk Type: defect | Status: reopened Priority: high | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump VRT_l_req_hash | -----------------------------------------------+---------------------------- Comment (by anders): I've only seen this happen once, so far. It might be hard to prove. At least, as long as the issues in #132, #142 and #144 still are unsolved, and which happens quite often, it's hard for me to check whether this bug is still happening and to keep Varnish in test-production at all. It takes a lot of time (24 hours) to build up the cache, and every time Varnish crashes, it has to start from scratch again. How are those bugs going? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 14 07:52:18 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 14 Aug 2007 07:52:18 -0000 Subject: [Varnish] #134: Varnishd dies on assert error in mgt_cli_callback when using varnishadm In-Reply-To: <052.8408d298c2a752aff22f14c2875325b3@projects.linpro.no> References: <052.8408d298c2a752aff22f14c2875325b3@projects.linpro.no> Message-ID: <061.df7a70a50fc54bc8f5570d9ddc903f13@projects.linpro.no> #134: Varnishd dies on assert error in mgt_cli_callback when using varnishadm -------------------------------------------+-------------------------------- Reporter: anders | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: normal | Resolution: Keywords: varnishd varnishadm core dump | -------------------------------------------+-------------------------------- Changes (by des): * owner: phk => des * status: new => assigned * milestone: => Varnish 1.1.1 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 14 21:48:47 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 14 Aug 2007 21:48:47 -0000 Subject: [Varnish] #150: Varnish 1.1 dies with assert error in wrk_do_one Message-ID: <052.1dd858a290f5a9442b47f881f4a14094@projects.linpro.no> #150: Varnish 1.1 dies with assert error in wrk_do_one ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: normal | Keywords: varnishd core dump wrk_do_one ----------------------+----------------------------------------------------- I am running Varnish 1.1 (from ports, with patches by des committed july 25th) in FreeBSD 6.2-RELEASE/amd64, on Intel hardware. Every now and then, Varnish dies with these error messages. Example 1: Child said (2, 4119): <used)) not true. errno = 0 (Unknown error: 0) Assert error in wrk_do_one(), cache_pool.c line 198: Condition(!isnan(w->used)) not true. errno = 0 (Unknown error: 0: 0) >> Cache child died pid=4119 status=0x6 Example 2: Child said (2, 5287): <used)) not true. errno = 32 (Broken pipe) >> Cache child died pid=5287 status=0x6 My VCL: {{{ backend foo { set backend.host = "80.91.1.1"; set backend.port = "80"; } backend bob { set backend.host = "80.91.1.2"; set backend.port = "80"; } backend foobar { set backend.host = "80.91.1.3"; set backend.port = "80"; } backend bar { set backend.host = "80.91.1.4"; set backend.port = "80"; } acl mypurge { "80.91.1.5"; } sub vcl_recv { if (req.http.host ~ "^(foo.aftenposten.no|bar.aftenposten.no|baz.aftenposten.no)$") { set req.backend = foo; } elsif (req.http.host ~ "^(bob.aftenposten.no)$") { set req.backend = bob; } elsif (req.http.host ~ "^(foobar.aftenposten.no|barbar.aftenposten.no|bazbaz.aftenposten.no)$") { set req.backend = foobar; } elsif (req.http.host ~ "^(www.bar.no|bar.no|www.baz.no|baz.no)$") { set req.backend = bar; } else { error 403 "Access denied. Contact cacheadmin at aftenposten.no if you have problems."; } if (req.request == "GET" || req.request == "HEAD") { if (req.http.Expect) { pipe; } if (req.http.Authenticate) { pass; } lookup; } elsif (req.request == "PURGE") { if (client.ip ~ aipurge) { lookup; } else { error 405 "Not allowed."; } } else { pass; } } sub vcl_miss { if (req.request == "PURGE") { error 404 "Not in cache."; } else { fetch; } } sub vcl_hit { if (req.request == "PURGE") { set obj.ttl = 0s; error 200 "Purged."; } else { deliver; } } sub vcl_fetch { if (obj.status == 404 || obj.status == 503) { pass; } if (obj.http.host ~ "^(foo.aftenposten.no|bar.aftenposten.no|baz.aftenposten.no)$") { if (obj.http.Set-Cookie) { remove obj.http.Set-Cookie; } } if (!obj.valid) { error; } if (!obj.cacheable) { pass; } insert; } }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Aug 15 13:07:47 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 15 Aug 2007 13:07:47 -0000 Subject: [Varnish] #150: Varnish 1.1 dies with assert error in wrk_do_one In-Reply-To: <052.1dd858a290f5a9442b47f881f4a14094@projects.linpro.no> References: <052.1dd858a290f5a9442b47f881f4a14094@projects.linpro.no> Message-ID: <061.1aa3aeb3bf31322ca73b7465518d3ae8@projects.linpro.no> #150: Varnish 1.1 dies with assert error in wrk_do_one -------------------------------------------+-------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: normal | Resolution: Keywords: varnishd core dump wrk_do_one | -------------------------------------------+-------------------------------- Comment (by anders): This problem still occurs with the 1.1 branch. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Aug 15 13:22:05 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 15 Aug 2007 13:22:05 -0000 Subject: [Varnish] #150: Varnish 1.1 dies with assert error in wrk_do_one In-Reply-To: <052.1dd858a290f5a9442b47f881f4a14094@projects.linpro.no> References: <052.1dd858a290f5a9442b47f881f4a14094@projects.linpro.no> Message-ID: <061.97dbc2d15799f1d8056b20642fbdb596@projects.linpro.no> #150: Varnish 1.1 dies with assert error in wrk_do_one -------------------------------------------+-------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: normal | Resolution: Keywords: varnishd core dump wrk_do_one | -------------------------------------------+-------------------------------- Comment (by teddy): Able to reproduce this every time with trunk version (1848) when giving varnish some load, and this on linux with kernel 2.6.17. -- Ticket URL: Varnish The Varnish HTTP Accelerator From MAILER-DAEMON at projects.linpro.no Sat Aug 18 11:27:24 2007 From: MAILER-DAEMON at projects.linpro.no (Mail Delivery System) Date: Sat, 18 Aug 2007 13:27:24 +0200 (CEST) Subject: Undelivered Mail Returned to Sender Message-ID: <20070818112724.682D11EC2B4@projects.linpro.no> This is the mail system at host projects.linpro.no. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system : Host or domain name not found. Name service error for name=fup.net type=MX: Host not found, try again -------------- next part -------------- An embedded message was scrubbed... From: "Varnish" Subject: Re: [Varnish] #143: Bogus message when loading a new VCL Date: Mon, 13 Aug 2007 10:10:47 -0000 Size: 2350 URL: From varnish-bugs at projects.linpro.no Sun Aug 19 17:03:55 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 19 Aug 2007 17:03:55 -0000 Subject: [Varnish] #150: Varnish 1.1 dies with assert error in wrk_do_one In-Reply-To: <052.1dd858a290f5a9442b47f881f4a14094@projects.linpro.no> References: <052.1dd858a290f5a9442b47f881f4a14094@projects.linpro.no> Message-ID: <061.d7814d16cd70db06dff6d5dcd216f9a6@projects.linpro.no> #150: Varnish 1.1 dies with assert error in wrk_do_one -------------------------------------------+-------------------------------- Reporter: anders | Owner: des Type: defect | Status: assigned Priority: high | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: normal | Resolution: Keywords: varnishd core dump wrk_do_one | -------------------------------------------+-------------------------------- Changes (by des): * owner: phk => des * status: new => assigned * milestone: => Varnish 1.1.1 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Aug 19 18:14:03 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 19 Aug 2007 18:14:03 -0000 Subject: [Varnish] #134: Varnishd dies on assert error in mgt_cli_callback when using varnishadm In-Reply-To: <052.8408d298c2a752aff22f14c2875325b3@projects.linpro.no> References: <052.8408d298c2a752aff22f14c2875325b3@projects.linpro.no> Message-ID: <061.5bd9778ef1134a7ccd452fa7cf355c76@projects.linpro.no> #134: Varnishd dies on assert error in mgt_cli_callback when using varnishadm -------------------------------------------+-------------------------------- Reporter: anders | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: normal | Resolution: fixed Keywords: varnishd varnishadm core dump | -------------------------------------------+-------------------------------- Changes (by des): * status: assigned => closed * resolution: => fixed Comment: Fixed in r1855 / r1856. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Aug 19 18:31:38 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 19 Aug 2007 18:31:38 -0000 Subject: [Varnish] #93: management interface crashes varnishd, coredump with signal 6 In-Reply-To: <050.3957960800ecbd874f5958db83bf051e@projects.linpro.no> References: <050.3957960800ecbd874f5958db83bf051e@projects.linpro.no> Message-ID: <059.6e9c256911396b0fcd5fcdfac510003b@projects.linpro.no> #93: management interface crashes varnishd, coredump with signal 6 ----------------------+----------------------------------------------------- Reporter: kang | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: 1.0.3 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by des): See #134. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Aug 19 18:31:44 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 19 Aug 2007 18:31:44 -0000 Subject: [Varnish] #93: management interface crashes varnishd, coredump with signal 6 In-Reply-To: <050.3957960800ecbd874f5958db83bf051e@projects.linpro.no> References: <050.3957960800ecbd874f5958db83bf051e@projects.linpro.no> Message-ID: <059.35a9d7ba696e0918b1f7578bc6fe0314@projects.linpro.no> #93: management interface crashes varnishd, coredump with signal 6 ----------------------+----------------------------------------------------- Reporter: kang | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 1.0.3 Severity: normal | Resolution: duplicate Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: assigned => closed * resolution: => duplicate -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 20 11:36:05 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 20 Aug 2007 11:36:05 -0000 Subject: [Varnish] #144: Race in backend socket address replacement. In-Reply-To: <052.869b9c75015371cffe23335fba6d1ce5@projects.linpro.no> References: <052.869b9c75015371cffe23335fba6d1ce5@projects.linpro.no> Message-ID: <061.6a9e9c4d5d99993af0922d0630570c06@projects.linpro.no> #144: Race in backend socket address replacement. ---------------------------------------+------------------------------------ Reporter: anders | Owner: phk Type: defect | Status: assigned Priority: high | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump sig 10 | ---------------------------------------+------------------------------------ Comment (by anders): Still seeing this bug with branch 1.1 up to date to commit 1846. Sent core-dumps and tarball of the binaries I use to phk & des. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 20 11:36:17 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 20 Aug 2007 11:36:17 -0000 Subject: [Varnish] #142: Varnishd core dumps because of segmentation violation In-Reply-To: <052.f72cc7589f3a3102380b0e8593362636@projects.linpro.no> References: <052.f72cc7589f3a3102380b0e8593362636@projects.linpro.no> Message-ID: <061.483f7fa7c8f90f4ec52abd3fc350d1da@projects.linpro.no> #142: Varnishd core dumps because of segmentation violation ---------------------------------------+------------------------------------ Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump sig 11 | ---------------------------------------+------------------------------------ Comment (by anders): Still seeing this bug with branch 1.1 up to date to commit 1846. Sent core-dumps and tarball of the binaries I use to phk & des. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 20 12:54:06 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 20 Aug 2007 12:54:06 -0000 Subject: [Varnish] #150: Varnish 1.1 dies with assert error in wrk_do_one In-Reply-To: <052.1dd858a290f5a9442b47f881f4a14094@projects.linpro.no> References: <052.1dd858a290f5a9442b47f881f4a14094@projects.linpro.no> Message-ID: <061.db8a82e362d6c529b1eb6934259a6430@projects.linpro.no> #150: Varnish 1.1 dies with assert error in wrk_do_one -------------------------------------------+-------------------------------- Reporter: anders | Owner: des Type: defect | Status: assigned Priority: high | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: normal | Resolution: Keywords: varnishd core dump wrk_do_one | -------------------------------------------+-------------------------------- Comment (by anders): Updated to branch 1.1 up to date to commit 1890. Running with debug on, I see: Child said (2, 13968): <wrk->used)) not true. errno = 0 (Unknown error: 0) Assert error in cnt_lookup(), cache_center.c line 491: Condition(!isnan(sp->wrk->used)) not true. errno = 0 (Unknown error: 0) Assert error in cnt_lookup(), cache_center.c line 491: Condition(!isnan(sp->wrk->used)) not true. errno = 0 (Unknown error: 0) >> Cache child died pid=13968 status=0x86 Let me know if you want the core-dump. Didn't get much out of the backtrace however. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 20 21:45:04 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 20 Aug 2007 21:45:04 -0000 Subject: [Varnish] #107: Varnish 1.0.4 RPM for RHEL 4 has broken init.d script In-Reply-To: <055.e90ca9c6b10a7688d0f4061bc41da518@projects.linpro.no> References: <055.e90ca9c6b10a7688d0f4061bc41da518@projects.linpro.no> Message-ID: <064.fb519e47a7e58f743af3d84297b71faf@projects.linpro.no> #107: Varnish 1.0.4 RPM for RHEL 4 has broken init.d script -----------------------+---------------------------------------------------- Reporter: dstoliker | Owner: ingvar Type: defect | Status: closed Priority: normal | Milestone: Varnish 1.1 Component: build | Version: 1.0.4 Severity: normal | Resolution: fixed Keywords: | -----------------------+---------------------------------------------------- Changes (by des): * version: trunk => 1.0.4 * milestone: => Varnish 1.1 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 21 09:24:35 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 21 Aug 2007 09:24:35 -0000 Subject: [Varnish] #150: Varnish 1.1 dies with assert error in wrk_do_one In-Reply-To: <052.1dd858a290f5a9442b47f881f4a14094@projects.linpro.no> References: <052.1dd858a290f5a9442b47f881f4a14094@projects.linpro.no> Message-ID: <061.1f8fc9b67570d8a98428f52603191478@projects.linpro.no> #150: Varnish 1.1 dies with assert error in wrk_do_one -------------------------------------------+-------------------------------- Reporter: anders | Owner: des Type: defect | Status: closed Priority: high | Milestone: Varnish 1.1.2 Component: varnishd | Version: 1.1 Severity: normal | Resolution: fixed Keywords: varnishd core dump wrk_do_one | -------------------------------------------+-------------------------------- Changes (by phk): * status: assigned => closed * resolution: => fixed Comment: Believed fixed by #1913 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 21 14:57:43 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 21 Aug 2007 14:57:43 -0000 Subject: [Varnish] #151: Varnish delivers always the same file Message-ID: <053.3a0b43fb8cbd05d6a3728876f7eb8f57@projects.linpro.no> #151: Varnish delivers always the same file ---------------------+------------------------------------------------------ Reporter: greenad | Owner: des Type: defect | Status: new Priority: high | Milestone: Component: build | Version: 1.1 Severity: blocker | Keywords: 1.1.1 ---------------------+------------------------------------------------------ Hi I am using Varnish 1.0.4 without any problems. But 1.1/1.1.1 behave strange - for some reasons they always deliver the first fetched file ... over and over again. starting varnish {{{ /usr/local/bin/varnishd -a 0.0.0.0:8080 -n /var/varnish -f /etc/varnish/default.net.vcl -t 120s -s file,/var/lib/varnish/varnish_storage.bin,10m }}} config {{{ acl purge { "127.0.0.1"; } backend default { set backend.host = "127.0.0.1"; set backend.port = "80"; } sub vcl_recv { if (req.request != "GET" && req.request != "HEAD") { if (req.request == "PURGE") { if (!client.ip ~ purge) { error 405 "Not allowed."; } lookup; } pipe; } if (req.http.Expect) { pipe; } if (req.http.Authenticate || req.http.Authorization) { pass; } lookup; } sub vcl_pipe { pipe; } sub vcl_pass { pass; } sub vcl_hash { hash; } sub vcl_hit { if (req.request == "PURGE") { set obj.ttl = 0s; error 200 "Purged."; } if (!obj.cacheable) { pass; } deliver; } sub vcl_miss { if (req.request == "PURGE") { error 404 "Not in cache."; } fetch; } sub vcl_fetch { if (req.http.Set-Cookie) { insert; } if (obj.ttl < 120s) { set obj.ttl = 120s; } if (!obj.valid) { error; } if (!obj.cacheable) { pass; } insert; } sub vcl_timeout { discard; } }}} varnishlog {{{ 11 SessionOpen c 89.59.113.78 61274 11 ReqStart c 89.59.113.78 61274 1832852093 11 RxRequest c GET 11 RxURL c /photos/100.jpg 11 RxProtocol c HTTP/1.1 11 RxHeader c Host: img.page.test:8080 11 RxHeader c User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 11 RxHeader c Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 11 RxHeader c Accept-Language: de-de,en-us;q=0.8,de;q=0.5,en;q=0.3 11 RxHeader c Accept-Encoding: gzip,deflate 11 RxHeader c Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 11 RxHeader c Keep-Alive: 300 11 RxHeader c Connection: keep-alive 11 RxHeader c Pragma: no-cache 11 RxHeader c Cache-Control: no-cache 11 VCL_call c recv 11 VCL_return c lookup 11 VCL_call c hash 11 VCL_return c hash 11 Hit c 1832852090 11 VCL_call c hit 11 VCL_return c deliver 11 Length c 185835 11 VCL_call c deliver 11 VCL_return c deliver 11 TxProtocol c HTTP/1.1 11 TxStatus c 200 11 TxResponse c OK 11 TxHeader c Expires: Fri, 24 Aug 2007 14:48:03 GMT 11 TxHeader c Content-Type: image/jpeg 11 TxHeader c Date: Tue, 21 Aug 2007 14:48:03 GMT 11 TxHeader c Server: image_server 11 TxHeader c Content-Length: 185835 11 TxHeader c X-Varnish: 1832852093 1832852090 11 TxHeader c Age: 91 11 TxHeader c Via: 1.1 varnish 11 TxHeader c Connection: keep-alive 11 ReqEnd c 1832852093 1187707778.423660994 1187707778.424011946 0.041718960 0.000022888 0.000328064 0 StatAddr 89.59.113.78 0 91 2 2 0 0 1 494 371670 0 CLI Rd ping 0 CLI Wr 0 200 PONG 1187707781 11 TxHeader c Connection: keep-alive 11 ReqEnd c 1832852094 1187707802.443674088 1187707802.444056034 0.091289043 0.000030994 0.000350952 0 StatAddr 89.59.113.78 0 115 3 3 0 0 1 748 557505 11 ReqStart c 89.59.113.78 61276 1832852095 11 RxRequest c GET 11 RxURL c /photos/6639575.jpg 11 RxProtocol c HTTP/1.1 11 RxHeader c Host: img.page.test:8080 11 RxHeader c User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 11 RxHeader c Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 11 RxHeader c Accept-Language: de-de,en-us;q=0.8,de;q=0.5,en;q=0.3 11 RxHeader c Accept-Encoding: gzip,deflate 11 RxHeader c Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 11 RxHeader c Keep-Alive: 300 11 RxHeader c Connection: keep-alive 11 VCL_call c recv 11 VCL_return c lookup 11 VCL_call c hash 11 VCL_return c hash 11 Hit c 1832852090 11 VCL_call c hit 11 VCL_return c deliver 11 Length c 185835 11 VCL_call c deliver 11 VCL_return c deliver 11 TxProtocol c HTTP/1.1 11 TxStatus c 200 11 TxResponse c OK 11 TxHeader c Expires: Fri, 24 Aug 2007 14:48:03 GMT 11 TxHeader c Content-Type: image/jpeg 11 TxHeader c Date: Tue, 21 Aug 2007 14:48:03 GMT 11 TxHeader c Server: image_server 11 TxHeader c Content-Length: 185835 11 TxHeader c X-Varnish: 1832852095 1832852090 11 TxHeader c Age: 116 11 TxHeader c Via: 1.1 varnish 11 TxHeader c Connection: keep-alive 11 ReqEnd c 1832852095 1187707803.618964911 1187707803.619365931 1.174908876 0.000022173 0.000378847 0 StatAddr 89.59.113.78 0 116 3 4 0 0 1 1002 743340 0 CLI Rd ping 0 CLI Wr 0 200 PONG 1187707805 11 SessionOpen c 89.59.113.78 61277 11 ReqStart c 89.59.113.78 61277 1832852096 11 RxRequest c GET 11 RxURL c /photos/6639575.jpg 11 RxProtocol c HTTP/1.1 11 RxHeader c Host: img.page.test:8080 11 RxHeader c User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 11 RxHeader c Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 11 RxHeader c Accept-Language: de-de,en-us;q=0.8,de;q=0.5,en;q=0.3 11 RxHeader c Accept-Encoding: gzip,deflate 11 RxHeader c Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 11 RxHeader c Keep-Alive: 300 11 RxHeader c Connection: keep-alive 11 RxHeader c Cache-Control: max-age=0 11 VCL_call c recv 11 VCL_return c lookup 11 VCL_call c hash 11 VCL_return c hash 11 Hit c 1832852090 11 VCL_call c hit 11 VCL_return c deliver 11 Length c 185835 11 VCL_call c deliver 11 VCL_return c deliver 11 TxProtocol c HTTP/1.1 11 TxStatus c 200 11 TxResponse c OK 11 TxHeader c Expires: Fri, 24 Aug 2007 14:48:03 GMT 11 TxHeader c Content-Type: image/jpeg 11 TxHeader c Date: Tue, 21 Aug 2007 14:48:03 GMT 11 TxHeader c Server: image_server 11 TxHeader c Content-Length: 185835 11 TxHeader c X-Varnish: 1832852096 1832852090 11 TxHeader c Age: 149 11 TxHeader c Via: 1.1 varnish 11 TxHeader c Connection: keep-alive 11 ReqEnd c 1832852096 1187707836.168909073 1187707836.169548035 0.123310089 0.000025988 0.000612974 0 StatAddr 89.59.113.78 0 149 4 5 0 0 1 1256 929175 0 CLI Rd ping 0 CLI Wr 0 200 PONG 1187707838 0 CLI Rd ping 0 CLI Wr 0 200 PONG 1187707841 11 SessionClose c timeout 11 StatSess c 89.59.113.78 61277 0 1 1 0 0 0 254 185835 11 SessionOpen c 89.59.113.78 61280 11 ReqStart c 89.59.113.78 61280 1832852097 11 RxRequest c GET 11 RxURL c /photos/2609215.jpg 11 RxProtocol c HTTP/1.1 11 RxHeader c Host: img.page.test:8080 11 RxHeader c User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 11 RxHeader c Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 11 RxHeader c Accept-Language: de-de,en-us;q=0.8,de;q=0.5,en;q=0.3 11 RxHeader c Accept-Encoding: gzip,deflate 11 RxHeader c Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 11 RxHeader c Keep-Alive: 300 11 RxHeader c Connection: keep-alive 11 VCL_call c recv 11 VCL_return c lookup 11 VCL_call c hash 11 VCL_return c hash 11 Hit c 1832852090 11 VCL_call c hit 11 VCL_return c deliver 11 Length c 185835 11 VCL_call c deliver 11 VCL_return c deliver 11 TxProtocol c HTTP/1.1 11 TxStatus c 200 11 TxResponse c OK 11 TxHeader c Expires: Fri, 24 Aug 2007 14:48:03 GMT 11 TxHeader c Content-Type: image/jpeg 11 TxHeader c Date: Tue, 21 Aug 2007 14:48:03 GMT 11 TxHeader c Server: image_server 11 TxHeader c Content-Length: 185835 11 TxHeader c X-Varnish: 1832852097 1832852090 11 TxHeader c Age: 185 11 TxHeader c Via: 1.1 varnish 11 TxHeader c Connection: keep-alive 11 ReqEnd c 1832852097 1187707872.356697083 1187707872.357018948 0.030522108 0.000023842 0.000298023 0 StatAddr 89.59.113.78 0 185 5 6 0 0 1 1510 1115010 }}} so matter what kind of GET request ... i always get back the content of 100.jpg (the first fetched file after varnish was started) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 21 15:33:12 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 21 Aug 2007 15:33:12 -0000 Subject: [Varnish] #151: Varnish delivers always the same file In-Reply-To: <053.3a0b43fb8cbd05d6a3728876f7eb8f57@projects.linpro.no> References: <053.3a0b43fb8cbd05d6a3728876f7eb8f57@projects.linpro.no> Message-ID: <062.3ff94a1f0350241ae951b771627155c3@projects.linpro.no> #151: Varnish delivers always the same file ----------------------+----------------------------------------------------- Reporter: greenad | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 1.1.1 Severity: normal | Resolution: invalid Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: new => closed * severity: blocker => normal * component: build => varnishd * priority: high => normal * version: 1.1 => 1.1.1 * keywords: 1.1.1 => * resolution: => invalid Comment: The ticket system is for bugs, not support questions. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 21 18:18:16 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 21 Aug 2007 18:18:16 -0000 Subject: [Varnish] #151: Varnish delivers always the same file In-Reply-To: <053.3a0b43fb8cbd05d6a3728876f7eb8f57@projects.linpro.no> References: <053.3a0b43fb8cbd05d6a3728876f7eb8f57@projects.linpro.no> Message-ID: <062.ce3760d2225bfaf21ac336855b3a6feb@projects.linpro.no> #151: Varnish delivers always the same file ----------------------+----------------------------------------------------- Reporter: greenad | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 1.1.1 Severity: normal | Resolution: invalid Keywords: | ----------------------+----------------------------------------------------- Comment (by greenad): i am just wondering since varnish 1.0.4 works wonderful with exact this config (besides the new -n command line parameter) ... so should i post again to the mailing list? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 23 18:47:14 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 23 Aug 2007 18:47:14 -0000 Subject: [Varnish] #152: Varnish 1.1.1 compile fails on Solaris 10 Message-ID: <053.a7b950c8b9db8b2dd5be8558033bb4aa@projects.linpro.no> #152: Varnish 1.1.1 compile fails on Solaris 10 ---------------------+------------------------------------------------------ Reporter: jimlane | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: ---------------------+------------------------------------------------------ I am trying to compile varnish 1.1.1 on Solaris 10. The configure script runs cleanly but the compile fails with these error messages: /bin/bash ../../libtool --tag=CC --mode=link /usr/local/bin/gcc -include config.h -g -O2 -o varnishadm varnishadm-varnishadm.o ../../lib/libvarnish/libvarnish.la ../../lib/libvarnishcompat/libvarnishcompat.la mkdir .libs /usr/local/bin/gcc -include config.h -g -O2 -o .libs/varnishadm varnishadm-varnishadm.o ../../lib/libvarnish/.libs/libvarnish.so -lrt ../../lib/libvarnishcompat/.libs/libvarnishcompat.so -R/usr/local/lib Undefined first referenced symbol in file bind ../../lib/libvarnish/.libs/libvarnish.so listen ../../lib/libvarnish/.libs/libvarnish.so socket ../../lib/libvarnish/.libs/libvarnish.so setsockopt ../../lib/libvarnish/.libs/libvarnish.so connect ../../lib/libvarnish/.libs/libvarnish.so getaddrinfo ../../lib/libvarnish/.libs/libvarnish.so freeaddrinfo ../../lib/libvarnish/.libs/libvarnish.so gai_strerror ../../lib/libvarnish/.libs/libvarnish.so ld: fatal: Symbol referencing errors. No output written to .libs/varnishadm collect2: ld returned 1 exit status I took all defaults on the configure and I'm using GCC 3.4.6 for the compile. It looks like I'm either missing a library or have a wrong version somewhere (I don't really understand what this message is trying to tell me). What am I doing wrong here? Regards, Jim Lane -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sat Aug 25 11:28:14 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sat, 25 Aug 2007 11:28:14 -0000 Subject: [Varnish] #153: Files are missing from the released tarball of varnis 1.1.1 Message-ID: <052.035b380a412468a9afb80d73437a5018@projects.linpro.no> #153: Files are missing from the released tarball of varnis 1.1.1 -----------------------+---------------------------------------------------- Reporter: bahner | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: packaging | Version: 1.1.1 Severity: normal | Keywords: -----------------------+---------------------------------------------------- Here is a diff of `ls` in the debian/-directory of tags/1.1.1 and the tarball: bahner at stat:0:~/src$ diff *.list 7d6 < files 10,16d8 < libvarnish-dev.dirs < libvarnish-dev.install < libvarnish.dirs < libvarnish.install < libvarnish.postinst.debhelper < libvarnish.postrm.debhelper < libvarnish.substvars 27d18 < varnish.dirs 30d20 < varnish.install 32,34d21 < varnish.manpages < varnish.postinst < varnish.postinst.debhelper 36,38d22 < varnish.postrm.debhelper < varnish.prerm.debhelper < varnish.substvars 40d23 < watch -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Aug 29 10:43:48 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 29 Aug 2007 10:43:48 -0000 Subject: [Varnish] #58: missing dependency In-Reply-To: <051.6cfb21e12027e836d6ea84ab583c0e6b@projects.linpro.no> References: <051.6cfb21e12027e836d6ea84ab583c0e6b@projects.linpro.no> Message-ID: <060.a8cd34d6e65888592f5ecef39a2daf16@projects.linpro.no> #58: missing dependency ----------------------------+----------------------------------------------- Reporter: perbu | Owner: bahner Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: dapper install | ----------------------------+----------------------------------------------- Changes (by des): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Aug 29 10:44:27 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 29 Aug 2007 10:44:27 -0000 Subject: [Varnish] #153: Files are missing from the released tarball of varnis 1.1.1 In-Reply-To: <052.035b380a412468a9afb80d73437a5018@projects.linpro.no> References: <052.035b380a412468a9afb80d73437a5018@projects.linpro.no> Message-ID: <061.c7f490c462b69cdea2cbc7af067a436e@projects.linpro.no> #153: Files are missing from the released tarball of varnis 1.1.1 -----------------------+---------------------------------------------------- Reporter: bahner | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Varnish 1.1.2 Component: packaging | Version: 1.1.1 Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Changes (by des): * status: new => assigned * milestone: => Varnish 1.1.2 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Aug 29 10:44:42 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 29 Aug 2007 10:44:42 -0000 Subject: [Varnish] #153: Files are missing from the released tarball of varnis 1.1.1 In-Reply-To: <052.035b380a412468a9afb80d73437a5018@projects.linpro.no> References: <052.035b380a412468a9afb80d73437a5018@projects.linpro.no> Message-ID: <061.9e00d8906ff9d8e6f770e6f06a6d3829@projects.linpro.no> #153: Files are missing from the released tarball of varnis 1.1.1 -----------------------+---------------------------------------------------- Reporter: bahner | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Varnish 1.1.2 Component: packaging | Version: 1.1.1 Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Old description: > Here is a diff of `ls` in the debian/-directory of tags/1.1.1 and the > tarball: > bahner at stat:0:~/src$ diff *.list > 7d6 > < files > 10,16d8 > < libvarnish-dev.dirs > < libvarnish-dev.install > < libvarnish.dirs > < libvarnish.install > < libvarnish.postinst.debhelper > < libvarnish.postrm.debhelper > < libvarnish.substvars > 27d18 > < varnish.dirs > 30d20 > < varnish.install > 32,34d21 > < varnish.manpages > < varnish.postinst > < varnish.postinst.debhelper > 36,38d22 > < varnish.postrm.debhelper > < varnish.prerm.debhelper > < varnish.substvars > 40d23 > < watch New description: Here is a diff of `ls` in the debian/-directory of tags/1.1.1 and the tarball: {{{ bahner at stat:0:~/src$ diff *.list 7d6 < files 10,16d8 < libvarnish-dev.dirs < libvarnish-dev.install < libvarnish.dirs < libvarnish.install < libvarnish.postinst.debhelper < libvarnish.postrm.debhelper < libvarnish.substvars 27d18 < varnish.dirs 30d20 < varnish.install 32,34d21 < varnish.manpages < varnish.postinst < varnish.postinst.debhelper 36,38d22 < varnish.postrm.debhelper < varnish.prerm.debhelper < varnish.substvars 40d23 < watch }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Aug 29 10:53:24 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 29 Aug 2007 10:53:24 -0000 Subject: [Varnish] #152: Varnish 1.1.1 compile fails on Solaris 10 In-Reply-To: <053.a7b950c8b9db8b2dd5be8558033bb4aa@projects.linpro.no> References: <053.a7b950c8b9db8b2dd5be8558033bb4aa@projects.linpro.no> Message-ID: <062.0bcaad1b8887df12b2769fcb0d033025@projects.linpro.no> #152: Varnish 1.1.1 compile fails on Solaris 10 ---------------------+------------------------------------------------------ Reporter: jimlane | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Varnish 2.0 release Component: build | Version: 1.1.1 Severity: normal | Resolution: Keywords: | ---------------------+------------------------------------------------------ Changes (by des): * status: new => assigned * version: trunk => 1.1.1 * milestone: => Varnish 2.0 release Old description: > I am trying to compile varnish 1.1.1 on Solaris 10. The configure script > runs cleanly but the compile fails with these error messages: > > /bin/bash ../../libtool --tag=CC --mode=link /usr/local/bin/gcc > -include config.h -g -O2 -o varnishadm varnishadm-varnishadm.o > ../../lib/libvarnish/libvarnish.la > ../../lib/libvarnishcompat/libvarnishcompat.la > mkdir .libs > /usr/local/bin/gcc -include config.h -g -O2 -o .libs/varnishadm > varnishadm-varnishadm.o ../../lib/libvarnish/.libs/libvarnish.so -lrt > ../../lib/libvarnishcompat/.libs/libvarnishcompat.so -R/usr/local/lib > Undefined first referenced > symbol in file > bind > ../../lib/libvarnish/.libs/libvarnish.so > listen > ../../lib/libvarnish/.libs/libvarnish.so > socket > ../../lib/libvarnish/.libs/libvarnish.so > setsockopt > ../../lib/libvarnish/.libs/libvarnish.so > connect > ../../lib/libvarnish/.libs/libvarnish.so > getaddrinfo > ../../lib/libvarnish/.libs/libvarnish.so > freeaddrinfo > ../../lib/libvarnish/.libs/libvarnish.so > gai_strerror > ../../lib/libvarnish/.libs/libvarnish.so > ld: fatal: Symbol referencing errors. No output written to > .libs/varnishadm > collect2: ld returned 1 exit status > > I took all defaults on the configure and I'm using GCC 3.4.6 for the > compile. It looks like I'm either missing a library or have a wrong > version somewhere (I don't really understand what this message is trying > to tell me). > > What am I doing wrong here? > > Regards, > Jim Lane New description: I am trying to compile varnish 1.1.1 on Solaris 10. The configure script runs cleanly but the compile fails with these error messages: {{{ /bin/bash ../../libtool --tag=CC --mode=link /usr/local/bin/gcc -include config.h -g -O2 -o varnishadm varnishadm-varnishadm.o ../../lib/libvarnish/libvarnish.la ../../lib/libvarnishcompat/libvarnishcompat.la mkdir .libs /usr/local/bin/gcc -include config.h -g -O2 -o .libs/varnishadm varnishadm-varnishadm.o ../../lib/libvarnish/.libs/libvarnish.so -lrt ../../lib/libvarnishcompat/.libs/libvarnishcompat.so -R/usr/local/lib Undefined first referenced symbol in file bind ../../lib/libvarnish/.libs/libvarnish.so listen ../../lib/libvarnish/.libs/libvarnish.so socket ../../lib/libvarnish/.libs/libvarnish.so setsockopt ../../lib/libvarnish/.libs/libvarnish.so connect ../../lib/libvarnish/.libs/libvarnish.so getaddrinfo ../../lib/libvarnish/.libs/libvarnish.so freeaddrinfo ../../lib/libvarnish/.libs/libvarnish.so gai_strerror ../../lib/libvarnish/.libs/libvarnish.so ld: fatal: Symbol referencing errors. No output written to .libs/varnishadm collect2: ld returned 1 exit status }}} I took all defaults on the configure and I'm using GCC 3.4.6 for the compile. It looks like I'm either missing a library or have a wrong version somewhere (I don't really understand what this message is trying to tell me). What am I doing wrong here? Regards, Jim Lane Comment: Solaris is currently not supported due to lack of resources. You can work around these specific errors by defining {{{LDFLAGS="-lsocket -lns"}}} in your environment before running {{{configure}}}, but you will probably run into other issues. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Aug 29 15:20:45 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 29 Aug 2007 15:20:45 -0000 Subject: [Varnish] #153: Files are missing from the released tarball of varnis 1.1.1 In-Reply-To: <052.035b380a412468a9afb80d73437a5018@projects.linpro.no> References: <052.035b380a412468a9afb80d73437a5018@projects.linpro.no> Message-ID: <061.82390cfd9482d0550035278e65e7b289@projects.linpro.no> #153: Files are missing from the released tarball of varnis 1.1.1 -----------------------+---------------------------------------------------- Reporter: bahner | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Varnish 1.1.2 Component: packaging | Version: 1.1.1 Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Comment (by des): Some of these do not exist in Subversion (e.g. {{{files}}}). Others were not included in the tarball because you did not update {{{EXTRA_DIST}}} in {{{Makefile.am}}}. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Aug 29 15:30:09 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 29 Aug 2007 15:30:09 -0000 Subject: [Varnish] #153: Files are missing from the released tarball of varnish 1.1.1 In-Reply-To: <052.035b380a412468a9afb80d73437a5018@projects.linpro.no> References: <052.035b380a412468a9afb80d73437a5018@projects.linpro.no> Message-ID: <061.5d86d95fa84dcab3e616c14ad820141e@projects.linpro.no> #153: Files are missing from the released tarball of varnish 1.1.1 -----------------------+---------------------------------------------------- Reporter: bahner | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Varnish 1.1.2 Component: packaging | Version: 1.1.1 Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Changes (by des): * summary: Files are missing from the released tarball of varnis 1.1.1 => Files are missing from the released tarball of varnish 1.1.1 Comment: Fixed in #1927, but the question is, how do we prevent this from reoccurring? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 31 09:09:24 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 31 Aug 2007 09:09:24 -0000 Subject: [Varnish] #154: Child dies with assert error in bes_GetHostname() Message-ID: <053.14a988a88891a63a17c7cf2ccfae0302@projects.linpro.no> #154: Child dies with assert error in bes_GetHostname() ----------------------+----------------------------------------------------- Reporter: henning | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: varnishd assert bes_GetHostname ----------------------+----------------------------------------------------- Running r1929 on Debian Etch/amd64 on Intel cpu, varnishd child process occasionally dies and is restarted. {{{ Child said (2, 26293): <magic == 0x2c2f9c5a) not true. errno = 0 (Success) >> Cache child died pid=26293 status=0x6 Clean child Child cleaned start child pid 26460 Child said (2, 26460): < Varnish The Varnish HTTP Accelerator From phk at phk.freebsd.dk Fri Aug 31 10:00:47 2007 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Fri, 31 Aug 2007 10:00:47 +0000 Subject: [Varnish] #154: Child dies with assert error in bes_GetHostname() In-Reply-To: Your message of "Fri, 31 Aug 2007 09:09:24 GMT." <053.14a988a88891a63a17c7cf2ccfae0302@projects.linpro.no> Message-ID: <8617.1188554447@critter.freebsd.dk> In message <053.14a988a88891a63a17c7cf2ccfae0302 at projects.linpro.no>, "Varnish" writes: >#154: Child dies with assert error in bes_GetHostname() >----------------------+----------------------------------------------------- > Reporter: henning | Owner: phk > Type: defect | Status: new > Priority: normal | Milestone: >Component: varnishd | Version: trunk > Severity: normal | Keywords: varnishd assert bes_GetHostname >----------------------+----------------------------------------------------- > Running r1929 on Debian Etch/amd64 on Intel cpu, varnishd child process > occasionally dies and is restarted. > > {{{ > Child said (2, 26293): < cache_backend_simple.c line 343: > Condition((b)->magic == 0x2c2f9c5a) not true. > errno = 0 (Success) > >> > Cache child died pid=26293 status=0x6 > Clean child > Child cleaned > start child pid 26460 > Child said (2, 26460): < managed to mmap 4294967296 bytes of 4294967296 > Ready > CLI ready > }}} I just fixed that in r1930 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk at FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From varnish-bugs at projects.linpro.no Fri Aug 31 11:22:43 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 31 Aug 2007 11:22:43 -0000 Subject: [Varnish] #155: varnishncsa -b does not work Message-ID: <052.15db299ad6ec4d546be3f9c42090b487@projects.linpro.no> #155: varnishncsa -b does not work -------------------------+-------------------------------------------------- Reporter: anders | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: varnishncsa | Version: 1.1.1 Severity: normal | Keywords: varnishncsa -------------------------+-------------------------------------------------- If I run varnishncsa without parameters, I get lots of data. Also if I run with -c. But if I run with -b, I get nothing: root at cache5:~# varnishncsa -b ^C If I run varnishlog -b, I get plenty of information, do the issue is not that nothing is being fetched. It seems varnishncsa -b does not work. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 31 18:15:24 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 31 Aug 2007 18:15:24 -0000 Subject: [Varnish] #154: Child dies with assert error in bes_GetHostname() In-Reply-To: <053.14a988a88891a63a17c7cf2ccfae0302@projects.linpro.no> References: <053.14a988a88891a63a17c7cf2ccfae0302@projects.linpro.no> Message-ID: <062.bad61001add3679635abbe15090b06f0@projects.linpro.no> #154: Child dies with assert error in bes_GetHostname() ---------------------------------------------+------------------------------ Reporter: henning | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: varnishd assert bes_GetHostname | ---------------------------------------------+------------------------------ Changes (by phk): * status: new => closed * resolution: => fixed Comment: fixed in r1930 -- Ticket URL: Varnish The Varnish HTTP Accelerator