Sun Feb 07, 2016 5:11 am

Just to give you a heads up, I had a lot of problems syncing the blockchain on my RPi2. It downloaded the first 50-60% just fine, but then it started crashing every few minutes. I eventually set up a temporary node on my laptop and finished syncing the blockchain on my Pi's 128GB flash drive. Now that the blockchain is up to date, it's been running great on my Pi! I was having this problem initially too.

I also had it overclocked to 1000 Mhz, but when I set it back to the stock speed of 900 Mhz, it hasn't crashed since.

I'm wondering what you had your clock speed set at. I was having this problem initially too.I also had it overclocked to 1000 Mhz, but when I set it back to the stock speed of 900 Mhz, it hasn't crashed since.I'm wondering what you had your clock speed set at.

Is this related to cooling issues? The case I bought for it had some cooling bricks that I stuck on the chips. I noticed your setup does not have this. Crashes due to overheating are probably nasty crashes in that they cannot be intercepted using software.If the bitcoind itself crashes, it would be possible to restart it. I personally prefer daemontools by D.J. Bernstein ( http://cr.yp.to ) and use that on all my servers / computers. It compiles effortlessly on the Pi. My default bitcoind startup script has two bitcoind launching lines. One starts bitcoind 'regularly' - this should never complete and thus the second line is never launched. Except for when bitcoind shuts down by itself. The second line launches bitcoind in the exact same configuration, but with the reindex command. Yes that takes some time on a Pi, so it may be worthwhile to change that on a Pi with a check to see if the log complains about a reindex need. On a more powerful PC, that works just fine. Using this logic, I never have to look if a node is up. It is almost impossible to crash it in such a way that it needs manual attention.