./env: line 323: /root/.cabal/bin/cardano-cli: No such file or directory
Failed to query protocol-parameters from node, not yet fully started?
./env: line 323: /root/.cabal/bin/cardano-cli: No such file or directory
Node status is running,
gLive status: starting
started
./env: line 323: /root/.cabal/bin/cardano-cli: No such file or directory
Failed to query protocol-parameters from node, not yet fully started?
./env: line 323: /root/.cabal/bin/cardano-cli: No such file or directory
Failed to query protocol-parameters from node, not yet fully started?
sleeping for 10s and testing againâŚ
So the problem is in automatic detection of path to cardano-cli executable?
It seems that installing cncli via readme from github somehow screwed that.
# Install & Automate CNCLI
## Installation
You can install CNCLI using either the release binaries or compiling the Rust code. Both installation examples hereby illustrated are instructions for an Ubuntu Linux server and use standard system paths from the Linux [File System Hierarchy Standard](https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard).
### Install the binary release
To install CNCLI from a binary release, download the [latest release](https://github.com/AndrewWestberg/cncli/releases) and extract it in the ```/usr/local/bin/``` directory of the ```block producing node``` server of your stake pool. Adjust the ```<latest_release_version>``` variable in the command to the latest release available:
```bash
curl -sLJ https://github.com/AndrewWestberg/cncli/releases/download/v<latest_release_version>/cncli-<latest_release_version>-x86_64-unknown-linux-gnu.tar.gz -o /tmp/cncli-<latest_release_version>-x86_64-unknown-linux-gnu.tar.gz
```
```bash
tar xzvf /tmp/cncli-<latest_release_version>-x86_64-unknown-linux-gnu.tar.gz -C /usr/local/bin/
```
### Compile from source
This file has been truncated. show original
yes, the path is the problem⌠check if u have the files here:
cd ${HOME}/.cabal/bin/ â check if u have the cardano-cli file
cd ${HOME}/.cargo/bin/ â check if u have the cncli file
then check the bash ⌠if has the correct path:
nano or cat ${HOME}/.bashrc
/opt/cardano/cnode/scripts$ cd ${HOME}/.cabal/bin/
~/.cabal/bin$ ls
bech32 cardano-address cardano-cli cardano-node cardano-node-chairman cardano-ping cardano-submit-api cardano-topology db-analyser db-converter tracer-transfomers-example1 tracer-transfomers-example2
~/.cabal/bin$ cd ${HOME}/.cargo/bin/
~/.cargo/bin$ ls
cargo cargo-clippy cargo-fmt cargo-miri clippy-driver cncli rls rust-gdb rust-lldb rustc rustdoc rustfmt rustup
At the end of .bashrc:
[ -f â/home/user/.ghcup/envâ ] && source â/home/user/.ghcup/envâ # ghcup-env
export CNODE_HOME=/opt/cardano/cnode
source â$HOME/.cargo/envâ
âexport PATH=/home/user/.cabal/bin:/home/user/.cargo/bin:/home/user/.cabal/bin:/home/user/.ghcup/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/binâ
I have only this
[ -f â/home/test/.ghcup/envâ ] && source â/home/test/.ghcup/envâ # ghcup-env
export CNODE_HOME=/opt/cardano/cnode
export CARDANO_NODE_SOCKET_PATH=/db/socket
source â$HOME/.cargo/envâ
try to bkp in notepad⌠and remove the last line
this line :
âexport PATH=/home/user/.cabal/bin:/home/user/.cargo/bin:/home/user/.cabal/bin:/home/user/.ghcup/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/binâ
Removed, but still the sameâŚ
Maybe the problem is in export PATH duplicate entriesâŚ
but how are now the lines in env? try this way, or try both uncommented or commented
#CCLI="${HOME}/.cabal/bin/cardano-cli" # Override automatic detection of path to cardano-cli executable
CNCLI="${HOME}/.cargo/bin/cncli" # Override automatic detection of path to cncli executable (GitHub - AndrewWestberg/cncli: A community-based cardano-node CLI tool )
also run this command:
. â${HOME}/.bashrcâ - replace the " from your keyboard, the forum change the format
Uncomented CNCLI in env,
and run . â${HOME}/.bashrcâ
but still the sameâŚ
. â${HOME}/.bashrcâ
Command ââexportâ not found, did you mean:
command âmexportâ from deb mblaze (0.6-1)
Try: sudo apt install
try to substitute $HOME
with /home/user
I think when the script executed it will be /root/ instead of /home/user
likely your user is not the root
3 Likes
good catch⌠I thought he edited the user. to not show to the public :), as I did
but after all of these tests u need to check the node, if itâs starting again
1 Like
Thank You guys, its working nowâŚ
The node is restarting ok.
1 Like
happy for you, what was the solution? share it with us
laplasz:
$HOME
with /home/user
replacing $HOME
with /home/user
in env
perfect, mark it as the solution, cheers.
1 Like
yes, but the problem was with $HOME env variable - probably the nodes started as a service and there the user is root in that case and the $HOME for it is /root. Maybe it is possible to define different acting user from root for a service - I am not familiar with servicesâŚ
1 Like