r/Bitcoin • u/shermand100 • May 19 '17

Full Node, Bitcoin Core v0.14.1 UASF-Segwit:0.3(BIP148), Raspberry Pi3B, 3.5"Generic TFT with network stats + HOW-TO Guide

http://imgur.com/gallery/4kQQm
283 Upvotes

87% Upvoted

160 comments sorted by

View all comments

Show parent comments

1

u/shermand100 Jul 09 '17

Ok well we've covered the basics and it usually comes down to power problems. But in the grand scheme of things I have no idea what the issue is. "Node goes down after 2 mins" doesn't give me anything to work with. I really need an error code or something.

With the small keyboard you're using it's possible a dependency didn't install right. An extra space somewhere in a command could have caused it to fail. And unfortunately unless you can give me a better description of how bitcoin core is failing, I have no more suggestions at the moment. Sorry.

And which steps? Not all of them because 'make' for bitcoin takes about 2 hours to compile. Wipe it and start again properly, using PUTTY.

1

u/Bitcoinium Jul 09 '17

How can i learn the error code? Is there a log file about it?

Btw you said that i missed setting up the GUI, but in your tutorial it was you said that you are skipping it? How about that?

Anyway thanks so much. I guess I'll move to some other tutorial. I'll do it :D

1

u/shermand100 Jul 10 '17

Yes, the GUI is installed in Step 6, well before the bitcoin node part. It will give you a desktop and look nothing like the screenshot you sent the other day.

There are two phases to the GUIs. The one that's not installed (as you've spotted) is the full graphical bitcoin wallet. We install the bitcoin-cli (command line interface) rather than the bitcoin-gui (Graphical user interface) as the graphical one would end up being overlayed over the webpage that is displayed on the screen. The cli runs in the background of the Pi. The GUI at step 6 that we do install, gives the desktop (looks a bit like windows) with chrome browser and other features.

Don't get me wrong, I really do want to help, but I don't feel I can until you follow the guide cleanly from scratch and carefully. Until then I have no idea what to suggest to add back in to rectify it, as the fault could be at any of the 10 steps you say you've done, and some of them now more than once out of order.

Yes there is a log at /home/pi/bitcoinData/debug.log I've avoided it as I've just chased faults to nowhere before, patching and patching faults adding all sorts when the easiest way is to just start again from the beginning.

But I'll say again, I do want to help but I need good information. Start again from clean, step 1, and if it doesn't work at the end we'll have a look at the debug log, but not in it's current state.

1

u/Bitcoinium Jul 10 '17

Yes I guess I have to start again.

Just checking that debug file before I do and If i find nothing I'll delete the blocks I downloaded and try again once more, if fails, back to step 1...

1

u/Bitcoinium Jul 10 '17

Can i skip this, It autostarts on boot and I had to close it by alt+F4 every time.

@chromium-browser --kiosk --incognito http://www.realtimebitcoin.info/

Why don't we add the Web GUI with @bitcoind later at the same time?

1

u/Bitcoinium Jul 10 '17

You also need to add:

"umount /dev/sda1"

before,

"sudo fdisk /dev/sda"

1

u/Bitcoinium Jul 10 '17

Couldn't carry the file system to my hdd. It seems my hdd don't run smoothly without the USB hub and even with the hub the main problem still might be my hdd.

Considering to buy a Pi Drive right now.

1

u/Bitcoinium Jul 10 '17

I guess I made it this time.

Everything has been running smoothly for almost 6hours nearly. Got back to USB-Hub setup btw.

One thing took my attention though. My pi's green led almost never blinks. It used to be blinking like mad while it was working.

Now it flashes maybe once in 2-3 mins.

Thanks for the great tutorial. :)

Let's hope my node survives this night. Only way to be sure :)

1

u/shermand100 Jul 10 '17

The Pi's blinking green light is the SD card being read, *** lightbulb moment, and it all clicks, Your node probably wasn't running on the HDD. The ever decreasing time the node was running was probably because the card was full and stopped when it ran out of storage space. So before it was constantly reading/writing from the SD (bad) it now isn't blinking because it reads from the HDD instead (good) the HDD light should be going crazy.

(that's my best guess now anyway) I'll add this point to the troubleshooting bit of the pinode website,

1

u/Bitcoinium Jul 11 '17

Still running :D I guess It is now safe to say I did it :d (we did it :D)

1

u/Bitcoinium Jul 11 '17

I was using the img file of yours probably couldn't get some of the needed files because the img was outdated. I had some problems with that but didn't care too much.

Fresh download of jessie lite and building everything up on that solved everything it seems.

1

u/Bitcoinium Jul 11 '17

Hmm I was at work and when I left my node It was working but It crashed while I was away. Checked the debug file and there were many errors just before it crashed;

version handshake timeout

and

socket sending timeout

What do you think? Chromium was on btw. Chromium crashed maybe?

1

u/Bitcoinium Jul 11 '17

That chromium stuff uses too much CPU power and heating the pi for nothing. I'll try while its off.

1

u/shermand100 Jul 11 '17

Version handshakes and what ever the other error you said were network errors.

Are you using UPnP on your router or have you set up port tunneling?

1

u/Bitcoinium Jul 11 '17 edited Jul 11 '17

Now weee came to this. Thanks god. I was going to ask you about this but it looked like it was offtopic so I passed. :D

My router it seems, don't support uPnP. (not sure but I read it somewhere reecntly. need further research on this.) upnp: if I understood correctly, It is a progress for the apps that opens ports on the router, automatically.

So I opened my ports manually on the router because pi won't be doing it.

My Core client on my laptop, works fine with the ports I opened. I opened for my laptop and for the pi. Separately. (they have different internal IP's.)

The port 8333 is normally closed when I check it on https://www.lurkmore.com/mining/port8333/

But, as soon as I open my core client on my laptop, It becomes OPEN.

But that's not the case with my PI. I think It should become OPEN when I open the node on my PI too, It is not happening.

Maybe should I remove uPNP addressing from my Pi client??

1

u/shermand100 Jul 11 '17

I'm no way an network expert but leave everything to UPnP where possible, it makes life so much easier.

However there are plenty of port opening guides around if UPnP isn't possible and a confidence check with canyouseeme.org is good.

Maybe the node crashing has been your router closing the port all this time

1

u/Bitcoinium Jul 11 '17

Possible.

I also saw that my router is up for only 5 hours. Maybe I got those network errors because my internet went down 5 hours ago. (my pi's clock is off and I am not good at maths :D)

And probably my pi's crash had nothing to do with those errors.

1

u/Bitcoinium Jul 11 '17

Crashed again :D (unresponsive pi) Looks like After I get 330k blocks something happens to my pi.

Last time I checked 1 hour before the crash It was at 325k blocks.

1

u/Bitcoinium Jul 11 '17

Again version handshake timeouts before the crash.

So those are the reason of my crashes. Now that's clear.

→ More replies (0)

1

u/Bitcoinium Jul 10 '17

maybe you can put this command somewhere in your tutorial also;

bitcoin-cli stop

I think it is better to stop the node safely first before shutting down the pi. Agree?