From varnish-bugs at projects.linpro.no Mon Mar 2 08:40:58 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Mar 2009 08:40:58 -0000 Subject: [Varnish] #459: Varnish crashes with assert error in hsh_rush(), cache_hash.c line 403 Message-ID: <052.8cd544c938e7d765661cbdf58ee87f9a@projects.linpro.no> #459: Varnish crashes with assert error in hsh_rush(), cache_hash.c line 403 ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: critical | Keywords: ----------------------+----------------------------------------------------- I am running Varnish trunk/3802 in FreeBSD/amd64 7.0-RELEASE, with a large dataset (upto 5 million objects). I use these parameters: -p diag_bitmap=0x8000 -p obj_workspace=2048 -p lru_interval=3600 -h critbit -p ping_interval=0 -p cli_timeout=30 -p auto_restart=off -p thread_pools=4 -p thread_pool_max=4000 -p session_linger=40 -p listen_depth=4096 -p srcaddr_hash=20480 -p default_ttl=604800 -T localhost:8080 -f /usr/local/etc/varnish.vcl $varnishd_files -P /var/run/varnishd.pid I got this crash: {{{ Child (62255) Panic message: Assert error in hsh_rush(), cache_hash.c line 403: Condition((sp)->magic == 0x2c2f9c5a) not true. thread = (cache- worker)sp = 0x808d01008 { fd = 492, id = 492, xid = 1120424694, client = 193.217.162.198:8202, step = STP_DELIVER, handling = deliver, ws = 0x808d01078 { id = "sess", {s,f,r,e} = {0x808d01808,,+1024,0x0,+16384}, }, worker = 0x7fffd78bda60 { }, vcl = { srcname = { "input", "Default", }, }, }, Child cleanup complete }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 2 09:51:45 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Mar 2009 09:51:45 -0000 Subject: [Varnish] #458: b17 and c22 tests fail: SEGV on Solaris if VRT_error called with reason==NULL In-Reply-To: <051.3991c000d3d368d8291f8a4b03cf43ab@projects.linpro.no> References: <051.3991c000d3d368d8291f8a4b03cf43ab@projects.linpro.no> Message-ID: <060.ec9cad904b2934108ee4c561e96287f8@projects.linpro.no> #458: b17 and c22 tests fail: SEGV on Solaris if VRT_error called with reason==NULL ----------------------+----------------------------------------------------- Reporter: slink | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by tfheen): Fixed in r3847. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 2 09:55:26 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Mar 2009 09:55:26 -0000 Subject: [Varnish] #458: b17 and c22 tests fail: SEGV on Solaris if VRT_error called with reason==NULL In-Reply-To: <051.3991c000d3d368d8291f8a4b03cf43ab@projects.linpro.no> References: <051.3991c000d3d368d8291f8a4b03cf43ab@projects.linpro.no> Message-ID: <060.52b674221b77aa998de5a3c4efd77427@projects.linpro.no> #458: b17 and c22 tests fail: SEGV on Solaris if VRT_error called with reason==NULL ----------------------+----------------------------------------------------- Reporter: slink | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by tfheen): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 2 09:59:01 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Mar 2009 09:59:01 -0000 Subject: [Varnish] #439: adding several cookie will remove redirection In-Reply-To: <056.a60faa3b741776d321e3406485e54948@projects.linpro.no> References: <056.a60faa3b741776d321e3406485e54948@projects.linpro.no> Message-ID: <065.da3a01dea5e96b11896d2d6fb70f3710@projects.linpro.no> #439: adding several cookie will remove redirection ------------------------+--------------------------------------------------- Reporter: scouzinier | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ------------------------+--------------------------------------------------- Changes (by phk): * owner: => phk * component: build => varnishd Old description: > header Location is remove by varnish if we use several time Set-Cookie. > > this header will should redirect the user. > It's work without varnish, not with varnish. > HTTP/1.1 302 Found > Date: Mon, 09 Feb 2009 10:52:43 GMT > Server: Apache > Set-Cookie: SiteNameClient=qmdjrt7t1gp79elac25vhf8bg5; path=/; > domain=.toto.fr > Expires: Mon, 26 Jul 1997 05:00:00 GMT > Cache-Control: no-cache, must-revalidate > Pragma: no-cache > Last-Modified: Mon, 09 Feb 2009 10:52:43 GMT > X-Powered-By: eZ Publish > Served-by: org-www.toto.fr > Content-language: fr-FR > Set-Cookie: user_logged=non; path=/; domain=.toto.fr > Set-Cookie: session_user_logged=non; path=/; domain=.toto.fr > Set-Cookie: user_info=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; > path=/; domain=.toto.fr > Set-Cookie: EZ_TICKET=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; > path=/; domain=.toto.fr:80 > Set-Cookie: cine1=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; > domain=.toto.fr > Set-Cookie: id1=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; > domain=.toto.fr > Set-Cookie: cine2=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; > domain=.toto.fr > Set-Cookie: id2=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; > domain=.toto.fr > Set-Cookie: cine3=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; > domain=.toto.fr > Set-Cookie: id3=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; > domain=.toto.fr > Set-Cookie: cine4=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; > domain=.toto.fr > Set-Cookie: id4=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; > domain=.toto.fr > Set-Cookie: user_logged=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; > path=/; domain=.toto.fr > Set-Cookie: username=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; > path=/; domain=.toto.fr > Set-Cookie: clubtoto_grade=deleted; expires=Sun, 10-Feb-2008 10:52:42 > GMT; path=/; domain=.toto.fr > Set-Cookie: clubtoto_action=deleted; expires=Sun, 10-Feb-2008 10:52:42 > GMT; path=/; domain=.toto.fr > Set-Cookie: clubtoto_points=deleted; expires=Sun, 10-Feb-2008 10:52:42 > GMT; path=/; domain=.toto.fr > Set-Cookie: clubtoto_grade_id=deleted; expires=Sun, 10-Feb-2008 10:52:42 > GMT; path=/; domain=.toto.fr > Set-Cookie: avatar_toto=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; > path=/; domain=.toto.fr:80 > Set-Cookie: toto_fileavatar=deleted; expires=Sun, 10-Feb-2008 10:52:42 > GMT; path=/; domain=.toto.fr:80 > Location: http://org-www.toto.fr > Content-Length: 200 > Connection: close > Content-Type: text/html; charset=utf-8 > > Sample page: > header("HTTP/1.x 302 Found"); > header("Server: Apache"); > header("Last-Modified: Mon, 09 Feb 2009 08:53:13 GMT"); > header("X-Powered-By: eZ Publish"); > header("Served-by: org-www.toto.fr"); > header("Content-Language: fr-FR"); > > header("Expires: Mon, 26 Jul 1997 05:00:00 GMT"); > header("Cache-Control: no-cache, must-revalidate"); > header("Pragma: no-cache"); > header("Date: Mon, 09 Feb 2009 08:53:13 GMT"); > > for($i=0;$i<=18;$i++) > setcookie("a$i","a$i", time()+3600,"/",".toto.fr"); > > header("Location: http://org-www.toto.fr/"); > > ?> > > When max value for $i is 17, the page will work with varnish > When max value for $i is 18, the page won't work with varnish New description: header Location is remove by varnish if we use several time Set-Cookie. this header will should redirect the user. It's work without varnish, not with varnish. {{{ HTTP/1.1 302 Found Date: Mon, 09 Feb 2009 10:52:43 GMT Server: Apache Set-Cookie: SiteNameClient=qmdjrt7t1gp79elac25vhf8bg5; path=/; domain=.toto.fr Expires: Mon, 26 Jul 1997 05:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Last-Modified: Mon, 09 Feb 2009 10:52:43 GMT X-Powered-By: eZ Publish Served-by: org-www.toto.fr Content-language: fr-FR Set-Cookie: user_logged=non; path=/; domain=.toto.fr Set-Cookie: session_user_logged=non; path=/; domain=.toto.fr Set-Cookie: user_info=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr Set-Cookie: EZ_TICKET=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr:80 Set-Cookie: cine1=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr Set-Cookie: id1=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr Set-Cookie: cine2=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr Set-Cookie: id2=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr Set-Cookie: cine3=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr Set-Cookie: id3=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr Set-Cookie: cine4=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr Set-Cookie: id4=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr Set-Cookie: user_logged=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr Set-Cookie: username=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr Set-Cookie: clubtoto_grade=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr Set-Cookie: clubtoto_action=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr Set-Cookie: clubtoto_points=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr Set-Cookie: clubtoto_grade_id=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr Set-Cookie: avatar_toto=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr:80 Set-Cookie: toto_fileavatar=deleted; expires=Sun, 10-Feb-2008 10:52:42 GMT; path=/; domain=.toto.fr:80 Location: http://org-www.toto.fr Content-Length: 200 Connection: close Content-Type: text/html; charset=utf-8 }}} Sample page: {{{ }}} When max value for $i is 17, the page will work with varnish When max value for $i is 18, the page won't work with varnish -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 2 10:02:46 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Mar 2009 10:02:46 -0000 Subject: [Varnish] #439: adding several cookie will remove redirection In-Reply-To: <056.a60faa3b741776d321e3406485e54948@projects.linpro.no> References: <056.a60faa3b741776d321e3406485e54948@projects.linpro.no> Message-ID: <065.28ac800d8b028de9423358b5813058a5@projects.linpro.no> #439: adding several cookie will remove redirection ------------------------+--------------------------------------------------- Reporter: scouzinier | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: duplicate Keywords: | ------------------------+--------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => duplicate Comment: This is an indication of the problem #455 is trying to solve, closing this, follow action on #455. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 2 10:09:33 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Mar 2009 10:09:33 -0000 Subject: [Varnish] #459: Varnish crashes with assert error in hsh_rush(), cache_hash.c line 403 In-Reply-To: <052.8cd544c938e7d765661cbdf58ee87f9a@projects.linpro.no> References: <052.8cd544c938e7d765661cbdf58ee87f9a@projects.linpro.no> Message-ID: <061.a94dc13c9994bb11dc5f26f66e1e3675@projects.linpro.no> #459: Varnish crashes with assert error in hsh_rush(), cache_hash.c line 403 ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: critical | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by phk): See also #414, could be same. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 2 10:17:14 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Mar 2009 10:17:14 -0000 Subject: [Varnish] #453: Assert error in WS_Release(), cache_ws.c line 170 In-Reply-To: <049.082c25eebb1351993cafbd750e5b4d24@projects.linpro.no> References: <049.082c25eebb1351993cafbd750e5b4d24@projects.linpro.no> Message-ID: <058.5e1eb36d6e0107e6ab5d1cb185046fa0@projects.linpro.no> #453: Assert error in WS_Release(), cache_ws.c line 170 --------------------+------------------------------------------------------- Reporter: sky | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+------------------------------------------------------- Old description: > {{{ > Child (6824) Panic message: Assert error in WS_Release(), cache_ws.c line > 170: Condition(bytes <= ws->e - ws->f) not true. errno = 107 > (Transport endpoint is not connected) thread = (cache-worker)sp = > 0x7faedda86008 { fd = 379, id = 379, xid = 433628655, client = > 83.223.112.138:17948, step = STP_FETCH, handling = error, err_code > = 200, err_reason = (null), ws = 0x7faedda86078 { id = "sess", > {s,f,r,e} = {0x7faedda86808,,+3180,(nil),+131072}, }, worker = > 0x7fb5385fcc00 { }, vcl = { srcname = { "input", > "Default", }, }, obj = 0x7fc6ace39000 { refcnt = 1, xid = > 433628655, ws = 0x7fc6ace39028 { id = "obj", {s,f,r,e} = > {0x7fc6ace39358,,+3211,+3240,+3240}, }, http = { ws = > 0x7fc6ace39028 { id = "obj", {s,f,r,e} = > {0x7fc6ace39358,,+3211,+3240,+3240}, }, hd = { > "Server: Apache", "Content-language: en", "X-Article-Id: > 0", > > }}} > > Segfault after roughly 24 hours of running. New description: {{{ Child (6824) Panic message: Assert error in WS_Release(), cache_ws.c line 170: Condition(bytes <= ws->e - ws->f) not true. errno = 107 (Transport endpoint is not connected) thread = (cache-worker) sp = 0x7faedda86008 { fd = 379, id = 379, xid = 433628655, client = 83.223.112.138:17948, step = STP_FETCH, handling = error, err_code = 200, err_reason = (null), ws = 0x7faedda86078 { id = "sess", {s,f,r,e} = {0x7faedda86808,,+3180,(nil),+131072}, }, worker = 0x7fb5385fcc00 { }, vcl = { srcname = { "input", "Default", }, }, obj = 0x7fc6ace39000 { refcnt = 1, xid = 433628655, ws = 0x7fc6ace39028 { id = "obj", {s,f,r,e} = {0x7fc6ace39358,,+3211,+3240,+3240}, }, http = { ws = 0x7fc6ace39028 { id = "obj", {s,f,r,e} = {0x7fc6ace39358,,+3211,+3240,+3240}, }, hd = { "Server: Apache", "Content-language: en", "X-Article-Id: 0", }}} Segfault after roughly 24 hours of running. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 2 10:24:00 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Mar 2009 10:24:00 -0000 Subject: [Varnish] #450: Varnish 2.0.3 compile using SunStudio 12 (w/ latest patches applied) In-Reply-To: <054.815087577ad79d2c94b8baad670dad3e@projects.linpro.no> References: <054.815087577ad79d2c94b8baad670dad3e@projects.linpro.no> Message-ID: <063.dcdf25b7ac51dc0bb6ecaad86152030b@projects.linpro.no> #450: Varnish 2.0.3 compile using SunStudio 12 (w/ latest patches applied) -------------------------------+-------------------------------------------- Reporter: whocares | Owner: Type: defect | Status: closed Priority: low | Milestone: Component: build | Version: 2.0 Severity: normal | Resolution: fixed Keywords: SunStudio Solaris | -------------------------------+-------------------------------------------- Changes (by tfheen): * status: new => closed * resolution: => fixed Comment: Fixed in r3827. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 2 11:48:13 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Mar 2009 11:48:13 -0000 Subject: [Varnish] #460: error in documentation on rewrite of url's Message-ID: <056.7a8afab1cec21f5a2e76021a43d8b673@projects.linpro.no> #460: error in documentation on rewrite of url's ---------------------------------+------------------------------------------ Reporter: rejozenger | Type: documentation Status: new | Priority: low Milestone: Varnish 2.1 release | Component: documentation Version: trunk | Severity: trivial Keywords: documentation error | ---------------------------------+------------------------------------------ At [wiki:RedirectsAndRewrites] an example is given with two "set" statements. The variables in these two statements are invalid and should be respectively req.http.host (instead of req.host) and req.http.url (instead of req.url). Allthough I am logged in, I seem not to have enough credentials to update the documentation. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 2 11:55:36 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Mar 2009 11:55:36 -0000 Subject: [Varnish] #457: Doesn't work when cil_banner is on In-Reply-To: <052.8068a3839384c29f74be95e5c18c1882@projects.linpro.no> References: <052.8068a3839384c29f74be95e5c18c1882@projects.linpro.no> Message-ID: <061.e1ba9662b202c9ee03b876274e784722@projects.linpro.no> #457: Doesn't work when cil_banner is on ------------------------+--------------------------------------------------- Reporter: petter | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: varnishadm | Version: trunk Severity: normal | Resolution: fixed Keywords: | ------------------------+--------------------------------------------------- Changes (by tfheen): * status: new => closed * resolution: => fixed Comment: Fixed in r3850. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 2 11:59:40 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Mar 2009 11:59:40 -0000 Subject: [Varnish] #460: error in documentation on rewrite of url's In-Reply-To: <056.7a8afab1cec21f5a2e76021a43d8b673@projects.linpro.no> References: <056.7a8afab1cec21f5a2e76021a43d8b673@projects.linpro.no> Message-ID: <065.0bf7c71742cdec6dfa1e1ed6659f2e7c@projects.linpro.no> #460: error in documentation on rewrite of url's ---------------------------------+------------------------------------------ Reporter: rejozenger | Owner: Type: documentation | Status: closed Priority: low | Milestone: Varnish 2.1 release Component: documentation | Version: trunk Severity: trivial | Resolution: fixed Keywords: documentation error | ---------------------------------+------------------------------------------ Changes (by kristian): * status: new => closed * resolution: => fixed Comment: Fixed. While req.url is valid, but req.host is not. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 2 12:02:37 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Mar 2009 12:02:37 -0000 Subject: [Varnish] #451: No X-Forwaded-For on piped requests In-Reply-To: <050.462f53ad036d807bb4c71ce294a1ab4f@projects.linpro.no> References: <050.462f53ad036d807bb4c71ce294a1ab4f@projects.linpro.no> Message-ID: <059.82f2d7137a029f86000ae0c74707ce00@projects.linpro.no> #451: No X-Forwaded-For on piped requests --------------------+------------------------------------------------------- Reporter: joel | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by tfheen): * status: new => closed * resolution: => fixed Comment: Documented that X-F-F is not set on subsequent requests and that you might want to use set req.http.connection = "close" in the default.vcl. (All in r3852) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 2 14:20:57 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Mar 2009 14:20:57 -0000 Subject: [Varnish] #461: Varnish crashes with assert error in HSH_Lookup(), cache_hash.c line 312 Message-ID: <052.8746dd7cb31c0c6d4eedaf97338a84be@projects.linpro.no> #461: Varnish crashes with assert error in HSH_Lookup(), cache_hash.c line 312 ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: critical | Keywords: ----------------------+----------------------------------------------------- I am running Varnish trunk/3846 in FreeBSD/amd64 7.1-RELEASE, with a large dataset (upto 5 million objects). I use these parameters: -p diag_bitmap=0x8000 -p obj_workspace=2048 -p lru_interval=3600 -h critbit -p ping_interval=0 -p cli_timeout=30 -p auto_restart=off -p thread_pools=4 -p thread_pool_max=4000 -p session_linger=40 -p listen_depth=4096 -p srcaddr_hash=20480 -p default_ttl=604800 -T localhost:8080 -f /usr/local/etc/varnish.vcl $varnishd_files -P /var/run/varnishd.pid I got this crash: {{ Child (22139) Panic message: Assert error in HSH_Lookup(), cache_hash.c line 312: Condition(oh->refcnt > 1) not true. thread = (cache-worker)sp = 0x807e89008 { fd = 646, id = 646, xid = 439499437, client = 138.62.101.134:11474, step = STP_LOOKUP, handling = hash, ws = 0x807e89078 { id = "sess", {s,f,r,e} = {0x807e89810,,+655,0x0,+16384}, }, worker = 0x7ffff158ba60 { }, vcl = { srcname = { "input", "Default", }, }, }, Child cleanup complete }} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 2 18:26:32 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Mar 2009 18:26:32 -0000 Subject: [Varnish] #414: Another Varnish crash with -h critbit In-Reply-To: <052.d1b5f20b8f9b6ec243165098c2b9a912@projects.linpro.no> References: <052.d1b5f20b8f9b6ec243165098c2b9a912@projects.linpro.no> Message-ID: <061.206572c6f5971ce256b1f8f077ab9f8f@projects.linpro.no> #414: Another Varnish crash with -h critbit ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by phk): r3860 should help some. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 2 21:02:44 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Mar 2009 21:02:44 -0000 Subject: [Varnish] #448: Allow caching with past-date Expires (without cache-control) In-Reply-To: <052.231975af1f2f90f9a363156d9b36c5d3@projects.linpro.no> References: <052.231975af1f2f90f9a363156d9b36c5d3@projects.linpro.no> Message-ID: <061.69d630abf531ec57c1976d4f0463cc36@projects.linpro.no> #448: Allow caching with past-date Expires (without cache-control) ----------------------+----------------------------------------------------- Reporter: stonor | Owner: tfheen Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by tfheen): * owner: phk => tfheen -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 2 21:13:36 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Mar 2009 21:13:36 -0000 Subject: [Varnish] #448: Allow caching with past-date Expires (without cache-control) In-Reply-To: <052.231975af1f2f90f9a363156d9b36c5d3@projects.linpro.no> References: <052.231975af1f2f90f9a363156d9b36c5d3@projects.linpro.no> Message-ID: <061.f22d6bc3a013d7c73182eff397e1c9ad@projects.linpro.no> #448: Allow caching with past-date Expires (without cache-control) ----------------------+----------------------------------------------------- Reporter: stonor | Owner: tfheen Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by tfheen): You can work around this by setting obj.cacheable to true as well as obj.ttl in vcl_fetch. The attached patch implements setting obj.cacheable automatically when obj.ttl is set. It might get applied a bit later in the 2.1 cycle. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Mar 3 14:43:55 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 03 Mar 2009 14:43:55 -0000 Subject: [Varnish] #374: Implement restart in vcl_error In-Reply-To: <053.fd2fc11de17ab07a4a0b42ad6d8273db@projects.linpro.no> References: <053.fd2fc11de17ab07a4a0b42ad6d8273db@projects.linpro.no> Message-ID: <062.e65b9f1c8b83a8c6d0dfba7a0ff55ec9@projects.linpro.no> #374: Implement restart in vcl_error -------------------------------+-------------------------------------------- Reporter: tcouery | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 2.1 release Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: restart vcl_error | -------------------------------+-------------------------------------------- Comment (by nygren): I really miss this feature. Regards Fredrik Nygren -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Mar 3 14:58:42 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 03 Mar 2009 14:58:42 -0000 Subject: [Varnish] #374: Implement restart in vcl_error In-Reply-To: <053.fd2fc11de17ab07a4a0b42ad6d8273db@projects.linpro.no> References: <053.fd2fc11de17ab07a4a0b42ad6d8273db@projects.linpro.no> Message-ID: <062.cd3950857f032a8c21c76c1323996241@projects.linpro.no> #374: Implement restart in vcl_error -------------------------------+-------------------------------------------- Reporter: tcouery | Owner: kristian Type: defect | Status: new Priority: normal | Milestone: Varnish 2.1 release Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: restart vcl_error | -------------------------------+-------------------------------------------- Changes (by kristian): * owner: phk => kristian Comment: Is changing backend the only use case here? If so, you can use a backend director for your backends which will cover this scenario. The random director allows for weighting of specific backends too. (I'm working on restart in vcl_error since it's needed for #369) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Mar 3 14:58:53 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 03 Mar 2009 14:58:53 -0000 Subject: [Varnish] #374: Implement restart in vcl_error In-Reply-To: <053.fd2fc11de17ab07a4a0b42ad6d8273db@projects.linpro.no> References: <053.fd2fc11de17ab07a4a0b42ad6d8273db@projects.linpro.no> Message-ID: <062.edb7b845c9945a36464baa104bfcee0d@projects.linpro.no> #374: Implement restart in vcl_error -------------------------------+-------------------------------------------- Reporter: tcouery | Owner: kristian Type: defect | Status: assigned Priority: normal | Milestone: Varnish 2.1 release Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: restart vcl_error | -------------------------------+-------------------------------------------- Changes (by kristian): * status: new => assigned -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Mar 3 15:04:51 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 03 Mar 2009 15:04:51 -0000 Subject: [Varnish] #374: Implement restart in vcl_error In-Reply-To: <053.fd2fc11de17ab07a4a0b42ad6d8273db@projects.linpro.no> References: <053.fd2fc11de17ab07a4a0b42ad6d8273db@projects.linpro.no> Message-ID: <062.70ac830392b47889df3145fda48f8b85@projects.linpro.no> #374: Implement restart in vcl_error -------------------------------+-------------------------------------------- Reporter: tcouery | Owner: kristian Type: defect | Status: assigned Priority: normal | Milestone: Varnish 2.1 release Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: restart vcl_error | -------------------------------+-------------------------------------------- Comment (by phk): I could imagine other uses than changing backend, for instance URL normalization etc. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Mar 4 18:53:21 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 04 Mar 2009 18:53:21 -0000 Subject: [Varnish] #374: Implement restart in vcl_error In-Reply-To: <053.fd2fc11de17ab07a4a0b42ad6d8273db@projects.linpro.no> References: <053.fd2fc11de17ab07a4a0b42ad6d8273db@projects.linpro.no> Message-ID: <062.5ced0b739a263fe19d60629d78f3bc87@projects.linpro.no> #374: Implement restart in vcl_error -------------------------------+-------------------------------------------- Reporter: tcouery | Owner: kristian Type: defect | Status: assigned Priority: normal | Milestone: Varnish 2.1 release Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: restart vcl_error | -------------------------------+-------------------------------------------- Comment (by tcouery): When a server starts to malfunction, users have errors until the backend director detect the problem. In combination with this feature, we can avoid this -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Mar 4 19:05:41 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 04 Mar 2009 19:05:41 -0000 Subject: [Varnish] #462: Using Varnish on port 8080 Message-ID: <051.b6ca5292398857a95e4aa36de99f0e06@projects.linpro.no> #462: Using Varnish on port 8080 ---------------------------------+------------------------------------------ Reporter: mshen | Type: defect Status: new | Priority: normal Milestone: Varnish 2.1 release | Component: build Version: trunk | Severity: normal Keywords: | ---------------------------------+------------------------------------------ Varnish works great when configured on port 80, but when I run: varnishd -a :8080 -T localhost:6082 -f web.vcl I cannot access the website using http://IP_address:8080. Is it possible to make varnish work in this way? I'm working on a reverse proxy for a webservice which will not use port 80 can I use Varnish for this purpose? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 6 00:39:32 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 06 Mar 2009 00:39:32 -0000 Subject: [Varnish] #463: varnish returns no content on error 403/404 from thttpd backend Message-ID: <048.4491cba94f3aeda640c0f9b04ff300ad@projects.linpro.no> #463: varnish returns no content on error 403/404 from thttpd backend -------------------+-------------------------------------------------------- Reporter: wg | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: trunk | Severity: normal Keywords: | -------------------+-------------------------------------------------------- Response from backend: {{{ HTTP/1.1 404 Not Found Server: thttpd/2.25b 29dec2003 Content-Type: text/html; charset=iso-8859-1 Date: Thu, 05 Mar 2009 23:20:27 GMT Last-Modified: Thu, 05 Mar 2009 23:20:27 GMT Accept-Ranges: bytes Connection: close Cache-Control: no-cache,no-store 404 Not Found

404 Not Found

The requested URL '/does_not_exist.gif' was not found on this server.
thttpd/2.25b 29dec2003
Connection closed by foreign host. }}} but Varnish returns the following to client: {{{ HTTP/1.1 404 Not Found Server: thttpd/2.25b 29dec2003 Content-Type: text/html; charset=iso-8859-1 Last-Modified: Thu, 05 Mar 2009 23:20:56 GMT Cache-Control: no-cache,no-store X-Varnish-Host: web04.tp2.us Date: Thu, 05 Mar 2009 23:20:56 GMT X-Varnish: 378740109 Age: 0 Via: 1.1 varnish Connection: keep-alive }}} followed by no content and a time-out resulting in a time-out and blank page returned to client here is varnishlog output for the request: {{{ 327 ReqStart c 10.67.75.148 64993 378747348 327 RxRequest c GET 327 RxURL c /does_not_exist.gif 327 RxProtocol c HTTP/1.1 327 RxHeader c Host: images. 327 VCL_call c recv 327 VCL_return c lookup 327 VCL_call c hash 327 VCL_return c hash 327 VCL_call c miss 327 VCL_return c fetch 129 BackendOpen b ckimages 10.127.1.2 56256 10.127.1.2 80 327 Backend c 129 ckimages ckimages 129 TxRequest b GET 129 TxURL b /does_not_exist.gif 129 TxProtocol b HTTP/1.1 129 TxHeader b Host: images. 129 TxHeader b X-Varnish: 378747348 129 TxHeader b X-Forwarded-For: 10.67.75.148 129 RxProtocol b HTTP/1.1 129 RxStatus b 404 129 RxResponse b Not Found 129 RxHeader b Server: thttpd/2.25b 29dec2003 129 RxHeader b Content-Type: text/html; charset=iso-8859-1 129 RxHeader b Date: Thu, 05 Mar 2009 23:27:16 GMT 129 RxHeader b Last-Modified: Thu, 05 Mar 2009 23:27:16 GMT 129 RxHeader b Accept-Ranges: bytes 129 RxHeader b Connection: close 129 RxHeader b Cache-Control: no-cache,no-store 327 ObjProtocol c HTTP/1.1 327 ObjStatus c 404 327 ObjResponse c Not Found 327 ObjHeader c Server: thttpd/2.25b 29dec2003 327 ObjHeader c Content-Type: text/html; charset=iso-8859-1 327 ObjHeader c Date: Thu, 05 Mar 2009 23:27:16 GMT 327 ObjHeader c Last-Modified: Thu, 05 Mar 2009 23:27:16 GMT 327 ObjHeader c Cache-Control: no-cache,no-store 129 BackendClose b ckimages 327 TTL c 378747348 RFC 120 1236295636 0 0 0 0 327 VCL_call c fetch 327 VCL_return c pass 327 Length c 0 327 VCL_call c deliver 327 VCL_return c deliver 327 TxProtocol c HTTP/1.1 327 TxStatus c 404 327 TxResponse c Not Found 327 TxHeader c Server: thttpd/2.25b 29dec2003 327 TxHeader c Content-Type: text/html; charset=iso-8859-1 327 TxHeader c Last-Modified: Thu, 05 Mar 2009 23:27:16 GMT 327 TxHeader c Cache-Control: no-cache,no-store 327 TxHeader c X-Varnish-Host: web04.tp2.us 327 TxHeader c Date: Thu, 05 Mar 2009 23:27:16 GMT 327 TxHeader c X-Varnish: 378747348 327 TxHeader c Age: 0 327 TxHeader c Via: 1.1 varnish 327 TxHeader c Connection: keep-alive 327 ReqEnd c 378747348 1236295636.380182028 1236295636.380813122 2.589750290 0.000571012 0.000060081 0 ExpPick - 378747348 ttl 0 ExpKill - 378747348 -10 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 6 04:24:09 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 06 Mar 2009 04:24:09 -0000 Subject: [Varnish] #463: varnish returns no content on error 403/404 from thttpd backend In-Reply-To: <048.4491cba94f3aeda640c0f9b04ff300ad@projects.linpro.no> References: <048.4491cba94f3aeda640c0f9b04ff300ad@projects.linpro.no> Message-ID: <057.e67905cc2d82a5cd946ffecaaa7d3f4f@projects.linpro.no> #463: varnish returns no content on error 403/404 from thttpd backend --------------------+------------------------------------------------------- Reporter: wg | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+------------------------------------------------------- Comment (by wg): My bad, I forgot to specify version as 2.0.2, not trunk -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sat Mar 7 21:07:13 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sat, 07 Mar 2009 21:07:13 -0000 Subject: [Varnish] #464: Varnish won't build on solaris Message-ID: <055.a00768cebb44c580e3934ceafb255b7a@projects.linpro.no> #464: Varnish won't build on solaris -----------------------+---------------------------------------------------- Reporter: joevandyk | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: trunk | Severity: normal Keywords: | -----------------------+---------------------------------------------------- 2.0.3 won't build on my system. (but I think that build failure was fixed in trunk). Trying to build the trunk version: gmake[2]: Entering directory `/varnish/varnish-cache/bin' Making all in varnishadm gmake[3]: Entering directory `/varnish/varnish-cache/bin/varnishadm' /bin/bash ../../libtool --tag=CC --mode=link gcc -g -O2 -o varnishadm varnishadm.o ../../lib/libvarnish/libvarnish.la ../../lib/libvarnishcompat/libvarnishcompat.la -lnsl -lsocket gcc -g -O2 -o .libs/varnishadm varnishadm.o ../../lib/libvarnish/.libs/libvarnish.so -lrt -lm ../../lib/libvarnishcompat/.libs/libvarnishcompat.so -lnsl -lsocket -R/usr/local/lib Undefined first referenced symbol in file isfinite ../../lib/libvarnish/.libs/libvarnish.so ld: fatal: Symbol referencing errors. No output written to .libs/varnishadm collect2: ld returned 1 exit status gmake[3]: *** [varnishadm] Error 1 gmake[3]: Leaving directory `/varnish/varnish-cache/bin/varnishadm' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/varnish/varnish-cache/bin' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/varnish/varnish-cache' gmake: *** [all] Error 2 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sat Mar 7 21:08:08 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sat, 07 Mar 2009 21:08:08 -0000 Subject: [Varnish] #464: Varnish won't build on solaris In-Reply-To: <055.a00768cebb44c580e3934ceafb255b7a@projects.linpro.no> References: <055.a00768cebb44c580e3934ceafb255b7a@projects.linpro.no> Message-ID: <064.f9c11e435f473c8f5ae2ab76bf1a6909@projects.linpro.no> #464: Varnish won't build on solaris -----------------------+---------------------------------------------------- Reporter: joevandyk | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Comment (by joevandyk): Same problem reported here: http://projects.linpro.no/pipermail/varnish- misc/2008-October/002172.html -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Mar 10 08:24:32 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 10 Mar 2009 08:24:32 -0000 Subject: [Varnish] #465: regsub seems no use in sub_recv as a hash key Message-ID: <054.718ef071bbedab1d4b361c82b70a7e9e@projects.linpro.no> #465: regsub seems no use in sub_recv as a hash key --------------------------+------------------------------------------------- Reporter: flyincat | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: 2.0 | Severity: normal Keywords: hash req.url | --------------------------+------------------------------------------------- I'm using varnish 2.0.2 right now. But I encountered a problem with the varnish cache hash. I reset req.url by {{{ if (req.url ~ ".(jpg|gif|png)\?.*") { set req.url = regsub(req.url, "\?.*", ""); } }}} cause my urls are all followed with a parameter, and I want to cache the pictures. however, when I visited a same url with a different parameter, varnish told me it's missed and fetch content from the backend server. (For example, I first visit a url: http://www.example.com/h/Mzatest.jpg?m=0301, then I change the parameter 0301 to 0302 and retrieve again.It will told me it's missed) I solved this problem by reset hash key in sub_hash: {{{ sub vcl_hash { if (req.url ~ ".(jpg|gif|png)\?.*") { set req.hash += regsub(req.url, "\?.*", ""); } else { set req.hash += req.url; } hash; }}} It works! -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Mar 11 10:11:41 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 11 Mar 2009 10:11:41 -0000 Subject: [Varnish] #465: regsub seems no use in sub_recv as a hash key In-Reply-To: <054.718ef071bbedab1d4b361c82b70a7e9e@projects.linpro.no> References: <054.718ef071bbedab1d4b361c82b70a7e9e@projects.linpro.no> Message-ID: <063.b73f6425ec1f7ebe3d04826c1f361903@projects.linpro.no> #465: regsub seems no use in sub_recv as a hash key --------------------------+------------------------------------------------- Reporter: flyincat | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: 2.0 Severity: normal | Resolution: worksforme Keywords: hash req.url | --------------------------+------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => worksforme Comment: I tried to reproduce this problem and could not. You should not need to do anything with vcl_hash{} if you rewrite the req.url in vcl_recv{} since it uses the most recent set value for req.url. Are you sure it is not some other thing that causes the miss ? Host: header for instance ? Poul-Henning -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Mar 11 10:53:00 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 11 Mar 2009 10:53:00 -0000 Subject: [Varnish] #466: Range requests are not stripped Message-ID: <049.fe9aee350d3eaa168aa1a5f93ba23cea@projects.linpro.no> #466: Range requests are not stripped ----------------------+----------------------------------------------------- Reporter: phk | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------------------------------- Varnish does not support range requests, but we mistakenly forward them to the backend. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Mar 11 11:08:43 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 11 Mar 2009 11:08:43 -0000 Subject: [Varnish] #466: Range requests are not stripped In-Reply-To: <049.fe9aee350d3eaa168aa1a5f93ba23cea@projects.linpro.no> References: <049.fe9aee350d3eaa168aa1a5f93ba23cea@projects.linpro.no> Message-ID: <058.f6842bcc7abd438ce8fe16c38aa39fc5@projects.linpro.no> #466: Range requests are not stripped ----------------------+----------------------------------------------------- Reporter: phk | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: fixed in r3910 Should be merged to 2.0.3 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Mar 11 11:57:12 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 11 Mar 2009 11:57:12 -0000 Subject: [Varnish] #462: Using Varnish on port 8080 In-Reply-To: <051.b6ca5292398857a95e4aa36de99f0e06@projects.linpro.no> References: <051.b6ca5292398857a95e4aa36de99f0e06@projects.linpro.no> Message-ID: <060.639ce4e7d1b7e69aba0b2420d0929a78@projects.linpro.no> #462: Using Varnish on port 8080 --------------------+------------------------------------------------------- Reporter: mshen | Owner: Type: defect | Status: closed Priority: normal | Milestone: Varnish 2.1 release Component: build | Version: trunk Severity: normal | Resolution: worksforme Keywords: | --------------------+------------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => worksforme Comment: Without logfiles or other details it is very hard to figure out what is wrong. One very likely cause is the Host: header does not satisfy the backend when it is on IP:8080 form, try setting a suitable Host: header in your VCL and see if that helps. Your backends http-error log files should tell you if this is indeed the trouble. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Mar 12 10:23:00 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 12 Mar 2009 10:23:00 -0000 Subject: [Varnish] #467: prevent percent-aspects of munin plugin from scaling Message-ID: <050.a304b631f86c5a94e2698d09ae1dfbe2@projects.linpro.no> #467: prevent percent-aspects of munin plugin from scaling -------------------+-------------------------------------------------------- Reporter: anti | Type: enhancement Status: new | Priority: normal Milestone: | Component: munin Version: trunk | Severity: trivial Keywords: | -------------------+-------------------------------------------------------- Percentage aspects (like ratio and cache-usage) are easier to compare, if they are always shown in a 0-100 scale. The current munin-plugin tries to do that, but "graph_scale no" only tells munin not to scale the numbers. ''graph_scale no makes munin (rrd) not scale the number. Normally a reading of 1000 would be scaled to 1k and 1000000 to '1M' (according to scales set with --base explained above).'' (http://munin.projects.linpro.no/wiki/HowToWritePlugins) To actually have rrdtool always paint the graph on a 0-100% scale, it is necessary to set graph_args accordingly, replacing the `print "graph_scale no\n";` in source:trunk/varnish-tools/munin/varnish_munin_plugin.pl#L149 with `print "graph_args --lower-limit 0 --upper-limit 100 --rigid\n";` -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Mar 12 18:41:31 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 12 Mar 2009 18:41:31 -0000 Subject: [Varnish] #468: spanish accentuated domains Message-ID: <055.80f79ada41e35c88da910e12aeeaa9b8@projects.linpro.no> #468: spanish accentuated domains -------------------------+-------------------------------------------------- Reporter: ajlozanob | Owner: phk Type: enhancement | Status: new Priority: normal | Milestone: After Varnish 2.1 Component: varnishd | Version: 2.0 Severity: blocker | Keywords: accetuated domain spanish -------------------------+-------------------------------------------------- I have one customer who have some spanish domains, with accents, like : www.productosconstrucci?n.es, and i can't get it run in my ACL, Any idea? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Mar 12 18:52:54 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 12 Mar 2009 18:52:54 -0000 Subject: [Varnish] #469: Vedicsoft best IT recruiting company Message-ID: <068.7f3e61f0e19cf2ccee08b03cc8849bc6@projects.linpro.no> #469: Vedicsoft best IT recruiting company --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ Reporter: vedicsoftitrecrutiment | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: trunk | Severity: normal Keywords: Vedicsoft, Vedicsoftit, vedicsoft it recrutiment, Vedicsoft proffesional, Vedicsoft professionals, Vedicsoft Enterprise Resource Planning, Vedicsoft SAP, Vedicsoft Enterprise Application | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ [Vedicsoft][www.vedicsoft.com] is one of the leading providers of IT professional services in Data Management, Business Intelligence and Business Integration. We provide end-to-end solutions in building decision support systems for fortune 1000 and mid-market companies. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Mar 12 19:07:32 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 12 Mar 2009 19:07:32 -0000 Subject: [Varnish] #470: cryptic error message when drive is full Message-ID: <054.da702999a39b226cda07dfa84b3c1c6d@projects.linpro.no> #470: cryptic error message when drive is full ----------------------+----------------------------------------------------- Reporter: jacquesm | Type: enhancement Status: new | Priority: normal Milestone: | Component: build Version: 2.0 | Severity: normal Keywords: | ----------------------+----------------------------------------------------- When the file system that varnishd intends to use for its cache is full then it will give the following error: Error: (-sfile) size "50%": Absolute number required A more effective error message would be: No space on device. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 13 09:12:02 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 13 Mar 2009 09:12:02 -0000 Subject: [Varnish] #468: spanish accentuated domains In-Reply-To: <055.80f79ada41e35c88da910e12aeeaa9b8@projects.linpro.no> References: <055.80f79ada41e35c88da910e12aeeaa9b8@projects.linpro.no> Message-ID: <064.acbc5dc7594256f2bfcde6c5c71f3de4@projects.linpro.no> #468: spanish accentuated domains ---------------------------------------+------------------------------------ Reporter: ajlozanob | Owner: phk Type: enhancement | Status: closed Priority: normal | Milestone: After Varnish 2.1 Component: varnishd | Version: 2.0 Severity: blocker | Resolution: invalid Keywords: accetuated domain spanish | ---------------------------------------+------------------------------------ Changes (by kristian): * status: new => closed * resolution: => invalid Comment: You need to use the puny-code, ie: www.xn--productosconstruccin-t8b.es. Tools like http://mct.verisign- grs.com/conversiontool/convertServlet?input=www.productosconstrucci?n.es&type=UTF8 can convert for you. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 13 14:24:25 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 13 Mar 2009 14:24:25 -0000 Subject: [Varnish] #448: Allow caching with past-date Expires (without cache-control) In-Reply-To: <052.231975af1f2f90f9a363156d9b36c5d3@projects.linpro.no> References: <052.231975af1f2f90f9a363156d9b36c5d3@projects.linpro.no> Message-ID: <061.aa7295a589dd7455acc5b9797df48b5e@projects.linpro.no> #448: Allow caching with past-date Expires (without cache-control) ----------------------+----------------------------------------------------- Reporter: stonor | Owner: tfheen Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by stonor): great, thanks! -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sat Mar 14 06:45:52 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sat, 14 Mar 2009 06:45:52 -0000 Subject: [Varnish] #464: Varnish won't build on solaris In-Reply-To: <055.a00768cebb44c580e3934ceafb255b7a@projects.linpro.no> References: <055.a00768cebb44c580e3934ceafb255b7a@projects.linpro.no> Message-ID: <064.c6ffb79543b9510a50898940586f80df@projects.linpro.no> #464: Varnish won't build on solaris -----------------------+---------------------------------------------------- Reporter: joevandyk | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Comment (by IgorMinar): On Solaris there is no `isfinite`, but instead there is `finite`. This patched worked for me: {{{ diff -ur lib/libvarnish/num.c varnish-2.0.3-patched/lib/libvarnish/num.c --- lib/libvarnish/num.c Thu Feb 12 03:15:24 2009 +++ lib/libvarnish/num.c Fri Feb 13 13:24:10 2009 @@ -54,7 +54,7 @@ return (err_miss_num); fval = strtod(p, &end); - if (end == p || !isfinite(fval)) + if (end == p || !finite(fval)) return (err_invalid_num); if (*end == '\0') { }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sat Mar 14 06:52:05 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sat, 14 Mar 2009 06:52:05 -0000 Subject: [Varnish] #464: Varnish won't build on solaris In-Reply-To: <055.a00768cebb44c580e3934ceafb255b7a@projects.linpro.no> References: <055.a00768cebb44c580e3934ceafb255b7a@projects.linpro.no> Message-ID: <064.75339a60206023611d85f6d98aa586a4@projects.linpro.no> #464: Varnish won't build on solaris -----------------------+---------------------------------------------------- Reporter: joevandyk | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Comment (by IgorMinar): oh and I also had to apply this patch: {{{ --- config.h.in Fri Feb 13 16:38:45 2009 +++ config.h.in Fri Feb 13 14:25:47 2009 @@ -222,3 +222,10 @@ /* Define to `unsigned int' if does not define. */ /* #undef size_t */ + +# ifndef NAN +# define NAN (0.0/0.0) +# endif + +# define __BEGIN_DECLS /* empty */ +# define __END_DECLS /* empty */ }}} I see that `__BEGIN_DECLS` was removed from the trunk, I wonder if something can be done about NAN too. Maybe there is a more suitable solution than the one in my patch. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Mar 15 07:07:58 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Mar 2009 07:07:58 -0000 Subject: [Varnish] #471: Compilation fixes for NetBSD (and probably others) Message-ID: <053.fa6986291a83952a25214719c7b1abe3@projects.linpro.no> #471: Compilation fixes for NetBSD (and probably others) -------------------------------+-------------------------------------------- Reporter: michael | Type: defect Status: new | Priority: normal Milestone: After Varnish 2.1 | Component: build Version: trunk | Severity: normal Keywords: | -------------------------------+-------------------------------------------- When version-bumping varnish in pkgsrc (http://www.pkgsrc.org/), I noticed that small changes are still necessary. In particular, sys/types.h needs to be included in bin/varnishhist/varnishhist.c and bin/varnishreplay/varnishreplay.c. Also, the two #if defined(__FreeBSD__) in bin/varnishd/cache_pool.c should be expanded to #if defined(__FreeBSD__) || defined(__DragonFly__). Patches are attached, please apply them. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Mar 15 07:12:34 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Mar 2009 07:12:34 -0000 Subject: [Varnish] #471: Compilation fixes for NetBSD (and probably others) In-Reply-To: <053.fa6986291a83952a25214719c7b1abe3@projects.linpro.no> References: <053.fa6986291a83952a25214719c7b1abe3@projects.linpro.no> Message-ID: <062.c9cda2afdb955fdf0843b0977481cd51@projects.linpro.no> #471: Compilation fixes for NetBSD (and probably others) ---------------------+------------------------------------------------------ Reporter: michael | Owner: Type: defect | Status: new Priority: normal | Milestone: After Varnish 2.1 Component: build | Version: trunk Severity: normal | Resolution: Keywords: | ---------------------+------------------------------------------------------ Comment (by michael): Sorry, I got the milestone wrong. This affects varnish-2.0.3. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Mar 15 09:58:06 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Mar 2009 09:58:06 -0000 Subject: [Varnish] #472: Crash in HSH_Prepare (ESI in use) Message-ID: <054.e14ddd59dbeecaaa4924d6215e2db662@projects.linpro.no> #472: Crash in HSH_Prepare (ESI in use) ----------------------+----------------------------------------------------- Reporter: kristian | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------------------------------- This seems to happen under _some_ load, but not a lot. Typically on ESI- heavy pages combined with several misses. {{{ (gdb) bt full #0 0x00002b46c1003bb5 in raise () from /lib64/libc.so.6 No symbol table info available. #1 0x00002b46c1004fb0 in abort () from /lib64/libc.so.6 No symbol table info available. #2 0x000000000041b0d7 in pan_ic (func=, file=, line=, cond=, err=-1428692184, xxx=) at cache_panic.c:317 l = p = 0x2b46c15002d8
q = sp = (const struct sess *) 0x0 #3 0x00000000004158ac in HSH_Prepare (sp=0x2aabeb367008, nhashcount=6) at cache_hash.c:187 p = u = __func__ = "HSH_Prepare" #4 0x000000000040efc8 in cnt_lookup (sp=0x2aabeb367008) at cache_center.c:583 o = __func__ = "cnt_lookup" #5 0x0000000000410a22 in CNT_Session (sp=0x2aabeb367008) at steps.h:38 done = -348753912 w = (struct worker *) 0x2aacdba44c60 __func__ = "CNT_Session" #6 0x0000000000423ce8 in ESI_Deliver (sp=0x2aabeb367008) at cache_vrt_esi.c:810 eb = (struct esi_bit *) 0x2aabeb54fa40 obj = (struct object *) 0x2aaaab2b3000 __func__ = "ESI_Deliver" #7 0x000000000041cc4f in RES_WriteObj (sp=0x2aabeb367008) at cache_response.c:150 st = u = lenbuf = "\bp6?*\000\000\000\000\000\000\000\000\000\000`L??" __func__ = "RES_WriteObj" #8 0x000000000040faba in cnt_deliver (sp=0x2aabeb367008) at cache_center.c:180 __func__ = "cnt_deliver" #9 0x000000000041073a in CNT_Session (sp=0x2aabeb367008) at steps.h:42 done = 0 w = (struct worker *) 0x2aacdba44c60 __func__ = "CNT_Session" #10 0x000000000041c642 in wrk_do_cnt_sess (w=0x2aacdba44c60, priv=) at cache_pool.c:398 sess = (struct sess *) 0x2aabeb367008 __func__ = "wrk_do_cnt_sess" #11 0x000000000041bd25 in wrk_thread (priv=0x2b46c1413100) at cache_pool.c:310 ww = {magic = 1670491599, nobjhead = 0x2aabeb838740, nobj = 0x2aaaab862000, lastused = 1237110660.244344, cond = {__data = { __lock = 0, __futex = 2478, __total_seq = 1239, __wakeup_seq = 1239, __woken_seq = 1239, __mutex = 0x2b46c14f0288, __nwaiters = 0, __broadcast_seq = 0}, __size = "\000\000\000\000?\t\000\000?\004\000\000\000\000\000\000?\004\000\000\000\000\000\000?\004\000\000\000\000\000\000\210\002O?F+\000\000\000\000\000\000\000\000\000", __align = 10642928959488}, list = {vtqe_next = 0x2aacda241c60, vtqe_prev = 0x2b46c1413110}, wrq = 0x2aabeb367198, wfd = 0x0, werr = 0, iov = {{iov_base = 0x2aabeb54fa50, iov_len = 4}, {iov_base = 0x2aaaac5085cd, iov_len = 127}, {iov_base = 0x43f5d6, iov_len = 2}, {iov_base = 0x43dae7, iov_len = 1}, {iov_base = 0x43cd05, iov_len = 8}, {iov_base = 0x43f5d6, iov_len = 2}, {iov_base = 0x2aabeb367855, iov_len = 212}, {iov_base = 0x43f5d6, iov_len = 2}, {iov_base = 0x2aabeb36792b, iov_len = 39}, {iov_base = 0x43f5d6, iov_len = 2}, {iov_base = 0x2aabeb367954, iov_len = 19}, {iov_base = 0x43f5d6, iov_len = 2}, { iov_base = 0x2aabeb367969, iov_len = 216}, {iov_base = 0x43f5d6, iov_len = 2}, {iov_base = 0x2aabeb367a43, iov_len = 30}, { iov_base = 0x43f5d6, iov_len = 2}, {iov_base = 0x2aabeb367a93, iov_len = 109}, {iov_base = 0x43f5d6, iov_len = 2}, { iov_base = 0x2aabeb367fe1, iov_len = 18}, {iov_base = 0x43f5d6, iov_len = 2}, {iov_base = 0x2aac3710f2a0, iov_len = 12}, { iov_base = 0x43f5d6, iov_len = 2}, {iov_base = 0x2aac3710f2ad, iov_len = 30}, {iov_base = 0x43f5d6, iov_len = 2}, { iov_base = 0x43f5d6, iov_len = 2}, {iov_base = 0x2aaaabfba000, iov_len = 179}, {iov_base = 0x43dfeb, iov_len = 16}, { iov_base = 0x43f5d6, iov_len = 2}, {iov_base = 0x2aacb892a9a6, iov_len = 17}, {iov_base = 0x43f5d6, iov_len = 2}, { iov_base = 0x43f5d6, iov_len = 2}, {iov_base = 0x2aaaab33c000, iov_len = 3059}, {iov_base = 0x43f5d6, iov_len = 2}, { iov_base = 0x43f5d6, iov_len = 2}, {iov_base = 0x43f5d6, iov_len = 2}, {iov_base = 0x2aaaab199000, iov_len = 29597}, { iov_base = 0x0, iov_len = 0} }, niov = 0, liov = 0, vcl = 0x0, srcaddr = 0x2aabeb8041c0, wlb = 0x2aacdba42c50 "'", wlp = 0x2aacdba42c50 "'", wle = 0x2aacdba44c50 "", wlr = 0, sha256ctx = 0x2aacdba45120} sha256 = {state = {1779033703, 3144134277, 1013904242, 2773480762, 1359893119, 2600822924, 528734635, 1541459225}, count = 0, buf = '\0' } __func__ = "wrk_thread" #12 0x00002b46c0c55143 in start_thread () from /lib64/libpthread.so.0 No symbol table info available. ---Type to continue, or q to quit--- #13 0x00002b46c10948cd in clone () from /lib64/libc.so.6 No symbol table info available. #14 0x0000000000000000 in ?? () No symbol table info available. (gdb) }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Mar 15 09:59:18 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Mar 2009 09:59:18 -0000 Subject: [Varnish] #472: Crash in HSH_Prepare (ESI in use) In-Reply-To: <054.e14ddd59dbeecaaa4924d6215e2db662@projects.linpro.no> References: <054.e14ddd59dbeecaaa4924d6215e2db662@projects.linpro.no> Message-ID: <063.1c81857777d8c0e561fc4eac15129e94@projects.linpro.no> #472: Crash in HSH_Prepare (ESI in use) ----------------------+----------------------------------------------------- Reporter: kristian | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 2.0 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by kristian): * owner: => phk * version: trunk => 2.0 * component: build => varnishd Comment: Err, forgot to mention some essential details: Varnish 2.0.3. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 16 03:42:07 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 16 Mar 2009 03:42:07 -0000 Subject: [Varnish] #432: Multiple lines of Set-Cookie in response headers aren't reflected in obj.http.Set-Cookie In-Reply-To: <053.1462d71fa5ff32c1ceb5a5db8975f3dc@projects.linpro.no> References: <053.1462d71fa5ff32c1ceb5a5db8975f3dc@projects.linpro.no> Message-ID: <062.39cf0ab067705f9dab734bedc4abc373@projects.linpro.no> #432: Multiple lines of Set-Cookie in response headers aren't reflected in obj.http.Set-Cookie ------------------------+--------------------------------------------------- Reporter: Mitchua | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 2.0 Severity: normal | Resolution: Keywords: Set-Cookie | ------------------------+--------------------------------------------------- Comment (by dixond): I confirm this definitely doesn't seem to work correctly. EG, in vcl_fetch I have: {{{ set obj.http.Stupid = obj.http.Set-Cookie; }}} And the result on a page that has two Set-Cookie lines is: {{{ Set-Cookie: I18N_LANGUAGE="en"; Path=/ Set-Cookie: cmsdir="/edit-cms"; Path=/ Stupid: I18N_LANGUAGE="en"; Path=/ }}} I am trying to make some decisions in vcl_fetch about whether to insert or pass an object based on what the backend has sent in terms of set-cookie (eg, is this a user-specific cookie or something else?), but my regex does not seem able to match against the contents of Set-Cookie at all, which is possibly because it doesn't really contain the full list of possible cookies...? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Mar 18 11:27:14 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 18 Mar 2009 11:27:14 -0000 Subject: [Varnish] #374: Implement restart in vcl_error In-Reply-To: <053.fd2fc11de17ab07a4a0b42ad6d8273db@projects.linpro.no> References: <053.fd2fc11de17ab07a4a0b42ad6d8273db@projects.linpro.no> Message-ID: <062.e242534628ae94ac19ff4919d093c9a9@projects.linpro.no> #374: Implement restart in vcl_error -------------------------------+-------------------------------------------- Reporter: tcouery | Owner: kristian Type: defect | Status: closed Priority: normal | Milestone: Varnish 2.1 release Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: restart vcl_error | -------------------------------+-------------------------------------------- Changes (by kristian): * status: assigned => closed * resolution: => fixed Comment: Implemented in r3948. Could use some testing. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 09:24:44 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 09:24:44 -0000 Subject: [Varnish] #414: Another Varnish crash with -h critbit In-Reply-To: <052.d1b5f20b8f9b6ec243165098c2b9a912@projects.linpro.no> References: <052.d1b5f20b8f9b6ec243165098c2b9a912@projects.linpro.no> Message-ID: <061.75497a8dbb4e36dcdfd918de67505058@projects.linpro.no> #414: Another Varnish crash with -h critbit ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: closed Priority: high | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: This seems to be fixed now. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 09:25:59 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 09:25:59 -0000 Subject: [Varnish] #430: Varnish crashes with Assert error in HSH_Deref In-Reply-To: <052.240c1acf64980e7d5debe86f76e68fc0@projects.linpro.no> References: <052.240c1acf64980e7d5debe86f76e68fc0@projects.linpro.no> Message-ID: <061.31524c0045eeca521cf77f73dfba3a87@projects.linpro.no> #430: Varnish crashes with Assert error in HSH_Deref ----------------------+----------------------------------------------------- Reporter: anders | 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: I think we have nailed this one, see #414 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 09:26:33 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 09:26:33 -0000 Subject: [Varnish] #434: Critbit crash: Assert error in hcb_delete In-Reply-To: <052.353eed9a394c1c1c65c805e20fcbf6b0@projects.linpro.no> References: <052.353eed9a394c1c1c65c805e20fcbf6b0@projects.linpro.no> Message-ID: <061.7947821bc99533ce635628744ea01d0a@projects.linpro.no> #434: Critbit crash: Assert error in hcb_delete ----------------------+----------------------------------------------------- Reporter: anders | 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: I belive this is fixed, see #414 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 09:27:19 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 09:27:19 -0000 Subject: [Varnish] #459: Varnish crashes with assert error in hsh_rush(), cache_hash.c line 403 In-Reply-To: <052.8cd544c938e7d765661cbdf58ee87f9a@projects.linpro.no> References: <052.8cd544c938e7d765661cbdf58ee87f9a@projects.linpro.no> Message-ID: <061.f5d7ebe6661820e21df4d2b8edd339d8@projects.linpro.no> #459: Varnish crashes with assert error in hsh_rush(), cache_hash.c line 403 ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: critical | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: Belived fixed, see #414 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 09:27:48 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 09:27:48 -0000 Subject: [Varnish] #461: Varnish crashes with assert error in HSH_Lookup(), cache_hash.c line 312 In-Reply-To: <052.8746dd7cb31c0c6d4eedaf97338a84be@projects.linpro.no> References: <052.8746dd7cb31c0c6d4eedaf97338a84be@projects.linpro.no> Message-ID: <061.0efd5c6458cd8213d08623d167d76137@projects.linpro.no> #461: Varnish crashes with assert error in HSH_Lookup(), cache_hash.c line 312 ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: critical | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: I think this is fixed, see #414 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 09:33:37 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 09:33:37 -0000 Subject: [Varnish] #432: Multiple lines of Set-Cookie in response headers aren't reflected in obj.http.Set-Cookie In-Reply-To: <053.1462d71fa5ff32c1ceb5a5db8975f3dc@projects.linpro.no> References: <053.1462d71fa5ff32c1ceb5a5db8975f3dc@projects.linpro.no> Message-ID: <062.150bdd31907e7c436433373aa0ad4b24@projects.linpro.no> #432: Multiple lines of Set-Cookie in response headers aren't reflected in obj.http.Set-Cookie ------------------------+--------------------------------------------------- Reporter: Mitchua | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 2.0 Severity: normal | Resolution: invalid Keywords: Set-Cookie | ------------------------+--------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => invalid Comment: This is a known issue from our wish-list: (point 21: http://varnish.projects.linpro.no/wiki/PostTwoShoppingList) I'm closing this ticket because we don't track change requests in tickets. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 09:38:17 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 09:38:17 -0000 Subject: [Varnish] #472: Crash in HSH_Prepare (ESI in use) In-Reply-To: <054.e14ddd59dbeecaaa4924d6215e2db662@projects.linpro.no> References: <054.e14ddd59dbeecaaa4924d6215e2db662@projects.linpro.no> Message-ID: <063.ebfaa866c3be7a88cb78175c284ecf63@projects.linpro.no> #472: Crash in HSH_Prepare (ESI in use) ----------------------+----------------------------------------------------- Reporter: kristian | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 2.0 Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: When you have many nested transactions, you need to increase the session_workspace parameter upwards. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 09:41:54 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 09:41:54 -0000 Subject: [Varnish] #448: Allow caching with past-date Expires (without cache-control) In-Reply-To: <052.231975af1f2f90f9a363156d9b36c5d3@projects.linpro.no> References: <052.231975af1f2f90f9a363156d9b36c5d3@projects.linpro.no> Message-ID: <061.bcf695b64567a99fbaed29336e3927fc@projects.linpro.no> #448: Allow caching with past-date Expires (without cache-control) ----------------------+----------------------------------------------------- Reporter: stonor | Owner: tfheen Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: worksforme Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => worksforme Comment: The reason we have both obj.cacheable and obj.ttl is that they control separate decisions. For instance, setting obj.ttl = 0s does not prevent the object from being cached for use in grace-schenarios. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 09:52:43 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 09:52:43 -0000 Subject: [Varnish] #437: Varnish 2.0.2 hanging with large amounts of traffic In-Reply-To: <049.251897e59bb49a5cfc6b8575603422fc@projects.linpro.no> References: <049.251897e59bb49a5cfc6b8575603422fc@projects.linpro.no> Message-ID: <058.821fb349b1c79c263d258c0cf560c07f@projects.linpro.no> #437: Varnish 2.0.2 hanging with large amounts of traffic ----------------------+----------------------------------------------------- Reporter: ajt | Owner: perbu Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: critical | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by phk): I am not really able to say much to this one on the available data, could be some kind of resource starvation or could be a bug, possibly a race somewere... Is the issue still happening ? Any core dumps ? Any messages in syslog ? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 09:57:04 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 09:57:04 -0000 Subject: [Varnish] #470: cryptic error message when drive is full In-Reply-To: <054.da702999a39b226cda07dfa84b3c1c6d@projects.linpro.no> References: <054.da702999a39b226cda07dfa84b3c1c6d@projects.linpro.no> Message-ID: <063.a429a207aafbaf321add808f0c485097@projects.linpro.no> #470: cryptic error message when drive is full -------------------------+-------------------------------------------------- Reporter: jacquesm | Owner: kristian Type: enhancement | Status: new Priority: normal | Milestone: Component: build | Version: 2.0 Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by tfheen): * owner: => kristian -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 09:58:40 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 09:58:40 -0000 Subject: [Varnish] #440: Script Using telnet In-Reply-To: <055.0f60ebef3051feb32d319c46c543adcb@projects.linpro.no> References: <055.0f60ebef3051feb32d319c46c543adcb@projects.linpro.no> Message-ID: <064.a9bd0794a1fe6070ca509f42d93e704f@projects.linpro.no> #440: Script Using telnet -------------------------+-------------------------------------------------- Reporter: commandos | Owner: phk Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: worksforme Keywords: | -------------------------+-------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => worksforme Comment: telnet is not very good at reading input from a pipe, it will usually close the connection as soon as the pipe is closed, not waiting for response. the example above with nc(1) is probably better, but if you do not have nc(1) on your system you can try this hack: (echo "purge.url test.html" ; sleep 2 ) | telnet localhost 8787 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 10:12:06 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 10:12:06 -0000 Subject: [Varnish] #471: Compilation fixes for NetBSD (and probably others) In-Reply-To: <053.fa6986291a83952a25214719c7b1abe3@projects.linpro.no> References: <053.fa6986291a83952a25214719c7b1abe3@projects.linpro.no> Message-ID: <062.8a874cab362b54b38b4e7b5951c63caf@projects.linpro.no> #471: Compilation fixes for NetBSD (and probably others) ---------------------+------------------------------------------------------ Reporter: michael | Owner: Type: defect | Status: closed Priority: normal | Milestone: After Varnish 2.1 Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | ---------------------+------------------------------------------------------ Changes (by tfheen): * status: new => closed * resolution: => fixed Comment: (In [3964]) Portability fixes from pkgsrc/NetBSD Apply portability patches from pkgsrc, thanks to michael for forwarding those. Fixes #471 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 10:15:15 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 10:15:15 -0000 Subject: [Varnish] #445: ESI Processor failing when including empty document In-Reply-To: <051.d9cc4c2d964ecaeec4fef3ec70a47eaa@projects.linpro.no> References: <051.d9cc4c2d964ecaeec4fef3ec70a47eaa@projects.linpro.no> Message-ID: <060.316175af79384783d1e65bd984f200bd@projects.linpro.no> #445: ESI Processor failing when including empty document ----------------------+----------------------------------------------------- Reporter: Skade | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: fixed in r3965. Should be merged to 2.0 Sorry about the delay in fixing this. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 10:31:19 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 10:31:19 -0000 Subject: [Varnish] #473: Small errors in example code. Message-ID: <052.2444ffdd455338474faedf608accc486@projects.linpro.no> #473: Small errors in example code. --------------------+------------------------------------------------------- Reporter: rhalff | Type: documentation Status: new | Priority: normal Milestone: | Component: documentation Version: trunk | Severity: normal Keywords: | --------------------+------------------------------------------------------- Hi, at his page in the wiki:Introduction Some code examples are wrong: {{{ if (req.request == 'POST') { pass; } }}} should be with double quotes: {{{ if (req.request == "POST") { pass; } }}} And there is a missing ';' in this piece of code: {{{ if (req.request == "GET" && req.url ~ "^/static/") { unset req.http.cookie; unset req.http.Authorization lookup; } }}} I've used this page to build my own config file, so copying and pasting this code will result in unnecessary errors. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 11:03:51 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 11:03:51 -0000 Subject: [Varnish] #428: Sending badly formed parameters to the management console kills Varnish In-Reply-To: <052.bfc72c097098110a4a483c75ec14892b@projects.linpro.no> References: <052.bfc72c097098110a4a483c75ec14892b@projects.linpro.no> Message-ID: <061.acd488be47e145ae7a6b8cf83276536f@projects.linpro.no> #428: Sending badly formed parameters to the management console kills Varnish ----------------------+----------------------------------------------------- Reporter: petter | Owner: tfheen Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Comment (by tfheen): (In [3966]) Merge r3825: Stop segfaulting when trying to set a nonexistant waiter We failed to properly check for the end of the list of waiters. Handle this correctly and add a test case Fixes #428 (adopt it for 2.0 where waiter is called acceptor) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 11:27:17 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 11:27:17 -0000 Subject: [Varnish] #464: Varnish won't build on solaris In-Reply-To: <055.a00768cebb44c580e3934ceafb255b7a@projects.linpro.no> References: <055.a00768cebb44c580e3934ceafb255b7a@projects.linpro.no> Message-ID: <064.61dcc12a22c3465bfa717e657f6d1959@projects.linpro.no> #464: Varnish won't build on solaris -----------------------+---------------------------------------------------- Reporter: joevandyk | Owner: tfheen Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Changes (by tfheen): * owner: => tfheen -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 11:27:32 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 11:27:32 -0000 Subject: [Varnish] #463: varnish returns no content on error 403/404 from thttpd backend In-Reply-To: <048.4491cba94f3aeda640c0f9b04ff300ad@projects.linpro.no> References: <048.4491cba94f3aeda640c0f9b04ff300ad@projects.linpro.no> Message-ID: <057.e5620d5ca9847eba7c4bfa7cd5b3b63f@projects.linpro.no> #463: varnish returns no content on error 403/404 from thttpd backend --------------------+------------------------------------------------------- Reporter: wg | Owner: tfheen Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+------------------------------------------------------- Changes (by tfheen): * owner: => tfheen -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 11:35:26 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 11:35:26 -0000 Subject: [Varnish] #467: prevent percent-aspects of munin plugin from scaling In-Reply-To: <050.a304b631f86c5a94e2698d09ae1dfbe2@projects.linpro.no> References: <050.a304b631f86c5a94e2698d09ae1dfbe2@projects.linpro.no> Message-ID: <059.a6e5b87e0c59cd45a469a1cb249f4ee6@projects.linpro.no> #467: prevent percent-aspects of munin plugin from scaling -------------------------+-------------------------------------------------- Reporter: anti | Owner: kristian Type: enhancement | Status: new Priority: normal | Milestone: Component: munin | Version: trunk Severity: trivial | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by tfheen): * owner: => kristian -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 11:42:14 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 11:42:14 -0000 Subject: [Varnish] #455: Make HTTP_HDR_MAX a ./configure option In-Reply-To: <054.a08f2c6f3146cb9876379a2ab230675e@projects.linpro.no> References: <054.a08f2c6f3146cb9876379a2ab230675e@projects.linpro.no> Message-ID: <063.56e5e855d46698a7e17c0d0e564d1452@projects.linpro.no> #455: Make HTTP_HDR_MAX a ./configure option -------------------------+-------------------------------------------------- Reporter: whocares | Owner: tfheen Type: enhancement | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: max headers | -------------------------+-------------------------------------------------- Changes (by tfheen): * owner: => tfheen -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 18:24:50 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 18:24:50 -0000 Subject: [Varnish] #398: logging off phpbb always causes "Error 503 Service Unavailable" In-Reply-To: <053.fcc528fb5f49a4e239de8466a1c0a6d5@projects.linpro.no> References: <053.fcc528fb5f49a4e239de8466a1c0a6d5@projects.linpro.no> Message-ID: <062.87ccbf95fd053d197d6760f87b5165d4@projects.linpro.no> #398: logging off phpbb always causes "Error 503 Service Unavailable" -------------------------------------------+-------------------------------- Reporter: mmpower | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 2.0 Severity: normal | Resolution: Keywords: Error 503 Service Unavailable | -------------------------------------------+-------------------------------- Comment (by mmpower): Replying to [comment:2 phk]: > Did you run varnishlog with "-c" argument ? If so, could you leave that out so that we can also see the log entries for the backend communication ? Sorry for the late rely. here is the log wikthout the -c option: 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571916 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571919 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571922 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571925 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571928 12 SessionOpen c 205.178.191.132 46563 12 ReqStart c 205.178.191.132 46563 844250232 12 RxRequest c GET 12 RxURL c /forum/login.php?logout=true&sid=890024b01e3a5656f50e926216c8afd6 12 RxProtocol c HTTP/1.1 12 RxHeader c Host: alpha.haiguinet.com 12 RxHeader c User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729) 12 RxHeader c Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 12 RxHeader c Accept-Language: en-us,en;q=0.5 12 RxHeader c Accept-Encoding: gzip,deflate 12 RxHeader c Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 12 RxHeader c Keep-Alive: 300 12 RxHeader c Connection: keep-alive 12 RxHeader c Referer: http://alpha.haiguinet.com/forum/index.php?sid=890024b01e3a5656f50e926216c8afd6 12 RxHeader c Cookie: setframeview=0; userstatusserver=http%3A//202.142.17.114%3A8080/flashIM/wdkstatus; flashservers=rtmp%3A//202.142.17.114%3A443/flashIM%2Crtmp%3A//202.142.17.124%3A443/freechat%2Chttp%3A//202.142.17.114%3A8080/flashgo%2Chttp%3A//202.142.17.124%3A808 12 VCL_call c recv 12 VCL_return c pass 12 VCL_call c pass 12 VCL_return c pass 13 BackendOpen b default 208.73.238.68 44465 211.147.252.114 80 13 TxRequest b GET 13 TxURL b /forum/login.php?logout=true&sid=890024b01e3a5656f50e926216c8afd6 13 TxProtocol b HTTP/1.1 13 TxHeader b Host: alpha.haiguinet.com 13 TxHeader b User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729) 13 TxHeader b Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 13 TxHeader b Accept-Language: en-us,en;q=0.5 13 TxHeader b Accept-Encoding: gzip,deflate 13 TxHeader b Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 13 TxHeader b Referer: http://alpha.haiguinet.com/forum/index.php?sid=890024b01e3a5656f50e926216c8afd6 13 TxHeader b Cookie: setframeview=0; userstatusserver=http%3A//202.142.17.114%3A8080/flashIM/wdkstatus; flashservers=rtmp%3A//202.142.17.114%3A443/flashIM%2Crtmp%3A//202.142.17.124%3A443/freechat%2Chttp%3A//202.142.17.114%3A8080/flashgo%2Chttp%3A//202.142.17.124%3A808 13 TxHeader b X-Forwarded-For: 205.178.191.132 13 TxHeader b X-Varnish: 844250232 13 TxHeader b X-Forwarded-for: 205.178.191.132 13 BackendClose b default 12 VCL_call c fetch 0 Debug - "VCL_error(0, (null))" 12 VCL_return c error 12 SessionClose c error returned 12 TxProtocol c HTTP/1.0 12 TxStatus c 503 12 TxResponse c Service Unavailable 12 TxHeader c Date: Fri, 20 Mar 2009 17:58:49 GMT 12 TxHeader c Server: Varnish 12 TxHeader c Retry-After: 0 12 TxHeader c Content-Type: text/html; charset=utf-8 12 TxHeader c X-Varnish: 844250232 12 TxHeader c Connection: close 12 ReqEnd c 844250232 1237571928.666558027 1237571929.572726011 0.000896931 nan nan 0 StatAddr - 205.178.191.132 0 852 27 60 3 0 27 25023 162245 12 StatSess c 205.178.191.132 46563 1 1 1 0 0 0 451 0 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571931 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571934 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571937 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571940 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Mar 20 18:32:16 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Mar 2009 18:32:16 -0000 Subject: [Varnish] #398: logging off phpbb always causes "Error 503 Service Unavailable" In-Reply-To: <053.fcc528fb5f49a4e239de8466a1c0a6d5@projects.linpro.no> References: <053.fcc528fb5f49a4e239de8466a1c0a6d5@projects.linpro.no> Message-ID: <062.6d2487d517a83d4196a5bb0a677df53c@projects.linpro.no> #398: logging off phpbb always causes "Error 503 Service Unavailable" -------------------------------------------+-------------------------------- Reporter: mmpower | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 2.0 Severity: normal | Resolution: Keywords: Error 503 Service Unavailable | -------------------------------------------+-------------------------------- Comment (by mmpower): oops format messed up... here is the log wikthout the -c option: {{{ 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571916 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571919 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571922 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571925 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571928 12 SessionOpen c 205.178.191.132 46563 12 ReqStart c 205.178.191.132 46563 844250232 12 RxRequest c GET 12 RxURL c /forum/login.php?logout=true&sid=890024b01e3a5656f50e926216c8afd6 12 RxProtocol c HTTP/1.1 12 RxHeader c Host: alpha.haiguinet.com 12 RxHeader c User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729) 12 RxHeader c Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 12 RxHeader c Accept-Language: en-us,en;q=0.5 12 RxHeader c Accept-Encoding: gzip,deflate 12 RxHeader c Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 12 RxHeader c Keep-Alive: 300 12 RxHeader c Connection: keep-alive 12 RxHeader c Referer: http://alpha.haiguinet.com/forum/index.php?sid=890024b01e3a5656f50e926216c8afd6 12 RxHeader c Cookie: setframeview=0; userstatusserver=http%3A//202.142.17.114%3A8080/flashIM/wdkstatus; flashservers=rtmp%3A//202.142.17.114%3A443/flashIM%2Crtmp%3A//202.142.17.124%3A443/freechat%2Chttp%3A//202.142.17.114%3A8080/flashgo%2Chttp%3A//202.142.17.124%3A808 12 VCL_call c recv 12 VCL_return c pass 12 VCL_call c pass 12 VCL_return c pass 13 BackendOpen b default 208.73.238.68 44465 211.147.252.114 80 13 TxRequest b GET 13 TxURL b /forum/login.php?logout=true&sid=890024b01e3a5656f50e926216c8afd6 13 TxProtocol b HTTP/1.1 13 TxHeader b Host: alpha.haiguinet.com 13 TxHeader b User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729) 13 TxHeader b Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 13 TxHeader b Accept-Language: en-us,en;q=0.5 13 TxHeader b Accept-Encoding: gzip,deflate 13 TxHeader b Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 13 TxHeader b Referer: http://alpha.haiguinet.com/forum/index.php?sid=890024b01e3a5656f50e926216c8afd6 13 TxHeader b Cookie: setframeview=0; userstatusserver=http%3A//202.142.17.114%3A8080/flashIM/wdkstatus; flashservers=rtmp%3A//202.142.17.114%3A443/flashIM%2Crtmp%3A//202.142.17.124%3A443/freechat%2Chttp%3A//202.142.17.114%3A8080/flashgo%2Chttp%3A//202.142.17.124%3A808 13 TxHeader b X-Forwarded-For: 205.178.191.132 13 TxHeader b X-Varnish: 844250232 13 TxHeader b X-Forwarded-for: 205.178.191.132 13 BackendClose b default 12 VCL_call c fetch 0 Debug - "VCL_error(0, (null))" 12 VCL_return c error 12 SessionClose c error returned 12 TxProtocol c HTTP/1.0 12 TxStatus c 503 12 TxResponse c Service Unavailable 12 TxHeader c Date: Fri, 20 Mar 2009 17:58:49 GMT 12 TxHeader c Server: Varnish 12 TxHeader c Retry-After: 0 12 TxHeader c Content-Type: text/html; charset=utf-8 12 TxHeader c X-Varnish: 844250232 12 TxHeader c Connection: close 12 ReqEnd c 844250232 1237571928.666558027 1237571929.572726011 0.000896931 nan nan 0 StatAddr - 205.178.191.132 0 852 27 60 3 0 27 25023 162245 12 StatSess c 205.178.191.132 46563 1 1 1 0 0 0 451 0 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571931 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571934 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571937 0 CLI - Rd ping 0 CLI - Wr 0 200 PONG 1237571940 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sat Mar 21 19:43:44 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sat, 21 Mar 2009 19:43:44 -0000 Subject: [Varnish] #437: Varnish 2.0.2 hanging with large amounts of traffic In-Reply-To: <049.251897e59bb49a5cfc6b8575603422fc@projects.linpro.no> References: <049.251897e59bb49a5cfc6b8575603422fc@projects.linpro.no> Message-ID: <058.91d809d29f233732fd4aa341ce34f9b9@projects.linpro.no> #437: Varnish 2.0.2 hanging with large amounts of traffic ----------------------+----------------------------------------------------- Reporter: ajt | Owner: perbu Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: critical | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by phk): New info: This could be the problem fixed with r3973. If you can, try applying that single-line fix to your sources and see if it helps. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sat Mar 21 19:45:30 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sat, 21 Mar 2009 19:45:30 -0000 Subject: [Varnish] #438: varnish hangs upon hot reconfiguration In-Reply-To: <053.dba0b7fe61d70346b1a6b6563506acb7@projects.linpro.no> References: <053.dba0b7fe61d70346b1a6b6563506acb7@projects.linpro.no> Message-ID: <062.d0849b3c5a494cbad4f8042d23753436@projects.linpro.no> #438: varnish hangs upon hot reconfiguration ----------------------+----------------------------------------------------- Reporter: solatis | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: trunk Severity: critical | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by phk): New info: This could possibly be the issue fixed with r3973. Please try to apply that single-line fix to your sources, and see if it helps. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Mar 22 02:43:04 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 22 Mar 2009 02:43:04 -0000 Subject: [Varnish] #474: kqueue: bug in usage of EV_SET Message-ID: <053.4475f1dd0a3aec95fd78da7e61e03e8e@projects.linpro.no> #474: kqueue: bug in usage of EV_SET ----------------------+----------------------------------------------------- Reporter: michael | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: major | Keywords: ----------------------+----------------------------------------------------- There?s a very subtle bug in http://varnish.projects.linpro.no/browser/trunk/varnish- cache/bin/varnishd/cache_waiter_kqueue.c#L162 (cache_waiter_kqueue.c:162 and :163). You use ke[j++]. However, the definition of EV_SET (see /usr/include/sys/event.h) uses this argument multiple times (at least on NetBSD) and therefore j gets incremented multiple times. Instead, you should increment j separately. This fixes using kqueue on NetBSD. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Mar 22 08:48:46 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 22 Mar 2009 08:48:46 -0000 Subject: [Varnish] #474: kqueue: bug in usage of EV_SET In-Reply-To: <053.4475f1dd0a3aec95fd78da7e61e03e8e@projects.linpro.no> References: <053.4475f1dd0a3aec95fd78da7e61e03e8e@projects.linpro.no> Message-ID: <062.5c83916103489c40c667ab5c33e8844d@projects.linpro.no> #474: kqueue: bug in usage of EV_SET ----------------------+----------------------------------------------------- Reporter: michael | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: major | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: (In [3974]) Don't trust EV_SET macro to only evaluate its arguments once, at least on NetBSD this is not the case. Fixes #474 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Mar 22 12:58:57 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 22 Mar 2009 12:58:57 -0000 Subject: [Varnish] #435: Expose -n to VCL In-Reply-To: <049.f988b0c545d2a86bc1db75f0765a1023@projects.linpro.no> References: <049.f988b0c545d2a86bc1db75f0765a1023@projects.linpro.no> Message-ID: <058.a18eecfdfda8e29e8fb9c2774b169ce1@projects.linpro.no> #435: Expose -n to VCL --------------------+------------------------------------------------------- Reporter: sky | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by sky): * status: new => closed * resolution: => fixed Comment: Added in r3949 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Mar 22 13:03:50 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 22 Mar 2009 13:03:50 -0000 Subject: [Varnish] #375: Secure communication between Client Browser and Varnish. In-Reply-To: <053.a0a53655033e615613b4b7acc1ae8533@projects.linpro.no> References: <053.a0a53655033e615613b4b7acc1ae8533@projects.linpro.no> Message-ID: <062.d85ec1e7b5ca280e78d4bf70a130c538@projects.linpro.no> #375: Secure communication between Client Browser and Varnish. -------------------------+-------------------------------------------------- Reporter: tuhintt | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Later Component: build | Version: trunk Severity: normal | Resolution: worksforme Keywords: | -------------------------+-------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => worksforme Comment: No, we do not support HTTPS at this time. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Mar 22 13:35:39 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 22 Mar 2009 13:35:39 -0000 Subject: [Varnish] #13: RFC compliance audit In-Reply-To: <049.e66c7bb40506de4c05d5f2a155d46d85@projects.linpro.no> References: <049.e66c7bb40506de4c05d5f2a155d46d85@projects.linpro.no> Message-ID: <058.efa116553499b365129c00f76a807334@projects.linpro.no> #13: RFC compliance audit ----------------------+----------------------------------------------------- Reporter: des | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * resolution: invalid => fixed Comment: (In [3976]) Continue the civilization of varnishtest: Unify the construction of the workdir name. Append uid to the name if non-zero (as in: "/tmp/__v1.488") to avoid multiple users stomping on each other. Blow away and recreate the workdir at the creation of an instance. Close and reopen the shmem for each launch, close during cleanup. Fixes #13 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Mar 22 13:36:17 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 22 Mar 2009 13:36:17 -0000 Subject: [Varnish] #316: varnishtest should mkdtemp or similar for its varnishd testing directory In-Reply-To: <052.7d2f84eda7603f58d11187dea6a0be3d@projects.linpro.no> References: <052.7d2f84eda7603f58d11187dea6a0be3d@projects.linpro.no> Message-ID: <061.77bef944567afcf607dce9561f0e373d@projects.linpro.no> #316: varnishtest should mkdtemp or similar for its varnishd testing directory -------------------------+-------------------------------------------------- Reporter: ingvar | Owner: phk Type: defect | Status: closed Priority: lowest | Milestone: Varnish 2.1 release Component: varnishtest | Version: trunk Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: fixed in 3976 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Mar 22 14:00:28 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 22 Mar 2009 14:00:28 -0000 Subject: =?utf-8?b?W1Zhcm5pc2hdICM0NzU6IHVzbGVlcCgpIGRvZXMgbm90IGhhbmRs?= =?utf-8?b?ZSBlcnJvcnMgY29ycmVjdGx5ICh2YWx1ZXMgPiAxLDAwMCwwMDAg?= =?utf-8?b?YXJlbuKAmXQgYWxsb3dlZCBvbiBOZXRCU0Qp?= Message-ID: <053.355e1e7b2cd43ffa0d272d0effcdf516@projects.linpro.no> #475: usleep() does not handle errors correctly (values > 1,000,000 aren?t allowed on NetBSD) ----------------------+----------------------------------------------------- Reporter: michael | Owner: phk Type: defect | Status: new Priority: high | Milestone: Varnish 2.1 release Component: varnishd | Version: trunk Severity: normal | Keywords: NetBSD ----------------------+----------------------------------------------------- On NetBSD, varnish was causing very high load. After a while of debugging, I found the usleep() calls to not sleep at all. This is caused by using param->wthread_purge_delay (= 1000) and multiplying it with 1000, this going beyond the limit of 1,000,000 for usleep(). On other systems, this error is ingored, on NetBSD however, usleep() will immediately return with -EINVAL. The attached patch adds a new function to libvarnish, called TIM_usleep, which handles this usleep()-error correctly and falls back to sleep(). This fixes the CPU issue with varnish on NetBSD :-). -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Mar 22 16:25:19 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 22 Mar 2009 16:25:19 -0000 Subject: [Varnish] #476: ESI code assumes no \0 Message-ID: <049.7df6f82b4c723a2b397d2d219578785e@projects.linpro.no> #476: ESI code assumes no \0 --------------------+------------------------------------------------------- Reporter: sky | Owner: sky Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------------------------------------------- This isn't true in CDATA and data:// URI fields. Correct solution is to check ew.p.st->len -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Mar 22 16:35:26 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 22 Mar 2009 16:35:26 -0000 Subject: =?utf-8?b?UmU6IFtWYXJuaXNoXSAjNDc1OiB1c2xlZXAoKSBkb2VzIG5vdCBo?= =?utf-8?b?YW5kbGUgZXJyb3JzIGNvcnJlY3RseSAodmFsdWVzID4gMSwwMDAs?= =?utf-8?b?MDAwIGFyZW7igJl0IGFsbG93ZWQgb24gTmV0QlNEKQ==?= In-Reply-To: <053.355e1e7b2cd43ffa0d272d0effcdf516@projects.linpro.no> References: <053.355e1e7b2cd43ffa0d272d0effcdf516@projects.linpro.no> Message-ID: <062.b4041014d41dcc8c26865fc648f24ec9@projects.linpro.no> #475: usleep() does not handle errors correctly (values > 1,000,000 aren?t allowed on NetBSD) ----------------------+----------------------------------------------------- Reporter: michael | Owner: phk Type: defect | Status: closed Priority: high | Milestone: Varnish 2.1 release Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: NetBSD | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: (In [3979]) Use TIM_sleep() instead of usleep() where duration might be longer than the one second Open Group allows. Fixes #475 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 23 11:13:17 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 23 Mar 2009 11:13:17 -0000 Subject: [Varnish] #477: Change defaults to respect Cache-Control: private Message-ID: <050.cb885dcd552a186f1314aa6843303453@projects.linpro.no> #477: Change defaults to respect Cache-Control: private -------------------+-------------------------------------------------------- Reporter: olau | Type: defect Status: new | Priority: normal Milestone: | Component: build Version: trunk | Severity: normal Keywords: | -------------------+-------------------------------------------------------- In some cases you'd want to bypass the cache if the web app behind is doing something based on the actual connection/request, e.g. inspecting the IP address to guestimate the country and then redirecting based on that. In this case, it makes sense to turn off any caches between the web app and the browser, but still allow the browser to cache the reply. As I read RFC2616, this is what Cache-Control: private is meant for. Thus I believe the default configuration of Varnish should take Cache- Control: private as a hint that the object is not cacheable and let it pass. As it is now, default Varnish will share the response between users which breaks the web app (this is not just theory, it actually broke mine :-). We talked about it on the mailing list here http://projects.linpro.no/pipermail/varnish-misc/2009-February/002575.html The only ill effect I can see of it is if you have a really broken backend that sends out Cache-Control: private even if it doesn't really mean it. But still defaulting to no caching is the safe choice. You can always configure Varnish to disregard the header if you know it's fine in your case. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 23 14:18:10 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 23 Mar 2009 14:18:10 -0000 Subject: [Varnish] #471: Compilation fixes for NetBSD (and probably others) In-Reply-To: <053.fa6986291a83952a25214719c7b1abe3@projects.linpro.no> References: <053.fa6986291a83952a25214719c7b1abe3@projects.linpro.no> Message-ID: <062.4f509a545d08fd7eb8db5c0f278cafca@projects.linpro.no> #471: Compilation fixes for NetBSD (and probably others) ---------------------+------------------------------------------------------ Reporter: michael | Owner: Type: defect | Status: closed Priority: normal | Milestone: After Varnish 2.1 Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | ---------------------+------------------------------------------------------ Comment (by tfheen): (In [3994]) Merge r3964: Portability fixes from pkgsrc/NetBSD Apply portability patches from pkgsrc, thanks to michael for forwarding those. Fixes #471 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 23 14:40:53 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 23 Mar 2009 14:40:53 -0000 Subject: [Varnish] #474: kqueue: bug in usage of EV_SET In-Reply-To: <053.4475f1dd0a3aec95fd78da7e61e03e8e@projects.linpro.no> References: <053.4475f1dd0a3aec95fd78da7e61e03e8e@projects.linpro.no> Message-ID: <062.1bce2f1b6a93b8a2824e76a0db169999@projects.linpro.no> #474: kqueue: bug in usage of EV_SET ----------------------+----------------------------------------------------- Reporter: michael | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: major | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Comment (by tfheen): (In [3997]) Merge r3974: Don't trust EV_SET macro to only evaluate its arguments once, at least on NetBSD this is not the case. Fixes #474 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Mar 23 14:51:26 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 23 Mar 2009 14:51:26 -0000 Subject: =?utf-8?b?UmU6IFtWYXJuaXNoXSAjNDc1OiB1c2xlZXAoKSBkb2VzIG5vdCBo?= =?utf-8?b?YW5kbGUgZXJyb3JzIGNvcnJlY3RseSAodmFsdWVzID4gMSwwMDAs?= =?utf-8?b?MDAwIGFyZW7igJl0IGFsbG93ZWQgb24gTmV0QlNEKQ==?= In-Reply-To: <053.355e1e7b2cd43ffa0d272d0effcdf516@projects.linpro.no> References: <053.355e1e7b2cd43ffa0d272d0effcdf516@projects.linpro.no> Message-ID: <062.b8699c45f3c93128f0a5b46c4c94b2ff@projects.linpro.no> #475: usleep() does not handle errors correctly (values > 1,000,000 aren?t allowed on NetBSD) ----------------------+----------------------------------------------------- Reporter: michael | Owner: phk Type: defect | Status: closed Priority: high | Milestone: Varnish 2.1 release Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: NetBSD | ----------------------+----------------------------------------------------- Comment (by tfheen): (In [3999]) Merge r3979: Use TIM_sleep() instead of usleep() Use TIM_sleep() instead of usleep() where duration might be longer than the one second Open Group allows. Fixes #475 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Mar 24 12:29:18 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 24 Mar 2009 12:29:18 -0000 Subject: [Varnish] #476: ESI code assumes no \0 In-Reply-To: <049.7df6f82b4c723a2b397d2d219578785e@projects.linpro.no> References: <049.7df6f82b4c723a2b397d2d219578785e@projects.linpro.no> Message-ID: <058.f0405471b6ff0a202395e9a761eb8d67@projects.linpro.no> #476: ESI code assumes no \0 --------------------+------------------------------------------------------- Reporter: sky | Owner: sky Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by sky): * status: new => closed * resolution: => fixed Comment: Fixed in r4002 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Mar 24 15:02:19 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 24 Mar 2009 15:02:19 -0000 Subject: [Varnish] #478: Panic: Condition(ws->f + b2 <= ws->e) not true. thread = (cache-worker)sp = 0x7efb0a086008 { Message-ID: <049.f648c173e8bd404a9c9a20699d436a12@projects.linpro.no> #478: Panic: Condition(ws->f + b2 <= ws->e) not true. thread = (cache-worker)sp = 0x7efb0a086008 { --------------------+------------------------------------------------------- Reporter: sky | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------------------------------------------- {{{ Child (21976) Panic message: Missing errorhandling code in WS_Reserve(), cache_ws.c line 159: Condition(ws->f + b2 <= ws->e) not true. thread = (cache-worker)sp = 0x7efb0a086008 { fd = 898, id = 898, xid = 19140662, client = 64.255.180.50:40205, step = STP_FETCH, handling = fetch, err_code = 200, err_reason = (null), ws = 0x7efb0a086070 { id = "sess", {s,f,r,e} = {0x7efb0a086800,,+3771,(nil),+131072}, }, worker = 0x7efc0fca8420 { }, vcl = { srcname = { "input", "Default", }, }, }, }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Mar 26 12:28:36 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 26 Mar 2009 12:28:36 -0000 Subject: [Varnish] #479: segfault with -s persistent in trunk as of r4002 Message-ID: <049.6f83aa5ef54bbfaea94f3b33540b532a@projects.linpro.no> #479: segfault with -s persistent in trunk as of r4002 --------------------+------------------------------------------------------- Reporter: sky | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------------------------------------------- After a few seconds {{{ #0 0x00007fa205a416e3 in build_trtable () from /lib/libc.so.6 #1 0x00007fa205a4bb85 in re_search_internal () from /lib/libc.so.6 #2 0x00007fa205a4ccaa in regexec@@GLIBC_2.3.4 () from /lib/libc.so.6 #3 0x0000000000431a67 in VRT_re_match ( s=0x7f79e6a659f5 "__utma=60657713.1765478813.1236680346.1238058831.1238058831.22; __utmz=60657713.1237718340.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); __gads=ID=f9bdbde7e34eb766:T=1237718351:S=ALNI_Mbon5T59uOC"..., re=0x7fa205609a80) at cache_vrt_re.c:79 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Mar 26 12:30:15 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 26 Mar 2009 12:30:15 -0000 Subject: [Varnish] #480: segfault with -s file Message-ID: <049.0acebd74ae9d0810100ecc78b413bd7e@projects.linpro.no> #480: segfault with -s file --------------------+------------------------------------------------------- Reporter: sky | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------------------------------------------- {{{ (gdb) bt #0 0x00007fbba2ecc095 in raise () from /lib/libc.so.6 #1 0x00007fbba2ecdaf0 in abort () from /lib/libc.so.6 #2 0x0000000000425c4e in pan_ic (func=0x455dde "Tcheck", file=0x455df0 "cache.h", line=700, cond=0x455de5 "(t.b) != 0", err=0, xxx=0) at cache_panic.c:317 #3 0x0000000000420819 in Tcheck (t={b = 0x0, e = 0x0}) at cache.h:700 #4 0x00000000004206ed in http_IsHdr (hh=0x7f9370cf0238, hdr=0x66cfdf "\005Date:") at cache_http.c:138 #5 0x000000000042256c in http_FilterFields (w=0x7f9578c1d420, fd=221, to=0x7f9578c1dde8, fm=0x7f9370cf00c0, how=32) at ../../include/http_headers.h:72 #6 0x0000000000428c50 in RES_BuildHttp (sp=0x7f9373f23008) at cache_response.c:105 #7 0x0000000000412572 in cnt_deliver (sp=0x7f9373f23008) at cache_center.c:167 #8 0x0000000000415d8c in CNT_Session (sp=0x7f9373f23008) at steps.h:42 #9 0x0000000000427811 in wrk_do_cnt_sess (w=0x7f9578c1d420, priv=0x7f9373f23008) at cache_pool.c:456 #10 0x00000000004270a7 in wrk_thread_real (qp=0x7fbba2b0a240, shm_workspace=32768, sess_workspace=131072) at cache_pool.c:351 #11 0x0000000000427495 in wrk_thread (priv=0x7fbba2b0a240) at cache_pool.c:387 #12 0x00007fbba369c3f7 in start_thread () from /lib/libpthread.so.0 #13 0x00007fbba2f71b3d in clone () from /lib/libc.so.6 #14 0x0000000000000000 in ?? () ( }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Mar 26 17:33:28 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 26 Mar 2009 17:33:28 -0000 Subject: [Varnish] #468: spanish accentuated domains In-Reply-To: <055.80f79ada41e35c88da910e12aeeaa9b8@projects.linpro.no> References: <055.80f79ada41e35c88da910e12aeeaa9b8@projects.linpro.no> Message-ID: <064.9fa608c556c12a3495e885e188fb3d67@projects.linpro.no> #468: spanish accentuated domains ---------------------------------------+------------------------------------ Reporter: ajlozanob | Owner: phk Type: enhancement | Status: closed Priority: normal | Milestone: After Varnish 2.1 Component: varnishd | Version: 2.0 Severity: blocker | Resolution: invalid Keywords: accetuated domain spanish | ---------------------------------------+------------------------------------ Comment (by ajlozanob): Many thanks- -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Mar 29 17:33:34 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 29 Mar 2009 17:33:34 -0000 Subject: [Varnish] #398: logging off phpbb always causes "Error 503 Service Unavailable" In-Reply-To: <053.fcc528fb5f49a4e239de8466a1c0a6d5@projects.linpro.no> References: <053.fcc528fb5f49a4e239de8466a1c0a6d5@projects.linpro.no> Message-ID: <062.a6eda87528f8e1fd722ed97c9812cd61@projects.linpro.no> #398: logging off phpbb always causes "Error 503 Service Unavailable" -------------------------------------------+-------------------------------- Reporter: mmpower | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 2.0 Severity: normal | Resolution: Keywords: Error 503 Service Unavailable | -------------------------------------------+-------------------------------- Comment (by joel): Can you paste the complete backend reply? I am having similar issues related to the amount of Set-Cookie headers in the reply (>18 gives 503 error) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Mar 29 17:47:33 2009 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 29 Mar 2009 17:47:33 -0000 Subject: [Varnish] #398: logging off phpbb always causes "Error 503 Service Unavailable" In-Reply-To: <053.fcc528fb5f49a4e239de8466a1c0a6d5@projects.linpro.no> References: <053.fcc528fb5f49a4e239de8466a1c0a6d5@projects.linpro.no> Message-ID: <062.ab782538abd17562125b2fd5f9badd9b@projects.linpro.no> #398: logging off phpbb always causes "Error 503 Service Unavailable" -------------------------------------------+-------------------------------- Reporter: mmpower | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 2.0 Severity: normal | Resolution: Keywords: Error 503 Service Unavailable | -------------------------------------------+-------------------------------- Comment (by joel): I think increasing HTTP_HDR_MAX_VAL in cache.h might help -- Ticket URL: Varnish The Varnish HTTP Accelerator