Some issues with my node...

[unamis76]

I've set up a node recently (and have been improving it gradually, from time to time). But in the last few weeks, the node has been crashing on a 1 week interval, more or less...

I've been seeing debug logs for the last two or three crashes and I haven't been seeing anything unusual. I'm running the node on a VM with 4GB RAM + 4GB vSWAP. I've tried raising/changing swap size, but it seems it's impossible with the host I'm using. I thought this would be enough to run a node, but apparently it is not, or the problem isn't RAM/SWAP, or I'm missing something.

I've been seeing a temporary cover up solution to this, but I've been unsuccessful thus far trying to find something that monitors if the node is running or not and restarts it with the correct parameters...

Here's a bit of the last crash debug:

Code:

2015-09-10 15:04:01 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-09-10 15:04:47 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-09-10 15:04:53 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-09-10 15:04:57 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=230000, us=*****************, peerid=13394
2015-09-10 15:04:58 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-09-10 15:05:07 UpdateTip: new best=000000000000000004467163bbb85f7a043f7ec3ea641c429efb6668c569574d  height=373885  log2_work=83.327898  tx=83074047  date=2015-09-10 15:03:44 progress=0.999999  cache=0.5MiB(0tx)
2015-09-10 15:05:12 ERROR: AcceptToMemoryPool: nonstandard transaction: dust
2015-09-10 15:05:15 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=373884, us=*************, peerid=13395
2015-09-10 15:05:42 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=*************, peerid=13396
2015-09-10 15:06:02 ping timeout: 1200.013952s
2015-09-10 15:07:01 socket send error Connection timed out (110)
2015-09-10 15:07:18 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=230000, us=***************, peerid=13397
2015-09-10 15:07:29 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=230000, us=***************, peerid=13398
2015-09-10 15:07:33 receive version message: /Satoshi:0.9.3/: version 70002, blocks=373885, us=*******************, peerid=13399

Any clues? Anything bad on the Debug.log? I can provide more of the file if needed.

[1715327589]

1715327589

[1715327589]

1715327589

[1715327589]

1715327589

[1715327589]

1715327589

[1715327589]

1715327589

[achow101]

Can you post more of the log? The little bit you gave doesn't help us at all.

[miguelmorales85]

I used to have the same issue, once every week the node failed.

too bad Im already reindexing..

[unamis76]

Can you post more of the log? The little bit you gave doesn't help us at all.

It's a bit big, so I'm having issues posting it here. Here's a direct link. Do you want me to post a hash of the file and a virus scan?

EDIT: went ahead and did it

[achow101]

Can you post more of the log? The little bit you gave doesn't help us at all.

It's a bit big, so I'm having issues posting it here. Here's a direct link. Do you want me to post a hash of the file and a virus scan?

EDIT: went ahead and did it

That is a large log file.

There doesn't seem to be anything wrong with it. The only thing I can think of right now is that there are too many transactions which is causing the mempool to grow too big. Maybe try to change the settings to limit how large the mempool can get.

Otherwise, the only other solution I can think of is to see if reinstalling and resyncing will help.

[unamis76]

Can you post more of the log? The little bit you gave doesn't help us at all.

It's a bit big, so I'm having issues posting it here. Here's a direct link. Do you want me to post a hash of the file and a virus scan?

EDIT: went ahead and did it

That is a large log file.

There doesn't seem to be anything wrong with it. The only thing I can think of right now is that there are too many transactions which is causing the mempool to grow too big. Maybe try to change the settings to limit how large the mempool can get.

Otherwise, the only other solution I can think of is to see if reinstalling and resyncing will help.

Yeah, didn't even check, but it's probably one or two weeks long

Thanks for confirming. I also couldn't detect anything out of the ordinary, and the file just stops when the client closes, without any error messages... If the node shuts down again I'll search on how to adjust the mempool, thank you I'll also be on the watch for a VPS deal with 8GB RAM...

Thanks again for the help.