Updated KES and now BPN is stuck in starting

Staking & Delegation Operate a Stake Pool
1

I see a few errors in the logs but they are not making much sense to me. Anyone else run into issues after updating node.cert?

I am running 1.24.2.

Any assistance would be greatly appreciated.

This is the method I followed and the only thing I can think of is that it doesn’t like my startKesPeriod of 131 No other changes have been made aside from updating the KES node.cert.

cd NODE_HOME slotNo=(cardano-cli query tip --mainnet | jq -r ‘.slotNo’)
slotsPerKESPeriod=$(cat NODE_HOME/{NODE_CONFIG}-shelley-genesis.json | jq -r ‘.slotsPerKESPeriod’)
kesPeriod=(({slotNo} / {slotsPerKESPeriod})) startKesPeriod={kesPeriod}
echo startKesPeriod: ${startKesPeriod}

cd $NODE_HOME
cardano-cli node key-gen-KES
–verification-key-file kes.vkey
–signing-key-file kes.skey

cd $NODE_HOME
chmod u+rwx $HOME/cold-keys
cardano-cli node issue-op-cert
–kes-verification-key-file kes.vkey
–cold-signing-key-file $HOME/cold-keys/node.skey
–operational-certificate-issue-counter $HOME/cold-keys/node.counter
–kes-period 131
–out-file node.cert
chmod a-rwx $HOME/cold-keys

sudo systemctl reload-or-restart cardano-node

2

Looks like I had bigger issues at play, both my relays apparently went down earlier today and for some reason I didn’t get any notifications. That was giving me the incorrect KES period. Going to sync up and try KES rotation again, will post my progress for posterity.

3

Yep, just needed to sync up, current KES was not 131 :slight_smile:

4

could you elaborate a tiny bit further. i believe im experiencing this exact problem. how were you able to sync back up?

5

For my situation the only thing that seemed to work was completely deleting the database files and then restart the nodes to allow them to fully sync again from the beginning.