Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <marek@palatinus.cz>) id 1VQkLX-0004Z6-A1
	for bitcoin-development@lists.sourceforge.net;
	Mon, 30 Sep 2013 20:45:35 +0000
X-ACL-Warn: 
Received: from mail-vc0-f182.google.com ([209.85.220.182])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1VQkLV-0006ZI-Gt
	for bitcoin-development@lists.sourceforge.net;
	Mon, 30 Sep 2013 20:45:35 +0000
Received: by mail-vc0-f182.google.com with SMTP id hf12so4169716vcb.41
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 30 Sep 2013 13:45:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:sender:from:date:message-id:subject
	:to:content-type;
	bh=214Z+rAbs2vTZ2v9uIloCezcUwaY42hVJ4/MPPud44E=;
	b=DBdnCJ3Xcq3sAE4UDp7gjDpeTk7ZuZ6ZmwZep1bljeJBpZFHQxN4H8cXmWKI6zpS2T
	gCdt3g2BGHU6I115uthXQKOFbYgtj1h8EsCg/rb5TZ9uWVnK9HYF5FN9ncNx3QD07cM6
	qlxQoGpY/n31SLizxvIxV/xzrFdkOp3gSa+xvnYcjNclHpMU4hSBdfppmkyYVaDBL0LO
	JEvXGn0BLrza2TuNYr2gBvWIt7Bz3JWX+CfecM4rVOZ+fEjWVT/z1YbDirZjKW5SEzAo
	pfTn+96VS39BHWmjRthICXszQMBTVr6Y36pYlORLF6RCvNV3MNdY4noRKFS4TK2Ru6HE
	jBcg==
X-Gm-Message-State: ALoCoQlLgxhmK0NDoWJCfiOzLyTA6Srh2vHDFdsrD3YqX8cxJSiTgBPYpo3k629+8dyg0uggCO6T
X-Received: by 10.220.46.72 with SMTP id i8mr24664026vcf.10.1380573927945;
	Mon, 30 Sep 2013 13:45:27 -0700 (PDT)
MIME-Version: 1.0
Sender: marek@palatinus.cz
Received: by 10.58.235.136 with HTTP; Mon, 30 Sep 2013 13:44:57 -0700 (PDT)
From: slush <slush@centrum.cz>
Date: Mon, 30 Sep 2013 22:44:57 +0200
X-Google-Sender-Auth: iOPyrbc9Rvs1smJi39WrC3HSb0c
Message-ID: <CAJna-Hi+eyRnZUtHpfvod_uRCmjPOL5HS3ZZpr54yzbKRRT9-w@mail.gmail.com>
To: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11c2c6748fcc9d04e79fead9
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(slush[at]centrum.cz)
	1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1VQkLV-0006ZI-Gt
Subject: [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 20:45:35 -0000

--001a11c2c6748fcc9d04e79fead9
Content-Type: text/plain; charset=ISO-8859-1

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

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

<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=
?=A0</div>

<div><br></div><div>Thanks,</div><div>slush</div></div>

--001a11c2c6748fcc9d04e79fead9--