Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <pieter.wuille@gmail.com>)
	id 1UFCv4-00049A-VJ; Tue, 12 Mar 2013 00:18:19 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.210.170 as permitted sender)
	client-ip=209.85.210.170; envelope-from=pieter.wuille@gmail.com;
	helo=mail-ia0-f170.google.com; 
Received: from mail-ia0-f170.google.com ([209.85.210.170])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1UFCv1-0005sU-Pu; Tue, 12 Mar 2013 00:18:18 +0000
Received: by mail-ia0-f170.google.com with SMTP id h8so4351331iaa.29
	for <multiple recipients>; Mon, 11 Mar 2013 17:18:10 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.186.134 with SMTP id fk6mr9812575igc.9.1363047490292;
	Mon, 11 Mar 2013 17:18:10 -0700 (PDT)
Received: by 10.50.171.8 with HTTP; Mon, 11 Mar 2013 17:18:10 -0700 (PDT)
Date: Tue, 12 Mar 2013 01:18:10 +0100
Message-ID: <CAPg+sBip_4Jtxhq+rm-na2=RSJ_PuoZt+akGgJyo0b_Bwbr1Dw@mail.gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>, 
	bitcoin-security@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=14dae9340f2d789ce004d7af39b7
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-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
	(pieter.wuille[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: 1UFCv1-0005sU-Pu
Subject: [Bitcoin-development] Warning: many 0.7 nodes break on large number
	of tx/block; fork risk
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: Tue, 12 Mar 2013 00:18:19 -0000

--14dae9340f2d789ce004d7af39b7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello everyone,

=CD've just seen many reports of 0.7 nodes getting stuck around block 22543=
0,
due to running out of lock entries in the BDB database. 0.8 nodes do not
seem to have a problem.

In any case, if you do not have this block:

  2013-03-12 00:00:10 SetBestChain: new
best=3D000000000000015aab28064a4c521d6a5325ff6e251e8ca2edfdfe6cb5bf832c
 height=3D225439  work=3D853779625563004076992  tx=3D14269257  date=3D2013-=
03-11
23:49:08

you're likely stuck. Check debug.log and db.log (look for 'Lock table is
out of available lock entries').

If this is a widespread problem, it is an emergency. We risk having
(several) forked chains with smaller blocks, which are accepted by 0.7
nodes. Can people contact pool operators to see which fork they are on?
Blockexplorer and blockchain.info seem to be stuck as well.

Immediate solution is upgrading to 0.8, or manually setting the number of
lock objects higher in your database. I'll follow up with more concrete
instructions.

If you're unsure, please stop processing transactions.

--=20
Pieter

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

<div dir=3D"ltr">Hello everyone,<div><br></div><div style>=CD&#39;ve just s=
een many reports of 0.7 nodes getting stuck around block 225430, due to run=
ning out of lock entries in the BDB database. 0.8 nodes do not seem to have=
 a problem.</div>
<div style><br></div><div style>In any case, if you do not have this block:=
</div><div style><br></div><div style><div>=A0 2013-03-12 00:00:10 SetBestC=
hain: new best=3D000000000000015aab28064a4c521d6a5325ff6e251e8ca2edfdfe6cb5=
bf832c =A0height=3D225439 =A0work=3D853779625563004076992 =A0tx=3D14269257 =
=A0date=3D2013-03-11 23:49:08</div>
<div style><br></div><div style>you&#39;re likely stuck. Check debug.log an=
d db.log (look for &#39;Lock table is out of available lock entries&#39;).<=
/div><div style><br></div><div style>If this is a widespread problem, it is=
 an emergency. We risk having (several) forked chains with smaller blocks, =
which are accepted by 0.7 nodes. Can people contact pool operators to see w=
hich fork they are on? Blockexplorer and <a href=3D"http://blockchain.info"=
>blockchain.info</a> seem to be stuck as well.</div>
<div style><br></div><div style>Immediate solution is upgrading to 0.8, or =
manually setting the number of lock objects higher in your database. I&#39;=
ll follow up with more concrete instructions.</div><div style><br></div>
<div style>If you&#39;re unsure, please stop processing transactions.</div>=
<div style><br></div><div style>--=A0</div><div style>Pieter</div></div></d=
iv>

--14dae9340f2d789ce004d7af39b7--