1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <luke@dashjr.org>) id 1R1v1a-0001Nu-MR
for bitcoin-development@lists.sourceforge.net;
Fri, 09 Sep 2011 06:57:18 +0000
X-ACL-Warn:
Received: from zinan.dashjr.org ([173.242.112.54])
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1R1v1Z-0004Bw-UB for bitcoin-development@lists.sourceforge.net;
Fri, 09 Sep 2011 06:57:18 +0000
Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net
[184.4.160.40]) (Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id 5B587204026
for <bitcoin-development@lists.sourceforge.net>;
Fri, 9 Sep 2011 06:57:12 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Fri, 9 Sep 2011 02:57:03 -0400
User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.5; x86_64; ; )
X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583
X-PGP-Key-ID: 665FC11DD53E9583
X-PGP-Keyserver: x-hkp://subkeys.pgp.net
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <201109090257.06644.luke@dashjr.org>
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1R1v1Z-0004Bw-UB
Subject: [Bitcoin-development] 0.3.23+patches bug: JSON-RPC leaves sockets
around when not connected
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: Fri, 09 Sep 2011 06:57:18 -0000
On Eligius, I have two bitcoinds running on the same system:
- a hub node, which is dedicated to relaying network activity between the
hundreds of nodes Eligius peers with
- a work node, which is dedicated to managing mining, and only ever connects
to the hub node
Lately, the hub node has been dying (yet to determine cause; I haven't changed
anything recently), leaving the work node with no connections. The work node,
of course, starts responding to getworks with "not connected" messages.
Strangely enough, the sockets used for these are never cleaned up properly,
and eventually overflow the system's socket limits.
I am using a very heavily patched 0.3.23, so this bug could be related to one
of those patches (perhaps the threaded JSON-RPC?), but I felt like I should
mention it somewhere else just in case before 0.4 final got released. I have
not tried to reproduce it on an unpatched bitcoind yet, and am extremely busy
lately so I might not get a chance before you guys finish 0.4.
|
