Thanks, I will heed your advice regarding the kill command.
Here are the properties of
/var/db/bitcoin
Code:
ls -lh /var/db/bitcoin
drwxr-xr-x 3 bitcoin bitcoin 512B Jan 27 13:01 bitcoin
Code:
ls -lh /var/db/bitcoin/
total 56
-rw------- 1 bitcoin bitcoin 0B Dec 5 15:59 .lock
-rw------- 1 bitcoin bitcoin 37B Dec 5 15:59 banlist.dat
drwx------ 3 bitcoin bitcoin 512B Dec 5 15:59 blocks
-rw------- 1 bitcoin bitcoin 45K Jan 27 13:01 debug.log
Here is the requested part for the
bitcoin.conf file
Code:
#----BITCOIN CORE----
## Specify data directory
datadir=/nfs2/blockchain
#Specify directory to hold blocks subdirectory for *.dat files (default: <datadir>)
blocksdir=/nfs2/blockchain
# ---- NETWORKING ----
# Bind to given address and always listen on it. Use [host]: port notation for IPv6
# bind = <addr>
bind = 192.168.1.13
# Listen for incoming connections on non-default port.
port = 8333
# Listen for connections on <port> (default: 8333, testnet: 18333, regtest: 18444)
I just noticed while discussing with you that in my
bitcoin.conf file, I specify to make the files in
/nfs2/blochain (which is a hard disk of the system that I added because the full node takes + - 349G .
If I check the properties
/nfs2/blockchain gives this.
Code:
ls -lh /nfs2/
total 32804
-r-------- 1 root wheel 32M Jun 2 2018 .sujournal
drwxr-xr-x 4 root wheel 512B Jan 27 14:42 blockchain
Code:
ls -lh /nfs2/blockchain/
total 115620
-rw------- 1 root wheel 75B Jan 27 13:23 .cookie
-rw------- 1 root wheel 0B Jan 8 08:20 .lock
-rw------- 1 root wheel 37B Jan 8 08:20 banlist.dat
-rw------- 1 root wheel 5B Jan 27 13:23 bitcoind.pid
drwx------ 3 root wheel 116K Jan 27 09:38 blocks
drwx------ 2 root wheel 46K Jan 27 14:17 chainstate
-rw------- 1 root wheel 9.9M Jan 27 14:50 debug.log
-rw------- 1 root wheel 242K Jan 27 11:43 fee_estimates.dat
-rw------- 1 root wheel 98M Jan 27 11:43 mempool.dat
-rw------- 1 root wheel 4.0M Jan 27 14:42 peers.dat
Shouldn't I
chown -R bitcoin:bitcoin /nfs2/blockchain
to allow
bitcoind user and
bitcoind group to have write access?
Because when starting the machine if I check the
/etc/rc.conf file it does contain the properties this.
Code:
bitcoind_enable="YES"
bitcoind_user="bitcoin"
bitcoind_group="bitcoin"
bitcoind_conf="/usr/local/etc/bitcoin.conf"
So as the bitcoind daemon is run by the user and the bitcoin group and they do not have access to
/nfs2/blockchain which only has access for the user root and the wheel group, this one does not launch not.
I think I made a stupid mistake.