Retire Pool gets stuck on last step

Staking & Delegation Setup a Stake Pool
1

Hi,

I am trying to retire my pool for several times now and I always face the same problem at the same place.

I am following Coincashew tutorial:

I manage to go through every step but on the last command:

cardano-cli transaction submit \
    --tx-file tx.signed \
    --mainnet

It hangs and I don’t get any feedback

Screen Shot 2021-10-08 at 21.19.13
Screen Shot 2021-10-08 at 21.19.131052×112 29 KB

Could you please guide me on what could it be?

Thanks!

2

If your node fully synced?

3

Regarding node sync check you can execute cardano-cli query tip --mainnet and check syncProgress.

4

You guys are right! This is the output after running cardano-cli query tip --mainnet

{
    "epoch": 289,
    "hash": "e72579f...",
    "slot": 39916796,
    "block": 6236059,
    "era": "Mary"
}
```
Could you guys let me know how do I sync the nodes? 

Thank you guys!
5

What version are you running?

cardano-cli --version
cardano-node --version
6

I am running cardano-node 1.27.0.

cardano-node 1.27.0 - linux-x86_64 - ghc-8.10

7

The latest version will give you syncProgress when running the command above.

Since the Alonso hard fork (Sep 12th) 1.27.0 is outdated.

You need to upgrade to the latest version 1.30.1 as soon as possible.

8

I could make it on 1.30.1, in case you can’t update as suggested.

9

Okay then first I’ll need to upgrade the versions, currently I am trying to upgrade to 1.30.1 by following these instructions:

But on the “last” step

journalctl --unit=cardano-node --follow

i’m getting the following error:

[relay2:cardano.node.ChainDB:Info:5] [2021-10-10 13:45:45.51 UTC] Closed db with immutable tip at fd6a583393c23911b2eb2b7734ec4d17a69a381b9ac533772b989e87e98cc452 at slot 39874230 and tip e72579ff89dc9ed325b723a33624b596c08141c7bd573ecfff56a1f7229e4d09 at slot 39916796

Oct 10 13:46:33 relay2 cardano-node[30644]: AesonException "Error in $: key \"AlonzoGenesisFile\" not found"

Any ideas how can i fix this error?

10

Read also the 1.29.0 upgrade instructions as there were some configuration parameters added. You cannot upgrade from 1.27.0 to 1.30.1 without adding parameters that were part of 1.29.0.