From varnish-bugs at projects.linpro.no Tue May 1 18:05:39 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 01 May 2007 18:05:39 -0000 Subject: [Varnish] #95: Log entries mixed up with -o In-Reply-To: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> References: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> Message-ID: <086.96efe3d2d014956175b5a0c8048c6d96@projects.linpro.no> #95: Log entries mixed up with -o ------------------------+--------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishlog | Version: Severity: normal | Resolution: fixed Keywords: | ------------------------+--------------------------------------------------- Changes (by des): * status: new => closed * resolution: => fixed Comment: Fixed in r1372. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue May 1 18:06:38 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 01 May 2007 18:06:38 -0000 Subject: [Varnish] #95: Log entries mixed up with -o In-Reply-To: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> References: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> Message-ID: <086.5cb39b68143d31e37d85faf683cd742c@projects.linpro.no> #95: Log entries mixed up with -o ------------------------+--------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishlog | Version: Severity: normal | Resolution: fixed Keywords: | ------------------------+--------------------------------------------------- Old description: > When using varnishlog -o, log entries for cache misses appear on the > same line as the preceding log entry: > > # varnishlog -o | grep 'VCL_call' | grep miss > 12 VCL_call c recv lookup 12 VCL_call c miss fetch > 15 VCL_call c recv lookup 15 VCL_call c miss fetch > 15 VCL_call c recv lookup 15 VCL_call c miss fetch > 12 VCL_call c recv lookup 12 VCL_call c miss fetch > 15 VCL_call c recv lookup 15 VCL_call c miss fetch > 15 VCL_call c recv lookup 15 VCL_call c miss fetch > ^C > > # varnishlog | grep 'VCL_call' | grep miss > 16 VCL_call c miss > 17 VCL_call c miss > 16 VCL_call c miss > 17 VCL_call c miss > 21 VCL_call c miss > 24 VCL_call c miss > ^C > > I am using Varnish 1.0.3 on FreeBSD/amd64, 6.2-RELEASE. New description: When using varnishlog -o, log entries for cache misses appear on the same line as the preceding log entry: {{{ # varnishlog -o | grep 'VCL_call' | grep miss 12 VCL_call c recv lookup 12 VCL_call c miss fetch 15 VCL_call c recv lookup 15 VCL_call c miss fetch 15 VCL_call c recv lookup 15 VCL_call c miss fetch 12 VCL_call c recv lookup 12 VCL_call c miss fetch 15 VCL_call c recv lookup 15 VCL_call c miss fetch 15 VCL_call c recv lookup 15 VCL_call c miss fetch ^C # varnishlog | grep 'VCL_call' | grep miss 16 VCL_call c miss 17 VCL_call c miss 16 VCL_call c miss 17 VCL_call c miss 21 VCL_call c miss 24 VCL_call c miss ^C }}} I am using Varnish 1.0.3 on FreeBSD/amd64, 6.2-RELEASE. Comment (by des): fixed formatting in original submission -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed May 2 10:25:47 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 02 May 2007 10:25:47 -0000 Subject: [Varnish] #95: Log entries mixed up with -o In-Reply-To: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> References: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> Message-ID: <086.0b956bd85573d76f022d7b8dda7d4cea@projects.linpro.no> #95: Log entries mixed up with -o ------------------------+--------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: reopened Priority: normal | Milestone: Component: varnishlog | Version: Severity: normal | Resolution: Keywords: | ------------------------+--------------------------------------------------- Changes (by denis at zeno.org): * status: closed => reopened * resolution: fixed => Comment: now it looks like this: 20 RxHeader c Host: www.zeno.org 20 VCL_call c recv lookup 20 VCL_call c hash hash 20 VCL_call c miss fetch 20 Backend c 23 vladoserver3 20 ObjProtocol c HTTP/1.1 20 ObjStatus c 200 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed May 2 12:15:04 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 02 May 2007 12:15:04 -0000 Subject: [Varnish] #95: Log entries mixed up with -o In-Reply-To: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> References: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> Message-ID: <086.d858d841289f3591ba4a079a7d758f46@projects.linpro.no> #95: Log entries mixed up with -o ------------------------+--------------------------------------------------- Reporter: anders | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: varnishlog | Version: Severity: normal | Resolution: Keywords: | ------------------------+--------------------------------------------------- Changes (by des): * status: reopened => new * owner: phk => des Comment: Sorry, it seems I'll have to look at it again. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed May 2 12:20:59 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 02 May 2007 12:20:59 -0000 Subject: [Varnish] #95: Log entries mixed up with -o In-Reply-To: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> References: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> Message-ID: <086.b1c32212b5592110f4a043b8fc5c6ed2@projects.linpro.no> #95: Log entries mixed up with -o ------------------------+--------------------------------------------------- Reporter: anders | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishlog | Version: Severity: normal | Resolution: Keywords: | ------------------------+--------------------------------------------------- Changes (by des): * status: new => assigned -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed May 2 12:21:41 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 02 May 2007 12:21:41 -0000 Subject: [Varnish] #95: Log entries mixed up with -o In-Reply-To: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> References: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> Message-ID: <086.9387fa12253c265dd9ae119741119645@projects.linpro.no> #95: Log entries mixed up with -o ------------------------+--------------------------------------------------- Reporter: anders | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishlog | Version: Severity: normal | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by des): Can you confirm that r1374 fixes this correctly? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed May 2 12:57:02 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 02 May 2007 12:57:02 -0000 Subject: [Varnish] #95: Log entries mixed up with -o In-Reply-To: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> References: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> Message-ID: <086.f69165e3776c21c67529b97f116320a6@projects.linpro.no> #95: Log entries mixed up with -o ------------------------+--------------------------------------------------- Reporter: anders | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishlog | Version: Severity: normal | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by denis at zeno.org): yes, this seems to work now -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed May 2 14:10:14 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 02 May 2007 14:10:14 -0000 Subject: [Varnish] #95: Log entries mixed up with -o In-Reply-To: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> References: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> Message-ID: <086.c07f719d0864ba9f2ebf1afabca100a0@projects.linpro.no> #95: Log entries mixed up with -o ------------------------+--------------------------------------------------- Reporter: anders | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishlog | Version: Severity: normal | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by denis at zeno.org): but "./varnishlog -o -i VCL_call" does not print the return value. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed May 2 14:27:35 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 02 May 2007 14:27:35 -0000 Subject: [Varnish] #95: Log entries mixed up with -o In-Reply-To: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> References: <077.04fcaa0aa0a89247a37b961a07a6f492@projects.linpro.no> Message-ID: <086.8f8ee0e38966d7006fb9064802540d1d@projects.linpro.no> #95: Log entries mixed up with -o ------------------------+--------------------------------------------------- Reporter: anders | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishlog | Version: Severity: normal | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by des): The return value is logged using a separate tag, {{{VCL_return}}}. In fact, the bug was in the code that merges {{{VCL_call}}} and {{{VCL_return}}} to a single line when they occur in succession. Try this: {{{ % varnishlog -c -o -i VCL_call -i VCL_return }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu May 3 08:12:21 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 03 May 2007 08:12:21 -0000 Subject: [Varnish] #100: Setting the TTL does not adjust Expires: header Message-ID: <077.529c2facc20f6e34f75b11da80424cd4@projects.linpro.no> #100: Setting the TTL does not adjust Expires: header ----------------------+----------------------------------------------------- Reporter: des | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------------------------------- Changing an object's TTL does not update its Expires: header. This can result in clients getting objects with an expiry date in the past. This may not necessarily be a problem, but there should be a way of updating Expires: if it is. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri May 4 12:18:51 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 04 May 2007 12:18:51 -0000 Subject: [Varnish] #102: RES_WriteObj() does not send body for POST Message-ID: <077.5c76543eb36707f6b0ba16aa648156dc@projects.linpro.no> #102: RES_WriteObj() does not send body for POST ----------------------+----------------------------------------------------- Reporter: des | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------------------------------- When handling certain AJAX applications, it is sometimes desirable to cache objects requested with {{{POST}}}, because some AJAX code uses {{{POST}}} instead of {{{GET}}} to work around caching issues in MSIE (see [http://en.wikipedia.org/wiki/XMLHttpRequest#Microsoft_Internet_Explorer_cache_issues]) This can be achieved with the following piece of VCL: {{{ sub vcl_recv { if (req.request == "POST" && (!req.http.content-length || req.http.content-length == "0")) { lookup; } } }}} Unfortunately, this does not work, because {{{RES_WriteObj()}}} only writes out the contents of the object if {{{sp->wantbody}}} is non-zero, and {{{sp->wantbody}}} is set to 1 in only one place, in {{{cnt_recv()}}}: {{{ sp->wantbody = !strcmp(sp->http->hd[HTTP_HDR_REQ].b, "GET"); }}} A quick fix is to set {{{sp->wantbody}}} to 1 also for {{{POST}}}: {{{ sp->wantbody = (!strcmp(sp->http->hd[HTTP_HDR_REQ].b, "GET") || !strcmp(sp->http->hd[HTTP_HDR_REQ].b, "POST")); }}} A better long-term fix is to allow {{{sp->wantbody}}} to be manipulated from VCL code, and move this logic to the default configuration (where it can be overriden by the user). -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri May 4 13:13:55 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 04 May 2007 13:13:55 -0000 Subject: [Varnish] #47: pass mode does not handle POST In-Reply-To: <077.977e6cfd0fca0f4c0d5229365ff9221c@projects.linpro.no> References: <077.977e6cfd0fca0f4c0d5229365ff9221c@projects.linpro.no> Message-ID: <086.dcc2a99a61421a3706f0e2e3b4d6a4cd@projects.linpro.no> #47: pass mode does not handle POST ----------------------+----------------------------------------------------- Reporter: des | Owner: des Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by des): Quick update to note that this is still an issue, and still something we want to solve. It would be really beneficial to have pass mode understand {{{POST}}}, because - it would allow connection reuse - response status and headers would be logged, so e.g. {{{varnishncsa}}} would be able to display {{{POST}}} requests -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue May 8 12:00:35 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 08 May 2007 12:00:35 -0000 Subject: [Varnish] #99: returning pass from vcl_hit crashes the child In-Reply-To: <077.bbbf162609d2057cd0329bf0e6d9ea47@projects.linpro.no> References: <077.bbbf162609d2057cd0329bf0e6d9ea47@projects.linpro.no> Message-ID: <086.7ca958f75aaf212283e5f3daf3f0b313@projects.linpro.no> #99: returning pass from vcl_hit crashes the child ----------------------------+----------------------------------------------- Reporter: denis at zeno.org | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: Severity: normal | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by denis at zeno.org): if (req.http.abc == "abc") { set obj.ttl = 5s; } This in vcl_hit() also kills a child sometimes (ca. every 10th request). So there is something really borken. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed May 9 07:26:48 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 09 May 2007 07:26:48 -0000 Subject: [Varnish] #103: Match requested IP to choose backend Message-ID: <077.48192d1b6ab31e0bc65846df4fdde4e3@projects.linpro.no> #103: Match requested IP to choose backend -------------------------+-------------------------------------------------- Reporter: teddy | Owner: phk Type: enhancement | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: -------------------------+-------------------------------------------------- In a virtual hosting environment with several backend servers with a large amount of domains/customers each, the possibility to match on which IP is requested (ie. varnish server has 15 IP-addresses assigned where each one represent one backend with vhosts) is needed to choose the correct backend. Matching on host headers becomes extremely ineffective. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu May 10 09:46:37 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 10 May 2007 09:46:37 -0000 Subject: [Varnish] #104: varnishncsa assertion fails sometimes Message-ID: <077.17e15d8e0c487140e5b5e9bed986d37d@projects.linpro.no> #104: varnishncsa assertion fails sometimes -----------------------+---------------------------------------------------- Reporter: dirkgomez | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: Severity: normal | Keywords: -----------------------+---------------------------------------------------- I've created a little varnishncsa watchdog script that restarts varnishncsa in case it doesn't run. It sometimes does report this error: Assert error in trimline(), varnishncsa.c line 160: Condition(p != NULL) not true. errno = 12 (Cannot allocate memory) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu May 10 09:47:56 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 10 May 2007 09:47:56 -0000 Subject: [Varnish] #104: varnishncsa assertion fails sometimes In-Reply-To: <077.17e15d8e0c487140e5b5e9bed986d37d@projects.linpro.no> References: <077.17e15d8e0c487140e5b5e9bed986d37d@projects.linpro.no> Message-ID: <086.303e4b02d221b5193df0484aaf07b10a@projects.linpro.no> #104: varnishncsa assertion fails sometimes -----------------------+---------------------------------------------------- Reporter: dirkgomez | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Comment (by dirkgomez): Doesn't belong to component build. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu May 10 09:56:33 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 10 May 2007 09:56:33 -0000 Subject: [Varnish] #104: varnishncsa assertion fails sometimes In-Reply-To: <077.17e15d8e0c487140e5b5e9bed986d37d@projects.linpro.no> References: <077.17e15d8e0c487140e5b5e9bed986d37d@projects.linpro.no> Message-ID: <086.7030791969e9ff34cb346b09cda8315c@projects.linpro.no> #104: varnishncsa assertion fails sometimes -------------------------+-------------------------------------------------- Reporter: dirkgomez | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: varnishncsa | Version: Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by des): * component: build => varnishncsa -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon May 14 13:35:07 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 14 May 2007 13:35:07 -0000 Subject: [Varnish] #94: broken fputs error checking in mgt_CallCc In-Reply-To: <077.b5831a8c6ed6a821489a56ab64f2e3cc@projects.linpro.no> References: <077.b5831a8c6ed6a821489a56ab64f2e3cc@projects.linpro.no> Message-ID: <086.096156122fc7063743bd443bb180fa1c@projects.linpro.no> #94: broken fputs error checking in mgt_CallCc ----------------------+----------------------------------------------------- Reporter: matled | 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 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri May 18 13:27:00 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 18 May 2007 13:27:00 -0000 Subject: [Varnish] #105: (varnishd), uid 0: exited on signal 6 (core dumped) Message-ID: <077.f59798cb09c13371a28a1a3471e223f5@projects.linpro.no> #105: (varnishd), uid 0: exited on signal 6 (core dumped) ----------------------+----------------------------------------------------- Reporter: patrik | Owner: phk Type: defect | Status: new Priority: high | Milestone: Varnish 1.0.4 Component: varnishd | Version: trunk Severity: critical | Keywords: ----------------------+----------------------------------------------------- Platform: 6.2-RELEASE FreeBSD 6.2-RELEASE. Version: r1451 from trunk. It seems like varnishd is crashing when having a lot of traffic (around 500 requests/sec) and receiving an "url.purge" command at the same time. Crash #1: #0 0x28108f37 in thr_kill () from /lib/libc.so.6 #1 0x280c41a5 in pthread_mutex_unlock () from /usr/lib/libthr.so.2 #2 0x280bc2ae in raise () from /usr/lib/libthr.so.2 #3 0x28183b78 in abort () from /lib/libc.so.6 #4 0x280a3cdd in lbv_assert (func=0x806a976 "EXP_TTLchange", file=0x806a91c "cache_expire.c", line=70, cond=0x806a984 "o->heap_idx != 0", err=0) at assert.c:58 #5 0x08050e3d in EXP_TTLchange (o=0x8251400) at cache_expire.c:70 #6 0x0805322a in HSH_Lookup (sp=0x822b004) at cache_hash.c:161 #7 0x0804fe3a in cnt_lookup (sp=0x822b004) at cache_center.c:450 #8 0x080508a0 in CNT_Session (sp=0x822b004) at steps.h:37 #9 0x0805751f in wrk_do_one (w=0xbe4e7cf0) at cache_pool.c:191 #10 0x08057a41 in wrk_thread (priv=0x80750a0) at cache_pool.c:244 #11 0x280be5cf in pthread_create () from /usr/lib/libthr.so.2 #12 0x00000000 in ?? () Crash #2: #0 0x28108f37 in thr_kill () from /lib/libc.so.6 #1 0x280c41a5 in pthread_mutex_unlock () from /usr/lib/libthr.so.2 #2 0x280bc2ae in raise () from /usr/lib/libthr.so.2 #3 0x28183b78 in abort () from /lib/libc.so.6 #4 0x280a3cdd in lbv_assert (func=0x80704ed "smf_alloc", file=0x806feb3 "storage_file.c", line=632, cond=0x8070524 "(smf) != NULL", err=22) at assert.c:58 #5 0x08066dbe in smf_alloc (st=0x8073120, size=131072) at storage_file.c:632 #6 0x08051a0b in fetch_chunked (sp=0x81e0004, fd=33, hp=0x81ec01c) at cache_fetch.c:153 #7 0x080526ed in Fetch (sp=0x81e0004) at cache_fetch.c:336 #8 0x0804f969 in cnt_fetch (sp=0x81e0004) at cache_center.c:290 #9 0x080508e2 in CNT_Session (sp=0x81e0004) at steps.h:40 #10 0x0805751f in wrk_do_one (w=0xbebeecf0) at cache_pool.c:191 #11 0x08057a41 in wrk_thread (priv=0x80750a0) at cache_pool.c:244 #12 0x280be5cf in pthread_create () from /usr/lib/libthr.so.2 #13 0x00000000 in ?? () -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri May 18 13:31:11 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 18 May 2007 13:31:11 -0000 Subject: [Varnish] #105: (varnishd), uid 0: exited on signal 6 (core dumped) In-Reply-To: <077.f59798cb09c13371a28a1a3471e223f5@projects.linpro.no> References: <077.f59798cb09c13371a28a1a3471e223f5@projects.linpro.no> Message-ID: <086.eb1cc084bacb4822873aaf3e37cc4799@projects.linpro.no> #105: (varnishd), uid 0: exited on signal 6 (core dumped) ----------------------+----------------------------------------------------- Reporter: patrik | Owner: phk Type: defect | Status: new Priority: high | Milestone: Varnish 1.0.4 Component: varnishd | Version: trunk Severity: critical | Resolution: Keywords: | ----------------------+----------------------------------------------------- -- Ticket URL: Varnish The Varnish HTTP Accelerator From vilhelm at aptoma.com Sun May 20 14:37:01 2007 From: vilhelm at aptoma.com (=?UTF-8?B?IlZpbGhlbG0gSy4gVmFyZMO4eSI=?=) Date: Sun, 20 May 2007 16:37:01 +0200 Subject: [Varnish] #105: (varnishd), uid 0: exited on signal 6 (core dumped) In-Reply-To: <077.f59798cb09c13371a28a1a3471e223f5@projects.linpro.no> References: <077.f59798cb09c13371a28a1a3471e223f5@projects.linpro.no> Message-ID: <46505D0D.1060707@aptoma.com> Varnish wrote: > #105: (varnishd), uid 0: exited on signal 6 (core dumped) > I have tried to attach the core files to this ticket via trac, but there's a limitation of 256k while the files have an size of 900-1000k. Can you fix this, or should i send the files somewhere else? -- Vilhelm. From des at linpro.no Sun May 20 14:39:38 2007 From: des at linpro.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Sun, 20 May 2007 16:39:38 +0200 Subject: [Varnish] #105: (varnishd), uid 0: exited on signal 6 (core dumped) In-Reply-To: <46505D0D.1060707@aptoma.com> ("Vilhelm K. =?utf-8?Q?Vard?= =?utf-8?Q?=C3=B8y=22's?= message of "Sun\, 20 May 2007 16\:37\:01 +0200") References: <077.f59798cb09c13371a28a1a3471e223f5@projects.linpro.no> <46505D0D.1060707@aptoma.com> Message-ID: <871whb36fp.fsf@des.linpro.no> "Vilhelm K. Vard?y" writes: > I have tried to attach the core files to this ticket via trac, but > there's a limitation of 256k while the files have an size > of 900-1000k. > > Can you fix this, or should i send the files somewhere else? I've increased the limit to 1 MB. DES -- Dag-Erling Sm?rgrav Senior Software Developer Linpro AS - www.linpro.no From varnish-bugs at projects.linpro.no Mon May 21 16:59:45 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 21 May 2007 16:59:45 -0000 Subject: [Varnish] #106: Varnish does not compile on OpenBSD. Message-ID: <077.6e4ea5f0ae63dadd3ef56ab1d8a5def4@projects.linpro.no> #106: Varnish does not compile on OpenBSD. --------------------+------------------------------------------------------- Reporter: brad | Owner: des Type: defect | Status: new Priority: normal | Milestone: Varnish 1.0.4 Component: build | Version: 1.0 Severity: major | Keywords: --------------------+------------------------------------------------------- Varnish 1.0.3/1.0.4 currently do not compile nor run on OpenBSD. I have patches here which allow Varnish to at least compile on OpenBSD. http://comstyle.com/varnish/patches/ I have a patch here to add the missing support for kqueue timers via the EVFILT_TIMER kqueue filter. http://comstyle.com/varnish/kqueue.diff But Varnish still does not work. The first time I attempted to start Varnish with no debugging enabled it was doing something as my HD was thrashing like crazy and my laptop become completely unresponsive for a minute or so and then I assume varnish died. I then attempted to start Varnish again with debugging enabled and I receive this assertion error. {{{ $ sudo varnishd -b 62.119.71.159:80 -d file /tmp/varnish.x16588 (unlinked) size 303706112 bytes (148294 fs- blocks, 74147 pages) Using old SHMFILE Assert error in DebugStunt(), varnishd.c line 311: Condition(dup2(pipes[0][1], 3) == 3) not true. errno = 9 (Bad file descriptor) Abort trap (core dumped) }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue May 22 13:25:44 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 22 May 2007 13:25:44 -0000 Subject: [Varnish] #106: Varnish does not compile on OpenBSD. In-Reply-To: <077.6e4ea5f0ae63dadd3ef56ab1d8a5def4@projects.linpro.no> References: <077.6e4ea5f0ae63dadd3ef56ab1d8a5def4@projects.linpro.no> Message-ID: <086.c811be42d760f1401cf1fee24c32900f@projects.linpro.no> #106: Varnish does not compile on OpenBSD. ----------------------+----------------------------------------------------- Reporter: brad | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: 1.0.4 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by des): BTW, {{{patch-config_h_in}}} is not needed as {{{config.h.in}}} is generated by autoheader. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue May 22 16:15:38 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 22 May 2007 16:15:38 -0000 Subject: [Varnish] #106: Varnish does not compile on OpenBSD. In-Reply-To: <077.6e4ea5f0ae63dadd3ef56ab1d8a5def4@projects.linpro.no> References: <077.6e4ea5f0ae63dadd3ef56ab1d8a5def4@projects.linpro.no> Message-ID: <086.f0e2bdbe149036c68eb47ef082a0c527@projects.linpro.no> #106: Varnish does not compile on OpenBSD. ----------------------+----------------------------------------------------- Reporter: brad | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 1.0.4 Severity: normal | Resolution: wontfix Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: assigned => closed * resolution: => wontfix Comment: I've spent most of the day looking into Varnish's behaviour on OpenBSD 4.1, and my conclusion so far is that the problems lie in OpenBSD's POSIX threads library. I don't have time to pursue this further, but if anyone is interested, I would suggest investigating the library's handling of signals (the management process gets a stray {{{SIGCHLD}}} early on, resulting in an error message from {{{mgt_sigchld}}}) and {{{poll()}}}. The infinite loop you observe seems to me to come from {{{poll()}}} returning 1 even though none of the polled descriptors are ready. Even if you fix these issues, I'm not sure running Varnish on OpenBSD is a good idea. I believe OpenBSD uses the very same M:N thread model that Solaris, FreeBSD and now NetBSD have abandoned. It's a good idea in theory, but it is based on the assumption that your userland thread scheduler can schedule threads (within the same process) faster than your kernel scheduler can, and this does not seem to be the case, judging from my {{{ktrace(1)}}} logs of {{{varnishd}}} running on OpenBSD 4.1. It also requires emulating all potentially blocking system calls in userland; this is where I suspect the {{{poll()}}} problem stems from. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sat May 26 05:23:39 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sat, 26 May 2007 05:23:39 -0000 Subject: [Varnish] #107: Varnish 1.0.4 RPM for RHEL 4 has broken init.d script Message-ID: <055.e90ca9c6b10a7688d0f4061bc41da518@projects.linpro.no> #107: Varnish 1.0.4 RPM for RHEL 4 has broken init.d script -----------------------+---------------------------------------------------- Reporter: dstoliker | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: -----------------------+---------------------------------------------------- The problem appears to lie in the different syntax of the functions included with /etc/init.d/functions dealing with pid files. For example, the v1.0.4 script start clause includes: daemon --pidfile ${PIDFILE} ${DAEMON} "$DAEMON_OPTS" -P ${PIDFILE} > /dev/null 2>&1 The daemon function included in CentOS4 (and presumably RHEL4) doesn't take the argument "--pidfile" whereas the version included with CentOS5 does. I've hacked up the init script and it ''seems'' work for CentOS4 - at least it starts, stops, restarts, reports status, and appears to function as expected. I don't really know or fully understand what functionality I've stripped out so YMMV. Here is the diff of the hacked up version and the original: {{{ 41c41 < daemon ${DAEMON} "$DAEMON_OPTS" -P ${PIDFILE} > /dev/null 2>&1 --- > daemon --pidfile ${PIDFILE} ${DAEMON} "$DAEMON_OPTS" -P ${PIDFILE} > /dev/null 2>&1 57c57 < killproc $DAEMON --- > killproc -p $PIDFILE $DAEMON 69c69 < status $PROCNAME --- > status -p $PIDFILE $PROCNAME }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon May 28 11:47:56 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 28 May 2007 11:47:56 -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.dcdc6fda35bc70ff18762e0cebfa4485@projects.linpro.no> #107: Varnish 1.0.4 RPM for RHEL 4 has broken init.d script -----------------------+---------------------------------------------------- Reporter: dstoliker | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Changes (by des): * status: new => assigned Comment: Unified diff for convenience: {{{ Index: varnish.initrc =================================================================== --- varnish.initrc (revision 1470) +++ varnish.initrc (working copy) @@ -38,7 +38,7 @@ echo -n "Please put configuration options in /etc/sysconfig/varnish" echo_failure else - daemon --pidfile ${PIDFILE} ${DAEMON} "$DAEMON_OPTS" -P ${PIDFILE} > /dev/null 2>&1 + daemon ${DAEMON} "$DAEMON_OPTS" -P ${PIDFILE} > /dev/null 2>&1 sleep 1 pkill -0 $PROCNAME RETVAL=$? @@ -54,7 +54,7 @@ ;; stop) echo -n "Stopping varnish HTTP accelerator: " - killproc -p $PIDFILE $DAEMON + killproc $DAEMON RETVAL=$? if [ $RETVAL -eq 0 ] then @@ -66,7 +66,7 @@ echo ;; status) - status -p $PIDFILE $PROCNAME + status $PROCNAME RETVAL=$? ;; restart|reload) }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue May 29 06:41:00 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 29 May 2007 06:41:00 -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.3231f5e3cd25bf175e00a549981e4312@projects.linpro.no> #107: Varnish 1.0.4 RPM for RHEL 4 has broken init.d script -----------------------+---------------------------------------------------- Reporter: dstoliker | Owner: ingvar Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Changes (by des): * owner: des => ingvar * status: assigned => new -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue May 29 17:06:04 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 29 May 2007 17:06:04 -0000 Subject: [Varnish] #108: varnish start didnt work Message-ID: <056.838996d189003c2dd5e919631172bfcc@projects.linpro.no> #108: varnish start didnt work ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: des Type: defect | Status: new Priority: normal | Milestone: Varnish 1.0.4 Component: packaging | Version: 1.0.4 Severity: normal | Keywords: ------------------------+--------------------------------------------------- On CentOs 4 I installed with: rpm -ivh varnish-libs-1.0.4-2el4.i386.rpm rpm -ivh varnish-1.0.4-2el4.i386.rpm All seems ok, but /etc/rc.d/init.d/varnish start reports FAILED I ran varnishd from the command line as root and its working great :-) I have it on 3 servers as a test but I'm worried its running as root. Any ideas ? Thanks Chris. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue May 29 20:09:33 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 29 May 2007 20:09:33 -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.47889dbe76db5e08bd4f3dc2dc8657f2@projects.linpro.no> #108: varnish start didnt work ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: des Type: defect | Status: new Priority: normal | Milestone: Varnish 1.0.4 Component: packaging | Version: 1.0.4 Severity: normal | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by chrisrixon): oops, Ticket #107 claims to address it :-O -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed May 30 08:39:11 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 30 May 2007 08:39:11 -0000 Subject: [Varnish] #109: Backend did not respond. Guru Meditation: Message-ID: <056.6ca93e87d93a2a3947ee0f5c3c336ef0@projects.linpro.no> #109: Backend did not respond. Guru Meditation: ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: phk Type: task | Status: new Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: 1.0.4 Severity: normal | Keywords: ------------------------+--------------------------------------------------- I am occasionally getting: "Error 503 Service Unavailable Backend did not respond. Guru Meditation: XID: 456452130" How long does varnish wait? Can the time be increased? Thanks Chris. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed May 30 10:53:32 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 30 May 2007 10:53:32 -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.37114e01e1e3176b58fb2d30986d9f68@projects.linpro.no> #107: Varnish 1.0.4 RPM for RHEL 4 has broken init.d script -----------------------+---------------------------------------------------- Reporter: dstoliker | Owner: ingvar Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Comment (by chrisrixon): Thanks very much. This worked on my CentOS 4.4 boxes :-) -- Ticket URL: Varnish The Varnish HTTP Accelerator