Topic: bitcoind: command not found (Read 353 times)

UPD

export LD_LIBRARY_PATH=/usr/local/lib:/usr/lib:/usr/local/lib64:/usr/lib64

./b2 install --prefix=/opt/boost --with=all

done

As I already said, it is because the ./configure  command failed with an error (check the log output above).

The error says your version of GCC compiler is too old. If you are on CentOS 7 it is probably 4.8.5. This is a really old version of GCC.

As I also said above, you need to download and install a newer version of GCC.

wget https://www.mirrorservice.org/sites/sourceware.org/pub/gcc/releases/gcc-8.5.0/gcc-8.5.0.tar.gz
tar zxf gcc-8.5.0.tar.gz
cd gcc-8.5.0
yum -y install bzip2
./contrib/download_prerequisites
./configure --disable-multilib --enable-languages=c,c++
make -j 2
make install

why doesn't this work?


[root@localhost bitcoin]# make
make: *** No targets specified and no makefile found.  Stop.
[root@localhost bitcoin]# sudo make install
make: *** No rule to make target `install'.  Stop.

It means you are using too old version of gcc compiler. Run GCC --version, you must have at least version 8 to have C++ 17 support.

If you are on Ubuntu you can run: apt-get install gcc-8 g++-8.

On CentOS it is a little more difficult and you need to install GCC from source.

From https://linuxhostsupport.com/blog/how-to-install-gcc-on-centos-7/:

Then you can run the Bitcoin Core build process again.

[root@localhost bitcoin]# make
make: *** No targets specified and no makefile found.  Stop.
[root@localhost bitcoin]# sudo make install
make: *** No rule to make target `install'.  Stop.


why ?

wget https://www.mirrorservice.org/sites/sourceware.org/pub/gcc/releases/gcc-8.5.0/gcc-8.5.0.tar.gz
tar zxf gcc-8.5.0.tar.gz
cd gcc-8.5.0
yum -y install bzip2
./contrib/download_prerequisites
./configure --disable-multilib --enable-languages=c,c++
make -j 2
make install

