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 <wtogami@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>;
	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: <CAJna-Hi+eyRnZUtHpfvod_uRCmjPOL5HS3ZZpr54yzbKRRT9-w@mail.gmail.com>
References: <CAJna-Hi+eyRnZUtHpfvod_uRCmjPOL5HS3ZZpr54yzbKRRT9-w@mail.gmail.com>
Date: Mon, 30 Sep 2013 11:01:36 -1000
Message-ID: <CAEz79PrGKH27GkDkM2whAdOYYj6-hc954Z=9v1GanBRQA3chvA@mail.gmail.com>
From: "Warren Togami Jr." <wtogami@gmail.com>
To: slush <slush@centrum.cz>
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"
	<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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=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 <slush@centrum.cz> 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

<div dir=3D"ltr"><a href=3D"https://github.com/litecoin-project/litecoin/is=
sues/67">https://github.com/litecoin-project/litecoin/issues/67</a><br><div=
>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.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon,=
 Sep 30, 2013 at 10:44 AM, slush <span dir=3D"ltr">&lt;<a href=3D"mailto:sl=
ush@centrum.cz" target=3D"_blank">slush@centrum.cz</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">Hi,<div><br></div><div>during several weeks I&#39;m observ=
ing more and more frequent issues with bitcoind. The problem is that bitcoi=
nd stops responding to RPC calls, but there&#39;s no other suspicious activ=
ity in bitcoind log, CPU usage is low, disk I/O is standard etc.</div>


<div><br></div><div>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&#39;t a problem of o=
ne specific node. Is there anybody else who&#39;s observing similar problem=
?=C2=A0</div>


<div><br></div><div>Thanks,</div><div>slush</div></div>
<br>-----------------------------------------------------------------------=
-------<br>
October Webinars: Code for Performance<br>
Free Intel webinars can help you accelerate application performance.<br>
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most fr=
om<br>
the latest Intel processors and coprocessors. See abstracts and register &g=
t;<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D60134791&amp;iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D60134791&amp;iu=3D/4140/ostg.clktrk</a><br>___________________=
____________________________<br>

Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br></div>

--001a113415e448c9b404e7a024b4--