@Alexd1985 : Thank you sir!
Yes! That was it. I launched the services again with âdeploy-as-systemd.shâ and that solved it. I can see the timers now with âsystemctl list-timers --allâ. Node is now onboarding in topologyUpdater. Thanks!
My issue was resolved simply by giving the node more time to start up for the first time after the update to 1.29.0. Everything is running great and we produced a block last night. Thanks for all of your help @Alexd1985
2 Likes
what is the best home server configuration with a xeon? and memory for the future?
Hi all, I seen to be missing the cabal-build-all.sh files from both my nodes? How can I get them?
donât you have the file inside scripts folder?
Hi Alex, thanks for sharing the update process. For some reason I get stuck here, when running
echo -e "package cardano-crypto-praos\n flags: -external-libsodium-vrf" > cabal.project.local
$CNODE_HOME/scripts/cabal-build-all.sh
or
$CNODE_HOME/scripts/cabal-build-all.sh -l
No itâs missing for some reason âŚ
Ooo u must wait⌠it will take a while
Run again prereqs.sh
cd ~/tmp
./prereqs.sh -f
I donât seem to have the tmp directory either??
Thanks Alex, do you know why Iâm getting thisâŚ
Did u ran the command with -l ?
$CNODE_HOME/scripts/cabal-build-all.sh -l
I did indeed, this happened with both with the -l and also using the original version you posted, with the echo line.
Did I have to update the scripts in the scripts folder before running the command?
Did u ran prereqs first?
ahh, no let me try that
When you are building it or when it is running?
When itâs runningâŚ
That seems a bit extreme - shall we consider that all previous guides mentioning that 8Gb is enough to build and 4Gb is enough to run, are now outdated and whoever already runs the node on the lower memory has to upgrade RAM asap?
U can run with ~4,4G RAM if u set the TraceMempool to false