On Fri, Oct 4, 2013 at 2:22 AM, Gavin Andresen wrote:
> 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
On Tue, Oct 1, 2013 at 6:58 PM, slush 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
> 1380610633.387730: POST / HTTP/1.1^M
> ThreadRPCServer method=getinfo
> CTxMemPool::accept() : accepted
> dc2941dd69b2f9fa2754f741dfba76489abef706bd237e3bd715181950723e4d (poolsz 1283)
> keypool reserve 15
> keypool return 15
> locktime : 5.996820 calltime : 0.000328 totaltime : 5.997148
>
I
On Tue, 2013-10-01 at 16:17 +0200, Jeff Garzik wrote:
> Olivier,
>
> What network activity was going on, during this test? i.e. during the
> call with 5.99 locktime, was bitcoind processing a block or sending a
> large transaction? There are plenty of valid reasons -- sadly -- that
> the locks
Olivier,
What network activity was going on, during this test? i.e. during the
call with 5.99 locktime, was bitcoind processing a block or sending a
large transaction? There are plenty of valid reasons -- sadly -- that
the locks are held for a long time, during random network events.
On Tue,
ad "RPC stops working":
* Client makes a 'getinfo' call and don't receive a response in a minute.
"What is your precise RPC usage? "
One process is asking getinfo every second as a fallback to possibly
misconfigured blocknotify. It also calls getblocktemplate every 30 second.
Second process is c
>
> Not sure yet exactly where the problem is but my current #1 suspect is:
>
> LOCK2(cs_main, pwalletMain->cs_wallet);
>
> with some kind of lock contention with the other threads.
>
I was right. It took more than 6 seconds to acquire the locks
I did modify bitcoinrpc.cpp:
namespace {
str
On Mon, 2013-09-30 at 22:44 +0200, slush wrote:
> 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 sta
On Mon, Sep 30, 2013 at 11:01 PM, Warren Togami Jr. wrote:
> 0.8.2 apparently was the first Bitcoin version to support RPC keepalive.
No, this is not correct at all. RPC keepalive was present in 0.7.0,
possibly earlier.
Come on, it took a 30 second 'git checkout' session to verify this.
> Wit
Can you please describe more than "RPC stops working"? What is your
precise RPC usage? getwork? getblocktemplate? other calls? What is
your OS?
On Mon, Sep 30, 2013 at 10:44 PM, slush wrote:
> Hi,
>
> during several weeks I'm observing more and more frequent issues with
> bitcoind. The prob
slush writes:
> I observed this problem with version 0.8.2, but it is still happening with
> 0.8.5.
I see this as well with 0.8.2+. I don't see it on 0.8.1. I originally
hit the '4 keep alive thread limit' where four clients on the same
bitcoind would result in other clients not being able to c
Oh, excuse me; it looked related to me.
It was not at all my intention to mess down the thread; on the contrary I
was trying to be of help and at the same time getting an answer.
No, I must recognize that I was not aware of sendmany. This is my first
time managing bulk transactions.
Thank you very
On Mon, Sep 30, 2013 at 3:00 PM, Fatima Castiglione Maldonado 发
wrote:
> I am new on the list. I got a similar problem.
> If I put "sendToAdress" transactions to bitcoind, it will accept between 1
> and 3 transactions per minute, depending on the underlying machine.
> If I try to send one transact
Hi,
I am new on the list. I got a similar problem.
If I put "sendToAdress" transactions to bitcoind, it will accept between 1
and 3 transactions per minute, depending on the underlying machine.
If I try to send one transaction every 20 seconds or less, bitcoind stops
responding to RPC calls.
Does
https://github.com/litecoin-project/litecoin/issues/67
0.8.2 apparently was the first Bitcoin version to support RPC keepalive.
With the 4 RPC thread limit, four keepalive connections will exhaust all
four and prevent further connections. This issue describes a workaround
where you build with mor
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
16 matches
Mail list logo
