BitcoinUnlimited: Node crashed with segfault in bitcoin-httpworker
Hello,
I switched one of my nodes from Classic to BitcoinUnlimited about a week ago, and today it crashed with this in dmesg:
[2474116.108519] bitcoin-httpwor[28515]: segfault at 30 ip 00007fc49ff3c452 sp 00007fc49c48c628 error 4 in
libstdc++.so.6.0.21[7fc49fe99000+16b000]
The only thing which is maybe uncommon about this server, is it only has intel atom cpu with 2GB of ram and it sets this when bitcoind starts:
export MALLOC_ARENA_MAX=1
As I’ve read this may help when low on ram, but that was the same with Classic have not changed anything.
And there is a python script which scrapes rpc info into collectd every 30 seconds (I guess this may call the http worker…), but the same script was running with Classic for some months without any problem.
BitcoinUnlimited was built from source, with the bu0.12.1c release. Distro is Slackware64-14.2.
there was nothing in debug.log, last entry is just a timestamp without log message:
2016-09-22 14:07:40 connect() to 91.234.48.232:8333 failed after select(): Connection refused (111)
2016-09-22 14:08:07 connect() to 91.234.48.232:8333 failed after select(): Connection refused (111)
2016-09-22 14:08:20
Let me know if I can provide any other info.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 45 (23 by maintainers)
@sickpig I am also positive that it is fixed now, it is now 15 days and it still runs fine. So thanks for fixing and I click the close button here now 😃