Ok, I guess u already downloaded the new scripts with prereqs.sh -f
then please try:
- copy the bin folder from another node to this one
- rebuild the node
Oh, I didnât update another node to 1.30.1 yet.
And the issue Iâm running into is why, in case something breaks.
Ok, rebuild the node; this is the relay?
Yes, this is the relay. When you say rebuild the node, do you mean the cabal command
$CNODE_HOME/scripts/cabal-build-all.sh -o ?
Yes, run again the comand⌠or⌠can u try first to delete the immutable, ledger and volatile files from db folder? and restart the node? Perhaps the db is corrupted
sudo rm -R immutable
Itâs resyncing now but last time it got stuck at 95.3%
Ok, now⌠copy the db from another node which is running
stop the node
go to db folder
then connect to another up and running node
sftp -P (ssh_port) username@IP
navigate to db folder
cd /opt/cardano/cnode/db
ls -l
get -R immutable (this will take ~30 min or more)
get -R ledger
get -R volatile
after this exit and start the node, now it should start in ~15 min
1 Like
Both my relay and bp kept stuck on starting as well. After updating to 1.30.1
Also deleted: immutable, ledger and volatile in the db folder.
But did not know that both nodes now have to sync from epoch 1 to the current epoch, this will take approx. 16 hours right? ;p
Hopefully the problem will be fixed after the process is done.
Btw, Alex do you know it has to do something with 1.30.1, is there some bug in it or so? Because I see a lot of SPOâs struggling with the same problem.
Cheers.
Only PO which used another guide before mine⌠and also to speed up the sync process u can copy the files from another synced node
Hello, I have a problem since installing the update I have an error COULD NOT CONNECT TO A RUNNING INSTANCE, 3 FAILED ATTEMPTS IN A ROW! when I run ./gLiveView.sh. How to solve this problem? Thanks in advance for your help
first, check if your node is up and runningâŚ
try journalctl -e -f -u cnode
Hello, I have solved my problem, thanks anyway for your help Alexd1985
1 Like
Hi Alex,
Shouldnât there be a â-lâ flag to âcabal-build-all.shâ to ensure that it uses the right version of libsodium?
Thanks!
TBH I donât know but feel free to add your knowledge 
I canât remember where I read it originally, but
guild-operators/cabal-build-all.sh at alpha ¡ cardano-community/guild-operators ¡ GitHub
suggests that this flag is needed to ensure the use of the correct (IOG forked?) libsodium. I used this on previous builds and it worked, so Iâm assuming it will here 
Possibly not needed!
TBH I never used it, perhaps should be used if you have more libsodium versions
tnx, trying it now
1 Like
Next question
When should I update CNTools? After rebuilding and installing? I tried to do it via gLiveView.sh, first saying âyesâ to ânew envâ, but after that it doesnât give the option to update the other scripts, and wonât subsequently load.
cntools will request to update when u will access it, if there are updates available
glive not= cntools