/ur/local/bin/bitcoind not found Ubuntu Desktop for Raspberry Pi4

[hypersex]

Hello.

I'm bumping this issue because I still have this issue with Bitcoin Core version 27, and I have tried everything mentioned here.

bicoin core release: bitcoin-27.0-aarch64-linux-gnu.tar.gz

When I try to execute the binaries

Code:

$ bitcoin-cli --version # same when trying to execute bitcoind and trying to execute directly from the /usr/local/bin folder
-bash: /usr/local/bin/bitcoin-cli: No such file or directory

I also tried @NotATether approach by cp -ra all files directly to /usr/local, and it still didn't work. FYI, this approach made the files be owned by my user, not by the root.

Code:

-rwxr-xr-x  1 pi pi  2150424 Apr 15 17:28 bitcoin-cli
-rwxr-xr-x  1 pi pi 40236344 Apr 15 17:28 bitcoin-qt
-rwxr-xr-x  1 pi pi  3928144 Apr 15 17:28 bitcoin-tx
-rwxr-xr-x  1 pi pi  1855064 Apr 15 17:28 bitcoin-util
-rwxr-xr-x  1 pi pi  8966416 Apr 15 17:28 bitcoin-wallet
-rwxr-xr-x  1 pi pi 14473240 Apr 15 17:28 bitcoind

Other information:

Code:

$ ldd /usr/local/bin/bitcoind
	not a dynamic executable

Code:

$ uname -a
Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux

I'm following this tutorial https://raspibolt.org/guide/bitcoin/bitcoin-client.html

I run out of ideas :\

Any suggestions?

Thank you

[1714938233]

1714938233

[1714938233]

1714938233

[achow101]

As the error suggests, the files are not in /usr/local/bin and so cannot be found to be executed. Make sure that they are there.

What commands have you specifically done in order to try to install the binaries, and what is their output?


This is an issue with your own installation, no new/alternate version of Bitcoin Core is going to fix this for you.

[hypersex]

As the error suggests, the files are not in /usr/local/bin and so cannot be found to be executed. Make sure that they are there.

What commands have you specifically done in order to try to install the binaries, and what is their output?


This is an issue with your own installation, no new/alternate version of Bitcoin Core is going to fix this for you.

I know that is my installation, but I don't know what I'm doing wrong.

The files are there, this output is from running ls -la inside /usr/local/bin

Code:

-rwxr-xr-x  1 pi pi  2150424 Apr 15 17:28 bitcoin-cli
-rwxr-xr-x  1 pi pi 40236344 Apr 15 17:28 bitcoin-qt
-rwxr-xr-x  1 pi pi  3928144 Apr 15 17:28 bitcoin-tx
-rwxr-xr-x  1 pi pi  1855064 Apr 15 17:28 bitcoin-util
-rwxr-xr-x  1 pi pi  8966416 Apr 15 17:28 bitcoin-wallet
-rwxr-xr-x  1 pi pi 14473240 Apr 15 17:28 bitcoind

The commands were:

Code:

