Node going down and need a reboot after 2-3 days

[Ducky-001]

The full node has crashed consistently every 2-3 days since i got it. It may be because it runs out of memory after a while. When I start it
it uses around 36-38% memory. After running for 13 hours or so it looks like this:

[Ducky-001]

[Ducky-001]

[MrChrisJ]

Ok thanks for reporting this. I setup Node #3 in the flat yesterday and will leave it running and see if I can recreate the same errors.

During testing I did get some crashing of bitcoin daemon but not more frequently that once per week and that was with the GUI running sometimes so I could tweet the stats. So 2-3 days seems a bit much to me. Let's see if I can reproduce the same and if not then worst comes to the worst I can send you replacement.

Might also be good to tweak raspi-config and the overclocking as well. Also if you plan to run in headless mode you can re-allocate more memory to system.

[Ducky-001]

Thanks!

The node is still running, but memory is getting thight

[MrChrisJ]

Ok and I am assuming you haven't made any changes to the Pi since you received it?

I am getting about half the memory usage after 14 hours of operation:

[MrChrisJ]

Ah ok I just noticed that you have more connections because I did not remap my port forwarding on my router to the new IP address. I have done that now and I dealing outbound connections as well. This I expect will increase the memory load.

In the bitcoin.conf file there is maxconnections= field which we can use to limit the max number on the #fullnode project. I will report back once I have gathered some more data.

[Ducky-001]

Yeah, I added the two lines, that's the only change. I came home now and it was died

[johnp1954]

Mine dies too after a couple of days

[MrChrisJ]

Ok. Update my end. I am on Day 3, more memory usage up to 72% now but no sign of crashing just yet:

Can you guys @johnp1954 & @Ducky-001 restart Bitcoin again with bitcoind -daemon command? Let me know if it throws up any errors.

I tweaked the bitcoin.conf file with the following options ... seeing as tho is only a low power computer

checklevel=1
limitfreerelay=10
maxconnections=24
minrelaytxfee=0.0001

[Emzy]

Using the new Jessie Raspberian with systemd as init-system would be an easy fix.
systemd will automatically restart a service that died.

File: /etc/systemd/system/bitcoind.service

[Unit]
Description=Bitcoins distributed currency daemon
After=network.target

[Service]
User=bitcoin
Group=bitcoin

Type=forking
PIDFile=/var/lib/bitcoind/bitcoind.pid
ExecStart=/usr/bin/bitcoind -daemon -pid=/var/lib/bitcoind/bitcoind.pid \
-conf=/etc/bitcoin/bitcoin.conf -datadir=/var/lib/bitcoind -disablewallet

Restart=always
PrivateTmp=true
TimeoutStopSec=60s
TimeoutStartSec=2s
StartLimitInterval=120s
StartLimitBurst=5

[Install]
WantedBy=multi-user.target

A quick hack, I have running on one small VPS Server, is starting bitcoind with this command:
while true ; do sleep 1; bitcoind ; done

[MrChrisJ]

Hey thanks @Emzy, these fullnodes run on Wheezy, would this still work?

[johnp1954]

Just got home and the fullnode has stopped what command do you want me to type in

John

On 6 Jan 2016, at 17:54, Chris Ellis notifications@github.com wrote:

Hey thanks @Emzy, these fullnodes run on Wheezy, would this still work?

—
Reply to this email directly or view it on GitHub.

[MrChrisJ]

Ok after 4 days my fullnode is still running fine. Not sure why I am not able to reproduce the same errors that you guys are getting but I will leave it on in case.

In the mean time here is a new bitcoin.conf file with changes made thanks to @MyVeryOwn and @johnp1954
https://gist.github.com/MrChrisJ/013bc7e14902b1c21208

[MrChrisJ]

Hey @johnp1954,

The command:
bitcoind -daemon