I believe so... this guide (which essentially follows the same flow of make and sudo make install says in the "Extra Guidance" section:


Ideally, as they suggest, you should probably rename the folder initially to something like "bitcoin-OLD", rather than deleting it... so if anything goes wrong, you can simply change the folder name back and you should still have it.

[root@localhost bitcoin]# git checkout tags/v22.0
Note: checking out 'tags/v22.0'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at a098814... Merge bitcoin/bitcoin#22921: Some small improvements to release notes
You have mail in /var/spool/mail/root
[root@localhost bitcoin]# ./autogen.sh
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `build-aux'.
libtoolize: copying file `build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `build-aux/m4'.
libtoolize: copying file `build-aux/m4/libtool.m4'
libtoolize: copying file `build-aux/m4/ltoptions.m4'
libtoolize: copying file `build-aux/m4/ltsugar.m4'
libtoolize: copying file `build-aux/m4/ltversion.m4'
libtoolize: copying file `build-aux/m4/lt~obsolete.m4'
configure.ac:45: installing 'build-aux/config.guess'
configure.ac:45: installing 'build-aux/config.sub'
configure.ac:28: installing 'build-aux/install-sh'
configure.ac:28: installing 'build-aux/missing'
Makefile.am: installing 'build-aux/depcomp'
parallel-tests: installing 'build-aux/test-driver'
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `build-aux'.
libtoolize: copying file `build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `build-aux/m4'.
libtoolize: copying file `build-aux/m4/libtool.m4'
libtoolize: copying file `build-aux/m4/ltoptions.m4'
libtoolize: copying file `build-aux/m4/ltsugar.m4'
libtoolize: copying file `build-aux/m4/ltversion.m4'
libtoolize: copying file `build-aux/m4/lt~obsolete.m4'
configure.ac:32: installing 'build-aux/compile'
configure.ac:5: installing 'build-aux/config.guess'
configure.ac:5: installing 'build-aux/config.sub'
configure.ac:9: installing 'build-aux/install-sh'
configure.ac:9: installing 'build-aux/missing'
Makefile.am: installing 'build-aux/depcomp'
parallel-tests: installing 'build-aux/test-driver'
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `build-aux'.
libtoolize: copying file `build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `build-aux/m4'.
libtoolize: copying file `build-aux/m4/libtool.m4'
libtoolize: copying file `build-aux/m4/ltoptions.m4'
libtoolize: copying file `build-aux/m4/ltsugar.m4'
libtoolize: copying file `build-aux/m4/ltversion.m4'
libtoolize: copying file `build-aux/m4/lt~obsolete.m4'
configure.ac:38: installing 'build-aux/config.guess'
configure.ac:38: installing 'build-aux/config.sub'
configure.ac:48: installing 'build-aux/install-sh'
configure.ac:48: installing 'build-aux/missing'
src/Makefile.am: installing 'build-aux/depcomp'
parallel-tests: installing 'build-aux/test-driver'
You have mail in /var/spool/mail/root
[root@localhost bitcoin]# export BDB_PREFIX='/home/code/bitcoin/db4'
[root@localhost bitcoin]# ./configure BDB_LIBS="-L${BDB_PREFIX}/lib -ldb_cxx-4.8" BDB_CFLAGS="-I${BDB_PREFIX}/include"
checking for pkg-config... /bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... (cached) yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking whether g++ supports C++17 features with -std=c++17... no
checking whether g++ supports C++17 features with +std=c++17... no
checking whether g++ supports C++17 features with -h std=c++17... no
checking whether g++ supports C++17 features with -std=c++1z... no
checking whether g++ supports C++17 features with +std=c++1z... no
checking whether g++ supports C++17 features with -h std=c++1z... no
configure: error: *** A compiler with support for C++17 language features is required.
You have mail in /var/spool/mail/root
[root@localhost bitcoin]# make
make: *** No targets specified and no makefile found.  Stop.
[root@localhost bitcoin]# sudo make install
make: *** No rule to make target `install'.  Stop.
[root@localhost bitcoin]# bitcoin-qt &
[1] 10512
[root@localhost bitcoin]# -bash: bitcoin-qt: command not found

[1]+  Exit 127                bitcoin-qt
[root@localhost bitcoin]# bitcoind
-bash: bitcoind: command not found

Does it apply if you install compile Bitcoin Core from source code and install using command sudo make install? Because that's what script (which mentioned by OP) do.

How To Recompile/Update Bitcoin Core

Recompiling Bitcoin Core and updating Bitcore Core are essentially the same procedure. We’re going to delete or rename the Bitcoin install directory, and then just reinstall Bitcoin all over again with the newer version.

how to uninstall the old Bitcoin Core version?

On the first line of your script:

https://gist.github.com/cdljsj/180e705fad8647590ee0ecc1f6182f43

Change BITCOIN_TAG="v0.18.0" to BITCOIN_TAG="v22.0", and uninstall the old Bitcoin Core version and run it again.

entered the command
export PATH = "/ opt / bitcoin-v0.16.1 / bin /: $ {PATH}" >> ~ / .bashrc
then fixed bitcoin.conf to / opt / ...
[root @ localhost ~] # bitcoind
Bitcoin server starting

thank you .
 

about the update, do not tell me the instructions for the correct update of the client on centos?

running version 0.16.1 :/

In this case, it is not necessary. [You only need to do that if you want to make bitcoind installed in /usr folder instead of /opt/bitcoin-v0.16.1]

I believe your bitcoind is installed in /opt/bitcoin-v0.16.1/bin/ .

So you just need to add that folder to your "PATH" environment variable.

By the way, 0.16 is quite an old version, shouldn't you install the latest 22.0 version instead?

Wouldn't it be correct to uninstall and reinstall everything so that there are no such problems in the future?

Make sure that bitcoind is in your PATH environment variable and restart the shell (by restarting the operating system or running a new "bash" shell).

I can't think what's the problem, the permission/owner-ship is correct and the symbolic link seems fine. If you don't mind shortcut (rather than neat solution), try adding /opt/bitcoin-v0.16.1/bin/ to your $PATH.

Looks alright, how about /home/bitcoind/bitcoind/bin/?

[root@localhost ~]# ls -lha /usr/bin | grep bitcoin
lrwxrwxrwx.   1 root root       39 oкт 15  2018 bitcoin-cli -> /home/bitcoind/bitcoind/bin/bitcoin-cli
lrwxrwxrwx.   1 root root       36 oкт 15  2018 bitcoind -> /home/bitcoind/bitcoind/bin/bitcoind

Can you run this command to see whether bitcoind is exist on /usr/bin with correct permission?


P.S. if the result is empty, it means bitcoind isn't exist on /usr/bin

Yep as @HCP suspects, the bitcoind binary isn't on your PATH. But since the bitcoind binary is located on /usr/bin/ I think somehow your whole Bash PATH is misconfigured, the location should be listed as default Bash PATH. Try to run "echo $PATH", the output should be like:


Anyway, as a temporary fix run below command:

After that, you probably now can run the bitcoind command. Try to check its version by running bitcoind --version.

sudo ln -s /opt/bitcoin-v0.16.1/bin/bitcoind /usr/bin/bitcoind
[root@localhost bin]# sudo ln -s /opt/bitcoin-v0.16.1/bin/bitcoind /usr/bin/bitcoind
ln: нe yдaлocь coздaть cимвoльнyю ccылкy «/usr/bin/bitcoind»: Фaйл cyщecтвyeт
could not create symlink '/ usr / bin / bitcoind': File exists

sudo ln -s /opt/bitcoin-${BITCOIN_TAG}/bin/bitcoin-cli /usr/bin/bitcoin-cli
same as above

how exactly did you "update" bitcoin core? It sounds like the location of the bitcoind binary is no longer included in your PATH.

Do you know where the bitcoind binary is located?

in processes pid 4261 bitcoin launched

decided to update to 0.21.1

Can you try this command?


Or go to the directory where your bitcoind is installed then open the terminal on that directory then use that command again.

If it doesn't work use this command

Then try the above command again.