How do I start a bitcoind server in deprecated mode for multiple functions

I have a bitcoind server running bitcoin-core version 0.17. Now since I need to use deprecated RPC methods I need to start the bitcoind server in deprecated mode, so I am already able to run it to support the accounts rpc methods by running the following command

bitcoind -deprecatedrpc=accounts 

However, I found that signrawtransaction has also been deprecated, so I ran the bitcoind server with the following command :

bitcoind -deprecatedrpc=accounts,signrawtransaction 

The server started successfully, however I was still getting this error :

"signrawtransaction is deprecated and will be fully removed in v0.18. To use signrawtransaction in v0.17, restart bitcoind with -deprecatedrpc=signrawtransaction.\nProjects should transition to using signrawtransactionwithkey and signrawtransactionwithwallet before upgrading to v0.18" 

So I started the server again with the following command :

bitcoind -deprecatedrpc=signrawtransaction 

And this time the transaction went through, however I need to start the bitcoind server to support both the deprecated methods. How can I do that?

bitcoind rest api tx endpoint

i am having a trouble with bitcoind REST API endpoint for retrieving transaction info. According to the documentation it should return confirmations among the retrieved data. But my bitcoind do not have this present in the response. I have rest=1 and txindex=1 so everything probably should be ok.

I have picked a random txid to demonstrate the response

This is what i got from the REST API tx endpoint ( with truncated vin/vout ):

{     "hash": "669a1302ee3ccb482cc545f56cca9112a2d24a7959f1da18f87603640ff9288e",      "vout": [ ... ],      "weight": 896,      "hex": "0100000001e96d13340057a99320702b9482a93114fb7ed0d27345242dd61a6ba967fe70a5010000006b483045022100833c21acd4e87aec7f794804606ef1699db2a5cc420f80af500243a43970cb8a0220617b9f55e2c6383f3093a4683af9fcdaad668b66e942553a6928b07e241141120121035deb8e150be5ccbfcca2a978d9bc3e2990afb61d08b49ce0494f39b10173c828ffffffff02dc9b68000000000017a91418b3b7d346e3f32cc4b3e0617fdf61e23d5ea2cc87cc8e6f1a000000001976a9140ae8e97489b9412f3f2ca6a63882f762174b368788ac00000000",      "blockhash": "0000000000000000000d5cfef192ed15ed37881cd5f0930d5613ac92a6b1b6e6",      "vin": [ ... ],      "txid": "669a1302ee3ccb482cc545f56cca9112a2d24a7959f1da18f87603640ff9288e",      "version": 1,      "locktime": 0,      "vsize": 224,      "size": 224 } 

And this is what i got from the bitcoin-cli getrawtransaction 669a1302ee3ccb482cc545f56cca9112a2d24a7959f1da18f87603640ff9288e 1 ( with truncated vin/vout ):

{   "txid": "669a1302ee3ccb482cc545f56cca9112a2d24a7959f1da18f87603640ff9288e",   "hash": "669a1302ee3ccb482cc545f56cca9112a2d24a7959f1da18f87603640ff9288e",   "version": 1,   "size": 224,   "vsize": 224,   "weight": 896,   "locktime": 0,   "vin": [ ... ],   "vout": [ ... ],   "hex": "0100000001e96d13340057a99320702b9482a93114fb7ed0d27345242dd61a6ba967fe70a5010000006b483045022100833c21acd4e87aec7f794804606ef1699db2a5cc420f80af500243a43970cb8a0220617b9f55e2c6383f3093a4683af9fcdaad668b66e942553a6928b07e241141120121035deb8e150be5ccbfcca2a978d9bc3e2990afb61d08b49ce0494f39b10173c828ffffffff02dc9b68000000000017a91418b3b7d346e3f32cc4b3e0617fdf61e23d5ea2cc87cc8e6f1a000000001976a9140ae8e97489b9412f3f2ca6a63882f762174b368788ac00000000",   "blockhash": "0000000000000000000d5cfef192ed15ed37881cd5f0930d5613ac92a6b1b6e6",   "confirmations": 5,   "time": 1558449750,   "blocktime": 1558449750 } 

