Hi! I built my node with the executable file of linux, how can I upgrade my node?
Thank you, Alexd! The first of my nodes updated successfully. Awaiting official IOHK word on Telegram before upgrading the rest. Cheers! 
1 Like
@Alexd1985 just to confirm, for testnet pool, instead of mainnet-alonzo-genesis.json, I must download from below URL ?
https://hydra.iohk.io/build/7416228/download/1/testnet-alonzo-genesis.json
Also below hash value to be specified inside config.json might also need to be changed ? how to calculate the same for testnet-alonzo-genesis.json ?
āAlonzoGenesisHashā: ā7e94a15f55d1e82d10f09203fa1d40f8eede58fd8066542cf6566008068ed874ā,
My producer restarted after the update as relay? Do I need to run this command again?
./deploy-as-systemd.sh
Doesnāt started yet (saying starting), how it looks now?
Iām having the same issue as Seshat. After updating, my core node is stuck on startingā¦ Any idea how to get it started?
Its the same with no connections either. I should say this morning it was having issues as well, so was one of the relays. The update fixed the relay and all looks good there. The update fixed the producer enough to allow gliveview to run, but no connections.
Aug 31 21:53:08 producer1 systemd[1]: Stopping Cardano Nodeā¦
Aug 31 21:53:13 producer1 systemd[1]: cnode.service: State āstop-sigtermā timed out. Killing.
Aug 31 21:53:13 producer1 systemd[1]: cnode.service: Killing process 8940 (bash) with signal SIGKILL.
Aug 31 21:53:13 producer1 systemd[1]: cnode.service: Killing process 9008 (cardano-node) with signal SIGKILL.
Aug 31 21:53:13 producer1 systemd[1]: cnode.service: Main process exited, code=killed, status=9/KILL
Aug 31 21:53:13 producer1 systemd[1]: cnode.service: Killing process 9008 (cardano-node) with signal SIGKILL.
Aug 31 21:53:13 producer1 systemd[1]: cnode.service: Failed with result ātimeoutā.
Aug 31 21:53:13 producer1 systemd[1]: Stopped Cardano Node.
Aug 31 21:53:13 producer1 systemd[1]: Started Cardano Node.
Aug 31 21:53:14 producer1 cnode[23715]: Listening on http://127.0.0.1:12798
Update: The relay is now showing 0 connections in or out. It was running fine an hour ago after the update.
Both servers have been up and running for months and produced a block. No settings have been changed since then. This morning they were both having issues. Relay #2 on 1.27 is still up and running fine
1 Like
Strangeā¦ can u run manually ./topology_Updater.sh script and check what is the message (for relay only)? Also the topology file looks ok on Relay or Producer?
Checking for script updatesā¦
{ āresultcodeā: ā502ā, ādatetimeā:ā2021-08-31 23:01:47ā, āclientIpā: ā34.136.xxx.xxxā, āmsgā: āinvalid blockNo [0]ā }
I have checked and rechecked the topology file on the producer.
Iām having the exact same issue as Seshat
I updated two relays and all went well, but since I updated my BP node it is stuck on āstartingā¦ā.
1.27.0 ran flawlessly for months before upgrading to 1.29.0
The problem I think are the relays, try for Producer to add IOHK (delete relays) nodes inside the topology File and restart the node
{
"Producers": [
{
"addr": "relays-new.cardano-mainnet.iohk.io",
"port": 3001,
"valency": 2
}
]
}
Does it start?
I deleted my relays in topology.json and replaced them with IOHK but the node still isnāt starting.
wait more timeā¦
as you can see my nodes are fine with 1.29.0
how are your relays? are synced?
Same for meā¦
Perhaps its nothing but I do want to say prior to this my Producer was connected to my Relay #1 using a internal to GCP address. Come to think of it my firewall rules would block anything but that address. This test could never work for me with the firewall rules set the way they are.
indeed, but show me your relays glive output
ok, no type nano topology_Updater.sh and show me the first 10 lines