Thursday, May 30, 2024
HomeBitcoinbitcoin core - Bitcoind.service cannot begin on mounted drive

bitcoin core – Bitcoind.service cannot begin on mounted drive


I am a developer and I attempt to set up bitcoin-core 25.0 on ubuntu 22.04 on a mounted drive; so long as I run the command bitcoind -daemon as a root, every thing is okay and I can write some blocks within the mounted drive; nevertheless, after I create a consumer and even with all permission to the mounted drive, the bitcoind.service fails and I am unable to determine the difficulty as a result of the error is at all times (code=exited, standing=1/FAILURE) with no different trace to assist in that subject; if somebody has created such a situation, are you able to please help?

Here is my bitcoin.conf file:

server=1
rpcauth=btc:c59370cd87d42948326c2f7d33fd8060$2e23117d4a676f9fb39949c91fb2e966a38c6302570f8d242d945bdd61a2f367
txindex=1
addresstype=bech32
changetype=bech32
zmqpubhashblock=tcp://127.0.0.1:29000
zmqpubrawtx=tcp://127.0.0.1:29000
rpcssl=0

#Listing the place bitcoin retailer knowledge
datadir=/mnt/blockstorage

# UTXO database cache measurement, in MiB
dbcache=2048
# Variety of allowed pending RPC requests (default is 16)
rpcworkqueue=128

# What number of seconds bitcoin will wait for an entire RPC HTTP request.
# after the HTTP connection is established.
rpcclienttimeout=30

Here is my bitcoind.service

[Unit]
Description=Bitcoin daemon
Documentation=https://github.com/bitcoin/bitcoin/blob/grasp/doc/init.md

# https://www.freedesktop.org/wiki/Software program/systemd/NetworkTarget/
After=network-online.goal
Desires=network-online.goal

[Service]
ExecStart=/usr/native/bin/bitcoind -daemon 
                            -pid=/mnt/blockstorage/bitcoind.pid 
                            -conf=/root/.bitcoin/bitcoin.conf 
                            -datadir=/mnt/blockstorage 
                            -startupnotify='systemd-notify --ready' 
                            -shutdownnotify='systemd-notify --stopping'

# Be certain the config listing is readable by the service consumer
PermissionsStartOnly=true
#ExecStartPre=/bin/chgrp bitcoin /and many others/bitcoin

# Course of administration
####################

Sort=notify
NotifyAccess=all
PIDFile=/mnt/blockstorage/bitcoind.pid

Restart=on-failure
TimeoutStartSec=infinity
TimeoutStopSec=600

# Listing creation and permissions
####################################

# Run as bitcoin:bitcoin
Person=btc
Group=btc

# /run/bitcoind
RuntimeDirectory=bitcoind
RuntimeDirectoryMode=0710

# /and many others/bitcoin
ConfigurationDirectory=bitcoin
ConfigurationDirectoryMode=0710

# /var/lib/bitcoind
StateDirectory=bitcoind
StateDirectoryMode=0710

# Hardening measures
####################

# Present a personal /tmp and /var/tmp.
PrivateTmp=true

# Mount /usr, /boot/ and /and many others read-only for the method.
ProtectSystem=full

# Deny entry to /residence, /root and /run/consumer
ProtectHome=false

# Disallow the method and all of its youngsters to realize
# new privileges by way of execve().
NoNewPrivileges=true

# Use a brand new /dev namespace solely populated with API pseudo units
# comparable to /dev/null, /dev/zero and /dev/random.
PrivateDevices=true

# Deny the creation of writable and executable reminiscence mappings.
MemoryDenyWriteExecute=true

[Install]
WantedBy=multi-user.goal

Instructions line as an example varied folders and to view subject

root@node:~# df -h
Filesystem      Measurement  Used Avail Use% Mounted on
tmpfs           794M  1.2M  793M   1% /run
/dev/vda1        71G   66G  1.1G  99% /
tmpfs           3.9G     0  3.9G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/vdb1       1.6T  8.8G  1.5T   1% /mnt/blockstorage
tmpfs           794M  4.0K  794M   1% /run/consumer/0

root@node:~# ls /root/.bitcoin/
anchors.dat  banlist.json  bitcoin.conf  blocks  chainstate  debug.log  fee_estimates.dat  mempool.dat  friends.dat  settings.json  wallets

root@node:~# bitcoind -daemon
Bitcoin Core beginning
root@ashantix2:~# ls /mnt/blockstorage
banlist.json  bitcoind.pid  blocks  chainstate  debug.log  fee_estimates.dat  indexes  misplaced+discovered  mempool.dat  friends.dat  settings.json

root@node:~# systemctl daemon-reload
root@node:~# systemctl allow bitcoind.service
root@node:~# systemctl begin bitcoind.service
Job for bitcoind.service failed as a result of the management course of exited with error code.
See "systemctl standing bitcoind.service" and "journalctl -xeu bitcoind.service" for particulars.
root@node:~# systemctl standing bitcoind.service
× bitcoind.service - Bitcoin daemon
     Loaded: loaded (/and many others/systemd/system/bitcoind.service; enabled; vendor preset: enabled)
     Lively: failed (Outcome: exit-code) since Fri 2023-06-23 04:39:38 UTC; 16s in the past
       Docs: https://github.com/bitcoin/bitcoin/blob/grasp/doc/init.md
    Course of: 6205 ExecStart=/usr/native/bin/bitcoind -daemon -pid=/mnt/blockstorage/bitcoind.pid -conf=/root/.bitcoin/bitcoin.conf -datadir=/mnt/blockstorage -startupnotify=systemd-notify --r>
   Essential PID: 6205 (code=exited, standing=1/FAILURE)
        CPU: 112ms

Jun 23 04:39:38 node systemd[1]: Failed to begin Bitcoin daemon.
Jun 23 04:39:38 node systemd[1]: bitcoind.service: Scheduled restart job, restart counter is at 5.
Jun 23 04:39:38 node systemd[1]: Stopped Bitcoin daemon.
Jun 23 04:39:38 node systemd[1]: bitcoind.service: Begin request repeated too shortly.
Jun 23 04:39:38 node systemd[1]: bitcoind.service: Failed with outcome 'exit-code'.
Jun 23 04:39:38 node systemd[1]: Failed to begin Bitcoin daemon.

btc consumer permissions on the mounted drive

root@node:/mnt/blockstorage# ls -l
complete 23712
-rw------- 1 btc  btc        31 Jun 23 01:20 banlist.json
drwx------ 3 btc  btc     12288 Jun 23 04:44 blocks
drwx------ 2 btc  btc      4096 Jun 23 04:36 chainstate
-rw------- 1 btc  btc  23384304 Jun 23 04:44 debug.log
-rw------- 1 btc  btc    247985 Jun 23 02:16 fee_estimates.dat
drwx------ 3 btc  btc      4096 Jun 23 01:20 indexes
drwx------ 2 btc  btc     16384 Jun 22 21:45 misplaced+discovered
-rw------- 1 btc  btc        18 Jun 23 02:16 mempool.dat
-rw------- 1 btc  btc    591159 Jun 23 02:16 friends.dat
-rw------- 1 root root        4 Jun 23 04:36 settings.json

I’ve spent nearly every week making an attempt to determine this out as a result of I do not perceive why I am unable to get the bitcoind.service to begin correctly.

Please help

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments