0

I'm trying to install a full node on a VPS instance of Inmotion Hosting linux server. I have no issues with downloading and installing the Bitcoin Core files from Bitcoin.org, but upon trying to start the daemon, the connection seems to fail around the time of validating/creating the new wallet. I currently have no wallet and expected the software to create a new one for me in the ./.bitcoin/wallet directory.

Below is the debug.log file (update after running in debug mode for additional info) and also critical parts of my bitcoin.conf file. Any ideas why the daemon may be crashing where it is? I've opened up port 8332 to the firewall (as best I can tell) and ensured nothing else is running on port 8332 (even tried using a variety of other ports and binding directly to a port on my dedicated IP with no luck) using netstat -antlp and reviewing all ports in use; it's not a port conflict.

Config:
server=1
daemon=1
listen=1
txindex=1
rpctimeout=300
rpcauth=valid user info
rpcallowip=127.0.0.1/8
rpcallowip=my dedicated ip
rpcport=8332

Debug.log:
2018-07-07 06:40:16 Bitcoin Core version v0.16.1 (release build)
2018-07-07 06:40:16 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-07-07 06:40:16 Assuming ancestors of block 0000000000000000005214481d2d96f898e3d5416e43359c145944a909d242e0 have valid signatures.
2018-07-07 06:40:16 Setting nMinimumChainWork=000000000000000000000000000000000000000000f91c579d57cad4bc5278cc
2018-07-07 06:40:16 Using the 'sse4' SHA256 implementation
2018-07-07 06:40:16 Default data directory /home/bluebo19/.bitcoin
2018-07-07 06:40:16 Using data directory /home/bluebo19/.bitcoin
2018-07-07 06:40:16 Using config file /home/bluebo19/.bitcoin/bitcoin.conf
2018-07-07 06:40:16 Using at most 125 automatic connections (16384 file descriptors available)
2018-07-07 06:40:16 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2018-07-07 06:40:16 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2018-07-07 06:40:16 Using 16 threads for script verification
2018-07-07 06:40:16 Allowing HTTP connections from: 127.0.0.0/8 ::1/128 127.0.0.0/8 199.250.202.0/24
2018-07-07 06:40:16 scheduler thread start
2018-07-07 06:40:16 Binding RPC on address :: port 8332
2018-07-07 06:40:16 libevent: getaddrinfo: address family for nodename not supported
2018-07-07 06:40:16 Binding RPC on address :: port 8332 failed.
2018-07-07 06:40:16 Binding RPC on address 0.0.0.0 port 8332
2018-07-07 06:40:16 Initialized HTTP server
2018-07-07 06:40:16 HTTP: creating work queue of depth 16
2018-07-07 06:40:16 Starting RPC
2018-07-07 06:40:16 Starting HTTP RPC server
2018-07-07 06:40:16 No rpcpassword set - using random cookie authentication
2018-07-07 06:40:16 Generated RPC authentication cookie /home/bluebo19/.bitcoin/.cookie
2018-07-07 06:40:16 Registering HTTP handler for / (exactmatch 1)
2018-07-07 06:40:16 Registering HTTP handler for /wallet/ (exactmatch 0)
2018-07-07 06:40:16 Starting HTTP server
2018-07-07 06:40:16 HTTP: starting 4 worker threads
2018-07-07 06:40:16


EXCEPTION: St12system_error
Resource temporarily unavailable
bitcoin in AppInit()

2018-07-07 06:40:16 Interrupting HTTP server
2018-07-07 06:40:16 Interrupting HTTP RPC server
2018-07-07 06:40:16 Interrupting RPC
2018-07-07 06:40:16 Shutdown: In progress...
2018-07-07 06:40:16 Stopping HTTP RPC server
2018-07-07 06:40:16 Unregistering HTTP handler for / (exactmatch 1)
2018-07-07 06:40:16 Stopping RPC
2018-07-07 06:40:16 RPC stopped.
2018-07-07 06:40:16 Stopping HTTP server
2018-07-07 06:40:16 Waiting for HTTP worker threads to exit
2018-07-07 06:40:16 Waiting for HTTP event thread to exit

  • 1
    try setting rpcthreads=1, seems like 4 is causing your VPS to throw an error (4 is the default, some VPS providers limit how many resources you can consume more strictly) – Raghav Sood Jul 5 '18 at 17:47
  • 1
    Also, ensure that port 8332 is not already in use by another program – Raghav Sood Jul 5 '18 at 17:48
  • @Raghav Sood - Changing the threads to 1 gets the same fail, just with: HTTP: starting 1 worker threads. Also, checked that the port is not in use using netstat -antlp command; nothing on port 8332 while also trying different ports while failing at the same place. – Scotty Don't Jul 5 '18 at 21:50
  • This error happens when you consume too many resources than available. So what's likely happening is that Bitcoin Core simply requires too many resources and is thus unable to run on your VPS as VPS's are generally low powered. – Andrew Chow Jul 7 '18 at 8:32
  • 1
    @Willtech Yes, it is worth trying to lower memory usage. However, depending on what resource is specifically unavailable, this may not work. – Andrew Chow Jul 8 '18 at 19:19

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.