Terminate called?

[wolfinger1]

Could someone explain what this means?

Also, on one of Chris's videos he says that we should change the password but when I do, I get an error. Do I need to restart after changing it?

[MrChrisJ]

Sorry my notification settings for Github are messed up.

Is this the password for the RPC? You will probably need to:
bitcoin-cli stop
Wait for a few mins for bitcoind to stop running, to see this in real time simply type:

top

Then:

sudo halt

This is the most graceful way of shutting down the fullnode without risking any disk errors. A new version of the software including the OS is due out in next 7 days so I can send you an upgrade free of charge if you want.

[wolfinger1]

Still having trouble with my Bitcoin full node -- cannot seem to find a way to get more than 8 connections.
listen=1
server=1
daemon=1
Ports forwarded and checked (they are OPEN)
any more ideas?

All help is appreciated. I am getting to the point of just throwing it out the window (not really.)

[Enegnei]

Have you increased max connections? Default is 8. @wolfinger1

maxconnections=8

[wolfinger1]

Yes maxconnections=24

[wolfinger1]

There was a brief moment in time (see photo above) where connections > 8 but that ended quickly and reverted back to 8. Been there ever since.

[MrChrisJ]

@wolfinger1 8 is the max number by default if you are not accepting inbound requests. This can be if either you do not have the line:

listen=1

Enabled in your bitcoin.conf file or if you have not setup port forwarding on your router.

To set up port forwarding you need to log in to the router, go to Advanced Settings and select Port Forwarding. You need to open up port number 8333 to 8333 on the IP address of your device.

UPNP was enabled on all the fullnodes but sometimes that doesn't work and it is necessary to go through these extra steps. Once you have done this you will notice that after a while the number of connections will increase.

Let us know how you get on.

[wolfinger1]

Screenshots

[MrChrisJ]

@wolfinger1 hi, I just read the thread above and it looks like you have done everything right. What you can try is stop bitcoin with bitcoin-cli stop then rename the bitcoin.conf to bitcoin_old.conf then create a new file and include just the minimum as laid out in the new guide for bitcoin 0.12. Which is:

bitcoin.conf:

listen=1
server=1
dbcache=50
daemon=1
testnet=0

The defaults should then kick back in. Alternatively if you wait another week or so you can download or I can send you a new copy of Bitcoin 0.12 with Raspbian Jessie.

Would be good to know who your internet provider is too in case there is something going on there.