From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: [Bitcoin-development] 0.3.23+patches bug: JSON-RPC leaves sockets around when not connected
Date: Fri, 9 Sep 2011 02:57:03 -0400 [thread overview]
Message-ID: <201109090257.06644.luke@dashjr.org> (raw)
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.
next reply other threads:[~2011-09-09 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 6:57 Luke-Jr [this message]
2011-09-09 20:00 ` John Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201109090257.06644.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox