From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VQnz6-0004Xv-P3 for bitcoin-development@lists.sourceforge.net; Tue, 01 Oct 2013 00:38:40 +0000 X-ACL-Warn: Received: from new1-smtp.messagingengine.com ([66.111.4.221]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1VQnz4-00017k-V2 for bitcoin-development@lists.sourceforge.net; Tue, 01 Oct 2013 00:38:40 +0000 Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 0FCF35A6 for ; Mon, 30 Sep 2013 20:20:46 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Mon, 30 Sep 2013 20:20:46 -0400 X-Sasl-enc: NSTF8E3yHG58xfxERcSIINAMrIJc676FguM5OfwUQxUJ 1380586845 Received: from tpyo (unknown [60.234.54.74]) by mail.messagingengine.com (Postfix) with ESMTPA id E1F726801C9 for ; Mon, 30 Sep 2013 20:20:44 -0400 (EDT) From: Chris Double To: "bitcoin-development\@lists.sourceforge.net" In-Reply-To: References: User-Agent: Notmuch/0.16+49~g2f7cfcd (http://notmuchmail.org) Emacs/24.1.1 (x86_64-pc-linux-gnu) Date: Tue, 01 Oct 2013 13:20:40 +1300 Message-ID: <874n91kfjb.fsf@double.co.nz> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: messagingengine.com] 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1VQnz4-00017k-V2 Subject: Re: [Bitcoin-development] bitcoind stops responding X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Oct 2013 00:38:40 -0000 slush writes: > I observed this problem with version 0.8.2, but it is still happening with > 0.8.5. I see this as well with 0.8.2+. I don't see it on 0.8.1. I originally hit the '4 keep alive thread limit' where four clients on the same bitcoind would result in other clients not being able to connect. I resolved that and still hit the RPC hanging issue. The most problem I've had is using 'getwork' which I believe is going the wayside anyway.