Is there something i am doing wrong that I do not get the confirmations from the REST API endpoint as said in docs?

Bitcoind version v0.17.0.0

Understanding default bitcoin wallet in bitcoind

I am new to block-chain, so please bear with my questions. I need to understand the basics of a bitcoin-wallet. So I have setup a bitcoin full node using bitcoind in running in testnet mode. As I understand that by default a wallet is created. Now when I am trying to get the address of the wallet by this command bitcoin-cli -testnet getaccount "", I am geeting an empty list. So is there no default wallet as such, also how do I create a new wallet? As I understand that a bitcoin wallet is basically a pot which holds several child addresses?

Connection Refused when running bitcoind in a non-root user and trying to make RPC calls

I’m new to Bitcoin development and I’m currently having difficulties trying to make RPC calls to a Bitcoin-Core daemon running in a SSH server. I suppose that the problem is with Firewall or closed ports, but I also do not know much about Network settings.

I’m using nbobtc/bitcoind-php package to make the RPC calls with HTTP requests, and it is running in a Docker container. I’m sure this is working and is not the problem.

So here’s what happening: when I run bitcoind in a normal user in my SSH server, and using nbobtc package to make the RPC calls, the connection always get refused in port 18332 (that is conffirmed when I try to telnet that port in SSH’s ip address):

Failed to connect to 192.168.xx.xxx port 18332: Connection refused

However, when I run bitcoind in super user (root), the RPC calls works just perfectly. But as I did not want to run bitcoind in root user, I’d like to find out what may be blocking me from making RPC calls to a normal user – or if is it even possible.

I’ve tried to open ports with ‘sudo ufw allow 18332’ and also with IPTABLES (but actually I’m not sure which one is being used by the SSH – it wasn’t me who configured it). I’m not sure if they have worked as with nc and telnet commands connection is still being refused.

Here’s what my bitcoin.conf looks like (I want to use testnet in here):

server=1 debug=net txindex=1 testnet=1 rpcuser=userb rpcpassword=test test.rpcport=18332  # I've already tried allowing the IP these 3 ways: # rpcallowip=192.168.xx.xx  # My machine's IP # rpcallowip=172.19.x.x/xx  # Docker's NBOBTC container IP # rpcallowip=0.0.0.0/0      # Allowing all IP  datadir=/home/bitcoin-dev/.bitcoin debuglogfile=/home/bitcoin-dev/.bitcoin/debug.log 

PS: I’m using Bitcoin-Core “subversion”: “Satoshi:0.17.1”

Here’s what appears in debug.log right after I run Bitcoind:

