Did u managed to solve it?
There is nothing special you need to do. I upgraded two BPs and had no issues at all. Back up your folders just in case, but I think the issue the first poster had appears to be a fluke and not common. Upgrade was seamless for me.
Hi thanks for checking in - not yet (late night) but in setting up another server I noticed that there were extra " in the bashrc file. So Iâm back on my original BP trying to rebuild it now (new BP only 27% synced overnight).
I think that might be causing issues with variables in this not (from cnode.sh) resolving:
Usage: cardano-node run [âtopology FILEPATH] [âdatabase-path FILEPATH]
[âsocket-path FILEPATH]
[âbyron-delegation-certificate FILEPATH]
[âbyron-signing-key FILEPATH]
[âshelley-kes-key FILEPATH]
[âshelley-vrf-key FILEPATH]
[âshelley-operational-certificate FILEPATH]
[âbulk-credentials-file FILEPATH] [âhost-addr IPV4]
[âhost-ipv6-addr IPV6] [âport PORT]
[âconfig NODE-CONFIGURATION] [âvalidate-db]
What message are u seeing?
It doesnât like the ârunâ
journalctl -e -f -u cnode.service
Hint: You are currently not seeing messages from other users and the system.
Users in groups âadmâ, âsystemd-journalâ can see all messages.
Pass -q to turn off this notice.
â Logs begin at Fri 2021-01-08 00:18:15 UTC. â
Apr 08 19:08:07 PRODUCER cnode[217038]: /opt/cardano/cnode/scripts/cnode.sh: line 44: cardano-node: command not found
if [[ -f â${POOL_DIR}/${POOL_OPCERT_FILENAME}â && -f â${POOL_DIR}/${POOL_VRF_SK_FILENAME}â && -f â${POOL_DIR}/${POOL_HOTKEY_SK_FILENAME}â ]]; then
cardano-node â${CPU_RUNTIME[@]}â run \
âtopology â${TOPOLOGY}â \
âconfig â${CONFIG}â \
âdatabase-path â${DB_DIR}â \
âsocket-path â${CARDANO_NODE_SOCKET_PATH}â \
âshelley-kes-key â${POOL_DIR}/${POOL_HOTKEY_SK_FILENAME}â \
âshelley-vrf-key â${POOL_DIR}/${POOL_VRF_SK_FILENAME}â \
âshelley-operational-certificate â${POOL_DIR}/${POOL_OPCERT_FILENAME}â \
âport ${CNODE_PORT} \
â${host_addr[@]}â
else
cardano-node â${CPU_RUNTIME[@]}â run \
âtopology â${TOPOLOGY}â \
âconfig â${CONFIG}â \
âdatabase-path â${DB_DIR}â \
âsocket-path â${CARDANO_NODE_SOCKET_PATH}â \
âport ${CNODE_PORT} \
â${host_addr[@]}â
fi
sudo systemctl status cnode
cardano-node - -version
cardano-cli - -version
cardano-node --version
cardano-node 1.26.1 - linux-x86_64 - ghc-8.10
git rev 3c556c5b09811c159dc7a92021f4d1c6aac3a104
cardano-cli --version
cardano-cli 1.26.1 - linux-x86_64 - ghc-8.10
git rev 3c556c5b09811c159dc7a92021f4d1c6aac3a104
sudo systemctl status cnode
â cnode.service - Cardano Node
Loaded: loaded (/etc/systemd/system/cnode.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2021-04-08 20:43:43 UTC; 682ms ago
Process: 410362 ExecStart=/bin/bash -l -c exec /opt/cardano/cnode/scripts/cnode.sh (code=exited, status=127)
Main PID: 410362 (code=exited, status=127)
Apr 08 20:43:43 PRODUCER systemd[1]: cnode.service: Main process exited, code=exited, status=127/n/a
Apr 08 20:43:43 PRODUCER systemd[1]: cnode.service: Failed with result âexit-codeâ.
Ok⌠go to ⌠cd opt/cardano/cnode
ls -l
and delete the scripts folder (should be only scripts insinde)
sudo rm -R scripts
then run prereq again (it will download all scripts folder again)
cd "$HOME/tmp"
curl -sS -o prereqs.sh https://raw.githubusercontent.com/cardano-community/guild-operators/master/scripts/cnode-helper-scripts/prereqs.sh
chmod 755 prereqs.sh
./prereqs.sh
. "${HOME}/.bashrc"
Edit again the env file
Then try to deploy again
./deploy-as-systemd.sh
sudo systemctl restart cnode
sudo systemctl status cnode
Doing now⌠note after running after a delete of scripts, then:
. â${HOME}/.bashrcâ
Command ââexportâ not found, did you mean:
command âmexportâ from deb mblaze (0.6-1)
Try: sudo apt install
Itâs ok, should be
THought it might have been erroring on these quotes in the bashrc file that donât look right to me
OK - after editing out those quotes - and re-running ./deploy-as-systemd.sh etc, we finally have a successful start!!
Note - I ran through those steps (including .cabal build) about 10 times last night (Not deleting the scripts folder). So unsure of root cause, but at least we are back! Again @Alexd1985 so appreciative of your help, and hope this can assist anyone else that gets in a mess somehow?
I still would like to know if those quotes are intended / corrupting the bashrc file?
Nope, I mean I donât know âŚ
I think downloading the scripts and deploy again solve it⌠I am saying because I did only this today for my relay