Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.181 as permitted sender)
	client-ip=209.85.215.181; envelope-from=gavinandresen@gmail.com;
	helo=mail-ea0-f181.google.com; 
MIME-Version: 1.0
In-Reply-To: <CAJna-Hj1c0k3Gb7rEMBeU9nQsFophU2CYzGUOEo3JxieOYA5dA@mail.gmail.com>
References: <CAJna-Hi+eyRnZUtHpfvod_uRCmjPOL5HS3ZZpr54yzbKRRT9-w@mail.gmail.com>
	<CAJHLa0MHSjZ_mwsCKa=rd1_39H0yq9j2jVwr0qWFTxTtrWXPCQ@mail.gmail.com>
	<CAJna-Hj1c0k3Gb7rEMBeU9nQsFophU2CYzGUOEo3JxieOYA5dA@mail.gmail.com>
Date: Fri, 4 Oct 2013 16:22:34 +1000
Message-ID: <CABsx9T2OvOs9ijj8kk4ZdBT5u-2Bb3rYG0AZtk3FFDWi+H_oHw@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: slush <slush@centrum.cz>
Content-Type: multipart/alternative; boundary=089e01681ba408a8d604e7e45449
Cc: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] bitcoind stops responding
Precedence: list

--089e01681ba408a8d604e7e45449
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Oct 1, 2013 at 6:58 PM, slush <slush@centrum.cz> wrote:

> One process is asking getinfo every second as a fallback to possibly
> misconfigured blocknotify. It also calls getblocktemplate every 30 second.
>

getinfo does a bunch of stuff; with 0.9 you will be able to use
getbestblockhash instead.



> Second process is calling getinfo once a minute to check if bitcoind is
> working. If it don't receive a response in a minute, it kills bitcoind and
> starts it again.
>

If you just want to see if bitcoind is responding to RPC requests, then
'help getinfo' would do the trick without acquiring any locks.

RE: running into the maximum-of-4-keepalive-requests : simple workaround is
to run with -rpcthreads=11 (or however many keepalive connections you need
to support).  I agree that the rpc code should be smarter; making the last
rpc thread ignore keepalive and always disconnecting should be a fairly
simple patch, and "patches welcome."

-- 
--
Gavin Andresen

--089e01681ba408a8d604e7e45449
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
On Tue, Oct 1, 2013 at 6:58 PM, slush <span dir=3D"ltr">&lt;<a href=3D"mail=
to:slush@centrum.cz" target=3D"_blank">slush@centrum.cz</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">One process is asking getinfo every second as a fallback t=
o possibly misconfigured blocknotify. It also calls getblocktemplate every =
30 second.<br></div></blockquote><div><br></div><div>getinfo does a bunch o=
f stuff; with 0.9 you will be able to use getbestblockhash instead.</div>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr=
">

<div class=3D"gmail_extra">Second process is calling getinfo once a minute =
to check if bitcoind is working. If it don&#39;t receive a response in a mi=
nute, it kills bitcoind and starts it again.</div></div></blockquote><div>
<br></div><div>If you just want to see if bitcoind is responding to RPC req=
uests, then &#39;help getinfo&#39; would do the trick without acquiring any=
 locks.</div><div><br></div><div>RE: running into the maximum-of-4-keepaliv=
e-requests : simple workaround is to run with -rpcthreads=3D11 (or however =
many keepalive connections you need to support). =A0I agree that the rpc co=
de should be smarter; making the last rpc thread ignore keepalive and alway=
s disconnecting should be a fairly simple patch, and &quot;patches welcome.=
&quot;</div>
<div><br></div></div>-- <br>--<br>Gavin Andresen<br>
</div></div>

--089e01681ba408a8d604e7e45449--