2019-05-06T14:43:10Z Bitcoin Core version v0.17.1 (release build) 2019-05-06T14:43:10Z InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2019-05-06T14:43:10Z Assuming ancestors of block 0000000000000037a8cd3e06cd5edbfe9dd1dbcc5dacab279376ef7cfc2b4c75 have valid signatures. 2019-05-06T14:43:10Z Setting nMinimumChainWork=00000000000000000000000000000000000000000000007dbe94253893cbd463 2019-05-06T14:43:10Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation 2019-05-06T14:43:10Z Default data directory /root/.bitcoin 2019-05-06T14:43:10Z Using data directory /home/bitcoin-dev/.bitcoin/testnet3 2019-05-06T14:43:10Z Using config file /home/bitcoin-dev/.bitcoin/bitcoin.conf 2019-05-06T14:43:10Z Using at most 125 automatic connections (1024 file descriptors available) 2019-05-06T14:43:10Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2019-05-06T14:43:10Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2019-05-06T14:43:10Z Using 4 threads for script verification 2019-05-06T14:43:10Z scheduler thread start 2019-05-06T14:43:10Z Binding RPC on address 0.0.0.0 port 18332 failed. 2019-05-06T14:43:10Z HTTP: creating work queue of depth 16 2019-05-06T14:43:10Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2019-05-06T14:43:10Z HTTP: starting 4 worker threads 2019-05-06T14:43:10Z Using wallet directory /home/bitcoin-dev/.bitcoin/testnet3/wallets 2019-05-06T14:43:10Z init message: Verifying wallet(s)... 2019-05-06T14:43:10Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010) 2019-05-06T14:43:10Z Using wallet wallet.dat 2019-05-06T14:43:10Z BerkeleyEnvironment::Open: LogDir=/home/bitcoin-dev/.bitcoin/testnet3/wallets/database ErrorFile=/home/bitcoin-dev/.bitcoin/testnet3/wallets/db.log 2019-05-06T14:43:10Z net: setting try another outbound peer=false 2019-05-06T14:43:10Z Cache configuration: 2019-05-06T14:43:10Z * Using 2.0MiB for block index database 2019-05-06T14:43:10Z * Using 56.0MiB for transaction index database 2019-05-06T14:43:10Z * Using 8.0MiB for chain state database 2019-05-06T14:43:10Z * Using 384.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2019-05-06T14:43:10Z init message: Loading block index... 2019-05-06T14:43:10Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/blocks/index 2019-05-06T14:43:10Z Opened LevelDB successfully 2019-05-06T14:43:10Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/blocks/index: 0000000000000000 2019-05-06T14:43:19Z LoadBlockIndexDB: last block file = 161 2019-05-06T14:43:19Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=755, size=30875345, heights=1513309...1514061, time=2019-04-29...2019-05-03) 2019-05-06T14:43:19Z Checking all blk files are present... 2019-05-06T14:43:20Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/chainstate 2019-05-06T14:43:20Z Opened LevelDB successfully 2019-05-06T14:43:20Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/chainstate: 2686d59caeb1917c 2019-05-06T14:43:20Z Loaded best chain: hashBestChain=00000000b3b6a5db140b6058b7abe5cb00d8af61afd2a237ae3468cd36e387fa height=927391 date=2016-09-08T15:04:00Z progress=0.311180 2019-05-06T14:43:20Z init message: Rewinding blocks... 2019-05-06T14:43:29Z init message: Verifying blocks... 2019-05-06T14:43:29Z Verifying last 6 blocks at level 3 2019-05-06T14:43:29Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE]. 2019-05-06T14:43:29Z No coin database inconsistencies in last 6 blocks (500 transactions) 2019-05-06T14:43:29Z  block index           19450ms 2019-05-06T14:43:29Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/indexes/txindex 2019-05-06T14:43:30Z Opened LevelDB successfully 2019-05-06T14:43:30Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/indexes/txindex: 0000000000000000 2019-05-06T14:43:30Z init message: Loading wallet... 2019-05-06T14:43:30Z txindex thread start 2019-05-06T14:43:30Z [default wallet] nFileVersion = 170100 2019-05-06T14:43:30Z [default wallet] Keys: 2005 plaintext, 0 encrypted, 2005 w/ metadata, 2005 total. Unknown wallet records: 1 2019-05-06T14:43:30Z Syncing txindex with block chain from height 694205 2019-05-06T14:43:30Z [default wallet] Wallet completed loading in             123ms 2019-05-06T14:43:30Z [default wallet] setKeyPool.size() = 2000 2019-05-06T14:43:30Z [default wallet] mapWallet.size() = 7 2019-05-06T14:43:30Z [default wallet] mapAddressBook.size() = 4 2019-05-06T14:43:30Z mapBlockIndex.size() = 1515581 2019-05-06T14:43:30Z nBestHeight = 927391 2019-05-06T14:43:30Z torcontrol thread start 2019-05-06T14:43:30Z Bound to [::]:18333 2019-05-06T14:43:30Z Bound to 0.0.0.0:18333 2019-05-06T14:43:30Z init message: Loading P2P addresses... 2019-05-06T14:43:30Z Loaded 10420 addresses from peers.dat  36ms 2019-05-06T14:43:30Z init message: Loading banlist... 2019-05-06T14:43:30Z Loaded 0 banned node ips/subnets from banlist.dat  29ms 2019-05-06T14:43:30Z init message: Starting network threads... 2019-05-06T14:43:30Z net thread start 2019-05-06T14:43:30Z dnsseed thread start 2019-05-06T14:43:30Z addcon thread start 2019-05-06T14:43:30Z msghand thread start 2019-05-06T14:43:30Z init message: Done loading 2019-05-06T14:43:30Z opencon thread start 

