Every other P2Pool user, including myself, is using it fine-- so the issue is likely specific to your configation.
What OS? Where did you get your bitcoin Core? How do you know it has crashed? Why do you believe it is RPC related?
Can you share your config file (without passwords, of course)?
Topic: RPC Bitcoin Core activate ... and it crash ! (Read 589 times)
Hello,
Since 0.9.1 ... developers have changed the way that RPC commands are executed in Bitcoin Core.
Since 0.9.1 ... when i use server=1 ... Bitcoin Core crash randomly when P2Pool node try to use it.
When i user server=0 (P2Pool always activated but it can't connect) ... Bitcoin Core don't crash.
Since the BIP66 is enforced, i can't have a reliable Bitcoin Core RPC activated + P2Pool stable ... because, when Bitcoin Core crash (shutdown without any message error box, no line in DEBUG.LOG too ...) and P2Pool stay active ... Bitcoin Core refuse to restart (except when i shutdown the P2Pool).
Problem is, as it, located of the entrance of the RPC feature of the Bitcoin Core.
I have test a long time, the :
- 0.9.2
- 0.9.4
- 0.9.5
- 0.10 RC
- 0.10 Final
- 0.10.2
- 0.11 RC2 and RC3 (because BIP66 urge merged is request)
1= Can developers try to "block RPC at start-up" of Bitcoin Core ?
2= Or, since 0.9.1 ... developpers have implemented an DDOS feature that it shutdown Bitcoin Core when RPC entrance is flooded by request (P2Pool request every 0,5s when Bitcoin Core have crashed).
Thanks.
Since 0.9.1 ... developers have changed the way that RPC commands are executed in Bitcoin Core.
Since 0.9.1 ... when i use server=1 ... Bitcoin Core crash randomly when P2Pool node try to use it.
When i user server=0 (P2Pool always activated but it can't connect) ... Bitcoin Core don't crash.
Since the BIP66 is enforced, i can't have a reliable Bitcoin Core RPC activated + P2Pool stable ... because, when Bitcoin Core crash (shutdown without any message error box, no line in DEBUG.LOG too ...) and P2Pool stay active ... Bitcoin Core refuse to restart (except when i shutdown the P2Pool).
Problem is, as it, located of the entrance of the RPC feature of the Bitcoin Core.
I have test a long time, the :
- 0.9.2
- 0.9.4
- 0.9.5
- 0.10 RC
- 0.10 Final
- 0.10.2
- 0.11 RC2 and RC3 (because BIP66 urge merged is request)
1= Can developers try to "block RPC at start-up" of Bitcoin Core ?
2= Or, since 0.9.1 ... developpers have implemented an DDOS feature that it shutdown Bitcoin Core when RPC entrance is flooded by request (P2Pool request every 0,5s when Bitcoin Core have crashed).
Thanks.
Jump to: