Title: Pruned node v0.11 bad alloc, memory issues Post by: shorena on October 08, 2015, 05:54:52 AM My pruned node version 0.11 seems unable to handle the recent spam attack. Even though it could handle the last ones when it still ran 0.10.x and was not pruned.
This is the last year worth of unconfirmed transactions. As you can see from the big mountain in july it handled the previous spam attack just fine. https://i.imgur.com/6LzWE74.png Here is the same period in more detail https://i.imgur.com/O4Q4Ztu.png This is the last 24 hours https://i.imgur.com/OUR8g6N.png As you can see it crashed yesterday evening, I rebooted it before I went to bed, but it crashed again during the night. The debug.log showed an bad alloc error. This is the bitcoin.conf file (without most rpc* stuff): Code: server=1 The node is limited to 2GB of ram. Its not much and as a result the node runs sluggish from time to time, but 0.10.x in unpruned mode never crashed. Any ideas what I could try to keep it running? Title: Re: Pruned node v0.11 bad alloc, memory issues Post by: Abdussamad on October 08, 2015, 12:10:44 PM See the part about transaction flooding:
https://bitcoin.org/en/release/v0.11.0 On reddit someone set minrelaytxfee to 0.0001 (https://www.reddit.com/r/Bitcoin/comments/3nxj27/psa_full_node_operators_set_a_higher/) (double what is suggested above) and his node is using very little RAM. Title: Re: Pruned node v0.11 bad alloc, memory issues Post by: shorena on October 08, 2015, 01:29:56 PM See the part about transaction flooding: https://bitcoin.org/en/release/v0.11.0 On reddit someone set minrelaytxfee to 0.0001 (https://www.reddit.com/r/Bitcoin/comments/3nxj27/psa_full_node_operators_set_a_higher/) (double what is suggested above) and his node is using very little RAM. Thanks, I will give minrelaytxfee=0.0002 a try. Not really happy with the solution, but it seems there is nothing else I can do for now. log: Code: | transactions |memory usage Title: Re: Pruned node v0.11 bad alloc, memory issues Post by: 2112 on October 08, 2015, 06:32:31 PM Thanks, I will give minrelaytxfee=0.0002 a try. Not really happy with the solution, but it seems there is nothing else I can do for now. Can't you enable swap? With swap enabled Bitcoin Core doesn't seem to have any significant problem dealing with the current flood. The overall server response time does increase but nothing crashes, although I haven't tried running 32-bit versions on the mainnet in a while.Title: Re: Pruned node v0.11 bad alloc, memory issues Post by: shorena on October 08, 2015, 07:34:50 PM Thanks, I will give minrelaytxfee=0.0002 a try. Not really happy with the solution, but it seems there is nothing else I can do for now. Can't you enable swap? With swap enabled Bitcoin Core doesn't seem to have any significant problem dealing with the current flood. The overall server response time does increase but nothing crashes, although I haven't tried running 32-bit versions on the mainnet in a while.Nope, no swap or hoster gets mad. Its pretty stable now, but the attack stopped anyway[1]. I guess I will have to wait for the next wave. Fow now the log script I wrote should give me more insight if it should crash again. I should probably considering an upgrade, disk space is low anyway. [1] http://statoshi.info/dashboard/db/transactions Title: Re: Pruned node v0.11 bad alloc, memory issues Post by: Abdussamad on October 09, 2015, 05:35:01 AM shorena 0.0002 is a bit too high. I suggest starting with 0.00005 like the article on bitcoin.org suggests and then increasing it from there if it's not enough.
Title: Re: Pruned node v0.11 bad alloc, memory issues Post by: shorena on October 09, 2015, 11:21:51 AM shorena 0.0002 is a bit too high. I suggest starting with 0.00005 like the article on bitcoin.org suggests and then increasing it from there if it's not enough. Should be a typo, I aimed for twice the default setting thus it should be 0.000 02. I will double check my config, thanks. Edit: Yes its a typo. |