From varnish-bugs at projects.linpro.no Fri Aug 1 02:37:15 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 01 Aug 2008 02:37:15 -0000 Subject: [Varnish] #275: Varnish child stops responding In-Reply-To: <052.c197ec9345dac369784c70e85c4b85ec@projects.linpro.no> References: <052.c197ec9345dac369784c70e85c4b85ec@projects.linpro.no> Message-ID: <061.046257281c5e57743e6a1dda93e7fe53@projects.linpro.no> #275: Varnish child stops responding ---------------------------------+------------------------------------------ Reporter: chenxy | Owner: phk Type: defect | Status: new Priority: high | Milestone: Varnish 2.0 code complete Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: Varnish child stuck | ---------------------------------+------------------------------------------ Comment (by chenxy): thank you very much. I use the latest version (rev 3029) , But it stop responding again, but no error, no assert. Sometimes a few days, sometimes a few hours. please download core file link : http://211.144.155.13/varnishd- cores.tar.gz. (57.94M) I will try the latest version . please wait the report again. run environment: FreeBSD/amd64 7.0-RELEASE. kernel: GENERIC 4BSD scheduler with softupdate by default,Not SCHED_ULE ( I can't reboot the server now ) work threads: use default setting command: {{{ varnishd -F -a 0.0.0.0:80 -f /usr/local/etc/vcl.conf \ -u nobody -g nobody \ -T 10.71.5.25:8080 \ -s file,/data0/varnish/v,16G \ -s file,/data1/varnish/v,16G \ -s file,/data2/varnish/v,16G \ -s file,/data3/varnish/v,16G \ -h classic,500009 \ -p sess_workspace=16384 -p listen_depth=4096 \ -p lru_interval=3600 \ -p ping_interval=10 >> $logdir/varnish.out 2>&1 }}} work log: {{{ Jul 28 09:54:52 236-25 varnishd[90761]: child (90766) Started Jul 28 09:54:52 236-25 varnishd[90761]: Child (90766) said Closed fds: 7 8 11 12 14 15 Jul 28 09:54:52 236-25 varnishd[90761]: Child (90766) said Child starts Jul 28 09:54:52 236-25 varnishd[90761]: Child (90766) said managed to mmap 17179869184 bytes of 17179869184 Jul 28 09:54:52 236-25 varnishd[90761]: Child (90766) said Ready Jul 28 13:21:07 236-25 varnishd[90761]: Child (90766) not responding to ping, killing it. Jul 28 21:21:14 236-25 kernel: pid 90766 (varnishd), uid 65534: exited on signal 3 (core dumped) Jul 28 13:21:14 236-25 varnishd[90761]: child (92810) Started Jul 28 13:21:14 236-25 varnishd[90761]: Child (92810) said Closed fds: 7 8 11 12 14 15 Jul 28 13:21:14 236-25 varnishd[90761]: Child (92810) said Child starts Jul 28 13:21:14 236-25 varnishd[90761]: Child (92810) said managed to mmap 17179869184 bytes of 17179869184 Jul 28 13:21:14 236-25 varnishd[90761]: Child (92810) said Ready }}} Varnish is not conflict with the system configuration ? Or because http header?eg: cookies) ? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 1 03:08:12 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 01 Aug 2008 03:08:12 -0000 Subject: [Varnish] #275: Varnish child stops responding In-Reply-To: <052.c197ec9345dac369784c70e85c4b85ec@projects.linpro.no> References: <052.c197ec9345dac369784c70e85c4b85ec@projects.linpro.no> Message-ID: <061.112c31762c007a2ef35580bfb43dacaa@projects.linpro.no> #275: Varnish child stops responding ---------------------------------+------------------------------------------ Reporter: chenxy | Owner: phk Type: defect | Status: new Priority: high | Milestone: Varnish 2.0 code complete Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: Varnish child stuck | ---------------------------------+------------------------------------------ Comment (by chenxy): ha ha !! Have error!!! {{{ Child (23795) not responding to ping, killing it. Child (23795) not responding to ping, killing it. Child (23795) not responding to ping, killing it. Child (23795) not responding to ping, killing it. Child (23795) died signal=6 (core dumped) Child (23795) Panic message: Assert error in VRT_r_req_xid(), cache_vrt.c line 484: Condition(snprintf(p, size, "%d", sp->xid) < size) not true. errno = 32 (Broken pipe) thread = (cache-worker)sp = 0x180ab88008 { fd = 1025, id = 1025, xid = 2147587817, client = 117.24.101.212:58399, step = STP_ERROR, err_code = 403, err_reason = Request denied., ws = 0x180ab88078 { id = "sess", {s,f,r,e} = {0x180ab887a0,,+337,0x0,+16384}, }, worker = 0x7fffe7139ac0 { }, vcl = { srcname = { "/usr/local/etc/vcl.conf", "Default", }, }, obj = 0x841b29000 { refcnt = 1, xid = 0, ws = 0x841b29028 { id = "obj", {s,f,r,e} = {0x841b29348,,+136,0x0,+7352}, }, http = { ws = 0x841b29028 { id = "obj", {s,f,r,e} = {0x841b29348,,+136,0x0,+7352}, }, hd = { "Date: Thu, 31 Jul 2008 13:46:02 GMT", "Server: Varnish", "Retry-After: 0", "Content-Type: text/html; charset=utf-8", }, }, len = 0, store = { }, }, }, Child cleanup complete child (40765) Started Child (40765) said Closed fds: 7 8 11 12 14 15 Child (40765) said Child starts Child (40765) said managed to mmap 17179869184 bytes of 17179869184 Child (40765) said managed to mmap 17179869184 bytes of 17179869184 Child (40765) said managed to mmap 17179869184 bytes of 17179869184 Child (40765) said managed to mmap 17179869184 bytes of 17179869184 Child (40765) said Ready }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 1 08:47:05 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 01 Aug 2008 08:47:05 -0000 Subject: [Varnish] #217: varnishtop freeze In-Reply-To: <049.a5bcd9b08e2b26a91152e804621bfcd7@projects.linpro.no> References: <049.a5bcd9b08e2b26a91152e804621bfcd7@projects.linpro.no> Message-ID: <058.069adc991c878710122bc6aa9c38e71d@projects.linpro.no> #217: varnishtop freeze ------------------------+--------------------------------------------------- Reporter: akv | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishtop | Version: trunk Severity: normal | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by tfheen): I'm unable to reproduce this problem, which version is this with, and can you say something about your software and hardware platform? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 1 10:14:12 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 01 Aug 2008 10:14:12 -0000 Subject: [Varnish] #275: Varnish child stops responding In-Reply-To: <052.c197ec9345dac369784c70e85c4b85ec@projects.linpro.no> References: <052.c197ec9345dac369784c70e85c4b85ec@projects.linpro.no> Message-ID: <061.25a494bb4634ffedc6b38e7420aedb9d@projects.linpro.no> #275: Varnish child stops responding ---------------------------------+------------------------------------------ Reporter: chenxy | Owner: phk Type: defect | Status: new Priority: high | Milestone: Varnish 2.0 code complete Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: Varnish child stuck | ---------------------------------+------------------------------------------ Comment (by chenxy): I think threads maybe dead locked with pthread_mutex_lock by signal in shmlog.c file -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 1 10:44:39 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 01 Aug 2008 10:44:39 -0000 Subject: [Varnish] #221: Add a link for mod_extract_forwarded to FAQ In-Reply-To: <051.432c340d6e11a4a159772edb0bee1ce9@projects.linpro.no> References: <051.432c340d6e11a4a159772edb0bee1ce9@projects.linpro.no> Message-ID: <060.9655972f310f61b8acc07a741230da06@projects.linpro.no> #221: Add a link for mod_extract_forwarded to FAQ ---------------------------+------------------------------------------------ Reporter: nejko | Owner: perbu Type: documentation | Status: closed Priority: normal | Milestone: Component: documentation | Version: trunk Severity: normal | Resolution: fixed Keywords: | ---------------------------+------------------------------------------------ Changes (by tfheen): * status: new => closed * resolution: => fixed Comment: Link added to FAQ. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 1 11:15:17 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 01 Aug 2008 11:15:17 -0000 Subject: [Varnish] #273: running out of virtual memory on 32 bit server In-Reply-To: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> References: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> Message-ID: <065.e9e0be69d98c8e7943fa713d765808b6@projects.linpro.no> #273: running out of virtual memory on 32 bit server ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: des Type: defect | Status: reopened Priority: normal | Milestone: Varnish 1.2 Component: build | Version: 1.1.2 Severity: major | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by chrisrixon): Replying to [comment:5 phk]: > Is this still varnish 1.1.2 or are you running a newer version now ? Yes std release. > If it is 1.1.2, could you try running -trunk to see if that has the same thread buildup behaviour ? ok, will do. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sat Aug 2 12:26:35 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sat, 02 Aug 2008 12:26:35 -0000 Subject: [Varnish] #273: running out of virtual memory on 32 bit server In-Reply-To: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> References: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> Message-ID: <065.9072dacf38b03fc2d7786cb84910e403@projects.linpro.no> #273: running out of virtual memory on 32 bit server ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: des Type: defect | Status: reopened Priority: normal | Milestone: Varnish 1.2 Component: build | Version: 1.1.2 Severity: major | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by chrisrixon): How do I download trunk? I tried : svn copy svn+ssh://projects.linpro.no/svn/varnish/trunk varnish but it asks me for a password. Thanks. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 4 01:58:33 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 04 Aug 2008 01:58:33 -0000 Subject: [Varnish] #273: running out of virtual memory on 32 bit server In-Reply-To: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> References: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> Message-ID: <065.8ee670b0651f6a410075fbee58a4374a@projects.linpro.no> #273: running out of virtual memory on 32 bit server ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: des Type: defect | Status: reopened Priority: normal | Milestone: Varnish 1.2 Component: build | Version: 1.1.2 Severity: major | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by chenxy): svn co http://varnish.projects.linpro.no/svn/trunk/varnish-cache varnish -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 4 14:08:47 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 04 Aug 2008 14:08:47 -0000 Subject: [Varnish] #273: running out of virtual memory on 32 bit server In-Reply-To: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> References: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> Message-ID: <065.ad3ac2b83742c68e904eee33dde80327@projects.linpro.no> #273: running out of virtual memory on 32 bit server ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: des Type: defect | Status: reopened Priority: normal | Milestone: Varnish 1.2 Component: build | Version: 1.1.2 Severity: major | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by chrisrixon): Thanks, got it downloaded and compiled. I got some vcl errors so I ran with default vcl. No improvement I'm afraid, VSZ(ps AUX) went up to 3108736K and then it stopped serving pages. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 4 20:36:20 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 04 Aug 2008 20:36:20 -0000 Subject: [Varnish] #273: running out of virtual memory on 32 bit server In-Reply-To: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> References: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> Message-ID: <065.69191162e861141aa809e08fcea05191@projects.linpro.no> #273: running out of virtual memory on 32 bit server ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: des Type: defect | Status: reopened Priority: normal | Milestone: Varnish 1.2 Component: build | Version: 1.1.2 Severity: major | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by phk): If I understand you right, you are running in 64bit mode now ? It sounds suspiciously like something is not 64bit mode somewhere, but I don't have enough information to guide you to find out what or where... If you run varnishd with "-d -d", it will run in the foreground (remember to type "start" to get it running) and any really weird stuff will be printed on the terminal. Also, with the -trunk version, check your syslog for indicative messages. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 5 09:07:04 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 05 Aug 2008 09:07:04 -0000 Subject: [Varnish] #273: running out of virtual memory on 32 bit server In-Reply-To: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> References: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> Message-ID: <065.64b4c2fee17a087e5f0677d5f26762ea@projects.linpro.no> #273: running out of virtual memory on 32 bit server ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: des Type: defect | Status: reopened Priority: normal | Milestone: Varnish 1.2 Component: build | Version: 1.1.2 Severity: major | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by chrisrixon): Replying to [comment:10 phk]: > If I understand you right, you are running in 64bit mode now ? No this is 32 bit. We do get lots of VM usage (and quite a few worker threads) but it runs fine on 64 bit as it can bust the 32 bit barrier on memory) > If you run varnishd with "-d -d", it will run in the foreground (remember to type "start" to get it running) and any really weird stuff will be printed on the terminal. > > Also, with the -trunk version, check your syslog for indicative messages. Ok will do. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 5 10:05:33 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 05 Aug 2008 10:05:33 -0000 Subject: [Varnish] #273: running out of virtual memory on 32 bit server In-Reply-To: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> References: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> Message-ID: <065.8d96a84fa69b70f85ced98e144ead7bf@projects.linpro.no> #273: running out of virtual memory on 32 bit server ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: des Type: defect | Status: reopened Priority: normal | Milestone: Varnish 1.2 Component: build | Version: 1.1.2 Severity: major | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by phk): So I'm not sure we have a problem or not. In 32bit mode, getting to 3GB of VM is pretty darn impressive, and the crash when varnish runs out of VM is fully expected. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 5 11:46:27 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 05 Aug 2008 11:46:27 -0000 Subject: [Varnish] #273: running out of virtual memory on 32 bit server In-Reply-To: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> References: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> Message-ID: <065.6878c326b7d3c7ed76f7cd2c53fdeaa1@projects.linpro.no> #273: running out of virtual memory on 32 bit server ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: des Type: defect | Status: reopened Priority: normal | Milestone: Varnish 1.2 Component: build | Version: 1.1.2 Severity: major | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by chrisrixon): > If you run varnishd with "-d -d", it will run in the foreground (remember to type "start" to get it running) and any really weird stuff will be printed on the terminal. varnish slowly went up to about 1G of VM and then very rapidly up to 3G at which point I dropped it from the load balancer: {{{ # varnish/bin/varnishd/varnishd -d -d -a :80 \ > -b localhost:81 \ > -u varn -g varn \ > -s file,/var/lib/varnish/varnish_storage.bin,128M storage_file: filename: /var/lib/varnish/varnish_storage.bin size 128 MB. Using old SHMFILE Debugging mode, enter "start" to start child start child (12493) Started 200 0 Child (12493) said Closed fds: 4 9 10 12 13 Child (12493) said Child starts Child (12493) said managed to mmap 134217728 bytes of 134217728 Child (12493) said Ready Manager got SIGINT Stopping Child unlink ./vcl.1P9zoqAU.o }}} > Also, with the -trunk version, check your syslog for indicative messages. Couldn't see anything bad in /var/log/messages -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 7 05:34:41 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 07 Aug 2008 05:34:41 -0000 Subject: [Varnish] #204: Handling of HTTP headers In-Reply-To: <049.5c2d5cb25689ca35813ab8bcfb5bb74e@projects.linpro.no> References: <049.5c2d5cb25689ca35813ab8bcfb5bb74e@projects.linpro.no> Message-ID: <058.e92976daec9b1fb99b9cd417eb9c067d@projects.linpro.no> #204: Handling of HTTP headers ---------------------------+------------------------------------------------ Reporter: des | Owner: des Type: enhancement | Status: assigned Priority: normal | Milestone: After 2.0 Component: documentation | Version: trunk Severity: normal | Resolution: Keywords: | ---------------------------+------------------------------------------------ Changes (by tfheen): * milestone: => After 2.0 Comment: Add milestone per email discussion. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 7 07:11:22 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 07 Aug 2008 07:11:22 -0000 Subject: [Varnish] #267: Fix ESI If-Modified-Since bug In-Reply-To: <049.5a4dfd969e0d14cf94a446690e240ee2@projects.linpro.no> References: <049.5a4dfd969e0d14cf94a446690e240ee2@projects.linpro.no> Message-ID: <058.8f33634c5c38dbc10cc2d7e08623459f@projects.linpro.no> #267: Fix ESI If-Modified-Since bug ----------------------+----------------------------------------------------- Reporter: sky | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by petter): Is this ticket still valid with the current -trunk version? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 7 07:14:02 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 07 Aug 2008 07:14:02 -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.87dc1676d84a6aefe970fa3a25beb89c@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: | ----------------------+----------------------------------------------------- Comment (by petter): Is this ticket still valid with the current -trunk version? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 7 07:14:21 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 07 Aug 2008 07:14:21 -0000 Subject: [Varnish] #61: Varnish -> Apache httpd mod_rewrite : 7 seconds delay In-Reply-To: <052.21ea811fe428f87847d7c614e5b9609c@projects.linpro.no> References: <052.21ea811fe428f87847d7c614e5b9609c@projects.linpro.no> Message-ID: <061.2b00ac1dda417714abdf9a05899c24ca@projects.linpro.no> #61: Varnish -> Apache httpd mod_rewrite : 7 seconds delay -------------------------+-------------------------------------------------- Reporter: edward | Owner: phk Type: enhancement | Status: new Priority: normal | Milestone: Component: varnishd | Version: Severity: major | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by petter): Is this ticket still valid with the current -trunk version? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 7 07:14:42 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 07 Aug 2008 07:14:42 -0000 Subject: [Varnish] #55: varnish stops responding with apache keepalive On In-Reply-To: <049.210f15126f587d48d25888bbf845f087@projects.linpro.no> References: <049.210f15126f587d48d25888bbf845f087@projects.linpro.no> Message-ID: <058.da8c63b67b95cc700fb5c38d3b236d2a@projects.linpro.no> #55: varnish stops responding with apache keepalive On -----------------------+---------------------------------------------------- Reporter: ced | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: major | Resolution: Keywords: Keepalive | -----------------------+---------------------------------------------------- Comment (by petter): Is this ticket still valid with the current -trunk version? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 7 07:16:56 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 07 Aug 2008 07:16:56 -0000 Subject: [Varnish] #213: Varnish crashes on SES_Delete(), cache_session.c line 340 In-Reply-To: <052.7ce88d4f130a0405121a4fb62801b0b5@projects.linpro.no> References: <052.7ce88d4f130a0405121a4fb62801b0b5@projects.linpro.no> Message-ID: <061.96f0e5759c57c5bcfc9ae9490ff08a2a@projects.linpro.no> #213: Varnish crashes on SES_Delete(), cache_session.c line 340 ----------------------+----------------------------------------------------- Reporter: anders | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by petter): * status: new => closed * resolution: => fixed Comment: It has been done. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 7 07:17:58 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 07 Aug 2008 07:17:58 -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.3dc25a7490d75e84f3df0a44d31ec210@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: | ----------------------+----------------------------------------------------- Comment (by anders): It hasn't happened in quite a while. Maybe it can be closed. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 7 07:19:42 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 07 Aug 2008 07:19:42 -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.06c9ffec7be3acdd0e9eb197dec1722d@projects.linpro.no> #193: Varnish fails to restart after ping timeout ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 1.2 Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by petter): * status: new => closed * resolution: => fixed Comment: Closing it under the assumption is is fixed. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 7 07:23:19 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 07 Aug 2008 07:23:19 -0000 Subject: [Varnish] #256: Varnish Child Exits In-Reply-To: <054.fa0dedc6e6244f9fa3695bed20cbbb1f@projects.linpro.no> References: <054.fa0dedc6e6244f9fa3695bed20cbbb1f@projects.linpro.no> Message-ID: <063.19db653562be4ee568189fc23f096fc8@projects.linpro.no> #256: Varnish Child Exits ----------------------+----------------------------------------------------- Reporter: maxclark | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Varnish 2.0 code complete Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by petter): * status: reopened => closed * resolution: => fixed Comment: Closing it due to missing answer from reporter. Please reopen it if it still is valid. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 7 07:54:00 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 07 Aug 2008 07:54:00 -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.669489b39f17f8c665686a2e0d1222ee@projects.linpro.no> #182: [patch]: New option to force flush from varnishncsa after each log line -------------------------+-------------------------------------------------- Reporter: adam | Owner: des Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishncsa | Version: trunk Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by petter): * status: new => closed * resolution: => fixed Comment: Flushing of log buffer when writing to file was done in r2324 by DES. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 7 09:02:55 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 07 Aug 2008 09:02:55 -0000 Subject: [Varnish] #267: Fix ESI If-Modified-Since bug In-Reply-To: <049.5a4dfd969e0d14cf94a446690e240ee2@projects.linpro.no> References: <049.5a4dfd969e0d14cf94a446690e240ee2@projects.linpro.no> Message-ID: <058.123061ad105176a4efd91fdffd097c47@projects.linpro.no> #267: Fix ESI If-Modified-Since bug ----------------------+----------------------------------------------------- Reporter: sky | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by phk): Yes, this ticket is still valid. For 2.0 we will handle it with an release note that IMS does not take included content into account. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 7 09:08:38 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 07 Aug 2008 09:08:38 -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.e024b3ac347b4e0c3036f38b43a2a4bf@projects.linpro.no> #78: URLS without trailing / direct to backend . ----------------------+----------------------------------------------------- Reporter: kevinm | Owner: des Type: defect | Status: closed Priority: high | Milestone: Component: varnishd | Version: Severity: major | Resolution: invalid Keywords: | ----------------------+----------------------------------------------------- Changes (by tfheen): * status: assigned => closed * resolution: => invalid Comment: This problem is because your server issues redirects including port and host name. If you are using Apache, you can turn this off by using "UseCanonicalName Off" in your server configuration. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 7 10:01:34 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 07 Aug 2008 10:01:34 -0000 Subject: [Varnish] #229: Updated munin plugins for Varnish hitrate/cachehitratio In-Reply-To: <052.e51d21cba3b4229abff0051e45686332@projects.linpro.no> References: <052.e51d21cba3b4229abff0051e45686332@projects.linpro.no> Message-ID: <061.29d1c1debee2f8df93851cd88512bb6b@projects.linpro.no> #229: Updated munin plugins for Varnish hitrate/cachehitratio -------------------------+-------------------------------------------------- Reporter: anders | Owner: des Type: enhancement | Status: closed Priority: normal | Milestone: Component: munin | Version: trunk Severity: normal | Resolution: invalid Keywords: | -------------------------+-------------------------------------------------- Changes (by petter): * status: new => closed * resolution: => invalid Comment: The existing munin plugin by DES covers this. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 8 13:07:33 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 08 Aug 2008 13:07:33 -0000 Subject: [Varnish] #223: fixed redhat varnishlog init script and added one for varnishncsa In-Reply-To: <052.0a72877af7628ee3eb86ab4b4655aad2@projects.linpro.no> References: <052.0a72877af7628ee3eb86ab4b4655aad2@projects.linpro.no> Message-ID: <061.63c1fea8ea614d513db33d945790d6dc@projects.linpro.no> #223: fixed redhat varnishlog init script and added one for varnishncsa -------------------------------------------+-------------------------------- Reporter: hillct | Owner: des Type: defect | Status: new Priority: normal | Milestone: Varnish 2.0 release Component: packaging | Version: trunk Severity: normal | Resolution: Keywords: varnishlog varnishncsa redhat | -------------------------------------------+-------------------------------- Changes (by tfheen): * milestone: Varnish 1.2 => Varnish 2.0 release -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 8 13:08:03 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 08 Aug 2008 13:08:03 -0000 Subject: [Varnish] #273: running out of virtual memory on 32 bit server In-Reply-To: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> References: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> Message-ID: <065.d0f94c0619ca09b0bed76f80c5620acf@projects.linpro.no> #273: running out of virtual memory on 32 bit server ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: des Type: defect | Status: reopened Priority: normal | Milestone: Component: build | Version: 1.1.2 Severity: major | Resolution: Keywords: | ------------------------+--------------------------------------------------- Changes (by tfheen): * milestone: Varnish 1.2 => -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 11 08:57:06 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 11 Aug 2008 08:57:06 -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.b403530b7574f9f722abac984617ef3a@projects.linpro.no> #182: [patch]: New option to force flush from varnishncsa after each log line -------------------------+-------------------------------------------------- Reporter: adam | Owner: des Type: enhancement | Status: reopened Priority: normal | Milestone: Component: varnishncsa | Version: trunk Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by adam): * status: closed => reopened * resolution: fixed => Comment: This is insufficient for when piping output through, e.g. cronolog(1). It would be nice to have an option to explicity turn this on, even when writing logfiles to stdout. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 11 10:04:20 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 11 Aug 2008 10:04:20 -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.6d543fa0526d4781298cb9d6f78305af@projects.linpro.no> #182: [patch]: New option to force flush from varnishncsa after each log line -------------------------+-------------------------------------------------- Reporter: adam | Owner: des Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishncsa | Version: trunk Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by petter): * status: reopened => closed * resolution: => fixed Comment: It now always flushes. See r3080. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 12 09:53:55 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 12 Aug 2008 09:53:55 -0000 Subject: [Varnish] #286: Modify Error Messages (Guru Meditation) Message-ID: <048.fa624ee49af8c171f0f574c5c7d6bbf7@projects.linpro.no> #286: Modify Error Messages (Guru Meditation) -------------------------+-------------------------------------------------- Reporter: ay | Owner: phk Type: enhancement | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: -------------------------+-------------------------------------------------- It would be good if we could edit the Error messages without modifying the source. Even if I am an old Amiga Hacker, other people tend to react to the term "Guru Meditation". It would also be very helpfull if $HOSTNAME was available on error pages -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 12 09:59:27 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 12 Aug 2008 09:59:27 -0000 Subject: [Varnish] #286: Modify Error Messages (Guru Meditation) In-Reply-To: <048.fa624ee49af8c171f0f574c5c7d6bbf7@projects.linpro.no> References: <048.fa624ee49af8c171f0f574c5c7d6bbf7@projects.linpro.no> Message-ID: <057.c52d3cfba1ba3d3b62e372221d45dc04@projects.linpro.no> #286: Modify Error Messages (Guru Meditation) -------------------------+-------------------------------------------------- Reporter: ay | Owner: phk Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: In -trunk as of about a week ago, the error message is constructed in the VCL code and you can write your own error page now. I don't think we have the hostname readily available, we don't need it for anything else I think. I have added it to the "after 2.0" wishlist. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 12 12:51:29 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 12 Aug 2008 12:51:29 -0000 Subject: [Varnish] #287: Install semi-bug Message-ID: <054.f48fb6ec452ca864daad92c0272325dc@projects.linpro.no> #287: Install semi-bug ----------------------+----------------------------------------------------- Reporter: The_ZoRo | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------------------------------- When you type make after a ./configure you end up with the following text: echo -e "This is a basic VCL configuration file for varnish. See the vcl(7)\n\ man page for details on VCL syntax and semantics.\n\ \n\ Default backend definition. Set this to point to your content\n\ server.\n\ \n\ backend default {\n\ .host = "127.0.0.1";\n\ .port = "8080";\n\ }\n\ \n\ Below is a commented-out copy of the default VCL logic. If you\n\ redefine any of these subroutines, the built-in logic will be\n\ appended to your code.\n" > tmp.vcl The bug: All those \n\ things. Present in trunk 3083 /Mads -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 12 12:56:53 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 12 Aug 2008 12:56:53 -0000 Subject: [Varnish] #287: Install semi-bug In-Reply-To: <054.f48fb6ec452ca864daad92c0272325dc@projects.linpro.no> References: <054.f48fb6ec452ca864daad92c0272325dc@projects.linpro.no> Message-ID: <063.9dadd06d477946b6749feda7be5b81cc@projects.linpro.no> #287: Install semi-bug ----------------------+----------------------------------------------------- Reporter: The_ZoRo | Owner: petter Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by petter): * owner: des => petter -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 12 13:02:06 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 12 Aug 2008 13:02:06 -0000 Subject: [Varnish] #287: Install semi-bug In-Reply-To: <054.f48fb6ec452ca864daad92c0272325dc@projects.linpro.no> References: <054.f48fb6ec452ca864daad92c0272325dc@projects.linpro.no> Message-ID: <063.4d08f5c2a7f5e2e9e0b128efa2b3a288@projects.linpro.no> #287: Install semi-bug ----------------------+----------------------------------------------------- Reporter: The_ZoRo | Owner: petter Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by petter): * status: new => closed * resolution: => fixed Comment: Fixed in r3085. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Aug 13 03:53:18 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 13 Aug 2008 03:53:18 -0000 Subject: [Varnish] #288: Run failed . Prompt : VCL compilation failed Message-ID: <052.1de83b17eb3067c5869e4d887195f4d8@projects.linpro.no> #288: Run failed . Prompt : VCL compilation failed --------------------+------------------------------------------------------- Reporter: chenxy | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: vcl --------------------+------------------------------------------------------- trunk r3087 varnishd -a 0.0.0.0:80 -f /usr/local/etc/vcl.conf -u nobody -g nobody -T 10.217.15.204:3500 -w 300,3000,600 -s file,/data0/varnish/v,800M -s file,/data1/varnish/v,800M -p sess_workspace=16384 -p listen_depth=4096 -p lru_interval=60 -p ping_interval=10 storage_file: filename: /data0/varnish/v size 800 MB. storage_file: filename: /data1/varnish/v size 800 MB. Unknown variable 'obj.valid' At: (/usr/local/etc/vcl.conf Line 50 Pos 10) if (!obj.valid) { ---------#########--- VCL compilation failed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Aug 13 03:59:45 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 13 Aug 2008 03:59:45 -0000 Subject: [Varnish] #288: Run failed . Prompt : VCL compilation failed In-Reply-To: <052.1de83b17eb3067c5869e4d887195f4d8@projects.linpro.no> References: <052.1de83b17eb3067c5869e4d887195f4d8@projects.linpro.no> Message-ID: <061.95e59c4e578750b70b602f3803da43d7@projects.linpro.no> #288: Run failed . Prompt : VCL compilation failed --------------------+------------------------------------------------------- Reporter: chenxy | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: vcl | --------------------+------------------------------------------------------- Comment (by chenxy): Replying to [ticket:288 chenxy]: sorry,look here {{{ varnishd -a 0.0.0.0:80 -f /usr/local/etc/vcl.conf -u nobody -g nobody -T 10.217.15.204:3500 -w 300,3000,600 -s file,/data0/varnish/v,800M -s file,/data1/varnish/v,800M -p sess_workspace=16384 -p listen_depth=4096 -p lru_interval=60 -p ping_interval=10 storage_file: filename: /data0/varnish/v size 800 MB. storage_file: filename: /data1/varnish/v size 800 MB. Unknown variable 'obj.valid' At: (/usr/local/etc/vcl.conf Line 50 Pos 10) if (!obj.valid) { ---------#########--- VCL compilation failed }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Aug 13 06:48:14 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 13 Aug 2008 06:48:14 -0000 Subject: [Varnish] #288: Run failed . Prompt : VCL compilation failed In-Reply-To: <052.1de83b17eb3067c5869e4d887195f4d8@projects.linpro.no> References: <052.1de83b17eb3067c5869e4d887195f4d8@projects.linpro.no> Message-ID: <061.159c09fdecfb6cf102fa6a9db6fb0a14@projects.linpro.no> #288: Run failed . Prompt : VCL compilation failed --------------------+------------------------------------------------------- Reporter: chenxy | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: worksforme Keywords: vcl | --------------------+------------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => worksforme Comment: Please check the new default VCL code, various changes made have removed the obj.valid check in vcl_fetch{}. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Aug 13 06:49:47 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 13 Aug 2008 06:49:47 -0000 Subject: [Varnish] #273: running out of virtual memory on 32 bit server In-Reply-To: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> References: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> Message-ID: <065.30a79429aa4934be3bee201c50d671f3@projects.linpro.no> #273: running out of virtual memory on 32 bit server ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: des Type: defect | Status: reopened Priority: normal | Milestone: Component: build | Version: 1.1.2 Severity: major | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by phk): Can we see your VCL code ? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Aug 13 06:54:38 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 13 Aug 2008 06:54:38 -0000 Subject: [Varnish] #267: Fix ESI If-Modified-Since bug In-Reply-To: <049.5a4dfd969e0d14cf94a446690e240ee2@projects.linpro.no> References: <049.5a4dfd969e0d14cf94a446690e240ee2@projects.linpro.no> Message-ID: <058.afa45552a146a55ce869677e6d8e3be6@projects.linpro.no> #267: Fix ESI If-Modified-Since bug ----------------------+----------------------------------------------------- Reporter: sky | 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: Gah, I can see I was confused about tickets here. Committed in 3091 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Aug 13 15:20:00 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 13 Aug 2008 15:20:00 -0000 Subject: [Varnish] #273: running out of virtual memory on 32 bit server In-Reply-To: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> References: <056.39825030aa405e311ecaa7bd0075720a@projects.linpro.no> Message-ID: <065.7ec49c25c1b894d62d8774c0017975d9@projects.linpro.no> #273: running out of virtual memory on 32 bit server ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: des Type: defect | Status: reopened Priority: normal | Milestone: Component: build | Version: 1.1.2 Severity: major | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by chrisrixon): Replying to [comment:15 phk]: > Can we see your VCL code ? There is no vcl. (see above command line) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 14 12:35:38 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 14 Aug 2008 12:35:38 -0000 Subject: [Varnish] #289: VCL insert bug in trunk Message-ID: <048.0e137abc9e4b9b2b5584d366925ad7f4@projects.linpro.no> #289: VCL insert bug in trunk ----------------------+----------------------------------------------------- Reporter: ay | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------------------------------- I upgraded from trunk 2919 to 3092 and i get this error from my vcl on 3092 sub vcl_fetch { include "/etc/varnish/identity.vcl"; remove obj.http.X-VG-Varnish-IP; set obj.http.X-VG-Varnish-IP = server.ip; set obj.grace = 5s; if (obj.http.Set-Cookie) { insert; } } Expected action, 'if' or '}' (/etc/varnish/default.vcl Line 77 Pos 17) insert; ----------------######- VCL compilation failed This works in 2919 but not in 3092 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 14 12:53:39 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 14 Aug 2008 12:53:39 -0000 Subject: [Varnish] #289: VCL insert bug in trunk In-Reply-To: <048.0e137abc9e4b9b2b5584d366925ad7f4@projects.linpro.no> References: <048.0e137abc9e4b9b2b5584d366925ad7f4@projects.linpro.no> Message-ID: <057.c7c6fce8cafd03a4635003a48e9bb71b@projects.linpro.no> #289: VCL insert bug in trunk ----------------------+----------------------------------------------------- Reporter: ay | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by ay): Found commit 3048 Log: Rename the vcl_fetch{} action "insert" to "deliver" as we may not insert (for instance on pass) but we certainly will deliver (unless error or restart actions are used instead -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 19 08:40:18 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 19 Aug 2008 08:40:18 -0000 Subject: [Varnish] #290: Make dir in /usr/local/var/varnish Message-ID: <054.a171d91cbb7594e23ea750517981ab8a@projects.linpro.no> #290: Make dir in /usr/local/var/varnish ----------------------+----------------------------------------------------- Reporter: The_ZoRo | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------------------------------- On a fresh trunk (3104): make, cd trunk/varnish-cache/bin/varnishd/ ./varnishd Gives: Cannot create working directory '/usr/local/var/varnish/NAME': No such file or directory When I mkdir varnish in /usr/local/var/ it works (meaning it makes the working file it's supposed to make Any ideas? /Mads -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 19 12:45:16 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 19 Aug 2008 12:45:16 -0000 Subject: [Varnish] #291: Default.vcl Message-ID: <054.6d1fc28d069a1c4393afd6c5bed06e2b@projects.linpro.no> #291: Default.vcl ---------------------------+------------------------------------------------ Reporter: The_ZoRo | Owner: des Type: documentation | Status: new Priority: normal | Milestone: Component: documentation | Version: trunk Severity: normal | Keywords: ---------------------------+------------------------------------------------ After a svn co and a make I end up with this: [[BR]] /usr/local/etc/varnish/default.vcl /mnt/varnish/trunk/varnish-cache/man/default.vcl /mnt/varnish/trunk/varnish-cache/etc/default.vcl /mnt/varnish/trunk/varnish-cache/bin/varnishd/default.vcl Is there any reason why Varnish needs to have 4(!) defualt.vcl files spread around the filesystem? and if so, why? My two cents: have one file and make links (or something else) to it where there are different files now. OR just have one file called default.vcl and rename the other to something more describing: Examples ''doc-default.vcl'', ''run-default.vcl'' As it is right now I don't see a reason for the ''etc'' and ''bin'' files. Also, it would make it much easier for new people to get up to speed with only one or two files and instructions on how to edit the defualt /whatever-it's-called.vcl file to get a running system up at 3AM when something else breaks. /Mads -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 19 19:27:16 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 19 Aug 2008 19:27:16 -0000 Subject: [Varnish] #292: Connection header delete-flags can get out of sync with headers. Message-ID: <049.a262507c2525db1599b17f70c09f414a@projects.linpro.no> #292: Connection header delete-flags can get out of sync with headers. --------------------+------------------------------------------------------- Reporter: phk | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 2.0 code complete Component: build | Version: trunk Severity: major | Keywords: --------------------+------------------------------------------------------- {{{ From: Adrian Otto Subject: Re: Bug in 1.1.2: Multiple headers stripped (oops) To: varnish-dev at projects.linpro.no I found the reason why I hit this bug, but I need some tips to understand how to debug what's happening in the VCL code. First, I'll explain the bug: 1) My default.vcl is configured to strip the Cookie header in vcl_recv like this: sub vcl_recv { if(req.http.Cookie) { remove req.http.Cookie; lookup; } } 2) The Connection header sent from the client browser specified that the "TE" header should be stripped, and was so marked in position 13 of http_DoConnection::hp->hdf, indicating that header at index 13 should be skipped when headers are copied into the backend request. 3) The VCL code ran to strip the cookie header, removed it, and shifted the other elements in the array UP one position. The Host header followed TE at position/index 14, and became position/index 13. 4) The code for copying/morphing the client request to the backend ran, and skipped position/index 13, which was the Host header. 5) Varnish kindly noticed that there was no Host header present in the backend connection, and added one of it's own using the IP address of the backend server as the content of that header. 6) The incorrect document was fetched for the backend because the Host header was not correct. }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 19 19:35:51 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 19 Aug 2008 19:35:51 -0000 Subject: [Varnish] #292: Connection header delete-flags can get out of sync with headers. In-Reply-To: <049.a262507c2525db1599b17f70c09f414a@projects.linpro.no> References: <049.a262507c2525db1599b17f70c09f414a@projects.linpro.no> Message-ID: <058.5e1216dc6aec2562aae4519949347426@projects.linpro.no> #292: Connection header delete-flags can get out of sync with headers. --------------------+------------------------------------------------------- Reporter: phk | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Varnish 2.0 code complete Component: build | Version: trunk Severity: major | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: Hook, line & sinker: Cood catch. Reproduced in testcase r00292 and fixed in 3110. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 22 13:21:36 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 22 Aug 2008 13:21:36 -0000 Subject: [Varnish] #293: Consider bumping the so version of misc libs Message-ID: <052.cc9994b94a5d9c977ab04c048382d3e0@projects.linpro.no> #293: Consider bumping the so version of misc libs --------------------+------------------------------------------------------- Reporter: ingvar | Owner: des Type: defect | Status: new Priority: normal | Milestone: Varnish 2.0 release Component: build | Version: trunk Severity: normal | Keywords: library so rpmbuild --------------------+------------------------------------------------------- I ran into all sorts of trouble last night when I tried to build varnish for Fedora9, and adding the test suite to the build. Finally, I found that LD_LIBRARY_PATH in the test script was ignored by rpmbuild, and since I had libvarnish-1.1.x, with matching so version, "make test" linked against libraries in /usr/lib, and varnishd in the test behaved ... very strange indeed. If varnish-2.0-presomething from svn is incompatible with eg. libvarnish.so.0 from varnish-1.1.x, the so version number of the libraries should be considered bumped. Ingvar -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 22 14:23:41 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 22 Aug 2008 14:23:41 -0000 Subject: [Varnish] #294: Missing variables Message-ID: <048.969f63a67f29a55a7ae1f06e107a7ef1@projects.linpro.no> #294: Missing variables --------------------+------------------------------------------------------- Reporter: ay | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------------------------------------------- I was hoping to do two things (from man-page) The following variables are always available: now The current time, in seconds since the epoch. The following variables are available in backend declarations: backend.host Host name or IP address of a backend. I was hoping to do two things: 1) Set ip of backend in headers remove obj.http.X-VG-Varnish-IP; set obj.http.X-VG-Varnish-IP = server.ip; remove obj.http.X-VG-Backend-IP; set obj.http.X-VG-Vackend-IP = backend.host; And in vcl_error

Error "} obj.status " " obj.response {"

  • Time: "} now {"
  • URL: "} req.request " " req.url {"
  • Client: "} client.ip {"
  • Cache: "} server.ip {"
  • Backend: " } backend.host {"
But I get Expected ';' got 'now' (program line 502), at (/etc/varnish/vg.vcl Line 168 Pos 22)
  • Time: "} now {"
  • ---------------------###-------- And Unknown variable 'backend.host' At: (/etc/varnish/vg.vcl Line 171 Pos 25)
  • Backned: "} backend.host {"
    • Changing backend.host to req.backend mentioned a few other places gives med [root at maddie ~]# varnishd -f /etc/varnish/vg.vcl String representation of 'req.backend' not implemented yet. (/etc/varnish/vg.vcl Line 171 Pos 25)
  • Backned: "} req.backend {"
    • Any chance of getting a string version of req.backend? And maybe updating the man page? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 25 08:38:43 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Aug 2008 08:38:43 -0000 Subject: [Varnish] #295: Varnishd using all available memory, even using limited malloc Message-ID: <048.ea710791e8668f55071568b187fd865f@projects.linpro.no> #295: Varnishd using all available memory, even using limited malloc --------------------+------------------------------------------------------- Reporter: ay | Owner: des Type: defect | Status: new Priority: normal | Milestone: Varnish 2.0 release Component: build | Version: trunk Severity: major | Keywords: leak memory malloc swap --------------------+------------------------------------------------------- I need some help to understand this I have a 64bit server with 32GB of RAM and 60GB SWAP And varnish is running with these parameters /usr/sbin/varnishd -a :80 -f /etc/varnish/nettby.vcl -T 127.0.0.1:82 -t 120 -u varnish -g varnish -p thread_pool_add_delay 100 -p thread_pool_timeout 600 -p client_http11 on -p lru_interval 3600 -s malloc,30G -P /var/run/varnish.pid malloc'ed 30G of memory.. So in theory I should not even need swap. But [root at sol ~]# free -m total used free shared buffers cached Mem: 32242 31735 507 0 0 92 -/+ buffers/cache: 31642 600 Swap: 59871 51322 8549 The machine is using 51GB of swap and is swapping in pages frequently [root at sol ~]# vmstat 1 procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu------ r b swpd free buff cache si so bi bo in cs us sy id wa st 0 0 52549748 446992 780 96284 29 11 48 157 1 1 4 2 92 1 0 0 0 52549708 530360 780 96348 280 0 280 0 9654 6935 4 8 87 1 0 0 0 52549708 528160 780 96420 0 0 0 0 6785 7560 2 2 96 0 0 0 0 52549664 526668 780 96316 316 0 316 0 6570 7350 2 2 95 1 0 0 0 52549648 524932 780 96396 104 0 104 0 6300 7456 2 1 96 0 0 0 0 52549644 523372 780 96400 28 0 28 0 6013 7099 2 2 96 0 0 0 0 52549640 521884 788 96424 28 0 28 28 5649 7343 2 2 96 0 0 [root at sol ~]# varnishstat -1 client_conn 2089633996 362.23 Client connections accepted client_req 8345199749 1446.62 Client requests received cache_hit 8289156139 1436.90 Cache hits cache_hitpass 1610 0.00 Cache hits for pass cache_miss 53623537 9.30 Cache misses backend_conn 53621117 9.30 Backend connections success backend_fail 4031 0.00 Backend connections failures backend_reuse 0 0.00 Backend connections reuses backend_recycle 0 0.00 Backend connections recycles backend_unused 0 0.00 Backend connections unused n_srcaddr 7689 . N struct srcaddr n_srcaddr_act 4164 . N active struct srcaddr n_sess_mem 59601 . N struct sess_mem n_sess 64719 . N struct sess n_object 2025596 . N struct object n_objecthead 2025576 . N struct objecthead n_smf 0 . N struct smf n_smf_frag 0 . N small free smf n_smf_large 0 . N large free smf n_vbe_conn 106 . N struct vbe_conn n_bereq 96 . N struct bereq n_wrk 78 . N worker threads n_wrk_create 15968 0.00 N worker threads created n_wrk_failed 0 0.00 N worker threads not created n_wrk_max 191919689 33.27 N worker threads limited n_wrk_queue 0 0.00 N queued work requests n_wrk_overflow 210128619 36.43 N overflowed work requests n_wrk_drop 31202342 5.41 N dropped work requests n_backend 1 . N backends n_expired 31600718 . N expired objects n_lru_nuked 20008124 . N LRU nuked objects n_lru_saved 0 . N LRU saved objects n_lru_moved 779599235 . N LRU moved objects n_deathrow 0 . N objects on deathrow losthdr 196 0.00 HTTP header overflows n_objsendfile 0 0.00 Objects sent with sendfile n_objwrite 6674989721 1157.09 Objects sent with write n_objoverflow 0 0.00 Objects overflowing workspace s_sess 2073648637 359.46 Total Sessions s_req 8345234372 1446.62 Total Requests s_pipe 0 0.00 Total pipe s_pass 0 0.00 Total pass s_fetch 53620083 9.29 Total fetch s_hdrbytes 2924438007698 506943.34 Total header bytes s_bodybytes 13839780950697 2399088.22 Total body bytes sess_closed 54123498 9.38 Session Closed sess_pipeline 0 0.00 Session Pipeline sess_readahead 42322579 7.34 Session Read Ahead sess_herd 8270331676 1433.64 Session herd shm_records 347828089203 60295.05 SHM records shm_writes 14631506809 2536.33 SHM writes shm_flushes 908314 0.16 SHM flushes due to overflow shm_cont 14245861 2.47 SHM MTX contention sm_nreq 0 0.00 allocator requests sm_nobj 0 . outstanding allocations sm_balloc 0 . bytes allocated sm_bfree 0 . bytes free sma_nreq 127269201 22.06 SMA allocator requests sma_nobj 4019319 . SMA outstanding allocations sma_nbytes 32212251961 . SMA outstanding bytes sma_balloc 891934739829 . SMA bytes allocated sma_bfree 859722487868 . SMA bytes free backend_req 53621117 9.30 Backend requests made -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 25 09:00:40 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Aug 2008 09:00:40 -0000 Subject: [Varnish] #296: Tuning keep-alive Message-ID: <048.4ee71176e67a3e1c5f8f1eabe50f450c@projects.linpro.no> #296: Tuning keep-alive -------------------------+-------------------------------------------------- Reporter: ay | Owner: phk Type: enhancement | Status: new Priority: normal | Milestone: After 2.0 Component: varnishd | Version: trunk Severity: normal | Keywords: -------------------------+-------------------------------------------------- Our main problem with varnish is that when some backend or even a remote server is very slow, keepalive towards the clients are queueing up thousands of request just idling, waiting for some other object to be finished. Setting down keep-alive might help in this situation. When varnish ends up in a thread-pile, even removing the original cause does not seem to fix the problem. But restarting it works. Resetting all connections. So if varnish could detect that it's starting to have a problem. Reseting keep-alive would be a pretty good way of getting out of a tight spot.... So, my feature request is acctually two things 1) Ajustable keep-alive (what is the default) 2) A way to reset keep-alive session without restarting varnish. Browses handles that nicly. If varnish could do it itself it would be even cooler. -- Audun -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 25 11:04:51 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Aug 2008 11:04:51 -0000 Subject: [Varnish] #297: make check fails on test a00007, fedora9, i386 Message-ID: <052.1ca0026f49d62620dd6e25abccf80a62@projects.linpro.no> #297: make check fails on test a00007, fedora9, i386 --------------------+------------------------------------------------------- Reporter: ingvar | Owner: des Type: defect | Status: new Priority: normal | Milestone: Varnish 2.0 release Component: build | Version: trunk Severity: normal | Keywords: a00007 --------------------+------------------------------------------------------- As requested from phk: There is a race condition somewhere in varhishtest that makes a00007, and from time to time, also a00006, fail in rpmbuild on fedora9/i386. Here are the last lines of output from varnishtest -v. btw, on Fedora9 (i386/Linux-2.6.25), error 107 is {{{ #define ENOTCONN 107 /* Transport endpoint is not connected */ }}} Ingvar {{{ #### s1 txresp| 987654321\n #### s1 txresp| \r\n #### c1 rxhdr| \r\n #### c1 rxhdr| HTTP/1.1 200 Ok\r\n #### c1 rxhdr| Content-Length: 10\r\n #### c1 rxhdr| \r\n #### c1 http[ 0] | HTTP/1.1 #### c1 http[ 1] | 200 #### c1 http[ 2] | Ok #### c1 http[ 3] | Content-Length: 10 #### c1 body| 987654321\n ### c1 Closing fd 5 ## c1 Ending ## s1 Waiting for server ### s1 shutting fd 4 Assert error in server_thread(), vtc_server.c line 100: Condition((shutdown(fd, SHUT_WR)) == 0) not true. errno = 107 (Transport endpoint is not connected) /bin/sh: line 4: 1282 Aborted (SIGABRT) ./varnishtest -v ${dir}$tst FAIL: ./tests/a00007.vtc }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 25 11:23:33 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Aug 2008 11:23:33 -0000 Subject: [Varnish] #298: Generated example default.vcl lacks quotation marks Message-ID: <052.d5c8760027ad368f13440b56886d4033@projects.linpro.no> #298: Generated example default.vcl lacks quotation marks --------------------+------------------------------------------------------- Reporter: ingvar | Owner: des Type: defect | Status: new Priority: normal | Milestone: Varnish 2.0 release Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------------------------------------------- The generated example default.vcl lacks the needed quotation marks around the host and port defenitions. {{{ varnish-cache$ make >/dev/null; head -10 etc/default.vcl | tail -4 #backend default { #.host = 127.0.0.1; #.port = 8080; #} }}} The following simple patch may possibly fix this. {{{ varnish-cache/etc$ svn diff Index: Makefile.am =================================================================== --- Makefile.am (revisjon 3120) +++ Makefile.am (arbeidskopi) @@ -12,8 +12,8 @@ server.\n\ \n\ backend default {\n\ - .host = "127.0.0.1";\n\ - .port = "8080";\n\ + .host = \"127.0.0.1\";\n\ + .port = \"8080\";\n\ }\n\ \n\ Below is a commented-out copy of the default VCL logic. If you\n\ }}} Ingvar -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 25 11:59:56 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Aug 2008 11:59:56 -0000 Subject: [Varnish] #297: make check fails on test a00007, fedora9, i386 In-Reply-To: <052.1ca0026f49d62620dd6e25abccf80a62@projects.linpro.no> References: <052.1ca0026f49d62620dd6e25abccf80a62@projects.linpro.no> Message-ID: <061.0b5ff99900055fe6f2f40836d0a8afc8@projects.linpro.no> #297: make check fails on test a00007, fedora9, i386 --------------------+------------------------------------------------------- Reporter: ingvar | Owner: des Type: defect | Status: new Priority: normal | Milestone: Varnish 2.0 release Component: build | Version: trunk Severity: normal | Resolution: Keywords: a00007 | --------------------+------------------------------------------------------- Comment (by ingvar): Complete varnishtest -v output: http://init.linpro.no/ingvar/varnish/a00006.fail http://init.linpro.no/ingvar/varnish/a00007.fail Ingvar -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 25 13:59:43 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Aug 2008 13:59:43 -0000 Subject: [Varnish] #299: "Via: 1.1 varnish" header/cookie in trunk Message-ID: <054.8a440b51f224d7e4dec4b5a42132c820@projects.linpro.no> #299: "Via: 1.1 varnish" header/cookie in trunk ----------------------+----------------------------------------------------- Reporter: The_ZoRo | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------------------------------- Shouldn't it be "Via 2.0 Varnish"/"trunk $SVN-rev" or something else? Or at least be configurable: 1) Allow it to be sent and/or 2) Edit what is sent to the clients /Mads -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 25 14:04:04 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Aug 2008 14:04:04 -0000 Subject: [Varnish] #299: "Via: 1.1 varnish" header/cookie in trunk In-Reply-To: <054.8a440b51f224d7e4dec4b5a42132c820@projects.linpro.no> References: <054.8a440b51f224d7e4dec4b5a42132c820@projects.linpro.no> Message-ID: <063.b463e4811c00c2fa5169516a0c0d68b5@projects.linpro.no> #299: "Via: 1.1 varnish" header/cookie in trunk ----------------------+----------------------------------------------------- Reporter: The_ZoRo | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: wontfix Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => wontfix Comment: No, the Via: header is described in 14.45 of RFC2616 as and the number is the HTTP protocol version seen, not the software version running. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Aug 25 14:06:11 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Aug 2008 14:06:11 -0000 Subject: [Varnish] #296: Tuning keep-alive In-Reply-To: <048.4ee71176e67a3e1c5f8f1eabe50f450c@projects.linpro.no> References: <048.4ee71176e67a3e1c5f8f1eabe50f450c@projects.linpro.no> Message-ID: <057.779d66a970634baeabaa8877c4aad0c0@projects.linpro.no> #296: Tuning keep-alive -------------------------+-------------------------------------------------- Reporter: ay | Owner: phk Type: enhancement | Status: closed Priority: normal | Milestone: After 2.0 Component: varnishd | Version: trunk Severity: normal | Resolution: worksforme Keywords: | -------------------------+-------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => worksforme Comment: The client side keepalive is controlled with the "session_timeout" parameter. The default value is 5 seconds, lowering it too far will cause increased work in connection establishment from clients. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 26 07:51:34 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 26 Aug 2008 07:51:34 -0000 Subject: [Varnish] #297: make check fails on test a00007, fedora9, i386 In-Reply-To: <052.1ca0026f49d62620dd6e25abccf80a62@projects.linpro.no> References: <052.1ca0026f49d62620dd6e25abccf80a62@projects.linpro.no> Message-ID: <061.3c77e3fc87ff2c59dc71691855b7a0ef@projects.linpro.no> #297: make check fails on test a00007, fedora9, i386 --------------------+------------------------------------------------------- Reporter: ingvar | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Varnish 2.0 release Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: a00007 | --------------------+------------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: fixed in r3127 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 26 07:53:50 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 26 Aug 2008 07:53:50 -0000 Subject: [Varnish] #289: VCL insert bug in trunk In-Reply-To: <048.0e137abc9e4b9b2b5584d366925ad7f4@projects.linpro.no> References: <048.0e137abc9e4b9b2b5584d366925ad7f4@projects.linpro.no> Message-ID: <057.e27b448dd2025efe1c955275835f9898@projects.linpro.no> #289: VCL insert bug in trunk ----------------------+----------------------------------------------------- Reporter: ay | 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 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 26 08:06:40 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 26 Aug 2008 08:06:40 -0000 Subject: [Varnish] #298: Generated example default.vcl lacks quotation marks In-Reply-To: <052.d5c8760027ad368f13440b56886d4033@projects.linpro.no> References: <052.d5c8760027ad368f13440b56886d4033@projects.linpro.no> Message-ID: <061.e11f620fc3a598e3dd3b58bc68e242ce@projects.linpro.no> #298: Generated example default.vcl lacks quotation marks --------------------+------------------------------------------------------- Reporter: ingvar | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Varnish 2.0 release Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: committed. thanks. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 26 15:03:41 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 26 Aug 2008 15:03:41 -0000 Subject: [Varnish] #300: Varnish dropping POST transactions Message-ID: <052.fe0cc5c6713f96ca021ec1b96e05d9b9@projects.linpro.no> #300: Varnish dropping POST transactions ----------------------+----------------------------------------------------- Reporter: edlott | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.1.2 Severity: major | Keywords: ----------------------+----------------------------------------------------- I built from source using the 1.1.2 branch. When I ran a 600-simultaneous user stress test from an automated script I noticed the following: * The apache logs reported 63586 POST instead of 63600 POST (14 less than expected). * Varnish's NCSA-style log reported 26 of these POST with invalid Code and Size entries. The NCSA-style log was configured so that it wouldn't report any of them (in fact, it didn't report the vast majority of post that I saw in the apache logs). The command-line options I used to start the ncsa-log daemon were "-a -c -w -D -P " I believe the following VCL snippet from my config file handles POST: if (req.request != "GET" && re1.request != "HEAD") { pipe; } All of this makes me think something isn't quite right with the "pipe" functionality under high loads. I noticed that the 1.1.2 branch hasn't been updated recently, so I'm assuming you abandoned it. Perhaps these bugs have been fixed for trunk. If trunk is the 'best-working' collection of source, are there particular revisions of trunk that are 'approved' (i.e. have any of your users put togeter a 'stability' report on their trunk builds so I can guess on a build that's most likely to work in a production setting). -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 26 15:24:53 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 26 Aug 2008 15:24:53 -0000 Subject: [Varnish] #300: Varnish dropping POST transactions In-Reply-To: <052.fe0cc5c6713f96ca021ec1b96e05d9b9@projects.linpro.no> References: <052.fe0cc5c6713f96ca021ec1b96e05d9b9@projects.linpro.no> Message-ID: <061.11095163a87a51d701e97eaa0875478c@projects.linpro.no> #300: Varnish dropping POST transactions ----------------------+----------------------------------------------------- Reporter: edlott | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 1.1.2 Severity: major | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: 1.1.x does not handle POST apart from moving bytes forth and back, hoping for the best. -trunk is a few hours from being "code complete" for 2.0 and has so many bugs fixed since 1.1.x that I have no way to count it. Give -trunk a spin. (And congratulations on opening our ticket #300 :-) phk -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Aug 26 23:25:34 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 26 Aug 2008 23:25:34 -0000 Subject: [Varnish] #301: varnish 1.1.2 freebsd 6.2 out of the box dies on startup - vca_kqueue_init() pthread_create cannot allocate memory Message-ID: <064.757adea44b80f4aa33e09a2eefe45cbd@projects.linpro.no> #301: varnish 1.1.2 freebsd 6.2 out of the box dies on startup - vca_kqueue_init() pthread_create cannot allocate memory --------------------------------+------------------------------------------- Reporter: GregoryOfManhattan | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------------------+------------------------------------------- clean build from current ports, out of the box commands show it just dies. {{{ /usr/local/sbin/varnishd -F -a :6081 -T localhost:6082 -f/usr/local/etc/varnish/default.vcl -sfile,/tmp Info: (-sfile) default to 80% size NB: Limiting size to 2GB on 32 bit architecture to prevent running out of address space. Specifiy explicit size to override. file /tmp/varnish.Mf2Ov4 (unlinked) size 2147467264 bytes (131071 fs- blocks, 524284 pages) Using old SHMFILE socket(): Protocol not supported rolling(1)... rolling(2)... start child pid 90498 Pushing vcls failed: CLI communication error Child said (1, 90498): <> unlink ./bin.AMGTyDi2 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Aug 27 16:57:44 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 27 Aug 2008 16:57:44 -0000 Subject: [Varnish] #301: varnish 1.1.2 freebsd 6.2 out of the box dies on startup - vca_kqueue_init() pthread_create cannot allocate memory In-Reply-To: <064.757adea44b80f4aa33e09a2eefe45cbd@projects.linpro.no> References: <064.757adea44b80f4aa33e09a2eefe45cbd@projects.linpro.no> Message-ID: <073.cb029abe33b2ad42afd83903b8e66357@projects.linpro.no> #301: varnish 1.1.2 freebsd 6.2 out of the box dies on startup - vca_kqueue_init() pthread_create cannot allocate memory --------------------------------+------------------------------------------- Reporter: GregoryOfManhattan | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------------------+------------------------------------------- Comment (by GregoryOfManhattan): please close this ticket. as i now see my /tmp partition is too small for the initial 2GB allocation for the default. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 28 07:50:21 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 28 Aug 2008 07:50:21 -0000 Subject: [Varnish] #302: Varnishstat: % of caching: Bytes actually sent VS bytes sent with no cache Message-ID: <054.e44e7565fe29a1bc40a93668492c2413@projects.linpro.no> #302: Varnishstat: % of caching: Bytes actually sent VS bytes sent with no cache -------------------------+-------------------------------------------------- Reporter: The_ZoRo | Owner: phk Type: enhancement | Status: new Priority: low | Milestone: After 2.0 Component: varnishstat | Version: Severity: normal | Keywords: -------------------------+-------------------------------------------------- Make varnishsstat able to show just how much traffic the backend does not have to serve. I'm tinking of something like this: Hitrate ratio: 10 100 xxx[[BR]] Hitrate avg: 0.TU 0.VW 0.YZ[[BR]] Bytes saved: x mb x mb x mb In short: number of bytes served from cache without hitting the backend -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 28 09:04:44 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 28 Aug 2008 09:04:44 -0000 Subject: [Varnish] #303: Description length in 2. column in varnishtop is too short Message-ID: <054.1517f0c50d06e68d29d27aaef67b8dae@projects.linpro.no> #303: Description length in 2. column in varnishtop is too short ------------------------+--------------------------------------------------- Reporter: The_ZoRo | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishtop | Version: trunk Severity: normal | Keywords: ------------------------+--------------------------------------------------- xx VCL_retur deliver xx RxProtoco HTTP/1.1 xx TxProtoco HTTP/1.1 xx VCL_retur lookup xx VCL_retur hash The 2. column should be longer to show what actions Varnish does, one or two characters would be enough I think. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Aug 28 09:57:27 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 28 Aug 2008 09:57:27 -0000 Subject: [Varnish] #301: varnish 1.1.2 freebsd 6.2 out of the box dies on startup - vca_kqueue_init() pthread_create cannot allocate memory In-Reply-To: <064.757adea44b80f4aa33e09a2eefe45cbd@projects.linpro.no> References: <064.757adea44b80f4aa33e09a2eefe45cbd@projects.linpro.no> Message-ID: <073.0df5f20b33482fa963f2902c17ac45af@projects.linpro.no> #301: varnish 1.1.2 freebsd 6.2 out of the box dies on startup - vca_kqueue_init() pthread_create cannot allocate memory --------------------------------+------------------------------------------- Reporter: GregoryOfManhattan | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: invalid Keywords: | --------------------------------+------------------------------------------- Changes (by tfheen): * status: new => closed * resolution: => invalid * component: build => varnishd Comment: Closing as invalid per submitters request. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Aug 29 09:38:03 2008 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 29 Aug 2008 09:38:03 -0000 Subject: [Varnish] #293: Consider bumping the so version of misc libs In-Reply-To: <052.cc9994b94a5d9c977ab04c048382d3e0@projects.linpro.no> References: <052.cc9994b94a5d9c977ab04c048382d3e0@projects.linpro.no> Message-ID: <061.c59c12d0789566e0f50d6f2c8e6d6016@projects.linpro.no> #293: Consider bumping the so version of misc libs ---------------------------------+------------------------------------------ Reporter: ingvar | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Varnish 2.0 release Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: library so rpmbuild | ---------------------------------+------------------------------------------ Changes (by tfheen): * status: new => closed * resolution: => fixed Comment: Fixed in revision 3140. -- Ticket URL: Varnish The Varnish HTTP Accelerator