For those using 1.26.1 in production

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 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]

@Alexd1985 the node rebuild, did not correct this issue? Any ideas?

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/ line 44: cardano-node: command not found


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} \



cardano-node “${CPU_RUNTIME[@]}” run \

–topology “${TOPOLOGY}” \

–config “${CONFIG}” \

–database-path “${DB_DIR}” \

–socket-path “${CARDANO_NODE_SOCKET_PATH}” \

–port ${CNODE_PORT} \



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/ (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
chmod 755
. "${HOME}/.bashrc"

Edit again the env file

Then try to deploy again


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 ./ 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?

1 Like

Nope, I mean I don’t know …

1 Like

I think downloading the scripts and deploy again solve it… I am saying because I did only this today for my relay

1 Like