From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VQkbA-0005Tu-67 for bitcoin-development@lists.sourceforge.net; Mon, 30 Sep 2013 21:01:44 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.53 as permitted sender) client-ip=209.85.215.53; envelope-from=wtogami@gmail.com; helo=mail-la0-f53.google.com; Received: from mail-la0-f53.google.com ([209.85.215.53]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VQkb9-0000lS-4y for bitcoin-development@lists.sourceforge.net; Mon, 30 Sep 2013 21:01:44 +0000 Received: by mail-la0-f53.google.com with SMTP id el20so5054382lab.12 for ; Mon, 30 Sep 2013 14:01:36 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.98.66 with SMTP id eg2mr3903864lbb.36.1380574896374; Mon, 30 Sep 2013 14:01:36 -0700 (PDT) Received: by 10.112.48.11 with HTTP; Mon, 30 Sep 2013 14:01:36 -0700 (PDT) In-Reply-To: References: Date: Mon, 30 Sep 2013 11:01:36 -1000 Message-ID: From: "Warren Togami Jr." To: slush Content-Type: multipart/alternative; boundary=001a113415e448c9b404e7a024b4 X-Spam-Score: -0.6 (/) 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: doubleclick.net] -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (wtogami[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 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: 1VQkb9-0000lS-4y Cc: "bitcoin-development@lists.sourceforge.net" 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: Mon, 30 Sep 2013 21:01:44 -0000 --001a113415e448c9b404e7a024b4 Content-Type: text/plain; charset=UTF-8 https://github.com/litecoin-project/litecoin/issues/67 0.8.2 apparently was the first Bitcoin version to support RPC keepalive. With the 4 RPC thread limit, four keepalive connections will exhaust all four and prevent further connections. This issue describes a workaround where you build with more RPC threads. On Mon, Sep 30, 2013 at 10:44 AM, slush wrote: > Hi, > > during several weeks I'm observing more and more frequent issues with > bitcoind. The problem is that bitcoind stops responding to RPC calls, but > there's no other suspicious activity in bitcoind log, CPU usage is low, > disk I/O is standard etc. > > I observed this problem with version 0.8.2, but it is still happening with > 0.8.5. Originally this happen just one or twice per day. Today my > monitoring scripts restarted bitcoind more than 30x, which sounds alarming. > This happen on various backends, so it isn't a problem of one specific > node. Is there anybody else who's observing similar problem? > > Thanks, > slush > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > --001a113415e448c9b404e7a024b4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
https://github.com/litecoin-project/litecoin/issues/67
0.8.2 apparently was the first Bitcoin version to support RPC keepalive. = =C2=A0With the 4 RPC thread limit, four keepalive connections will exhaust = all four and prevent further connections. =C2=A0This issue describes a work= around where you build with more RPC threads.


On Mon,= Sep 30, 2013 at 10:44 AM, slush <slush@centrum.cz> wrote:
Hi,

during several weeks I'm observ= ing more and more frequent issues with bitcoind. The problem is that bitcoi= nd stops responding to RPC calls, but there's no other suspicious activ= ity in bitcoind log, CPU usage is low, disk I/O is standard etc.

I observed this problem with version 0.8.2, but it is s= till happening with 0.8.5. Originally this happen just one or twice per day= . Today my monitoring scripts restarted bitcoind more than 30x, which sound= s alarming. This happen on various backends, so it isn't a problem of o= ne specific node. Is there anybody else who's observing similar problem= ?=C2=A0

Thanks,
slush

-----------------------------------------------------------------------= -------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most fr= om
the latest Intel processors and coprocessors. See abstracts and register &g= t;
http://pubads.g.doubleclick.net/gam= pad/clk?id=3D60134791&iu=3D/4140/ostg.clktrk
___________________= ____________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment


--001a113415e448c9b404e7a024b4--