Connection Refused when running bitcoind in a non-root user and trying to make RPC calls

I’m new to Bitcoin development and I’m currently having difficulties trying to make RPC calls to a Bitcoin-Core daemon running in a SSH server. I suppose that the problem is with Firewall or closed ports, but I also do not know much about Network settings.

I’m using nbobtc/bitcoind-php package to make the RPC calls with HTTP requests, and it is running in a Docker container. I’m sure this is working and is not the problem.

So here’s what happening: when I run bitcoind in a normal user in my SSH server, and using nbobtc package to make the RPC calls, the connection always get refused in port 18332 (that is conffirmed when I try to telnet that port in SSH’s ip address):

Failed to connect to 192.168.xx.xxx port 18332: Connection refused

However, when I run bitcoind in super user (root), the RPC calls works just perfectly. But as I did not want to run bitcoind in root user, I’d like to find out what may be blocking me from making RPC calls to a normal user – or if is it even possible.

I’ve tried to open ports with ‘sudo ufw allow 18332’ and also with IPTABLES (but actually I’m not sure which one is being used by the SSH – it wasn’t me who configured it). I’m not sure if they have worked as with nc and telnet commands connection is still being refused.

Here’s what my bitcoin.conf looks like (I want to use testnet in here):

server=1 debug=net txindex=1 testnet=1 rpcuser=userb rpcpassword=test test.rpcport=18332  # I've already tried allowing the IP these 3 ways: # rpcallowip=192.168.xx.xx  # My machine's IP # rpcallowip=172.19.x.x/xx  # Docker's NBOBTC container IP # rpcallowip=0.0.0.0/0      # Allowing all IP  datadir=/home/bitcoin-dev/.bitcoin debuglogfile=/home/bitcoin-dev/.bitcoin/debug.log 

PS: I’m using Bitcoin-Core “subversion”: “Satoshi:0.17.1”

Here’s what appears in debug.log right after I run Bitcoind:

