EDIT 3
Bumping my VPS to 1GB of bodily RAM stopped the crashing problem… UNTIL mentioned VPS ran out of disc house.
I added prune=10240 to my ~/.bitcoin/bitcoin.conf file such that the blockchain file would begin pruning transaction historical past upon reaching 10GB filesize (1024 MB * 10 = 10GB).
EDIT 2
This appears to be a reminiscence problem, not a VPN networking problem. I turned OpenVPN off and restarted bitcoind solely to see it silently crash once more.
I’ve now added a 1GB swapfile to develop the accessible reminiscence house (threat is it will trigger efficiency points for the OS). Will replace as soon as once more if this solves the problem. If not, I’ll most likely find yourself making an attempt to improve the VPS occasion to 1GB of bodily RAM from 512MB.
EDIT
Discovered some fascinating stuff within the log regarding tor…
root@sf-vps:~# cat ~/.bitcoin/debug.log | grep tor -i
2016-11-13 16:52:21 Default information listing /root/.bitcoin
2016-11-13 16:52:21 Utilizing information listing /root/.bitcoin
2016-11-13 16:52:21 Utilizing at most 125 connections (1024 file descriptors accessible)
2016-11-13 16:52:29 torcontrol thread begin
2016-11-13 17:08:43 Default information listing /root/.bitcoin
2016-11-13 17:08:43 Utilizing information listing /root/.bitcoin
2016-11-13 17:08:43 Utilizing at most 125 connections (1024 file descriptors accessible)
2016-11-13 17:08:50 torcontrol thread begin
2016-11-13 17:08:50 tor: Error connecting to Tor management socket
2016-11-13 17:08:50 tor: Not related to Tor management port 127.0.0.1:9051, making an attempt to reconnect
2016-11-13 17:08:51 tor: Error connecting to Tor management socket
2016-11-13 17:08:51 tor: Not related to Tor management port 127.0.0.1:9051, making an attempt to reconnect
2016-11-13 17:08:52 tor: Error connecting to Tor management socket
2016-11-13 17:08:52 tor: Not related to Tor management port 127.0.0.1:9051, making an attempt to reconnect
I’ve put in the Bitcoin software program on Ubuntu 16.04. I can run bitcoind -daemon for a couple of minutes, however after some time the method crashes.
Curiously, I do not see any causes in ~/.bitcoin/debug.log explaining why this system may need terminated.
I believe a few issues:
- Not sufficient disc house to retailer your complete blockchain. Nevertheless, I do not suppose that is the case as working
df - hexhibits a mixed whole of solely ~41% disc consumption:
root@sf-vps:~# df -h
Filesystem Measurement Used Avail Use% Mounted on
udev 241M 0 241M 0% /dev
tmpfs 50M 3.1M 47M 7% /run
/dev/vda1 20G 6.3G 13G 34% /
tmpfs 247M 0 247M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 247M 0 247M 0% /sys/fs/cgroup
tmpfs 50M 0 50M 0% /run/person/0
- Server will not be in a position to obtain inbound messages as I am working a VPN. Is it doable that I am experiencing a networking problem, e.g. inbound site visitors to port 8333 (the default for
bitcoind) will not be being allowed by my VPN? I am unable to keep in mind methods to change the VPN config to permit connections on particular ports, however that is the place I am wanting subsequent…
root@sf-vps:~# netstat -nr
Kernel IP routing desk
Vacation spot Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 159.203.240.1 0.0.0.0 UG 0 0 0 eth0
10.8.0.0 10.8.0.2 255.255.255.0 UG 0 0 0 tun0
10.8.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
10.12.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
159.203.240.0 0.0.0.0 255.255.240.0 U 0 0 0 eth0
Thanks prematurely in your assist 🙂