From varnish-bugs at projects.linpro.no Tue Jan 1 18:02:17 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 01 Jan 2008 18:02:17 -0000 Subject: [Varnish] #77: URL rewrite In-Reply-To: <050.43421cdca728d1b8e5023f154c4a71d2@projects.linpro.no> References: <050.43421cdca728d1b8e5023f154c4a71d2@projects.linpro.no> Message-ID: <059.e18d3f6024a825f9a0687f8959519b5d@projects.linpro.no> #77: URL rewrite -------------------------+-------------------------------------------------- Reporter: lapo | Owner: phk Type: enhancement | Status: reopened Priority: normal | Milestone: Component: varnishd | Version: Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by mmikulicic): * status: closed => reopened * resolution: fixed => Comment: The file "varnish-cache/lib/libvcl/syntax.txt" (in trunk) states that there is an action "rewrite", but the action table in vcc_action.c doesn't have a parser function for it. Furthermore the function VRT_rewrite is not defined anywhere. Is there a new, undocumented, way to rewrite urls? I skimmed through the code and I didn't find any hint. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 1 22:02:32 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 01 Jan 2008 22:02:32 -0000 Subject: [Varnish] #188: thread pileup In-Reply-To: <054.501398c9432dffc43debd3778be2327e@projects.linpro.no> References: <054.501398c9432dffc43debd3778be2327e@projects.linpro.no> Message-ID: <063.f26febcc028569592438957012493055@projects.linpro.no> #188: thread pileup ----------------------+----------------------------------------------------- Reporter: steinove | Owner: phk Type: defect | Status: assigned Priority: high | Milestone: Component: varnishd | Version: 1.1.1 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by akv): I have this problem too. I just upgraded to 1.1.2 and still have the problem. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jan 2 10:30:03 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 02 Jan 2008 10:30:03 -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.b32cd14a748d5c98e1fcc5a7466dddc1@projects.linpro.no> #144: Race in backend socket address replacement. ---------------------------------------+------------------------------------ Reporter: anders | Owner: phk Type: defect | Status: reopened Priority: high | Milestone: Varnish 1.2 Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump sig 10 | ---------------------------------------+------------------------------------ Comment (by anders): Running with Varnish 1.1.2 (in FreeBSD 6.2-RELEASE-p3), this still happens: {{{ (gdb) bt #0 0x0000000000408a90 in vbe_sock_conn (ai=0x0) at cache_backend.c:162 #1 0x0000000000408b98 in vbe_conn_try (bp=0xaf1b80, pai=0x7ffffd1e7838) at cache_backend.c:190 #2 0x0000000000408d14 in vbe_connect (sp=0xc15008, bp=0xaf1b80) at cache_backend.c:228 #3 0x000000000040912e in vbe_nextfd (sp=0xc15008) at cache_backend.c:299 #4 0x0000000000409372 in VBE_GetFd (sp=0xc15008) at cache_backend.c:336 #5 0x000000000040cafa in Fetch (sp=0xc15008) at cache_fetch.c:278 #6 0x000000000040a124 in cnt_fetch (sp=0xc15008) at cache_center.c:300 #7 0x000000000040b18d in CNT_Session (sp=0xc15008) at steps.h:40 #8 0x0000000000412cf8 in wrk_do_one (w=0x7ffffd1e7ad0) at cache_pool.c:194 #9 0x00000000004131f3 in wrk_thread (priv=0x8562e0) at cache_pool.c:248 #10 0x000000080098755b in pthread_create () from /usr/lib/libthr.so.2 #11 0x00007ffffcfea000 in ?? () Cannot access memory at address 0x7ffffd1ea000 (gdb) quit }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jan 2 10:42:46 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 02 Jan 2008 10:42:46 -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.7a2d989246d6c0753ff1ae087867052e@projects.linpro.no> #144: Race in backend socket address replacement. ---------------------------------------+------------------------------------ Reporter: anders | Owner: phk Type: defect | Status: reopened Priority: high | Milestone: Varnish 1.2 Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: varnishd core dump sig 10 | ---------------------------------------+------------------------------------ Comment (by anders): Some more info from the previous coredump/backtrace: {{{ (gdb) frame 5 #5 0x000000000040cafa in Fetch (sp=0xc15008) at cache_fetch.c:278 278 cache_fetch.c: No such file or directory. in cache_fetch.c (gdb) print *sp $1 = {magic = 741317722, fd = 65, id = 65, xid = 652152521, wrk = 0x7ffffd1e7ad0, sockaddrlen = 16, mysockaddrlen = 128, sockaddr = 0xc15410, mysockaddr = 0xc15490, addr = "84.211.134.255", '\0' , port = "16051\000\000\000\000\000\000\000\000\000\000", srcaddr = 0x28cbf00, doclose = 0x0, http = 0xc15180, t_open = 1199268349.6441126, t_req = 1199268349.9035521, t_resp = nan(0x8000000000000), t_end = 1199268349.6441126, step = STP_FETCH, handling = 32, wantbody = 1 '\001', err_code = 0, err_reason = 0x0, list = { vtqe_next = 0xd07008, vtqe_prev = 0xbb50d8}, backend = 0xaf1b80, bereq = 0xbbb000, obj = 0x2c33800, vcl = 0x2d816c49c0, mem = 0xc15000, workreq = {list = {vtqe_next = 0x0, vtqe_prev = 0x0}, sess = 0xc15008}, acct = {first = 1199268348.5672638, sess = 1, req = 3, pipe = 0, pass = 0, fetch = 3, hdrbytes = 1024, bodybytes = 26656}, nhashptr = 10, ihashptr = 4, lhashptr = 69, hashptr = 0xc15798} (gdb) print *hp $3 = {magic = 1680389577, ws = {{s = 0xbbb2a0 "X-Varnish: 652152521", e = 0xbbd2a0 "", f = 0xbbb2d5 "\nServer: Apache/2.2.3 (Debian) Resin/3.1.3", r = 0x0}}, rx_s = 0x0, rx_e = 0x0, pl_s = 0x0, pl_e = 0x0, conds = 0 '\0', logtag = HTTP_Tx, hd = {{b = 0x42a3e2 "GET", e = 0x42a3e5 ""}, { b = 0xc15514 "/dynamic/tms.jsp/1.0.0/finnvector/14/1660/1653.png", e = 0xc15546 ""}, {b = 0x42a11a "HTTP/1.1", e = 0x42a122 ""}, {b = 0x0, e = 0x0}, {b = 0x0, e = 0x0}, {b = 0xc15551 "Accept: */*", e = 0xc1555c ""}, { b = 0xc1555e "Referer: http://finn.no/finn/mappopup?finnkode=11172143&utmx=249915&utmy=6825202&mapTitle=Skotten+Seter,++F??vang&airPossible=1", e = 0xc155dd ""}, {b = 0xc155df "Accept-Language: no", e = 0xc155f2 ""}, {b = 0xc155f4 "UA-CPU: x86", e = 0xc155ff ""}, { b = 0xc15601 "Accept-Encoding: gzip, deflate", e = 0xc1561f ""}, { b = 0xc15621 "User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322)", e = 0xc15672 ""}, { b = 0xc15674 "Host: maptiles2.finn.no", e = 0xc1568b ""}, { b = 0xc156a5 "Cookie: finn_ld=aeb69f3baeb69f34baeebabd; JSESSIONID=cbapacpyQ6ArR95jm95Cr; RMID=54d386ff477b6170; WT_FPC=id=2a8d6d3b7025c46a8bc1199268218640:lv=1199268345093:ss=1199268218640; IADVISITOR=406416167; f"..., e = 0xc1578d ""}, {b = 0xbbb2a0 "X-Varnish: 652152521", e = 0xbbb2b4 ""}, {b = 0xbbb2b5 "X-Forwarded-for: 84.211.134.255", e = 0xbbb2d4 ""}, {b = 0x0, e = 0x0} }, hdf = '\0' , nhd = 15} }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jan 4 09:05:03 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 04 Jan 2008 09:05:03 -0000 Subject: [Varnish] #188: thread pileup In-Reply-To: <054.501398c9432dffc43debd3778be2327e@projects.linpro.no> References: <054.501398c9432dffc43debd3778be2327e@projects.linpro.no> Message-ID: <063.98adb7c1fdba1986540ac86482287dc7@projects.linpro.no> #188: thread pileup ----------------------+----------------------------------------------------- Reporter: steinove | Owner: phk Type: defect | Status: assigned Priority: high | Milestone: Component: varnishd | Version: 1.1.1 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by akv): After monitoring the n_wrk value, I realized out that the amount of worker threads were jumping up and down due to a bad behaving backend. We fixed this and n_wrk seems better now. But it would be nice if varnish were able to handle this instead of just becomming un-usable... -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 8 10:33:06 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 08 Jan 2008 10:33:06 -0000 Subject: [Varnish] #77: URL rewrite In-Reply-To: <050.43421cdca728d1b8e5023f154c4a71d2@projects.linpro.no> References: <050.43421cdca728d1b8e5023f154c4a71d2@projects.linpro.no> Message-ID: <059.43d646374ca8ae63548f520b63573f52@projects.linpro.no> #77: URL rewrite -------------------------+-------------------------------------------------- Reporter: lapo | Owner: phk Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishd | Version: Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by des): * status: reopened => closed * resolution: => fixed Comment: The file you refer to was an attempt to sketch a possible VCL syntax before implementation started, and does not in any way represent the actual syntax, which is fully documented in the {{{vcl(7)}}} manual page. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 8 10:38:33 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 08 Jan 2008 10:38:33 -0000 Subject: [Varnish] #192: varnishd 1.1.2 died in VBE_ClosedFd() In-Reply-To: <051.3035b4ae37c243d40690ad0cd9c173a8@projects.linpro.no> References: <051.3035b4ae37c243d40690ad0cd9c173a8@projects.linpro.no> Message-ID: <060.4f5175b1e448d8b3c0d0496d93df7c87@projects.linpro.no> #192: varnishd 1.1.2 died in VBE_ClosedFd() ----------------------+----------------------------------------------------- Reporter: jnlin | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 1.1.2 Severity: normal | Resolution: duplicate Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: new => closed * resolution: => duplicate Comment: Duplicate of #169. -- Ticket URL: Varnish The Varnish HTTP Accelerator From phk at phk.freebsd.dk Tue Jan 8 14:36:42 2008 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Tue, 08 Jan 2008 14:36:42 +0000 Subject: [Varnish] #181: osx leopard: unknown sendfile() implementation In-Reply-To: Your message of "Thu, 22 Nov 2007 17:58:34 GMT." <053.fe4dde1a1b9387be05d3390e48119f02@projects.linpro.no> Message-ID: <78567.1199803002@critter.freebsd.dk> In message <053.fe4dde1a1b9387be05d3390e48119f02 at projects.linpro.no>, "Varnish" writes: > i can't build varnish on OSX leopard. that's the output of my make: Remove the "HAVE_SENDFILE" from your config.h file (or hack configure.ac to never even look for sendfile. -- 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 Tue Jan 8 16:06:20 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 08 Jan 2008 16:06:20 -0000 Subject: [Varnish] #78: URLS without trailing / direct to backend . In-Reply-To: <052.898d4b1c1c82444eefb273439c7b645c@projects.linpro.no> References: <052.898d4b1c1c82444eefb273439c7b645c@projects.linpro.no> Message-ID: <061.280a45eb46873da7e60fb4146a339983@projects.linpro.no> #78: URLS without trailing / direct to backend . ----------------------+----------------------------------------------------- Reporter: kevinm | Owner: des Type: defect | Status: assigned Priority: high | Milestone: Component: varnishd | Version: Severity: major | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by seekgzl): [http://www.new-york-hotels.com.cn new york hotel][http://www.london- motel.cn london motel][http://www.cheap-hotel.net.cn cheap hotel][http://www.beijing-hotel-4star.com.cn beijing hotel 4 star][http://www.stair-railings.cn stair railings][http://www.beijing- hotel-list.com.cn beijing hotel list][http://www.beijing-hotel-map.cn beijing hotel map][http://www.cheapest-air-tickets.com.cn cheapest air tickets] [http://www.wrought-iron-railings.cn wrought iron railings] [http://www.steel-tube.net.cn/steel tube] [http://www.beijing-discount- hotel.cn/ beijing discount hotel] [http://www.cheap-beijing-hotel.cn/ cheap beijing hotel] [http://www.hotel-discount-beijing.cn/ hotel discount beijing] [http://www.hotel-in-beijing-china.cn hotel in beijing china] [http://www.baby-gifts.cn baby gifts] -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 8 16:07:03 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 08 Jan 2008 16:07:03 -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.a3a5b7a00bc06d7365c784a08a9d1d6f@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 seekgzl): [http://www.new-york-hotels.com.cn new york hotel][http://www.london- motel.cn london motel][http://www.cheap-hotel.net.cn cheap hotel][http://www.beijing-hotel-4star.com.cn beijing hotel 4 star][http://www.stair-railings.cn stair railings][http://www.beijing- hotel-list.com.cn beijing hotel list][http://www.beijing-hotel-map.cn beijing hotel map][http://www.cheapest-air-tickets.com.cn cheapest air tickets] [http://www.wrought-iron-railings.cn wrought iron railings] [http://www.steel-tube.net.cn/steel tube] [http://www.beijing-discount- hotel.cn/ beijing discount hotel] [http://www.cheap-beijing-hotel.cn/ cheap beijing hotel] [http://www.hotel-discount-beijing.cn/ hotel discount beijing] [http://www.hotel-in-beijing-china.cn hotel in beijing china] [http://www.baby-gifts.cn baby gifts] -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 8 16:07:36 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 08 Jan 2008 16:07:36 -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.4a1c92d3fdac6670c93a454c97312568@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 seekgzl): [http://www.new-york-hotels.com.cn new york hotel][http://www.london- motel.cn london motel][http://www.cheap-hotel.net.cn cheap hotel][http://www.beijing-hotel-4star.com.cn beijing hotel 4 star][http://www.stair-railings.cn stair railings][http://www.beijing- hotel-list.com.cn beijing hotel list][http://www.beijing-hotel-map.cn beijing hotel map][http://www.cheapest-air-tickets.com.cn cheapest air tickets] [http://www.wrought-iron-railings.cn wrought iron railings] [http://www.steel-tube.net.cn/steel tube] [http://www.beijing-discount- hotel.cn/ beijing discount hotel] [http://www.cheap-beijing-hotel.cn/ cheap beijing hotel] [http://www.hotel-discount-beijing.cn/ hotel discount beijing] [http://www.hotel-in-beijing-china.cn hotel in beijing china] [http://www.baby-gifts.cn baby gifts] -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 8 16:21:36 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 08 Jan 2008 16:21:36 -0000 Subject: [Varnish] #191: Varnish won't cache if apache keepalive is set to on In-Reply-To: <057.afbf7964f5f8580f04cb9d3e7d90da6b@projects.linpro.no> References: <057.afbf7964f5f8580f04cb9d3e7d90da6b@projects.linpro.no> Message-ID: <066.9b37c98fed050e6ba5b610340d90429b@projects.linpro.no> #191: Varnish won't cache if apache keepalive is set to on -------------------------+-------------------------------------------------- Reporter: michael.lee | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1.1 Severity: normal | Resolution: Keywords: keepalive | -------------------------+-------------------------------------------------- Comment (by des): You haven't provided nearly enough information to debug this issue. At the very least, full logs from the working and non-working case are needed. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 8 16:35:00 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 08 Jan 2008 16:35:00 -0000 Subject: [Varnish] #187: Insufficient logging data - actual bytes transferred needed In-Reply-To: <052.e24a3b4d3f02f7eafd5b154cbc7cbed9@projects.linpro.no> References: <052.e24a3b4d3f02f7eafd5b154cbc7cbed9@projects.linpro.no> Message-ID: <061.d9bbb2d76de60ac167319b37dd67fdea@projects.linpro.no> #187: Insufficient logging data - actual bytes transferred needed -------------------------+-------------------------------------------------- Reporter: rinogo | Owner: phk Type: enhancement | Status: new Priority: normal | Milestone: Component: varnishlog | Version: 1.1.1 Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by des): Currently, the best workaround is to disable {{{sendfile()}}} entirely. There are simply too many issues with it. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jan 10 11:43:23 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 10 Jan 2008 11:43:23 -0000 Subject: [Varnish] #193: Varnish fails to restart after ping timeout Message-ID: <052.1a8922089920002744d521a518795454@projects.linpro.no> #193: Varnish fails to restart after ping timeout --------------------+------------------------------------------------------- Reporter: anders | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: 1.2 Severity: normal | Keywords: --------------------+------------------------------------------------------- When working on a large data set, it is common that Varnish fails the ping test due to a long timeout. However, with 1.2 branch up to date to commit 2337, it fails to restart child: {{{ Starting varnishd. storage_file: filename: /data/varnish.dat size 153600 MegaBytes. Using old SHMFILE rolling(1)... rolling(2)... start start child pid 84476 200 0 Child said (2, 84476): <> Child not responding to ping Child not responding to ping Cache child died pid=84476 status=0x9 Clean child Child cleaned start child pid 96371 Pushing vcls failed: CLI communication error Child said (1, 96371): <> unlink ./vcl.1P9zoqAU.o }}} I am running Varnish on FreeBSD/amd64 6.3-RC2, on Intel (EMT64) hardware. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jan 10 12:03:57 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 10 Jan 2008 12:03:57 -0000 Subject: [Varnish] #193: Varnish fails to restart after ping timeout In-Reply-To: <052.1a8922089920002744d521a518795454@projects.linpro.no> References: <052.1a8922089920002744d521a518795454@projects.linpro.no> Message-ID: <061.4d4244d746fca7ffbeb5dbbcfa28b036@projects.linpro.no> #193: Varnish fails to restart after ping timeout ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.2 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * owner: des => phk * component: build => varnishd -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jan 11 15:05:59 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 11 Jan 2008 15:05:59 -0000 Subject: [Varnish] #194: Varnish crashes with assert error in HTC_Rx (cache_httpconn.c) Message-ID: <052.ccc503c1ee28328bd887f0182ca58a42@projects.linpro.no> #194: Varnish crashes with assert error in HTC_Rx (cache_httpconn.c) ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.2 Severity: normal | Keywords: varnishd core dump HTC_Rx cache_httpconn.c ----------------------+----------------------------------------------------- Varnish crashes with this error message: {{{ Child said (2, 27833): <ws->r) != 0) not true. errno = 35 (Resource temporarily unavailable) >> Cache child died pid=27833 status=0x86 }}} I am running Varnish on FreeBSD/amd64 6.3-RC2, on Intel (EMT64) hardware. My VCL: {{{ backend default { set backend.host = "192.168.110.1"; set backend.port = "80"; } acl purge { "192.168.100.1"/32; } sub vcl_recv { if (req.http.host ~ "^(bars.*.foo.no|bazcache.foo.no)$") { if (req.request == "GET" || req.request == "HEAD") { lookup; } elsif (req.request ~ "^(PURGE|REPURGE)$") { if (client.ip ~ purge) { if (req.request == "REPURGE") { purge_url(req.url); error 200 "Repurged."; } else { lookup; } } else { error 405 "Not allowed."; } } else { pipe; } } else { error 403 "Access denied. Contact cacheadmin at foo.no if you have problems."; } } sub vcl_miss { if (req.request ~ "^(PURGE|REPURGE)$") { 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 || obj.status == 500) { pass; } if (!obj.valid) { error; } if (!obj.cacheable) { pass; } if (obj.http.Cookie) { remove obj.http.Cookie; } if (obj.http.Set-Cookie) { remove obj.http.Set-Cookie; } insert; } sub vcl_hash { set req.hash += req.url; if (req.http.host ~ "^bars.*.foo.no$") { set req.hash += "bars.foo.no"; } else { set req.hash += req.http.host; } hash; } }}} Backtrace: {{{ (gdb) bt #0 0x0000000800c0d59c in thr_kill () from /lib/libc.so.6 #1 0x000000080099101c in raise () from /usr/lib/libthr.so.2 #2 0x0000000800c8d4cd in abort () from /lib/libc.so.6 #3 0x000000080066dc09 in lbv_assert (func=0x432ee4 "HTC_Rx", file=0x432e62 "cache_httpconn.c", line=163, cond=0x432eeb "(htc->ws->r) != 0", err=35) at assert.c:58 #4 0x0000000000417e71 in HTC_Rx (htc=0x131a0b0) at cache_httpconn.c:163 #5 0x00000000004085bf in vca_kev (kp=0x7fffff5fb350) at cache_acceptor_kqueue.c:107 #6 0x000000000040896d in vca_kqueue_main (arg=0x0) at cache_acceptor_kqueue.c:156 #7 0x000000080099355b in pthread_create () from /usr/lib/libthr.so.2 #8 0x0000000000000000 in ?? () Cannot access memory at address 0x7fffff5fc000 (gdb) print sp $1 = (struct sess *) 0x131a008 (gdb) print *sp $2 = {magic = 741317722, fd = -1, id = 36, xid = 0, restarts = 0, wrk = 0x0, sockaddrlen = 16, mysockaddrlen = 128, sockaddr = 0x131a670, mysockaddr = 0x131a6f0, addr = 0x131a770 "83.108.186.146", port = 0x131a77f "9718", srcaddr = 0x0, doclose = 0x0, http = 0x131a1c8, http0 = 0x131a410, ws = {{magic = 905626964, id = 0x4339f0 "sess", s = 0x131a770 "83.108.186.146", f = 0x131a784 "", r = 0x0, e = 0x131c770 ""}}, ws_ses = 0x131a784 "", ws_req = 0x131a995 "", htc = { {magic = 1041886673, fd = 36, ws = 0x131a070, rxbuf = {b = 0x131a784 "", e = 0x131a784 ""}, pipeline = {b = 0x0, e = 0x0}}}, t_open = 1200047595.0341094, t_req = nan(0x8000000000000), t_resp = nan(0x8000000000000), t_end = 1200047595.0341094, step = STP_DONE, cur_method = 0, handling = 128, wantbody = 1 '\001', err_code = 0, err_reason = 0x0, list = {vtqe_next = 0x1242008, vtqe_prev = 0x121d120}, backend = 0x0, bereq = 0x0, obj = 0x0, vcl = 0x0, mem = 0x131a000, workreq = {list = {vtqe_next = 0x0, vtqe_prev = 0x0}, sess = 0x131a008}, acct = {first = 1200047594.641866, sess = 1, req = 1, pipe = 0, pass = 0, fetch = 0, hdrbytes = 341, bodybytes = 52881}, nhashptr = 12, ihashptr = 4, lhashptr = 69, hashptr = 0x131a998} }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jan 11 15:13:48 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 11 Jan 2008 15:13:48 -0000 Subject: [Varnish] #194: Varnish crashes with assert error in HTC_Rx (cache_httpconn.c) In-Reply-To: <052.ccc503c1ee28328bd887f0182ca58a42@projects.linpro.no> References: <052.ccc503c1ee28328bd887f0182ca58a42@projects.linpro.no> Message-ID: <061.0e8d443cc1dc1f7fb1b86b288a5ea979@projects.linpro.no> #194: Varnish crashes with assert error in HTC_Rx (cache_httpconn.c) --------------------------------------------------------+------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.2 Severity: normal | Resolution: Keywords: varnishd core dump HTC_Rx cache_httpconn.c | --------------------------------------------------------+------------------- Comment (by anders): Two things: The sp/*sp above is from frame 5: {{{ (gdb) frame 5 #5 0x00000000004085bf in vca_kev (kp=0x7fffff5fb350) at cache_acceptor_kqueue.c:107 107 i = HTC_Rx(sp->htc); }}} Also, I am running Varnish 1.2 branch up to date to commit 2337. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jan 11 15:16:43 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 11 Jan 2008 15:16:43 -0000 Subject: [Varnish] #195: Varnish crashes in RES_BuildHttp (cache_response.c) Message-ID: <052.570abebb906f380f6b27b77133169c10@projects.linpro.no> #195: Varnish crashes in RES_BuildHttp (cache_response.c) ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.2 Severity: normal | Keywords: varnishd core dump RES_BuildHttp cache_response.c ----------------------+----------------------------------------------------- Varnish crashes with this error message: {{{ Cache child died pid=83172 status=0x8b Clean child }}} I am running Varnish 1.2 branch up to date to commit 2337, on FreeBSD/amd64 6.3-RC2 (on Intel (EMT64) hardware). My VCL: {{{ backend default { set backend.host = "192.168.110.1"; set backend.port = "80"; } acl purge { "192.168.100.1"/32; } sub vcl_recv { if (req.http.host ~ "^(bars.*.foo.no|bazcache.foo.no)$") { if (req.request == "GET" || req.request == "HEAD") { lookup; } elsif (req.request ~ "^(PURGE|REPURGE)$") { if (client.ip ~ purge) { if (req.request == "REPURGE") { purge_url(req.url); error 200 "Repurged."; } else { lookup; } } else { error 405 "Not allowed."; } } else { pipe; } } else { error 403 "Access denied. Contact cacheadmin at foo.no if you have problems."; } } sub vcl_miss { if (req.request ~ "^(PURGE|REPURGE)$") { 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 || obj.status == 500) { pass; } if (!obj.valid) { error; } if (!obj.cacheable) { pass; } if (obj.http.Cookie) { remove obj.http.Cookie; } if (obj.http.Set-Cookie) { remove obj.http.Set-Cookie; } insert; } sub vcl_hash { set req.hash += req.url; if (req.http.host ~ "^bars.*.foo.no$") { set req.hash += "bars.foo.no"; } else { set req.hash += req.http.host; } hash; } }}} Backtrace: {{{ (gdb) bt #0 0x000000000041ada6 in RES_BuildHttp (sp=0x8db4008) at cache_response.c:139 #1 0x000000000040e668 in cnt_deliver (sp=0x8db4008) at cache_center.c:155 #2 0x0000000000410bdd in CNT_Session (sp=0x8db4008) at steps.h:42 #3 0x00000000004192b8 in wrk_do_one (w=0x7ffff2995ad0) at cache_pool.c:193 #4 0x0000000000419793 in wrk_thread (priv=0x86d320) at cache_pool.c:246 #5 0x000000080099355b in pthread_create () from /usr/lib/libthr.so.2 #6 0x00007ffff2796000 in ?? () Cannot access memory at address 0x7ffff2996000 (gdb) frame 0 #0 0x000000000041ada6 in RES_BuildHttp (sp=0x8db4008) at cache_response.c:139 139 http_PrintfHeader(sp->wrk, sp->fd, sp->http, "Age: %.0f", (gdb) print sp $1 = (struct sess *) 0x8db4008 (gdb) print *sp $2 = {magic = 741317722, fd = 654, id = 654, xid = 0, restarts = 0, wrk = 0x0, sockaddrlen = 16, mysockaddrlen = 128, sockaddr = 0x8db4670, mysockaddr = 0x8db46f0, addr = 0x8db4770 "195.159.104.134", port = 0x8db4780 "12691", srcaddr = 0xcaabb00, doclose = 0x0, http = 0x8db41c8, http0 = 0x8db4410, ws = {{magic = 905626964, id = 0x4339f0 "sess", s = 0x8db4770 "195.159.104.134", f = 0x8db47a7 "ayers-2.5.js", r = 0x0, e = 0x8db6770 ""}}, ws_ses = 0x8db4786 "", ws_req = 0x8db4a07 "", htc = {{magic = 1041886673, fd = 654, ws = 0x8db4070, rxbuf = {b = 0x8db4786 "", e = 0x8db4786 ""}, pipeline = {b = 0x0, e = 0x0}}}, t_open = 1200059307.9467714, t_req = nan(0x8000000000000), t_resp = nan(0x8000000000000), t_end = 1200059307.9467714, step = STP_DONE, cur_method = 0, handling = 128, wantbody = 0 '\0', err_code = 0, err_reason = 0x0, list = {vtqe_next = 0x0, vtqe_prev = 0x0}, backend = 0x0, bereq = 0x0, obj = 0x0, vcl = 0x0, mem = 0x8db4000, workreq = {list = {vtqe_next = 0x8cf8158, vtqe_prev = 0x53ab90}, sess = 0x8db4008}, acct = { first = 1200059307.8567345, sess = 1, req = 1, pipe = 0, pass = 0, fetch = 0, hdrbytes = 177, bodybytes = 0}, nhashptr = 12, ihashptr = 4, lhashptr = 60, hashptr = 0x8db4a08} }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jan 11 17:02:59 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 11 Jan 2008 17:02:59 -0000 Subject: [Varnish] #196: Varnish crashes in ses_sum_acct (cache_session.c) Message-ID: <052.61fe925e2186fafc84082dac4cdf43db@projects.linpro.no> #196: Varnish crashes in ses_sum_acct (cache_session.c) ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.2 Severity: normal | Keywords: varnishd core dump ses_sum_acct cache_session.c ----------------------+----------------------------------------------------- Varnish crashes with this error message: Cache child died pid=46980 status=0x8b Clean child I am running Varnish 1.2 branch up to date to commit 2337, on FreeBSD/amd64 6.3-RC2 (on Intel (EMT64) hardware). My VCL: {{{ backend default { set backend.host = "192.168.110.1"; set backend.port = "80"; } acl purge { "192.168.100.1"/32; } sub vcl_recv { if (req.http.host ~ "^(bars.*.foo.no|bazcache.foo.no)$") { if (req.request == "GET" || req.request == "HEAD") { lookup; } elsif (req.request ~ "^(PURGE|REPURGE)$") { if (client.ip ~ purge) { if (req.request == "REPURGE") { purge_url(req.url); error 200 "Repurged."; } else { lookup; } } else { error 405 "Not allowed."; } } else { pipe; } } else { error 403 "Access denied. Contact cacheadmin at foo.no if you have problems."; } } sub vcl_miss { if (req.request ~ "^(PURGE|REPURGE)$") { 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 || obj.status == 500) { pass; } if (!obj.valid) { error; } if (!obj.cacheable) { pass; } if (obj.http.Cookie) { remove obj.http.Cookie; } if (obj.http.Set-Cookie) { remove obj.http.Set-Cookie; } insert; } sub vcl_hash { set req.hash += req.url; if (req.http.host ~ "^bars.*.foo.no$") { set req.hash += "bars.foo.no"; } else { set req.hash += req.http.host; } hash; } }}} Backtrace: {{{ (gdb) bt #0 0x000000000041b8b8 in ses_sum_acct (sum=0xb42170, inc=0x470) at cache_session.c:215 #1 0x000000000041b992 in SES_Charge (sp=0xb42008) at cache_session.c:230 #2 0x000000000040ea15 in cnt_done (sp=0xb42008) at cache_center.c:219 #3 0x0000000000410ccd in CNT_Session (sp=0xb42008) at steps.h:44 #4 0x00000000004192b8 in wrk_do_one (w=0x7ffff9dcfad0) at cache_pool.c:193 #5 0x0000000000419793 in wrk_thread (priv=0x86d320) at cache_pool.c:246 #6 0x000000080099355b in pthread_create () from /usr/lib/libthr.so.2 #7 0x00007ffff9bd0000 in ?? () Cannot access memory at address 0x7ffff9dd0000 (gdb) frame 0 #0 0x000000000041b8b8 in ses_sum_acct (sum=0xb42170, inc=0x470) at cache_session.c:215 215 sum->sess += inc->sess; (gdb) print sp No symbol "sp" in current context. (gdb) frame 1 #1 0x000000000041b992 in SES_Charge (sp=0xb42008) at cache_session.c:230 230 ses_sum_acct(&sp->acct, a); (gdb) print sp $1 = (struct sess *) 0xb42008 (gdb) print *sp $2 = {magic = 741317722, fd = 0, id = 0, xid = 0, restarts = 0, wrk = 0x0, sockaddrlen = 16, mysockaddrlen = 128, sockaddr = 0xb42670, mysockaddr = 0xb426f0, addr = 0x0, port = 0x0, srcaddr = 0x0, doclose = 0x0, http = 0x0, http0 = 0x0, ws = {{magic = 0, id = 0x0, s = 0x0, f = 0x0, r = 0x0, e = 0x0}}, ws_ses = 0x0, ws_req = 0x0, htc = {{magic = 0, fd = 0, ws = 0x0, rxbuf = {b = 0x0, e = 0x0}, pipeline = {b = 0x0, e = 0x0}}}, t_open = nan(0x8000000000000), t_req = nan(0x8000000000000), t_resp = nan(0x8000000000000), t_end = nan(0x8000000000000), step = STP_AGAIN, cur_method = 0, handling = 0, wantbody = 0 '\0', err_code = 0, err_reason = 0x0, list = { vtqe_next = 0x0, vtqe_prev = 0x0}, backend = 0x0, bereq = 0x0, obj = 0x0, vcl = 0x0, mem = 0xb42000, workreq = {list = {vtqe_next = 0x0, vtqe_prev = 0x0}, sess = 0x0}, acct = {first = 0, sess = 0, req = 0, pipe = 0, pass = 0, fetch = 0, hdrbytes = 0, bodybytes = 0}, nhashptr = 0, ihashptr = 0, lhashptr = 0, hashptr = 0x0} }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jan 11 17:44:57 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 11 Jan 2008 17:44:57 -0000 Subject: [Varnish] #188: thread pileup In-Reply-To: <054.501398c9432dffc43debd3778be2327e@projects.linpro.no> References: <054.501398c9432dffc43debd3778be2327e@projects.linpro.no> Message-ID: <063.635ef651bdf0effddafcf53a78697299@projects.linpro.no> #188: thread pileup ----------------------+----------------------------------------------------- Reporter: steinove | Owner: phk Type: defect | Status: assigned Priority: high | Milestone: Component: varnishd | Version: 1.1.1 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by frekri): Replying to [comment:1 phk]: > My best diagnosis, is that the backend is very slow for some particular popular object. > > One thread picks it up from the backend and a LOT of requests gets parked on the busy object until it comes back from the backend. > > Once it comes back, all the parked requests gets reinjected and causes the thread explosion. > > Some kind of pacing algorithm is obviously called for, the trick is to find one that doesn't need too many carefully tweaked numbers to work generally and reliably. > > Thinking... > > /phk On Nettby.no varnish crash almost every day. We run 4 varnish servers. After I read your post I moved all objects with high traffic to lighttpd and objects with less traffic to varnish. In total these objects had a lot of traffic. On each server we had 1100 hits/s before the last crash today. Before the crash we had increased iowait, but hits and everything else were normal. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jan 14 00:37:43 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 14 Jan 2008 00:37:43 -0000 Subject: [Varnish] #188: thread pileup In-Reply-To: <054.501398c9432dffc43debd3778be2327e@projects.linpro.no> References: <054.501398c9432dffc43debd3778be2327e@projects.linpro.no> Message-ID: <063.5ff9eb7b65f2d723aca09e6c2b3222d2@projects.linpro.no> #188: thread pileup ----------------------+----------------------------------------------------- Reporter: steinove | Owner: phk Type: defect | Status: assigned Priority: high | Milestone: Component: varnishd | Version: 1.1.1 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by frekri): Replying to [comment:5 frekri]: > Replying to [comment:1 phk]: > > My best diagnosis, is that the backend is very slow for some particular popular object. > > > > One thread picks it up from the backend and a LOT of requests gets parked on the busy object until it comes back from the backend. > > > > Once it comes back, all the parked requests gets reinjected and causes the thread explosion. > > > > Some kind of pacing algorithm is obviously called for, the trick is to find one that doesn't need too many carefully tweaked numbers to work generally and reliably. > > > > Thinking... > > > > /phk > > On Nettby.no varnish crash almost every day. We run 4 varnish servers. After I read your post I moved all objects with high traffic to lighttpd and objects with less traffic to varnish. In total these objects had a lot of traffic. > > On each server we had 1100 hits/s before the last crash today. Before the crash we had increased iowait, but hits and everything else were normal. Last described crash was because of to slow Swap Space(Disk). I have reconfigured varnish to use less memory than available ram. I was able to recreate the thread problem this weekend and I'm able to crash varnish like Steinove described on purpose when I gave it enough non-cached requests from our users. Let us know when you have a patch and we will test it for you. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jan 14 09:18:50 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 14 Jan 2008 09:18:50 -0000 Subject: [Varnish] #197: HTTP/1.0 query return no content Message-ID: <051.fc35504a2f711886fdf4302b5c601a42@projects.linpro.no> #197: HTTP/1.0 query return no content ----------------------+----------------------------------------------------- Reporter: chr79 | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.1.2 Severity: normal | Keywords: ----------------------+----------------------------------------------------- Varnish return no content when a query use HTTP/1.0 and the backend don't send a content-header. Log sample : {{{ 15 TxRequest b GET 15 TxURL b /bug.php 15 TxProtocol b HTTP/1.0 ... 15 RxProtocol b HTTP/1.1 15 RxStatus b 200 15 RxResponse b OK 15 RxHeader b Date: Fri, 11 Jan 2008 14:32:33 GMT 15 RxHeader b Server: Microsoft-IIS/4.0 15 RxHeader b Connection: close 15 RxHeader b Content-Type: text/css; charset: UTF-8 13 ObjProtocol c HTTP/1.1 13 ObjStatus c 200 13 ObjResponse c OK 13 ObjHeader c Date: Fri, 11 Jan 2008 14:32:33 GMT 13 ObjHeader c Server: - 13 ObjHeader c Content-Type: text/css; charset: UTF-8 15 BackendClose b default 13 TTL c 1588262781 RFC 120 1200061953 1200061953 0 0 0 13 VCL_call c fetch 13 VCL_return c pass 13 Length c 0 13 VCL_call c deliver }}} this can be solved by patching /bin/varnishd/cache_fetch.c : {{{ @@ -343,7 +343,7 @@ VSL(SLT_Debug, vc->fd, "Invalid Transfer-Encoding"); VBE_ClosedFd(sp->wrk, vc); return (-1); - } else if (strcmp(http_GetProto(hp), "HTTP/1.1")) { + } else if ((strcmp(http_GetProto(hp), "HTTP/1.1")) || (strcmp(http_GetProto(hp), "HTTP/1.0"))) { switch (http_GetStatus(hp)) { case 200: cls = fetch_eof(sp, vc->fd, hp); }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 15 15:02:26 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 15 Jan 2008 15:02:26 -0000 Subject: [Varnish] #166: debian/varnish.postinst fails In-Reply-To: <053.e799974f9ed4b655988a18eb8fa76c07@projects.linpro.no> References: <053.e799974f9ed4b655988a18eb8fa76c07@projects.linpro.no> Message-ID: <062.c6931f480a9a24f0369c36cf2f63bef0@projects.linpro.no> #166: debian/varnish.postinst fails ---------------------------------------+------------------------------------ Reporter: havardf | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: packaging | Version: trunk Severity: normal | Resolution: Keywords: postinst debian packaging | ---------------------------------------+------------------------------------ Comment (by madssj): This has been fixed in r2291. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 15 15:03:58 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 15 Jan 2008 15:03:58 -0000 Subject: [Varnish] #166: debian/varnish.postinst fails In-Reply-To: <053.e799974f9ed4b655988a18eb8fa76c07@projects.linpro.no> References: <053.e799974f9ed4b655988a18eb8fa76c07@projects.linpro.no> Message-ID: <062.728c8756c9a2e30e21a12f3058051c13@projects.linpro.no> #166: debian/varnish.postinst fails ---------------------------------------+------------------------------------ Reporter: havardf | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: packaging | Version: trunk Severity: normal | Resolution: Keywords: postinst debian packaging | ---------------------------------------+------------------------------------ Comment (by madssj): That and r2078. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 15 15:10:55 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 15 Jan 2008 15:10:55 -0000 Subject: [Varnish] #184: After a url purge the page takes about 20 sek or time out before it is viewed. In-Reply-To: <058.88bcec527e068e486073fafb55a2d4d2@projects.linpro.no> References: <058.88bcec527e068e486073fafb55a2d4d2@projects.linpro.no> Message-ID: <067.ba4795027cb1f475ded1079643c1b6f5@projects.linpro.no> #184: After a url purge the page takes about 20 sek or time out before it is viewed. --------------------------+------------------------------------------------- Reporter: krkomvarnish | Owner: des Type: defect | Status: new Priority: high | Milestone: Component: build | Version: 1.1.1 Severity: major | Resolution: Keywords: Purge | --------------------------+------------------------------------------------- Comment (by madssj): I dont think one sould have a `lookup` after a `purge_url` and a `error`. Try removing the `lookup` from your config file. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 15 15:29:34 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 15 Jan 2008 15:29:34 -0000 Subject: [Varnish] #75: Debian-package fails to delete storage_bin on purge In-Reply-To: <052.dfa1ad7ee7e7863373d4159cdf9a3059@projects.linpro.no> References: <052.dfa1ad7ee7e7863373d4159cdf9a3059@projects.linpro.no> Message-ID: <061.b517978824f291bd2d47e57ec6d81bcd@projects.linpro.no> #75: Debian-package fails to delete storage_bin on purge -----------------------+---------------------------------------------------- Reporter: bahner | Owner: bahner Type: defect | Status: closed Priority: normal | Milestone: Component: packaging | Version: Severity: normal | Resolution: fixed Keywords: debian | -----------------------+---------------------------------------------------- Changes (by madssj): * status: new => closed * resolution: => fixed * component: build => packaging Comment: Has been fixed for a while. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 15 15:36:12 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 15 Jan 2008 15:36:12 -0000 Subject: [Varnish] #183: spelling mistake in vcl(7): locahost In-Reply-To: <052.d70ffedeb9c2761ef7cd2d7e38ba0995@projects.linpro.no> References: <052.d70ffedeb9c2761ef7cd2d7e38ba0995@projects.linpro.no> Message-ID: <061.536e1c197a8166c597a2e7360f91f9c7@projects.linpro.no> #183: spelling mistake in vcl(7): locahost ---------------------------+------------------------------------------------ Reporter: Habbie | Owner: des Type: documentation | Status: new Priority: normal | Milestone: Component: documentation | Version: trunk Severity: trivial | Resolution: Keywords: man, vcl.7 | ---------------------------+------------------------------------------------ Changes (by madssj): * keywords: => man, vcl.7 * version: 1.1.1 => trunk Comment: In [source:/trunk/varnish-cache/man/vcl.7 at 1916#L100 vcl.7] `locahost` sould be `localhost`. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 15 15:38:41 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 15 Jan 2008 15:38:41 -0000 Subject: [Varnish] #182: [patch]: New option to force flush from varnishncsa after each log line In-Reply-To: <050.c8405dbdbdc0fbe5df3567e4c50c43a4@projects.linpro.no> References: <050.c8405dbdbdc0fbe5df3567e4c50c43a4@projects.linpro.no> Message-ID: <059.f4820fbc5669dba41a64f263b8ee25eb@projects.linpro.no> #182: [patch]: New option to force flush from varnishncsa after each log line -------------------------+-------------------------------------------------- Reporter: adam | Owner: des Type: enhancement | Status: new Priority: normal | Milestone: Component: varnishncsa | Version: trunk Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by madssj): * summary: New option to force flush from varnishncsa after each log line => [patch]: New option to force flush from varnishncsa after each log line -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 15 16:05:47 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 15 Jan 2008 16:05:47 -0000 Subject: [Varnish] #179: varnishd segfault on non-ascii headers In-Reply-To: <060.00f3b2ac37a955079a94258093928517@projects.linpro.no> References: <060.00f3b2ac37a955079a94258093928517@projects.linpro.no> Message-ID: <069.c9e72fd9d1e5e295cf8afa90a7539a75@projects.linpro.no> #179: varnishd segfault on non-ascii headers ----------------------------+----------------------------------------------- Reporter: denis at zeno.org | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by madssj): * summary: varnish splits up http when there are non ASCII characters in it (german umlaut in this case) => varnishd segfault on non-ascii headers Comment: I've just tested this on r2344, and it has not been fixed. The backend dies when a non ascii status header is sent. I've tested with this response: {{{ HTTP/1.1 302 K?DP???G Location: http://other.server.tld/path/to/dir/ }}} Which crashes the backend every time. The status code is irelevant. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 15 16:07:13 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 15 Jan 2008 16:07:13 -0000 Subject: [Varnish] #155: varnishncsa -b results in empty output In-Reply-To: <052.15db299ad6ec4d546be3f9c42090b487@projects.linpro.no> References: <052.15db299ad6ec4d546be3f9c42090b487@projects.linpro.no> Message-ID: <061.ddb9b80bc87add1eb049f908df1c548a@projects.linpro.no> #155: varnishncsa -b results in empty output -------------------------+-------------------------------------------------- Reporter: anders | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: varnishncsa | Version: 1.1.1 Severity: normal | Resolution: fixed Keywords: varnishncsa | -------------------------+-------------------------------------------------- Changes (by madssj): * status: new => closed * resolution: => fixed * summary: varnishncsa -b does not work => varnishncsa -b results in empty output Comment: This has been fixed in trunk. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 15 16:12:22 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 15 Jan 2008 16:12:22 -0000 Subject: [Varnish] #166: debian/varnish.postinst fails In-Reply-To: <053.e799974f9ed4b655988a18eb8fa76c07@projects.linpro.no> References: <053.e799974f9ed4b655988a18eb8fa76c07@projects.linpro.no> Message-ID: <062.9cb84abfda623c6676b1d9df630a321f@projects.linpro.no> #166: debian/varnish.postinst fails ---------------------------------------+------------------------------------ Reporter: havardf | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: packaging | Version: trunk Severity: normal | Resolution: fixed Keywords: postinst debian packaging | ---------------------------------------+------------------------------------ Changes (by madssj): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 15 16:14:11 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 15 Jan 2008 16:14:11 -0000 Subject: [Varnish] #197: HTTP/1.0 query return no content In-Reply-To: <051.fc35504a2f711886fdf4302b5c601a42@projects.linpro.no> References: <051.fc35504a2f711886fdf4302b5c601a42@projects.linpro.no> Message-ID: <060.2e8739fb98dc63031c87e94f5a3f0595@projects.linpro.no> #197: HTTP/1.0 query return no content ----------------------+----------------------------------------------------- Reporter: chr79 | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 1.1.2 Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by madssj): * status: new => closed * resolution: => fixed Comment: Is fixed in trunk. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 15 16:39:09 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 15 Jan 2008 16:39:09 -0000 Subject: [Varnish] #155: varnishncsa -b results in empty output In-Reply-To: <052.15db299ad6ec4d546be3f9c42090b487@projects.linpro.no> References: <052.15db299ad6ec4d546be3f9c42090b487@projects.linpro.no> Message-ID: <061.52a8df17b56be7ef567e98b243250627@projects.linpro.no> #155: varnishncsa -b results in empty output -------------------------+-------------------------------------------------- Reporter: anders | Owner: des Type: defect | Status: reopened Priority: normal | Milestone: Component: varnishncsa | Version: trunk Severity: normal | Resolution: Keywords: varnishncsa | -------------------------+-------------------------------------------------- Changes (by madssj): * status: closed => reopened * version: 1.1.1 => trunk * resolution: fixed => Comment: It seems as though there might be an issue with this on smp machines. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jan 16 00:26:07 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 16 Jan 2008 00:26:07 -0000 Subject: [Varnish] #198: Varnish doesn't respond to requests when cache is full Message-ID: <052.7d38759b21961d9b4ff23cf88818f62d@projects.linpro.no> #198: Varnish doesn't respond to requests when cache is full ----------------------+----------------------------------------------------- Reporter: frekri | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------------------------------- When I instruct Varnish to keep all elements of the cache it doesn't respond to requests when the cache has been filled up. I expect it to deliver the cached content and pipe non-cached. Add this to VCL and fill your cache to reconstruct: sub vcl_discard { keep; } -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jan 16 09:57:29 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 16 Jan 2008 09:57:29 -0000 Subject: [Varnish] #198: Varnish doesn't respond to requests when cache is full In-Reply-To: <052.7d38759b21961d9b4ff23cf88818f62d@projects.linpro.no> References: <052.7d38759b21961d9b4ff23cf88818f62d@projects.linpro.no> Message-ID: <061.2d726f38d8855fff0e1fdcebadf4f4bb@projects.linpro.no> #198: Varnish doesn't respond to requests when cache is full ----------------------+----------------------------------------------------- Reporter: frekri | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: invalid Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => invalid Comment: I can't tell which version of varnish you're using, but until the "degraded mode" code is finished, keeping expired content isn't going to do anything good for you. Poul-Henning -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jan 16 10:08:51 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 16 Jan 2008 10:08:51 -0000 Subject: [Varnish] #179: varnishd segfault on non-ascii headers In-Reply-To: <060.00f3b2ac37a955079a94258093928517@projects.linpro.no> References: <060.00f3b2ac37a955079a94258093928517@projects.linpro.no> Message-ID: <069.70cbe77fff154a5d54423678eb2a7964@projects.linpro.no> #179: varnishd segfault on non-ascii headers ----------------------------+----------------------------------------------- Reporter: denis at zeno.org | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------------+----------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: fixed in 2345 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jan 16 10:15:39 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 16 Jan 2008 10:15:39 -0000 Subject: [Varnish] #183: spelling mistake in vcl(7): locahost In-Reply-To: <052.d70ffedeb9c2761ef7cd2d7e38ba0995@projects.linpro.no> References: <052.d70ffedeb9c2761ef7cd2d7e38ba0995@projects.linpro.no> Message-ID: <061.24472005bb93fb71f00d7578bcc8f985@projects.linpro.no> #183: spelling mistake in vcl(7): locahost ---------------------------+------------------------------------------------ Reporter: Habbie | Owner: des Type: documentation | Status: closed Priority: normal | Milestone: Component: documentation | Version: trunk Severity: trivial | Resolution: fixed Keywords: man, vcl.7 | ---------------------------+------------------------------------------------ Changes (by phk): * status: new => closed * resolution: => fixed Comment: Fixed in 2346 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jan 16 10:18:22 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 16 Jan 2008 10:18:22 -0000 Subject: [Varnish] #189: C{ ... }C blocks not allowed outside sub, acl or backend In-Reply-To: <050.3378c91a54b1c5aa906fae97008af2b2@projects.linpro.no> References: <050.3378c91a54b1c5aa906fae97008af2b2@projects.linpro.no> Message-ID: <059.370ad5093de52b88c1da6fa50ef122a8@projects.linpro.no> #189: C{ ... }C blocks not allowed outside sub, acl or backend --------------------+------------------------------------------------------- Reporter: adam | 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 2336 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jan 16 10:27:08 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 16 Jan 2008 10:27:08 -0000 Subject: [Varnish] #196: Varnish crashes in ses_sum_acct (cache_session.c) In-Reply-To: <052.61fe925e2186fafc84082dac4cdf43db@projects.linpro.no> References: <052.61fe925e2186fafc84082dac4cdf43db@projects.linpro.no> Message-ID: <061.b7e64a4582b4009dd4803b9b9cfd2807@projects.linpro.no> #196: Varnish crashes in ses_sum_acct (cache_session.c) -------------------------------------------------------------+-------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.2 Severity: normal | Resolution: Keywords: varnishd core dump ses_sum_acct cache_session.c | -------------------------------------------------------------+-------------- Comment (by phk): I'm surprised that the fd/id/xid are all zero, in fact most of the session is zero, that looks really bogus. STP_AGAIN is also zero, so that is not relevant. Looks like a case of a session being forked, possibly the acceptor acting up again. No other obvious clue right now. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jan 16 10:28:36 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 16 Jan 2008 10:28:36 -0000 Subject: [Varnish] #195: Varnish crashes in RES_BuildHttp (cache_response.c) In-Reply-To: <052.570abebb906f380f6b27b77133169c10@projects.linpro.no> References: <052.570abebb906f380f6b27b77133169c10@projects.linpro.no> Message-ID: <061.0341463a9d41e9b497df409c7c6776d0@projects.linpro.no> #195: Varnish crashes in RES_BuildHttp (cache_response.c) ---------------------------------------------------------------+------------ Reporter: anders | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.2 Severity: normal | Resolution: Keywords: varnishd core dump RES_BuildHttp cache_response.c | ---------------------------------------------------------------+------------ Comment (by phk): sp->wrk == NULL is weird. I suspect this is also the acceptor acting up. (see also #196) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jan 16 15:35:36 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 16 Jan 2008 15:35:36 -0000 Subject: [Varnish] #187: Insufficient logging data - actual bytes transferred needed In-Reply-To: <052.e24a3b4d3f02f7eafd5b154cbc7cbed9@projects.linpro.no> References: <052.e24a3b4d3f02f7eafd5b154cbc7cbed9@projects.linpro.no> Message-ID: <061.83e7006e87e731c19a884939afda95fb@projects.linpro.no> #187: Insufficient logging data - actual bytes transferred needed -------------------------+-------------------------------------------------- Reporter: rinogo | Owner: phk Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishlog | Version: 1.1.1 Severity: normal | Resolution: duplicate Keywords: | -------------------------+-------------------------------------------------- Changes (by madssj): * status: new => closed * resolution: => duplicate Comment: Duplicate of #186. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jan 16 15:35:51 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 16 Jan 2008 15:35:51 -0000 Subject: [Varnish] #185: Repport bytes (really) transfered into statistics In-Reply-To: <050.27efe119bed31e21588d4686f12eaa60@projects.linpro.no> References: <050.27efe119bed31e21588d4686f12eaa60@projects.linpro.no> Message-ID: <059.247254c64b362bf6602880bfedb95282@projects.linpro.no> #185: Repport bytes (really) transfered into statistics -------------------------+-------------------------------------------------- Reporter: Gwen | Owner: des Type: enhancement | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: minor | Resolution: duplicate Keywords: | -------------------------+-------------------------------------------------- Changes (by madssj): * status: new => closed * resolution: => duplicate Comment: Duplicate of #186. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jan 16 18:07:55 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 16 Jan 2008 18:07:55 -0000 Subject: [Varnish] #173: Varnish dies with assert error in vca_kev In-Reply-To: <052.8574406c7e5bafedecb6ebc1dc83f0bb@projects.linpro.no> References: <052.8574406c7e5bafedecb6ebc1dc83f0bb@projects.linpro.no> Message-ID: <061.aeb0530f8a26553587c5441e44911a10@projects.linpro.no> #173: Varnish dies with assert error in vca_kev ----------------------------------------+----------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: trunk Severity: major | Resolution: Keywords: varnishd core dump vca_kev | ----------------------------------------+----------------------------------- Comment (by anders): This still happens with trunk up to date to 2237 in FreeBSD 7.0-PRERELEASE: {{{ Child said (2, 16839): <fd == kp->ident) not true. errno = 2 (No such file or directory) >> Cache child died pid=16839 status=0x86 }}} Backtrace: {{{ (gdb) bt #0 0x0000000800d0707c in thr_kill () from /lib/libc.so.7 #1 0x0000000800d90ceb in abort () from /lib/libc.so.7 #2 0x0000000800669a55 in lbv_assert (func=Variable "func" is not available. ) at assert.c:58 #3 0x00000000004086a3 in vca_kqueue_main (arg=Variable "arg" is not available. ) at cache_acceptor_kqueue.c:207 #4 0x0000000800a8ea88 in pthread_getprio () from /lib/libthr.so.3 #5 0x0000000000000000 in ?? () Cannot access memory at address 0x7fffff5fc000 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jan 18 09:09:16 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 18 Jan 2008 09:09:16 -0000 Subject: [Varnish] #180: Varnish core dump on Assert error in wrk_thread, kern.ipc.maxpipekva problem? In-Reply-To: <052.06c444aafd17907df1b1a198673d0246@projects.linpro.no> References: <052.06c444aafd17907df1b1a198673d0246@projects.linpro.no> Message-ID: <061.c066b7ee5630580790dc2df4be114013@projects.linpro.no> #180: Varnish core dump on Assert error in wrk_thread, kern.ipc.maxpipekva problem? ---------------------------------------------------------------+------------ Reporter: anders | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.2 Severity: normal | Resolution: Keywords: varnishd core dump wrk_thread kern.ipc.maxpipekva | ---------------------------------------------------------------+------------ Comment (by anders): I suppose we can close this one. It was a maxpipekva problem. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 22 18:12:58 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 22 Jan 2008 18:12:58 -0000 Subject: [Varnish] #199: varnish bug?! Message-ID: <051.07fad13d1ba0a317a4d53ab9fa5d543a@projects.linpro.no> #199: varnish bug?! ----------------------+----------------------------------------------------- Reporter: trall | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.1.2 Severity: major | Keywords: ----------------------+----------------------------------------------------- Hello varnishd seems to crash with the following message on debian etch, varnishd version 1.1.2 (backported from unstable) " Using old SHMFILE rolling(1)... rolling(2)... start child pid 17496 Child said (2, 17496): <> Assert error in ev_schedule_one(), mgt_event.c line 433: Condition(evb->lpfd < evb->npfd) not true. errno = 9 (Bad file descriptor) " this happens every time i start varnishd. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jan 24 15:02:34 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 24 Jan 2008 15:02:34 -0000 Subject: [Varnish] #200: Varnish crashes in VBE_new_bereq (cache_backend.c) Message-ID: <052.3d765983fa02fb4a4264f0672bbfa668@projects.linpro.no> #200: Varnish crashes in VBE_new_bereq (cache_backend.c) ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: varnishd core dump VBE_new_bereq ----------------------+----------------------------------------------------- Varnish crashes with this error message: {{{ Child said (2, 83138): <magic == 0x3b6d250c) not true. errno = 32 (Broken pipe) }}} I am running Varnish trunk up to date to commit 2344, with des' madvise patch applied: http://anders.fupp.net/test/varnishd_madvise.diff My VCL: {{{ backend default { set backend.host = "192.168.110.1"; set backend.port = "80"; } acl purge { "192.168.100.1"/32; } sub vcl_recv { if (req.http.host ~ "^(bars.*.foo.no|bazcache.foo.no)$") { if (req.request == "GET" || req.request == "HEAD") { lookup; } elsif (req.request ~ "^(PURGE|REPURGE)$") { if (client.ip ~ purge) { if (req.request == "REPURGE") { purge_url(req.url); error 200 "Repurged."; } else { lookup; } } else { error 405 "Not allowed."; } } else { pipe; } } else { error 403 "Access denied. Contact cacheadmin at foo.no if you have problems."; } } sub vcl_miss { if (req.request ~ "^(PURGE|REPURGE)$") { 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 || obj.status == 500) { pass; } if (!obj.valid) { error; } if (!obj.cacheable) { pass; } if (obj.http.Cookie) { remove obj.http.Cookie; } if (obj.http.Set-Cookie) { remove obj.http.Set-Cookie; } insert; } sub vcl_hash { set req.hash += req.url; if (req.http.host ~ "^bars.*.foo.no$") { set req.hash += "bars.foo.no"; } else { set req.hash += req.http.host; } hash; } }}} Backtrace: {{{ (gdb) bt #0 0x0000000800d16fec in thr_kill () from /lib/libc.so.7 #1 0x0000000800da0c5b in abort () from /lib/libc.so.7 #2 0x0000000800673d1f in lbv_assert (func=Could not find the frame base for "lbv_assert". ) at assert.c:58 #3 0x00000000004094fc in VBE_new_bereq () at cache_backend.c:143 #4 0x00000000004179a4 in http_FilterHeader (sp=0x14c5033008, how=8) at cache_http.c:630 #5 0x00000000004103f8 in cnt_miss (sp=0x14c5033008) at cache_center.c:611 #6 0x0000000000411556 in CNT_Session (sp=0x14c5033008) at steps.h:39 #7 0x000000000041a91d in wrk_do_one (w=0x7fffd46a4ae0) at cache_pool.c:193 #8 0x000000000041ae20 in wrk_thread (priv=0x800f11200) at cache_pool.c:247 #9 0x0000000800a9ea88 in pthread_getprio () from /lib/libthr.so.3 #10 0x00007fffd44a5000 in ?? () Error accessing memory address 0x7fffd46a5000: Bad address. (gdb) frame 3 #3 0x00000000004094fc in VBE_new_bereq () at cache_backend.c:143 143 CHECK_OBJ(bereq, BEREQ_MAGIC); (gdb) print *sp No symbol "sp" in current context. (gdb) print *bereq $6 = {magic = 0, list = {vtqe_next = 0x0, vtqe_prev = 0x53f090}, ws = {{ magic = 0, id = 0x0, s = 0x0, f = 0x0, r = 0x0, e = 0x0}}, http = {{ magic = 0, ws = 0x0, conds = 0 '\0', logtag = 0, status = 0, hd = {{ b = 0x0, e = 0x0} }, hdf = '\0' , nhd = 0}}} (gdb) frame 4 #4 0x00000000004179a4 in http_FilterHeader (sp=0x14c5033008, how=8) at cache_http.c:630 630 bereq = VBE_new_bereq(); (gdb) print *sp $1 = {magic = 741317722, fd = 3527, id = 3527, xid = 1007760133, restarts = 0, esis = 0, wrk = 0x7fffd46a4ae0, sockaddrlen = 16, mysockaddrlen = 128, sockaddr = 0x14c5033670, mysockaddr = 0x14c50336f0, addr = 0x14c5033770 "85.165.2.13", port = 0x14c503377c "10511", srcaddr = 0x1492db0660, doclose = 0x0, http = 0x14c50331c8, http0 = 0x14c5033410, ws = {{magic = 905626964, id = 0x4387b8 "sess", s = 0x14c5033770 "85.165.2.13", f = 0x14c50339ce "inn_ld=aebDate: Thu, 24 Jan 2008 14:39:40 GMT", r = 0x0, e = 0x14c5037770 ""}}, ws_ses = 0x14c5033782 "GET", ws_req = 0x14c5033996 "", htc = {{magic = 1041886673, fd = 3527, ws = 0x14c5033070, rxbuf = {b = 0x14c5033782 "GET", e = 0x14c5033996 ""}, pipeline = {b = 0x0, e = 0x0}}}, t_open = 1201185585.8976934, t_req = 1201185585.9043143, t_resp = nan(0x8000000000000), t_end = nan(0x8000000000000), step = STP_MISS, cur_method = 0, handling = 4, wantbody = 1 '\001', err_code = 0, err_reason = 0x0, list = {vtqe_next = 0x0, vtqe_prev = 0x0}, backend = 0x800f14140, bereq = 0x0, obj = 0x1111782000, vcl = 0x1489c03920, mem = 0x14c5033000, workreq = {list = {vtqe_next = 0x0, vtqe_prev = 0x0}, sess = 0x14c5033008}, acct = {first = 1201185585.8976934, sess = 0, req = 0, pipe = 0, pass = 0, fetch = 0, hdrbytes = 0, bodybytes = 0}, nhashptr = 6, ihashptr = 4, lhashptr = 53, hashptr = 0x14c5033998} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jan 24 15:11:54 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 24 Jan 2008 15:11:54 -0000 Subject: [Varnish] #200: Varnish crashes in VBE_new_bereq (cache_backend.c) In-Reply-To: <052.3d765983fa02fb4a4264f0672bbfa668@projects.linpro.no> References: <052.3d765983fa02fb4a4264f0672bbfa668@projects.linpro.no> Message-ID: <061.d10496424bd29afb59a44935063b90b3@projects.linpro.no> #200: Varnish crashes in VBE_new_bereq (cache_backend.c) ----------------------------------------------+----------------------------- Reporter: anders | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: varnishd core dump VBE_new_bereq | ----------------------------------------------+----------------------------- Changes (by des): * owner: phk => des * status: new => assigned Comment: Most likely related to the {{{madvise()}}} patch Anders is testing. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jan 28 12:35:22 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 28 Jan 2008 12:35:22 -0000 Subject: [Varnish] #199: varnish bug?! In-Reply-To: <051.07fad13d1ba0a317a4d53ab9fa5d543a@projects.linpro.no> References: <051.07fad13d1ba0a317a4d53ab9fa5d543a@projects.linpro.no> Message-ID: <060.b9245075f56d7eec1b30ab206280fabf@projects.linpro.no> #199: varnish bug?! ----------------------+----------------------------------------------------- Reporter: trall | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.1.2 Severity: major | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by trall): also happends in trunk: 1. 200 0 2. 3. 200 0 4. 5. start child pid 22022 6. Child said (2, 22022): <> 24. Clean child 25. Child stopping 26. Child said (3, 22022): <> 28. Cache child died pid=22022 status=0x100 29. Child cleaned 30. start child pid 22234 31. Child said (2, 22234): <> 49. Assert error in ev_schedule_one(), mgt_event.c line 433: 50. Condition(evb->lpfd < evb->npfd) not true. 51. errno = 9 (Bad file descriptor) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jan 28 12:59:41 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 28 Jan 2008 12:59:41 -0000 Subject: [Varnish] #201: "download as zip archive" doesnt build Message-ID: <051.df78b50376565f503f76536374ea7092@projects.linpro.no> #201: "download as zip archive" doesnt build ---------------------+------------------------------------------------------ Reporter: trall | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: website | Version: trunk Severity: normal | Keywords: ---------------------+------------------------------------------------------ try to download the zip archive from http://varnish.projects.linpro.no/browser/trunk and build it... -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 29 08:01:36 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 29 Jan 2008 08:01:36 -0000 Subject: [Varnish] #199: varnish bug?! In-Reply-To: <051.07fad13d1ba0a317a4d53ab9fa5d543a@projects.linpro.no> References: <051.07fad13d1ba0a317a4d53ab9fa5d543a@projects.linpro.no> Message-ID: <060.5385401f8e2c809c58f84626b2b5b98c@projects.linpro.no> #199: varnish bug?! ----------------------+----------------------------------------------------- Reporter: trall | Owner: phk Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: 1.1.2 Severity: major | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => assigned Comment: evb->npfd is never ever decreased, so I can only assume that this is memory corruption. Getting details out of a core dump might help locating the source. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 29 08:29:41 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 29 Jan 2008 08:29:41 -0000 Subject: [Varnish] #196: Varnish crashes in ses_sum_acct (cache_session.c) In-Reply-To: <052.61fe925e2186fafc84082dac4cdf43db@projects.linpro.no> References: <052.61fe925e2186fafc84082dac4cdf43db@projects.linpro.no> Message-ID: <061.4db7a6210846fcc7fb5ebfeb7fb13f0d@projects.linpro.no> #196: Varnish crashes in ses_sum_acct (cache_session.c) -------------------------------------------------------------+-------------- Reporter: anders | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 1.2 Severity: normal | Resolution: fixed Keywords: varnishd core dump ses_sum_acct cache_session.c | -------------------------------------------------------------+-------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: This was due to the kqueue acceptors race, fixed elsewhere. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 29 08:33:46 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 29 Jan 2008 08:33:46 -0000 Subject: [Varnish] #195: Varnish crashes in RES_BuildHttp (cache_response.c) In-Reply-To: <052.570abebb906f380f6b27b77133169c10@projects.linpro.no> References: <052.570abebb906f380f6b27b77133169c10@projects.linpro.no> Message-ID: <061.e3fdefb131bb2f1886afc4482d42a893@projects.linpro.no> #195: Varnish crashes in RES_BuildHttp (cache_response.c) ---------------------------------------------------------------+------------ Reporter: anders | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.2 Severity: normal | Resolution: Keywords: varnishd core dump RES_BuildHttp cache_response.c | ---------------------------------------------------------------+------------ Changes (by phk): * owner: phk => des Comment: This is indeed the same as #196. Leaving this one open to make sure we have a ticket to track merging to 1.x branches. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 29 08:35:36 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 29 Jan 2008 08:35:36 -0000 Subject: [Varnish] #173: Varnish dies with assert error in vca_kev In-Reply-To: <052.8574406c7e5bafedecb6ebc1dc83f0bb@projects.linpro.no> References: <052.8574406c7e5bafedecb6ebc1dc83f0bb@projects.linpro.no> Message-ID: <061.d52f750d0a2421ff96363f8e7813a3eb@projects.linpro.no> #173: Varnish dies with assert error in vca_kev ----------------------------------------+----------------------------------- Reporter: anders | Owner: phk Type: defect | Status: closed Priority: high | Milestone: Component: varnishd | Version: trunk Severity: major | Resolution: fixed Keywords: varnishd core dump vca_kev | ----------------------------------------+----------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: This is belived to be the same acceptor race as #195 & #196 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 29 08:37:40 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 29 Jan 2008 08:37:40 -0000 Subject: [Varnish] #181: osx leopard: unknown sendfile() implementation In-Reply-To: <053.fe4dde1a1b9387be05d3390e48119f02@projects.linpro.no> References: <053.fe4dde1a1b9387be05d3390e48119f02@projects.linpro.no> Message-ID: <062.48b2f00e3bed0e587d981ba7eccbb64f@projects.linpro.no> #181: osx leopard: unknown sendfile() implementation ---------------------+------------------------------------------------------ Reporter: batlogg | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: 1.1.1 Severity: normal | Resolution: fixed Keywords: | ---------------------+------------------------------------------------------ Changes (by phk): * status: new => closed * resolution: => fixed Comment: We have stopped using sendfile on all OS' until a suitable way to deal with their lack of feedback have been devised. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 29 08:38:30 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 29 Jan 2008 08:38:30 -0000 Subject: [Varnish] #173: Varnish dies with assert error in vca_kev In-Reply-To: <052.8574406c7e5bafedecb6ebc1dc83f0bb@projects.linpro.no> References: <052.8574406c7e5bafedecb6ebc1dc83f0bb@projects.linpro.no> Message-ID: <061.b2f25f57f69bb86aef89111bee44edea@projects.linpro.no> #173: Varnish dies with assert error in vca_kev ----------------------------------------+----------------------------------- Reporter: anders | Owner: phk Type: defect | Status: reopened Priority: high | Milestone: Component: varnishd | Version: trunk Severity: major | Resolution: Keywords: varnishd core dump vca_kev | ----------------------------------------+----------------------------------- Changes (by phk): * status: closed => reopened * resolution: fixed => Comment: Oops, anders says still being seen. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jan 29 12:21:58 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 29 Jan 2008 12:21:58 -0000 Subject: [Varnish] #173: Varnish dies with assert error in vca_kev In-Reply-To: <052.8574406c7e5bafedecb6ebc1dc83f0bb@projects.linpro.no> References: <052.8574406c7e5bafedecb6ebc1dc83f0bb@projects.linpro.no> Message-ID: <061.e930d9034a9da3963d8bc73e1e4f9a01@projects.linpro.no> #173: Varnish dies with assert error in vca_kev ----------------------------------------+----------------------------------- Reporter: anders | Owner: phk Type: defect | Status: reopened Priority: high | Milestone: Component: varnishd | Version: trunk Severity: major | Resolution: Keywords: varnishd core dump vca_kev | ----------------------------------------+----------------------------------- Comment (by anders): Happened again, with trunk/2344. Varnish ran for a couple of hours, collecting illion objects before it crashed: {{{ Child said (2, 72853): <fd == kp->ident) not true. errno = 2 (No such file or directory) >> Cache child died pid=72853 status=0x86 }}} Backtrace: {{{ (gdb) bt #0 0x0000000800d16fec in thr_kill () from /lib/libc.so.7 #1 0x0000000800da0c5b in abort () from /lib/libc.so.7 #2 0x0000000800673d1f in lbv_assert (func=Could not find the frame base for "lbv_assert". ) at assert.c:58 #3 0x0000000000408b38 in vca_kev (kp=0x7fffff5fb520) at cache_acceptor_kqueue.c:207 #4 0x0000000000408efe in vca_kqueue_main (arg=0x0) at cache_acceptor_kqueue.c:263 #5 0x0000000800a9ea88 in pthread_getprio () from /lib/libthr.so.3 #6 0x0000000000000000 in ?? () Cannot access memory at address 0x7fffff5fc000 (gdb) frame 3 #3 0x0000000000408b38 in vca_kev (kp=0x7fffff5fb520) at cache_acceptor_kqueue.c:207 207 assert(sp->fd == kp->ident); (gdb) print *sp $1 = {magic = 741317722, fd = -1, id = 591, xid = 0, restarts = 0, esis = 0, wrk = 0x0, sockaddrlen = 16, mysockaddrlen = 128, sockaddr = 0x148f57e670, mysockaddr = 0x148f57e6f0, addr = 0x148f57e770 "80.239.23.142", port = 0x148f57e77e "4822", srcaddr = 0x0, doclose = 0x0, http = 0x148f57e1c8, http0 = 0x148f57e410, ws = {{magic = 905626964, id = 0x438848 "sess", s = 0x148f57e770 "80.239.23.142", f = 0x148f57e783 "", r = 0x148f580783 "", e = 0x148f582770 ""}}, ws_ses = 0x148f57e783 "", ws_req = 0x148f57e956 "", htc = {{ magic = 1041886673, fd = 591, ws = 0x148f57e070, rxbuf = { b = 0x148f57e783 "", e = 0x148f57e783 ""}, pipeline = {b = 0x0, e = 0x0}}}, t_open = 1201608132.8032956, t_req = nan(0x8000000000000), t_resp = nan(0x8000000000000), t_end = 1201608132.8032956, step = STP_DONE, cur_method = 0, handling = 128, wantbody = 0 '\0', err_code = 0, err_reason = 0x0, list = {vtqe_next = 0x148dfb0008, vtqe_prev = 0x148ef2e120}, backend = 0x0, bereq = 0x0, obj = 0x0, vcl = 0x0, mem = 0x148f57e000, workreq = {list = {vtqe_next = 0x0, vtqe_prev = 0x0}, sess = 0x148f57e008}, acct = { first = 1201608130.8505447, sess = 1, req = 6, pipe = 0, pass = 0, fetch = 0, hdrbytes = 1056, bodybytes = 0}, nhashptr = 6, ihashptr = 4, lhashptr = 48, hashptr = 0x148f57e958} (gdb) print *kp $2 = {ident = 591, filter = -1, flags = 0, fflags = 0, data = 518, udata = 0x148f57e008} (gdb) print kp $3 = (const struct kevent *) 0x7fffff5fb520 (gdb) print sp $4 = (struct sess *) 0x148f57e008 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator