From varnish-bugs at projects.linpro.no Mon Jul 2 16:30:28 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 02 Jul 2007 16:30:28 -0000 Subject: [Varnish] #118: mac os x: Running varnishd results in dyld: lazy symbol binding failed: Symbol not found: _strndup In-Reply-To: <048.530f5b1a0bfe608510abfaf2329f9707@projects.linpro.no> References: <048.530f5b1a0bfe608510abfaf2329f9707@projects.linpro.no> Message-ID: <057.239c4ae23df150fe9d9bd4a835b695c4@projects.linpro.no> #118: mac os x: Running varnishd results in dyld: lazy symbol binding failed: Symbol not found: _strndup --------------------+------------------------------------------------------- Reporter: oh | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+------------------------------------------------------- Comment (by andre): I also see this problem with current trunk. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jul 3 13:49:52 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 03 Jul 2007 13:49:52 -0000 Subject: [Varnish] #124: listen on sevral adresses/ports. Message-ID: <051.3ea90417742d054a0d42354ce360528c@projects.linpro.no> #124: listen on sevral adresses/ports. -------------------------+-------------------------------------------------- Reporter: tiamo | Owner: phk Type: enhancement | Status: new Priority: normal | Milestone: Varnish 1.1 Component: varnishd | Version: trunk Severity: normal | Keywords: -------------------------+-------------------------------------------------- Maybe by allowing mutiple -a x.x.x.x:y -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jul 3 13:55:44 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 03 Jul 2007 13:55:44 -0000 Subject: [Varnish] #125: exit, quit command in telnet interface. Message-ID: <051.9cead11972a3e74d718d7abf4c4982f0@projects.linpro.no> #125: exit, quit command in telnet interface. -------------------------+-------------------------------------------------- Reporter: tiamo | Owner: phk Type: enhancement | Status: new Priority: lowest | Milestone: Component: varnishd | Version: trunk Severity: trivial | Keywords: -------------------------+-------------------------------------------------- exit, quit command in telnet interface. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jul 4 09:18:52 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 04 Jul 2007 09:18:52 -0000 Subject: [Varnish] #117: Mac OS X: Running varnishd results in Assert error in mgt_CallCc(), mgt_vcc.c line 222 In-Reply-To: <048.aa559d5bd4edda6a4d13bc3d880bcb57@projects.linpro.no> References: <048.aa559d5bd4edda6a4d13bc3d880bcb57@projects.linpro.no> Message-ID: <057.a6a557c4ca92ccd40aedb622fcf96dc9@projects.linpro.no> #117: Mac OS X: Running varnishd results in Assert error in mgt_CallCc(), mgt_vcc.c line 222 ----------------------+----------------------------------------------------- Reporter: oh | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.0.4 Severity: normal | Resolution: Keywords: mac os x | ----------------------+----------------------------------------------------- Comment (by optilude): I have found that if I use any regular expression match at all in a custom VCL file, I still get this error (using Varnish 1.0.4, installed via MacPorts). Using the ~ operator on an ACL is okay, but e.g. using req.url ~ "\.(css|js)" in an if() statement causes Varnish to fail with the dlclose() assertion error. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jul 5 14:47:32 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 05 Jul 2007 14:47:32 -0000 Subject: [Varnish] #126: SYN_ErrorPage() TTL should be a parameter Message-ID: <049.99e0c0710678c3cd2a4bfd5ebedf9e31@projects.linpro.no> #126: SYN_ErrorPage() TTL should be a parameter ----------------------+----------------------------------------------------- Reporter: des | Owner: des Type: defect | Status: new Priority: normal | Milestone: Varnish 1.1 Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------------------------------- The TTL used for synthetic error pages should be tunable, rather than fixed at 30 seconds. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jul 5 14:48:56 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 05 Jul 2007 14:48:56 -0000 Subject: [Varnish] #127: LRU hysteresis should be a parameter Message-ID: <049.21c16a6a8b75ac119971b918086204a9@projects.linpro.no> #127: LRU hysteresis should be a parameter ----------------------+----------------------------------------------------- Reporter: des | Owner: des Type: defect | Status: new Priority: normal | Milestone: Varnish 1.1 Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------------------------------- The hysteresis used to reduce contention on the LRU queue mutex should be configurable, rather than hardcoded to two seconds. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Jul 15 15:29:47 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Jul 2007 15:29:47 -0000 Subject: [Varnish] #62: Typo in vcl.7 In-Reply-To: <048.4f98998cd6e90aa597ec2899411f077b@projects.linpro.no> References: <048.4f98998cd6e90aa597ec2899411f077b@projects.linpro.no> Message-ID: <057.41dfa611bac5b08bdd646df2355d8658@projects.linpro.no> #62: Typo in vcl.7 ---------------------------+------------------------------------------------ Reporter: cs | Owner: des Type: documentation | Status: closed Priority: lowest | Milestone: Component: documentation | Version: Severity: trivial | Resolution: fixed Keywords: | ---------------------------+------------------------------------------------ Changes (by phk): * status: new => closed * resolution: => fixed Comment: has been fixed underway. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Jul 15 15:32:59 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Jul 2007 15:32:59 -0000 Subject: [Varnish] #81: Via: Varnish header duplicate In-Reply-To: <060.11cf44baffd081d5889215a80a0fe10d@projects.linpro.no> References: <060.11cf44baffd081d5889215a80a0fe10d@projects.linpro.no> Message-ID: <069.e80567a29047e7ce24b88a474482709e@projects.linpro.no> #81: Via: Varnish header duplicate ----------------------------+----------------------------------------------- Reporter: xing_litespeed | Owner: phk Type: enhancement | Status: closed Priority: low | Milestone: Varnish 2.0 Component: varnishd | Version: 1.0 Severity: minor | Resolution: wontfix Keywords: via header | ----------------------------+----------------------------------------------- Changes (by phk): * status: new => closed * resolution: => wontfix Comment: RFC2616 says: {{{ 14.45 Via The Via general-header field MUST be used by gateways and proxies to indicate the intermediate protocols and recipients between the user agent and the server on requests, and between the origin server and the client on responses. It is analogous to the "Received" field of RFC 822 [9] and is intended to be used for tracking message forwards, avoiding request loops, and identifying the protocol capabilities of all senders along the request/response chain. }}} I read this as all boxes must include a Via header, even if it is identical to an already present via header. As it is, with the editing functions now available in VCL, the administrator can override. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Jul 15 15:40:08 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Jul 2007 15:40:08 -0000 Subject: [Varnish] #77: URL rewrite In-Reply-To: <050.43421cdca728d1b8e5023f154c4a71d2@projects.linpro.no> References: <050.43421cdca728d1b8e5023f154c4a71d2@projects.linpro.no> Message-ID: <059.c95b2dbe78c9841dce0e18a8417991d1@projects.linpro.no> #77: URL rewrite -------------------------+-------------------------------------------------- Reporter: lapo | Owner: phk Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishd | Version: Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: Rewriting of URLs and all other HTTP headers are now possible in -trunk -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Jul 15 15:40:58 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Jul 2007 15:40:58 -0000 Subject: [Varnish] #72: glibc detected double free or corruption In-Reply-To: <050.99b54de45298c88fdb44dc3c9afbd9b1@projects.linpro.no> References: <050.99b54de45298c88fdb44dc3c9afbd9b1@projects.linpro.no> Message-ID: <059.727afd91ce6eb7a7195338f5bc6ee1ad@projects.linpro.no> #72: glibc detected double free or corruption ----------------------+----------------------------------------------------- Reporter: mark | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 1.0 Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: I belive this on has been resolved. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Jul 15 15:41:55 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Jul 2007 15:41:55 -0000 Subject: [Varnish] #53: Missing errorhandling code in PassSession() In-Reply-To: <053.c778e80fd7d60e1fa360cb68e35dc838@projects.linpro.no> References: <053.c778e80fd7d60e1fa360cb68e35dc838@projects.linpro.no> Message-ID: <062.bf3d422963b49f73dfef35eb0ae56ed1@projects.linpro.no> #53: Missing errorhandling code in PassSession() ----------------------+----------------------------------------------------- Reporter: erlends | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: assigned => closed * resolution: => fixed Comment: The entire pass code path has been rewritten. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Jul 15 15:42:35 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Jul 2007 15:42:35 -0000 Subject: [Varnish] #52: varnishlog prints garbage In-Reply-To: <053.1afa9488f704899199effccc384c0f0d@projects.linpro.no> References: <053.1afa9488f704899199effccc384c0f0d@projects.linpro.no> Message-ID: <062.801b98d5818048ab8824c379a8b47abc@projects.linpro.no> #52: varnishlog prints garbage ------------------------+--------------------------------------------------- Reporter: erlends | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: varnishlog | Version: Severity: normal | Resolution: worksforme Keywords: | ------------------------+--------------------------------------------------- Changes (by phk): * status: assigned => closed * resolution: => worksforme -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Jul 15 15:46:42 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Jul 2007 15:46:42 -0000 Subject: [Varnish] #87: Main varnish child gets spawned again and again In-Reply-To: <051.0c2ba1bd1bbc5da901324515b9b0fe0a@projects.linpro.no> References: <051.0c2ba1bd1bbc5da901324515b9b0fe0a@projects.linpro.no> Message-ID: <060.daca909c9fefb4a6cd14eb8b0fb751c5@projects.linpro.no> #87: Main varnish child gets spawned again and again ----------------------+----------------------------------------------------- Reporter: Thias | 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: Close this ticket, it is an instance of the "Varnish doesn't do LRU yet" class. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Jul 15 15:47:12 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Jul 2007 15:47:12 -0000 Subject: [Varnish] #67: All varnish-child-processes dies In-Reply-To: <048.1597aa14c065539691716c6539c5e792@projects.linpro.no> References: <048.1597aa14c065539691716c6539c5e792@projects.linpro.no> Message-ID: <057.5b1486dbf44e1902f721ad7c7e34456e@projects.linpro.no> #67: All varnish-child-processes dies ----------------------+----------------------------------------------------- Reporter: ay | Owner: phk Type: defect | Status: closed Priority: high | Milestone: Component: varnishd | Version: Severity: major | Resolution: duplicate Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => duplicate Comment: Close this ticket, it is an instance of "Varnish doesn't do LRU yet". -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Jul 15 15:47:45 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Jul 2007 15:47:45 -0000 Subject: [Varnish] #70: Assert error in smf_alloc(), storage_file.c line 624 In-Reply-To: <050.ec23f08e6bdd2f180fd241fbc2e73fb6@projects.linpro.no> References: <050.ec23f08e6bdd2f180fd241fbc2e73fb6@projects.linpro.no> Message-ID: <059.f62d65afb54b52755836279b83e41d12@projects.linpro.no> #70: Assert error in smf_alloc(), storage_file.c line 624 ----------------------+----------------------------------------------------- Reporter: mark | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 1.0 Severity: normal | Resolution: duplicate Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => duplicate Comment: Close this ticket, it is an instance of "Varnish doesn't do LRU yet". -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Jul 15 15:49:12 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Jul 2007 15:49:12 -0000 Subject: [Varnish] #9: VCL compiler error checking In-Reply-To: <049.8a212460c972839adb80a3491f7ddc0e@projects.linpro.no> References: <049.8a212460c972839adb80a3491f7ddc0e@projects.linpro.no> Message-ID: <058.efb8da5c4cbaf6b9a9ee8c1f2597eeb4@projects.linpro.no> #9: VCL compiler error checking ----------------------+----------------------------------------------------- Reporter: des | Owner: phk Type: defect | Status: closed Priority: low | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: I think this has been resolved. We now try to load the compiled object into the manager process, and if that fails, we fail the CLI operation, but do not panic anything. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Jul 15 15:50:58 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Jul 2007 15:50:58 -0000 Subject: [Varnish] #66: Varnish stops feeding pages In-Reply-To: <053.d18c837c1685237d45cc0e23831fabde@projects.linpro.no> References: <053.d18c837c1685237d45cc0e23831fabde@projects.linpro.no> Message-ID: <062.5d42709cfacaf9f973279f84e702b174@projects.linpro.no> #66: Varnish stops feeding pages ----------------------+----------------------------------------------------- Reporter: jakobbg | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 1.0 Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: I belive this bug has been fixed in the meantime. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Jul 15 15:53:09 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Jul 2007 15:53:09 -0000 Subject: [Varnish] #21: Thoughts about the prefetcher In-Reply-To: <049.5c25cff3778121775a115b7841aa7037@projects.linpro.no> References: <049.5c25cff3778121775a115b7841aa7037@projects.linpro.no> Message-ID: <058.0121dc5c1d2431d08206326491fc8b35@projects.linpro.no> #21: Thoughts about the prefetcher -------------------------+-------------------------------------------------- Reporter: phk | Owner: phk Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: Moved to architects notes on wiki -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Jul 15 16:06:22 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Jul 2007 16:06:22 -0000 Subject: [Varnish] #124: listen on sevral adresses/ports. In-Reply-To: <051.3ea90417742d054a0d42354ce360528c@projects.linpro.no> References: <051.3ea90417742d054a0d42354ce360528c@projects.linpro.no> Message-ID: <060.c575960ad5a2c904f32998232a29b995@projects.linpro.no> #124: listen on sevral adresses/ports. -------------------------+-------------------------------------------------- Reporter: tiamo | Owner: phk Type: enhancement | Status: closed Priority: normal | Milestone: Varnish 1.1 Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: This has been implemented long time ago: Specify a whitespace separated list of addresses to -a, for instance: {{{ -a ":8080 :8081 :8082" }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sun Jul 15 17:18:33 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sun, 15 Jul 2007 17:18:33 -0000 Subject: [Varnish] #80: Missing errorhandler causes crash In-Reply-To: <052.c892a82f842be9d649d4537b9564f61d@projects.linpro.no> References: <052.c892a82f842be9d649d4537b9564f61d@projects.linpro.no> Message-ID: <061.4335ddfb453ddb8affcd5df5a98daf30@projects.linpro.no> #80: Missing errorhandler causes crash --------------------+------------------------------------------------------- Reporter: xingli | Owner: des Type: defect | Status: closed Priority: high | Milestone: Varnish 1.1 Component: build | Version: 1.0 Severity: major | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by phk): * status: assigned => closed * resolution: => fixed Comment: lets close this one. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jul 18 15:22:50 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 18 Jul 2007 15:22:50 -0000 Subject: [Varnish] #128: varnishd dies on the VCL keyword `error` Message-ID: <051.99c325a0ed65a278cd7574b696bd1506@projects.linpro.no> #128: varnishd dies on the VCL keyword `error` ----------------------+----------------------------------------------------- Reporter: bartc | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 1.1 Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------------------------------- When a `error ` command in VCL gets called, my varnishd (from a recent svn checkout) dies. This is the VCL file I'm using: {{{ backend default { set backend.host = "127.0.0.1"; set backend.port = "9678"; } sub vcl_recv { if (req.url == "/foo") { error 404 "No"; } lookup; } }}} A normal GET which doesn't trigger the `error` works ok: {{{ $ nc localhost 6081 GET /test HTTP/1.1 Host: localhost HTTP/1.1 200 OK Server: Zope/(Zope 2.9.7-final, python 2.4.4, linux2) ZServer/1.1 Plone/2.5.3-final Date: Wed, 18 Jul 2007 15:05:42 GMT Content-Type: text/html; charset=iso-8859-15 Content-Length: 10 X-Varnish: 1993066366 Age: 0 Via: 1.1 varnish Looks ok. }}} When calling the error statement in the VCL however, Varnish doesn't respond: {{{ $ nc localhost 6081 GET /foo HTTP/1.1 Host: localhost }}} No response is returned. The varnishd started with -d -d has the following in its output: {{{ >> Child said (2, 18788): <hd[HTTP_HDR_STATUS].b) != 0) not true. errno = 0 (Success) >> Cache child died pid=18788 status=0x6 Clean child Child cleaned status CLI 200 33 Child in state died, (restarting) }}} And it stays in that state; subsequent `status` commands show the status as `Child in state died, (restarting)` as well. I'm using an svn checkout from source:branches/1.1#1714 (revision 1714) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jul 20 07:05:36 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Jul 2007 07:05:36 -0000 Subject: [Varnish] #129: POST request with pipe method not fully working in trunk Message-ID: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> #129: POST request with pipe method not fully working in trunk ----------------------+----------------------------------------------------- Reporter: jpulz | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: trunk Severity: major | Keywords: ----------------------+----------------------------------------------------- While experimenting with varnish to speed up our CMS, i found the following regression: POST requests with pipe method are not working with the most browsers when using trunk (rev. 1723), while they do work with all tested browsers in 1.0.4 I see the following behavior: We have a search page which uses POST request to get the search string submitted, i enter a string to search for and hit the search button. Now the browser is stuck and the only thing i see with varnishlog is `SessionOpen c ` Now i can either wait for a session timeout or hit the browsers "stop" button. In both cases i see the client request, the backend connect and so on in varnishlog after the session is closed. I also see that the clients POST request is given as POST request to the backend and that the pipe method is being used, but everything happens only after the client session is closed. Tested browsers and results for trunk (rev. 1723): ||working|| Opera 9.x on FreeBSD, Linux and Windows (all native) ||not working|| IE7 on Windows XP ||not working|| Firefox 2.x on FreeBSD, Linux and Windows (all native) ||not working|| Seamonkey 1.x on FreeBSD and Windows (all native) So far, all browser/OS combinations are working correctly when using 1.0.4 varnishd is running on "FreeBSD 6.2-STABLE Tue Jul 17 15:17:11 CEST 2007 amd64" -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jul 20 08:43:52 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Jul 2007 08:43:52 -0000 Subject: [Varnish] #129: POST request with pipe method not fully working in trunk In-Reply-To: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> References: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> Message-ID: <060.4b9042897da2f84ba1a9a5704b468c10@projects.linpro.no> #129: POST request with pipe method not fully working in trunk ----------------------+----------------------------------------------------- Reporter: jpulz | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * owner: phk => des * priority: high => normal * status: new => assigned * severity: major => normal Comment: Just for kicks, try the patch from r1728 and let me know if it makes any difference. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jul 20 09:47:22 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Jul 2007 09:47:22 -0000 Subject: [Varnish] #129: POST request with pipe method not fully working in trunk In-Reply-To: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> References: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> Message-ID: <060.701fa0a6676701ae8bd09c4827258009@projects.linpro.no> #129: POST request with pipe method not fully working in trunk ----------------------+----------------------------------------------------- Reporter: jpulz | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by jpulz): Just updated to r1731 and it works a bit better. The problem now is, that sporadically some requests stuck as reported before, but i can't tell under which sepcific conditions these "hangs" occur. Anyway, thanks for your fast repsonse. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jul 20 09:59:12 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Jul 2007 09:59:12 -0000 Subject: [Varnish] #129: POST request with pipe method not fully working in trunk In-Reply-To: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> References: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> Message-ID: <060.cfd3f521198cc1c570caa2f3a4be50b8@projects.linpro.no> #129: POST request with pipe method not fully working in trunk ----------------------+----------------------------------------------------- Reporter: jpulz | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by des): Strange. I didn't actually expect that patch to help, it just adds some additional error checking to the pipe code. I'll have to try to reproduce this... -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jul 20 14:21:40 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Jul 2007 14:21:40 -0000 Subject: [Varnish] #92: VCL-check for purge prevents caching In-Reply-To: <052.46106d4c127fd8b9ab2bb7951181de8c@projects.linpro.no> References: <052.46106d4c127fd8b9ab2bb7951181de8c@projects.linpro.no> Message-ID: <061.e042da973b56c7c6b5a54ac1c09868bd@projects.linpro.no> #92: VCL-check for purge prevents caching ----------------------+----------------------------------------------------- Reporter: stonor | Owner: phk Type: defect | Status: reopened Priority: normal | Milestone: Component: varnishd | Version: Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by denis at zeno.org): * status: closed => reopened * resolution: fixed => Comment: Hi Iam using if(req.http.Cache-Control == "no-cache") { set obj.ttl = 0s; error 200 "Hey, we got a purge"; } in my VLC code and my varnish childs get killed by sig 11 and sig 6 when I hit the reload button. Iam using CURRENT r1714 on 64bit FreeBSD 6.2 RELEASE p5 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jul 20 16:00:12 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Jul 2007 16:00:12 -0000 Subject: [Varnish] #130: Build of varnishhist, varnishstat and varnishtop fails with gcc 4.2.0 Message-ID: <048.0b7218bd5544d76ac492b1489dbef2b3@projects.linpro.no> #130: Build of varnishhist, varnishstat and varnishtop fails with gcc 4.2.0 --------------------+------------------------------------------------------- Reporter: cs | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------------------------------------------- Build of varnishhist, varnishstat and varnishtop fails. This happens with non-vendor gcc 4.2.0 on FreeBSD 6.2/i386 building Varnish 1.1 (but trunk should be affected as well). IIRC, C99 compilers require stdbool.h for the definition of 'false' {{{ [...] Making all in varnishhist /openpkg-dev/bin/cc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I /openpkg-dev/include -I/openpkg-dev/include/ncurses -DOPKG_PIDFILE =\"/openpkg-dev/var/varnish/varnishd.pid\" -include config.h -O2 -pipe -MT varnishhist-varnishhist.o -MD -MP -MF .deps/varnishhist-varnishhist.Tpo -c -o varnishhist-varnishhist.o `test -f 'varnishhist.c' || echo './'`varnishhist.c varnishhist.c: In function 'do_curses': varnishhist.c:250: error: 'false' undeclared (first use in this function) varnishhist.c:250: error: (Each undeclared identifier is reported only once varnishhist.c:250: error: for each function it appears in.) make[3]: *** [varnishhist-varnishhist.o] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 error: Bad exit status from /u/cs/tmp/openpkg/rpm-tmp.2106 (%build) }}} Following diff fixes the problem {{{ Index: bin/varnishhist/varnishhist.c --- bin/varnishhist/varnishhist.c.orig 2007-07-20 13:30:04 +0200 +++ bin/varnishhist/varnishhist.c 2007-07-20 16:16:26 +0200 @@ -41,6 +41,7 @@ #include #include #include +#include #include #include Index: bin/varnishstat/varnishstat.c --- bin/varnishstat/varnishstat.c 2007-07-20 13:30:04 +0200 +++ bin/varnishstat/varnishstat.c 2007-07-20 16:18:58 +0200 @@ -40,6 +40,7 @@ #include #include #include +#include #include #include #include Index: bin/varnishtop/varnishtop.c --- bin/varnishtop/varnishtop.c.orig 2007-07-20 13:30:04 +0200 +++ bin/varnishtop/varnishtop.c 2007-07-20 16:22:58 +0200 @@ -39,6 +39,7 @@ #include #include #include +#include #include #include #include }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jul 20 16:07:47 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 20 Jul 2007 16:07:47 -0000 Subject: [Varnish] #131: Target 'install-data-local' in Makefile.in doesn't honor any $DESTDIR Message-ID: <048.e4e080fad0630b81653aec71dbdba105@projects.linpro.no> #131: Target 'install-data-local' in Makefile.in doesn't honor any $DESTDIR --------------------+------------------------------------------------------- Reporter: cs | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------------------------------------------- Target 'install-data-local' in Makefile.in doesn't honor any $DESTDIR. Following patch fixes the problem for Varnish 1.1 (sorry for 'Version: trunk' in the ticket properties, '1.1' is still missing there) {{{ Index: Makefile --- Makefile.in.orig 2007-07-20 13:33:02 +0200 +++ Makefile.in 2007-07-20 16:37:05 +0200 @@ -670,7 +670,7 @@ install-data-local: - $(install_sh) -d -m 0755 $(localstatedir)/varnish + $(install_sh) -d -m 0755 $(DESTDIR)$(localstatedir)/varnish # Tell versions [3.59,3.63) of GNU make to not export all variables. # Otherwise a system limit (for SysV at least) may be exceeded. .NOEXPORT: }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jul 24 02:33:50 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 24 Jul 2007 02:33:50 -0000 Subject: [Varnish] #118: mac os x: Running varnishd results in dyld: lazy symbol binding failed: Symbol not found: _strndup In-Reply-To: <048.530f5b1a0bfe608510abfaf2329f9707@projects.linpro.no> References: <048.530f5b1a0bfe608510abfaf2329f9707@projects.linpro.no> Message-ID: <057.6a9b4fe95b150b4bd1d4c234b546f644@projects.linpro.no> #118: mac os x: Running varnishd results in dyld: lazy symbol binding failed: Symbol not found: _strndup --------------------+------------------------------------------------------- Reporter: oh | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+------------------------------------------------------- Comment (by vamoose): I'm also seeing this problem installed on mac osx tiger w/ Varnish 1.1. Does anyone have a solution for this? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jul 24 08:00:39 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 24 Jul 2007 08:00:39 -0000 Subject: [Varnish] #118: mac os x: Running varnishd results in dyld: lazy symbol binding failed: Symbol not found: _strndup In-Reply-To: <048.530f5b1a0bfe608510abfaf2329f9707@projects.linpro.no> References: <048.530f5b1a0bfe608510abfaf2329f9707@projects.linpro.no> Message-ID: <057.16bf5b9982b09475dd25bf98fd5846b1@projects.linpro.no> #118: mac os x: Running varnishd results in dyld: lazy symbol binding failed: Symbol not found: _strndup --------------------+------------------------------------------------------- Reporter: oh | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+------------------------------------------------------- Changes (by des): * status: new => assigned Comment: Weird - this did not show up in my testing last week. I'll investigate. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jul 24 08:11:18 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 24 Jul 2007 08:11:18 -0000 Subject: [Varnish] #118: mac os x: Running varnishd results in dyld: lazy symbol binding failed: Symbol not found: _strndup In-Reply-To: <048.530f5b1a0bfe608510abfaf2329f9707@projects.linpro.no> References: <048.530f5b1a0bfe608510abfaf2329f9707@projects.linpro.no> Message-ID: <057.644786ad5c05427498a1e7564a97260f@projects.linpro.no> #118: mac os x: Running varnishd results in dyld: lazy symbol binding failed: Symbol not found: _strndup --------------------+------------------------------------------------------- Reporter: oh | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+------------------------------------------------------- Comment (by des): This seems to be a bug in libtool, which ignores -export-dynamic. Run autogen.sh and configure, then look for the following line in {{{$(top_srcdir)/libtool}}}: {{{ export_dynamic_flag_spec="" }}} This should be changed to {{{ export_dynamic_flag_spec="-flat_namespace" }}} Then run {{{make clean; make install}}} and it should work. I'm not sure how to fix this properly. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jul 24 14:00:11 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 24 Jul 2007 14:00:11 -0000 Subject: [Varnish] #128: varnishd dies on the VCL keyword `error` In-Reply-To: <051.99c325a0ed65a278cd7574b696bd1506@projects.linpro.no> References: <051.99c325a0ed65a278cd7574b696bd1506@projects.linpro.no> Message-ID: <060.43398aaa2a28dab69bd6f20b254e3562@projects.linpro.no> #128: varnishd dies on the VCL keyword `error` ----------------------+----------------------------------------------------- Reporter: bartc | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * owner: phk => des * status: new => assigned Comment: r1751 should fix the assertion failure in [source:trunk], and will be merged to [source:branches/1.1] soon. The inability to restart the child was fixed in r1710 / r1711 in [source:trunk], and r1723 in [source:branches/1.1]. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jul 24 14:03:09 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 24 Jul 2007 14:03:09 -0000 Subject: [Varnish] #131: Target 'install-data-local' in Makefile.in doesn't honor any $DESTDIR In-Reply-To: <048.e4e080fad0630b81653aec71dbdba105@projects.linpro.no> References: <048.e4e080fad0630b81653aec71dbdba105@projects.linpro.no> Message-ID: <057.c53dcfc20f4b171acd2a7caff019e124@projects.linpro.no> #131: Target 'install-data-local' in Makefile.in doesn't honor any $DESTDIR --------------------+------------------------------------------------------- Reporter: cs | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Varnish 1.1.1 Component: build | Version: 1.1 Severity: normal | Resolution: Keywords: | --------------------+------------------------------------------------------- Changes (by des): * status: new => assigned * version: trunk => 1.1 * milestone: => Varnish 1.1.1 Comment: Fixed in [source:trunk] in r1572, to be merged soon. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jul 24 14:03:24 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 24 Jul 2007 14:03:24 -0000 Subject: [Varnish] #128: varnishd dies on the VCL keyword `error` In-Reply-To: <051.99c325a0ed65a278cd7574b696bd1506@projects.linpro.no> References: <051.99c325a0ed65a278cd7574b696bd1506@projects.linpro.no> Message-ID: <060.248f84b736549f6a01d7e98bf32d79d6@projects.linpro.no> #128: varnishd dies on the VCL keyword `error` ----------------------+----------------------------------------------------- Reporter: bartc | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * version: trunk => 1.1 * milestone: => Varnish 1.1.1 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jul 24 14:09:58 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 24 Jul 2007 14:09:58 -0000 Subject: [Varnish] #130: Build of varnishhist, varnishstat and varnishtop fails with gcc 4.2.0 In-Reply-To: <048.0b7218bd5544d76ac492b1489dbef2b3@projects.linpro.no> References: <048.0b7218bd5544d76ac492b1489dbef2b3@projects.linpro.no> Message-ID: <057.b7508c686c789c9203021fa650d655ac@projects.linpro.no> #130: Build of varnishhist, varnishstat and varnishtop fails with gcc 4.2.0 -------------------------+-------------------------------------------------- Reporter: cs | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Varnish 1.1.1 Component: varnishhist | Version: 1.1 Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by des): * status: new => assigned * version: trunk => 1.1 * component: build => varnishhist * milestone: => Varnish 1.1.1 Comment: I'm unable to reproduce this with gcc 4.2.0 on FreeBSD 7. In any case, the correct fix is to spell {{{false}}} as {{{FALSE}}}, which is defined somewhere within the bowels of {{{}}}. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jul 24 14:11:37 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 24 Jul 2007 14:11:37 -0000 Subject: [Varnish] #130: Build of varnishhist, varnishstat and varnishtop fails with gcc 4.2.0 In-Reply-To: <048.0b7218bd5544d76ac492b1489dbef2b3@projects.linpro.no> References: <048.0b7218bd5544d76ac492b1489dbef2b3@projects.linpro.no> Message-ID: <057.d67fc27c5274a4668d1815b65da3ea37@projects.linpro.no> #130: Build of varnishhist, varnishstat and varnishtop fails with gcc 4.2.0 -------------------------+-------------------------------------------------- Reporter: cs | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Varnish 1.1.1 Component: varnishhist | Version: 1.1 Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by des): Fixed in [source:trunk] in r1573, to be merged soon. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jul 24 14:30:08 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 24 Jul 2007 14:30:08 -0000 Subject: [Varnish] #92: VCL-check for purge prevents caching In-Reply-To: <052.46106d4c127fd8b9ab2bb7951181de8c@projects.linpro.no> References: <052.46106d4c127fd8b9ab2bb7951181de8c@projects.linpro.no> Message-ID: <061.6d16d71dc3cb3b288de666037df1c670@projects.linpro.no> #92: VCL-check for purge prevents caching ----------------------+----------------------------------------------------- Reporter: stonor | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: reopened => closed * resolution: => fixed Comment: Superseded by #128. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jul 24 14:45:15 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 24 Jul 2007 14:45:15 -0000 Subject: [Varnish] #129: POST request with pipe method not fully working in trunk In-Reply-To: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> References: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> Message-ID: <060.d0fd0166ededaf623f74b1e613c1bf51@projects.linpro.no> #129: POST request with pipe method not fully working in trunk ----------------------+----------------------------------------------------- Reporter: jpulz | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by des): From your description, it sounds like the backend does not start processing the request because it's waiting for additional data, which implies that Varnish does not forward the entire unmodified request to the backend. Is there any way you could capture this with {{{tcpdump}}}? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jul 26 07:17:10 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 26 Jul 2007 07:17:10 -0000 Subject: [Varnish] #132: Varnish 1.1 dies with assert error in SES_Delete Message-ID: <052.fe8cf8964ac10aa02472af7aa5d37aad@projects.linpro.no> #132: Varnish 1.1 dies with assert error in SES_Delete ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: blocker | Keywords: core dump SES_Delete ----------------------+----------------------------------------------------- I am running Varnish 1.1 in FreeBSD 6.2-RELEASE/amd64, on Intel hardware. Running at peak load with a disk cache bigger than available RAM, varnishd dies: Child said (2, 77109): <obj) == 0) not true. errno = 0 (Unknown error: 0) >> Cache child died pid=77109 status=0x6 I have 4.5 GB RAM. At the time varnishd died, it had around 9 GB data in the cache according to varnishstat/sm_balloc and 550000 objects. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jul 26 07:24:23 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 26 Jul 2007 07:24:23 -0000 Subject: [Varnish] #133: Varnish 1.1 dies with assert error in HSH_Ref Message-ID: <052.662bbe1925b2879c08b0767221ea6600@projects.linpro.no> #133: Varnish 1.1 dies with assert error in HSH_Ref ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: 1.1 Severity: blocker | Keywords: core dump HSH_Ref ----------------------+----------------------------------------------------- I am running Varnish 1.1 in FreeBSD 6.2-RELEASE/amd64, on Intel hardware. Running at peak load, varnishd dies with this error: Child said (2, 7371): <> Child said (2, 7371): <magic == 0x1b96615d) not true. errno = 0 (Unknown error: 0) This happened around 40 minutes after the crash mentioned in ticket 132, meaning that the cache hit ratio was low (I have a large dataset, this is for finn.no). I don't know if it is related or not. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jul 26 07:30:53 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 26 Jul 2007 07:30:53 -0000 Subject: [Varnish] #132: Varnish 1.1 dies with assert error in SES_Delete In-Reply-To: <052.fe8cf8964ac10aa02472af7aa5d37aad@projects.linpro.no> References: <052.fe8cf8964ac10aa02472af7aa5d37aad@projects.linpro.no> Message-ID: <061.d09f21be8cba80033bf054d7ae8dc05f@projects.linpro.no> #132: Varnish 1.1 dies with assert error in SES_Delete ----------------------------------+----------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: blocker | Resolution: Keywords: core dump SES_Delete | ----------------------------------+----------------------------------------- Comment (by anders): I meant to say "running with a cache bigger than available RAM". -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jul 26 08:09:55 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 26 Jul 2007 08:09:55 -0000 Subject: [Varnish] #133: Varnish 1.1 dies with assert error in HSH_Ref In-Reply-To: <052.662bbe1925b2879c08b0767221ea6600@projects.linpro.no> References: <052.662bbe1925b2879c08b0767221ea6600@projects.linpro.no> Message-ID: <061.84cea8335d25f7e79e311c064c4a0eb2@projects.linpro.no> #133: Varnish 1.1 dies with assert error in HSH_Ref -------------------------------+-------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: core dump HSH_Ref | -------------------------------+-------------------------------------------- Changes (by des): * severity: blocker => major * milestone: => Varnish 1.1.1 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jul 26 08:10:13 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 26 Jul 2007 08:10:13 -0000 Subject: [Varnish] #132: Varnish 1.1 dies with assert error in SES_Delete In-Reply-To: <052.fe8cf8964ac10aa02472af7aa5d37aad@projects.linpro.no> References: <052.fe8cf8964ac10aa02472af7aa5d37aad@projects.linpro.no> Message-ID: <061.2863e84e0523ec8176cbfcd315709cf5@projects.linpro.no> #132: Varnish 1.1 dies with assert error in SES_Delete ----------------------------------+----------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: core dump SES_Delete | ----------------------------------+----------------------------------------- Changes (by des): * priority: normal => high * version: trunk => 1.1 * severity: blocker => major * milestone: => Varnish 1.1.1 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jul 26 08:26:14 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 26 Jul 2007 08:26:14 -0000 Subject: [Varnish] #133: Varnish 1.1 dies with assert error in HSH_Ref In-Reply-To: <052.662bbe1925b2879c08b0767221ea6600@projects.linpro.no> References: <052.662bbe1925b2879c08b0767221ea6600@projects.linpro.no> Message-ID: <061.3b877c10f80c3fbb99eaffbad8153b92@projects.linpro.no> #133: Varnish 1.1 dies with assert error in HSH_Ref -------------------------------+-------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: core dump HSH_Ref | -------------------------------+-------------------------------------------- Comment (by anders): Hmm. I was using some patches from trunk, for bugs that are fixed there, and this ticket might be self-induced! Sorry. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jul 26 08:33:22 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 26 Jul 2007 08:33:22 -0000 Subject: [Varnish] #134: Varnishd dies on assert error in mgt_cli_callback when using varnishadm Message-ID: <052.8408d298c2a752aff22f14c2875325b3@projects.linpro.no> #134: Varnishd dies on assert error in mgt_cli_callback when using varnishadm ----------------------+----------------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.1 Severity: normal | Keywords: varnishd varnishadm core dump ----------------------+----------------------------------------------------- I am using Varnish 1.1 in FreeBSD 6.2-RELEASE/amd64, now from ports, with des updates from july 25 (Varnish 1.1 + vendor fixes). I am running varnishd with -T localhost:8080. Also, my kernel has IPV6 support removed. Localhost in /etc/hosts has only an IPv4 address, 127.0.0.1. When running varnishadm, it fails: varnishadm -T localhost:8080 help Command failed with error code 101 And varnishd + management process dies: CLI Assert error in mgt_cli_callback(), mgt_cli.c line 324: Condition(i <= cp->nbuf) not true. errno = 0 (Unknown error: 0) Abort trap (core dumped) Using IP address does not help: varnishadm -T 127.0.0.1:8080 help Using other commands, like vcl.list fails with the same assert error. -- Ticket URL: Varnish The Varnish HTTP Accelerator From phk at phk.freebsd.dk Thu Jul 26 08:37:02 2007 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Thu, 26 Jul 2007 08:37:02 +0000 Subject: [Varnish] #133: Varnish 1.1 dies with assert error in HSH_Ref In-Reply-To: Your message of "Thu, 26 Jul 2007 07:24:23 GMT." <052.662bbe1925b2879c08b0767221ea6600@projects.linpro.no> Message-ID: <35338.1185439022@critter.freebsd.dk> In message <052.662bbe1925b2879c08b0767221ea6600 at projects.linpro.no>, "Varnish" writes: >#133: Varnish 1.1 dies with assert error in HSH_Ref > Child said (2, 7371): < getnameinfo = 5 ai_family not supported > >> > Child said (2, 7371): < Condition((oh)->magic == 0x1b96615d) not true. > errno = 0 (Unknown error: 0) Varnish is not resistant against running out of malloc space and far too many places still have asserts instead of proper handling of this. This obviously needs to be fixed over time. But I still quite can't make sense out of this, because I conclude that you are running on a 64 bit system and so you shouldn't really run out of memory this early. Can I get you to double check the per process limits limits(1)/ulimit(1) are on your machine? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk at FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From varnish-bugs at projects.linpro.no Thu Jul 26 12:54:57 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 26 Jul 2007 12:54:57 -0000 Subject: [Varnish] #133: Varnish 1.1 dies with assert error in HSH_Ref In-Reply-To: <052.662bbe1925b2879c08b0767221ea6600@projects.linpro.no> References: <052.662bbe1925b2879c08b0767221ea6600@projects.linpro.no> Message-ID: <061.765b3497bab232d4a0f763871ba99390@projects.linpro.no> #133: Varnish 1.1 dies with assert error in HSH_Ref -------------------------------+-------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: core dump HSH_Ref | -------------------------------+-------------------------------------------- Comment (by anders): Please close this ticket. My fault. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jul 26 13:19:55 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 26 Jul 2007 13:19:55 -0000 Subject: [Varnish] #128: varnishd dies on the VCL keyword `error` In-Reply-To: <051.99c325a0ed65a278cd7574b696bd1506@projects.linpro.no> References: <051.99c325a0ed65a278cd7574b696bd1506@projects.linpro.no> Message-ID: <060.193ae63b1d989d5f239939c60f736e6a@projects.linpro.no> #128: varnishd dies on the VCL keyword `error` ----------------------+----------------------------------------------------- Reporter: bartc | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by bartc): I tried [source:trunk#1775 current trunk] and `error` works fine with that version. Thanks! -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jul 26 13:37:15 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 26 Jul 2007 13:37:15 -0000 Subject: [Varnish] #133: Varnish 1.1 dies with assert error in HSH_Ref In-Reply-To: <052.662bbe1925b2879c08b0767221ea6600@projects.linpro.no> References: <052.662bbe1925b2879c08b0767221ea6600@projects.linpro.no> Message-ID: <061.eb527d7b34568ea104631d5c7d407048@projects.linpro.no> #133: Varnish 1.1 dies with assert error in HSH_Ref -------------------------------+-------------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: closed Priority: high | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: major | Resolution: fixed Keywords: core dump HSH_Ref | -------------------------------+-------------------------------------------- Changes (by des): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jul 26 13:37:33 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 26 Jul 2007 13:37:33 -0000 Subject: [Varnish] #128: varnishd dies on the VCL keyword `error` In-Reply-To: <051.99c325a0ed65a278cd7574b696bd1506@projects.linpro.no> References: <051.99c325a0ed65a278cd7574b696bd1506@projects.linpro.no> Message-ID: <060.459b5d3cae9a20089de40498154d3ad9@projects.linpro.no> #128: varnishd dies on the VCL keyword `error` ----------------------+----------------------------------------------------- Reporter: bartc | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: assigned => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jul 31 12:34:37 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 31 Jul 2007 12:34:37 -0000 Subject: [Varnish] #132: Varnish 1.1 dies with assert error in SES_Delete In-Reply-To: <052.fe8cf8964ac10aa02472af7aa5d37aad@projects.linpro.no> References: <052.fe8cf8964ac10aa02472af7aa5d37aad@projects.linpro.no> Message-ID: <061.c005047c6158f79d53b3766db7d09376@projects.linpro.no> #132: Varnish 1.1 dies with assert error in SES_Delete ----------------------------------+----------------------------------------- Reporter: anders | Owner: phk Type: defect | Status: new Priority: high | Milestone: Varnish 1.1.1 Component: varnishd | Version: 1.1 Severity: major | Resolution: Keywords: core dump SES_Delete | ----------------------------------+----------------------------------------- Comment (by anders): phk asked me to provide /proc//map, after Varnish has been running for a while. This did not work well: cat /proc/52264/map cat: /proc/52264/map: File too large root at cache10:~# less /proc/53881/map >varnishd.map root at cache10:~# more varnishd.map read error Using http://people.freebsd.org/~wkoszek/vmshow.c I could get some information about the memory usage. After allocating 3872804864 bytes (varnishstat sm_balloc), I get the attached output (vmshow.txt) from vmshow. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jul 31 14:33:33 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 31 Jul 2007 14:33:33 -0000 Subject: [Varnish] #129: POST request with pipe method not fully working in trunk In-Reply-To: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> References: <051.3a33da6325e7182a168a5815ae0bbf95@projects.linpro.no> Message-ID: <060.c23050e4670169bd754cd05f3b226511@projects.linpro.no> #129: POST request with pipe method not fully working in trunk ----------------------+----------------------------------------------------- Reporter: jpulz | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by teddy): I am also experiencing this problem in both 1.1 and latest trunk (r1792) and there is no difference in the behavior from the versions. I had the same problems a few months ago, and then i think it was the sendfile issue. As last time, I suppose this is a problem occurring depending on what kernel one are running, and mine is 2.6.17. Even though it might be affecting only a few kernels, isn't this pretty critical? No POST in pipe, no POST in pass... If jpulz doesnt reply with a tcpdump capture of this by tomorrow, I will try to get you one. -- Ticket URL: Varnish The Varnish HTTP Accelerator