KES keys expired - trouble rotating

cpu is running around ~0.5%

glive is still at the “Starting…” status for the last 45mins

also cntools still says the KES keys have expired even after rotating, this could maybe the main issue as our pool is only just a month old

Forget about KES warning, the node doesn’t started

type sudo systemctl status cnode

ok says the node is active and running

Show me the output, what is the output for sudo systemctl status cnode?

also type nano ${HOME}/.bashrc and show me the last lines… the lines with export…


putty_1IQlXVkqRB

Ok, now… go to the topology file, delete the relay from there and add the IOHK nodes


{
  "Producers": [
    {
      "addr": "relays-new.cardano-mainnet.iohk.io",
      "port": 3001,
      "valency": 2
    }
  ]
}

Save the file and restart the node, how is the CPU now?

putty_v4X7pUYBRF

so far the highest I’ve seen is 1%

Do u have teams?

no I don’t

Can u show me the env file?

actually just got teams up if you prefer using that, here’s a screenshot of the env file…

Do you happen to have any backup of old files (priv/pool/) in the same folder or within any renamed folder? when we were rotating our keys from old to new, we kept a backup of folder with a different name than original folder and it was interfering with the key rotation.

I ended up deleting the db folder and starting again. now syncing.

Waiting to see if the KES keys have rotated ok.

I read through this and having some simular problems since upgrading to 1.29.0. First, I had to upgrade each stake from 8GB to 16GB, however, when it came back up it said my KES Expiration data was today. I have attempted twice to generate the node.cert and ensure it has the permissions to get to access the poolkeys folder and run updated script from coincashew. The dates seem correct and no errors on creating the kes.skey and the node.cert from my air gap. I did however try to update my cardano-cli and cardano-node (binaries) on my air gap but ran into problems so I renamed the updated files and put the previous ones back. Would the older binaries prevent the kes update if they don’t match on block producer and air gap? At this point I think I need help because I am running around in circles. I can’t get the KES expiration date to change from yesterday.

Journal errors for cardano-node

Sep 28 23:25:23 wagyu cardano-node[776]: [wagyu:cardano.node.LeadershipCheck:Inf o:119] [2021-09-28 23:25:23.00 UTC] {“kind”:“TraceStartLeadershipCheck”,“chainDe nsity”:4.9500182e-2,“slot”:41305232,“delegMapSize”:839772,“utxoSize”:3316604,“cr edentials”:“Cardano”}

but why you are saying you have issues with the new certificate? in glive it shows you the correct/new EXPIRATION date?

try this command on live Producer

curl localhost:12798/metrics | grep KES

what is the output?

Screenshot 2021-09-29 at 11.47.14

Just to conclude the initial issue. All is good. Key rotation had worked fine (just needed to connect).

1 Like