raspiblitz: Bitcoind: Can't open PID from file

Fresh 1.6.2 install with LND recovered from backup. Bitcoind is active but it isn’t syncing, get Failed to parse PID from file and after service restart get Can't open PID from file as shown in the below status output:

● bitcoind.service - Bitcoin daemon
   Loaded: loaded (/etc/systemd/system/bitcoind.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2020-12-23 12:20:38 GMT; 1min 32s ago
  Process: 10999 ExecStartPre=/home/admin/config.scripts/blitz.systemd.sh log blockchain STARTED (code=exited, status=0/
  Process: 11001 ExecStart=/usr/local/bin/bitcoind -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf -pid=/home/bitcoin/
 Main PID: 11002 (bitcoind)
    Tasks: 18 (limit: 4915)
   Memory: 199.2M
   CGroup: /system.slice/bitcoind.service
           └─11002 /usr/local/bin/bitcoind -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf -pid=/home/bitcoin/.bitcoin

Dec 23 12:20:38 raspberrypi systemd[1]: Starting Bitcoin daemon...
Dec 23 12:20:38 raspberrypi systemd[1]: bitcoind.service: Can't open PID file /home/bitcoin/.bitcoin/bitcoind.pid (yet?)
Dec 23 12:20:38 raspberrypi systemd[1]: Started Bitcoin daemon.
$ ls -l /home/bitcoin/.bitcoin/
total 324
-rw------- 1 bitcoin bitcoin     37 Dec 22 20:22 banlist.dat
-r--r--r-- 1 root    root       854 Dec 22 23:56 bitcoin.conf
-rw------- 1 bitcoin bitcoin      5 Dec 24 08:43 bitcoind.pid
drwx------ 1 bitcoin bitcoin 114010 Dec 21 16:33 blocks
drwx------ 1 bitcoin bitcoin  48572 Dec 24 08:43 chainstate
-rw------- 1 bitcoin bitcoin   6877 Dec 24 08:49 debug.log
-rw------- 1 bitcoin bitcoin 247985 Dec 23 15:30 fee_estimates.dat
-rw------- 1 bitcoin bitcoin     17 Dec 23 15:30 mempool.dat
-rw------- 1 bitcoin bitcoin    820 Dec 24 08:43 onion_private_key
-rw------- 1 bitcoin bitcoin  49552 Dec 23 15:30 peers.dat

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 25 (8 by maintainers)

Commits related to this issue

Most upvoted comments

@jodobear delete those files and do restart should be fine.

We are using: KillMode=process in the systemd service files which is not recommended and can cause leftover subrocesses likely causing this issue.

https://www.man7.org/linux/man-pages/man5/systemd.kill.5.html

Will remove all the KillMode= entries so it defaults to control-group.

@openoms Thank you, you are great … Node is syncing… actually I had ordered a pre-synced RaspiBlitz … but what the heck

Bildschirmfoto 2021-05-12 um 22 20 55

We are keeping this issue open because it has a pending PR #1930 … but moving it to next release because the fix would be to cloase to final realease of v1.6.3 to include.

@openoms do you see any downsides to remove the PID file from the system service? PR #1930 up for discussion

PR #1902 merged … this should delete the blocking file on boot. Will be part of v1.6.3 release - closing issue.