2019-05-06T14:43:10Z Bitcoin Core version v0.17.1 (release build) 2019-05-06T14:43:10Z InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2019-05-06T14:43:10Z Assuming ancestors of block 0000000000000037a8cd3e06cd5edbfe9dd1dbcc5dacab279376ef7cfc2b4c75 have valid signatures. 2019-05-06T14:43:10Z Setting nMinimumChainWork=00000000000000000000000000000000000000000000007dbe94253893cbd463 2019-05-06T14:43:10Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation 2019-05-06T14:43:10Z Default data directory /root/.bitcoin 2019-05-06T14:43:10Z Using data directory /home/bitcoin-dev/.bitcoin/testnet3 2019-05-06T14:43:10Z Using config file /home/bitcoin-dev/.bitcoin/bitcoin.conf 2019-05-06T14:43:10Z Using at most 125 automatic connections (1024 file descriptors available) 2019-05-06T14:43:10Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2019-05-06T14:43:10Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2019-05-06T14:43:10Z Using 4 threads for script verification 2019-05-06T14:43:10Z scheduler thread start 2019-05-06T14:43:10Z Binding RPC on address 0.0.0.0 port 18332 failed. 2019-05-06T14:43:10Z HTTP: creating work queue of depth 16 2019-05-06T14:43:10Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2019-05-06T14:43:10Z HTTP: starting 4 worker threads 2019-05-06T14:43:10Z Using wallet directory /home/bitcoin-dev/.bitcoin/testnet3/wallets 2019-05-06T14:43:10Z init message: Verifying wallet(s)... 2019-05-06T14:43:10Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010) 2019-05-06T14:43:10Z Using wallet wallet.dat 2019-05-06T14:43:10Z BerkeleyEnvironment::Open: LogDir=/home/bitcoin-dev/.bitcoin/testnet3/wallets/database ErrorFile=/home/bitcoin-dev/.bitcoin/testnet3/wallets/db.log 2019-05-06T14:43:10Z net: setting try another outbound peer=false 2019-05-06T14:43:10Z Cache configuration: 2019-05-06T14:43:10Z * Using 2.0MiB for block index database 2019-05-06T14:43:10Z * Using 56.0MiB for transaction index database 2019-05-06T14:43:10Z * Using 8.0MiB for chain state database 2019-05-06T14:43:10Z * Using 384.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2019-05-06T14:43:10Z init message: Loading block index... 2019-05-06T14:43:10Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/blocks/index 2019-05-06T14:43:10Z Opened LevelDB successfully 2019-05-06T14:43:10Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/blocks/index: 0000000000000000 2019-05-06T14:43:19Z LoadBlockIndexDB: last block file = 161 2019-05-06T14:43:19Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=755, size=30875345, heights=1513309...1514061, time=2019-04-29...2019-05-03) 2019-05-06T14:43:19Z Checking all blk files are present... 2019-05-06T14:43:20Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/chainstate 2019-05-06T14:43:20Z Opened LevelDB successfully 2019-05-06T14:43:20Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/chainstate: 2686d59caeb1917c 2019-05-06T14:43:20Z Loaded best chain: hashBestChain=00000000b3b6a5db140b6058b7abe5cb00d8af61afd2a237ae3468cd36e387fa height=927391 date=2016-09-08T15:04:00Z progress=0.311180 2019-05-06T14:43:20Z init message: Rewinding blocks... 2019-05-06T14:43:29Z init message: Verifying blocks... 2019-05-06T14:43:29Z Verifying last 6 blocks at level 3 2019-05-06T14:43:29Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE]. 2019-05-06T14:43:29Z No coin database inconsistencies in last 6 blocks (500 transactions) 2019-05-06T14:43:29Z  block index           19450ms 2019-05-06T14:43:29Z Opening LevelDB in /home/bitcoin-dev/.bitcoin/testnet3/indexes/txindex 2019-05-06T14:43:30Z Opened LevelDB successfully 2019-05-06T14:43:30Z Using obfuscation key for /home/bitcoin-dev/.bitcoin/testnet3/indexes/txindex: 0000000000000000 2019-05-06T14:43:30Z init message: Loading wallet... 2019-05-06T14:43:30Z txindex thread start 2019-05-06T14:43:30Z [default wallet] nFileVersion = 170100 2019-05-06T14:43:30Z [default wallet] Keys: 2005 plaintext, 0 encrypted, 2005 w/ metadata, 2005 total. Unknown wallet records: 1 2019-05-06T14:43:30Z Syncing txindex with block chain from height 694205 2019-05-06T14:43:30Z [default wallet] Wallet completed loading in             123ms 2019-05-06T14:43:30Z [default wallet] setKeyPool.size() = 2000 2019-05-06T14:43:30Z [default wallet] mapWallet.size() = 7 2019-05-06T14:43:30Z [default wallet] mapAddressBook.size() = 4 2019-05-06T14:43:30Z mapBlockIndex.size() = 1515581 2019-05-06T14:43:30Z nBestHeight = 927391 2019-05-06T14:43:30Z torcontrol thread start 2019-05-06T14:43:30Z Bound to [::]:18333 2019-05-06T14:43:30Z Bound to 0.0.0.0:18333 2019-05-06T14:43:30Z init message: Loading P2P addresses... 2019-05-06T14:43:30Z Loaded 10420 addresses from peers.dat  36ms 2019-05-06T14:43:30Z init message: Loading banlist... 2019-05-06T14:43:30Z Loaded 0 banned node ips/subnets from banlist.dat  29ms 2019-05-06T14:43:30Z init message: Starting network threads... 2019-05-06T14:43:30Z net thread start 2019-05-06T14:43:30Z dnsseed thread start 2019-05-06T14:43:30Z addcon thread start 2019-05-06T14:43:30Z msghand thread start 2019-05-06T14:43:30Z init message: Done loading 2019-05-06T14:43:30Z opencon thread start 