$ tar -xvf bitcoin-$VERSION-aarch64-linux-gnu.tar.gz
$ sudo install -m 0755 -o root -g root -t /usr/local/bin bitcoin-27.0/bin/*

I also tried to copy all content from the tar.gz by running:

Code:

$ sudo install -m 0755 -o root -g root -t /usr/local bitcoin-27.0/*

But some folders were omitted. Then I try copying with

Code:

cp -ra bitcoin-27.0/* /usr/local

[achow101]

Try removing all of your install attempts from your system and start over from scratch. The first install command of just the bin/ directory should work.

Also check that you can execute any other binary that already exists in /usr/local/bin, and that you can run any of the binaries from where you've untar'd them before installing.

What is your PATH environment variable set to? Check it with

Code:

echo $PATH

 What do you get if you do

Code:

which bitcoind
which bitcoin-cli

[NotATether]

Code:

cp -ra bitcoin-27.0/* /usr/local

Permission issues can be resolved by using sudo before the command:

Code:

sudo cp -ra bitcoin-27.0/* /usr/local

but that won't solve the executable issue.

Try making bitcoind executable using chmod +x and see what happens when you run it.

Also post the output of:

Code:

file /usr/local/bin/bitcoind
stat /usr/local/bin/bitcoind

as LDD should not fail unless the file isn't actually a program.

It should say something like:

Code:

/usr/local/bin/bitcoind: ELF 64-bit LSB pie executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, stripped

[Cricktor]

My Raspibolt Pi doesn't have the file command installed, so I'm pasting here the results from my RaspiBlitz:

Code:

admin@192.168.178.119:~ ₿ which bitcoind
/usr/local/bin/bitcoind

admin@192.168.178.119:~ ₿ file /usr/local/bin/bitcoind
/usr/local/bin/bitcoind: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, stripped

admin@192.168.178.119:~ ₿ ldd /usr/local/bin/bitcoind
	linux-vdso.so.1 (0x0000007fa766a000)
	libpthread.so.0 => /lib/aarch64-linux-gnu/libpthread.so.0 (0x0000007fa683c000)
	libm.so.6 => /lib/aarch64-linux-gnu/libm.so.6 (0x0000007fa6791000)
	libgcc_s.so.1 => /lib/aarch64-linux-gnu/libgcc_s.so.1 (0x0000007fa676d000)
	libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x0000007fa65f7000)
	/lib/ld-linux-aarch64.so.1 (0x0000007fa763a000)

admin@192.168.178.119:~ ₿ ls -laF /usr/local/bin/bitcoind
-rwxr-xr-x 1 root root 14272536 Mar 17 18:45 /usr/local/bin/bitcoind*

My $PATH from my Raspibolt is:

Code:

admin@raspibolt:~ $ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games

[hypersex]

What is your PATH environment variable set to? Check it with

Code:

echo $PATH

 What do you get if you do

Code:

which bitcoind
which bitcoin-cli

Output

Code:

echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games

Code:

which bitcoind
/usr/local/bin/bitcoind

Code:

which bitcoin-cli
/usr/local/bin/bitcoin-cli

Also post the output of:

Code:

file /usr/local/bin/bitcoind
stat /usr/local/bin/bitcoind

as LDD should not fail unless the file isn't actually a program.

It should say something like:

Code:

/usr/local/bin/bitcoind: ELF 64-bit LSB pie executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, stripped

Output

Code:

file /usr/local/bin/bitcoind
/usr/local/bin/bitcoind: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, stripped

Code:

stat /usr/local/bin/bitcoind
  File: /usr/local/bin/bitcoind
  Size: 14473240  	Blocks: 28272      IO Block: 4096   regular file
Device: b302h/45826d	Inode: 131453      Links: 1
Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2024-05-02 21:16:02.485079758 +0100
Modify: 2024-05-02 21:16:02.533078916 +0100
Change: 2024-05-02 21:16:02.533078916 +0100
 Birth: 2024-05-02 21:16:02.485079758 +0100

I also created a small bash script into /usr/local/bin, and I was able to run

[achow101]

And it still does not work?

[hypersex]

And it still does not work?

no

[Cricktor]

@hypersex
My Raspibolt runs the same OS version. I'd assume that you followed the Raspibolt setup instructions and didn't mess up something. If you deviated from the instructions or made other changes that nobody here can know, I'd say: start over and don't mess things up.

What happens and is shown when you execute Core with an absolute path? Like this:

Code:

$ /usr/local/bin/bitcoind

Please, show the output of ls -laF /usr/local/bin

Code:

admin@raspibolt:~ $ ls -laF /usr/local/bin
total 89088
drwxr-xr-x  2 root root     4096 Jun  3  2023 ./
drwxr-xr-x 10 root root     4096 Apr  4  2022 ../
-rwxr-xr-x  1 root root  2080792 Jun  3  2023 bitcoin-cli*
-rwxr-xr-x  1 root root 38962464 Jun  3  2023 bitcoin-qt*
-rwxr-xr-x  1 root root  3743816 Jun  3  2023 bitcoin-tx*
-rwxr-xr-x  1 root root  1900120 Jun  3  2023 bitcoin-util*
-rwxr-xr-x  1 root root  8602152 Jun  3  2023 bitcoin-wallet*
-rwxr-xr-x  1 root root 13731856 Jun  3  2023 bitcoind*
-rwxr-xr-x  1 root root 22179600 Jun  3  2023 test_bitcoin*
admin@raspibolt:~ $ 

My executables file sizes will differ from yours as I haven't updated my Raspibolt's Bitcoin Core v25.0 yet. That shouldn't matter for you, I'm looking for other clues why you can't execute the files.


Just to get everything together: your executables are owned by user pi. Your files are world readable and executable, so trying to run them with another user account shouldn't matter, unless this user account has some weird restrictions. Did you tinker with some advanced settings like AppArmor or SELinux e.g.?

[NotATether]

And it still does not work?

no

Does it work when you extract the bitcoin core tarball to your home folder, run chown with your user and group, and try to run that bitcoind?

I mean, I doubt this will change anything, given that the file is world-executable, but its worth a shot.

Also try checking file output of other files in /usr/bin to make sure that they match with the one you got for bitcoind.