Why my bitcoind cannot query all the blocks?

I just install the bitcoind and run:

bitcoind -daemon 

and when i tried to:

bitcoin-cli getblockhash 195876 

i got an message:

error code: -8 error message: Block height out of range 

the command:

bitcoin-cli getblockchaininfo 

got me the data –

{ "chain": "main", "blocks": 195807,  ...... } 

but the current block height is more than 574000 why does bincoind doesnt see all the blocks?

How to move sync’s data to another partition after run Bitcoind for a while?

I have download a new bitcoin package from official site. And then I ran it with daemon mode also with default configuration (Default means not bitcoin.conf file was created in ~/.bitcoin/.bitcoin.conf). After ran 2 hours. I got stuck, and the process exit. When I checked my disk with:

df -lh 

And then, I got those:

Filesystem      Size  Used Avail Use% Mounted on /dev/vda1        20G   20G  118M 100% / devtmpfs        3.9G     0  3.9G   0% /dev tmpfs           3.9G     0  3.9G   0% /dev/shm tmpfs           3.9G  233M  3.6G   6% /run tmpfs           3.9G     0  3.9G   0% /sys/fs/cgroup /dev/vdb        800G  7.7G  792G   1% /data tmpfs           783M     0  783M   0% /run/user/1000 tmpfs           783M     0  783M   0% /run/user/1001 

And I googled for a while, but could’t find a good way to move all sync’s data to the /dev/vdb. I understand what my mistake came from, but I just fixed it by move data and then put a new configuration with --data-dir=/dev/vdb. and then keep sync it.

So, How do I reach that?

bitcoind bulk import private keys to different wallets and update with one rescan

i was wonder if someone already has this thoughts or problems:

i generate bitcoin addresses and private keys by a script – to not dependent on the bitcoin daemon. i manage them in a database. by generating the bitcoin addresses i generate one address and also select a wallet name by some criterias.

BITCOIN ADDRESS | PRIVATE KEY | WALLETNAME

After a specific time i want to import the private keys to the given wallets (“WALLET NAMES”) (to the wallets defined in the database before.. )

i do this import with importprivkey without a rescan. i was wonder if its possible to import the private keys to the wallets and to rescan one time and update all wallets with this one rescan to avoid for every wallet a explicit rescans each one and a half hour time..

is it possible to import the private keys rescan=false and after this to run bitcoind with all wallets loaded and do the rescan which should be affecting all the wallets and update all of them in one rescan?

does anyone was think about this before and has a solution for this?

best regards Jack

Bitcoind is not running properly in centOS server

I just try to setup full node in centos(Linux distribution) server. I download binary for Linux from https://bitcoincore.org/bin/bitcoin-core-0.17.1/ . I just start bitcoind using the following command

bitcoind -daemon 

Result

Bitcoin server starting 

Then I just test with bitcoin-cli using the following command

bitcoin-cli getbalance 

Result

it return balance 

Then I close my SSH terminal. And re login. But at that time bitcoind is not running. I don’t know what is the reason for that. I already try the same process in ubuntu 18.04. But that was working perfectly. Please give any idea to run bitcoind in background as permanently(on centos).

Thank you