value of command cardano-cli text-view decode-cbor --in-file <path>/node.cert | grep int | head -1 will check, right ?
but when i try to check return from above command and the output from above command is 03 # int(3)
something like that ?
yes, this is how should look, and should incremented by 1 each time when you rotate the KES
and note somewhere the last number, and next time when you will rotate the KES should be grater than this one
for example if now it will show you 5 next time (after 90 days) you must have 6…next 7 , etc
new certificate SHOULD NEVER have less than the last/old one
alright, Alex
Thank you before your help and response, Alex
and i want to make sure about config file. what are the config files that are currently used?
i use 7 config files such as mainnet-config.json , mainnet-db-sync-config.json , mainnet-shelley-genesis.json, mainnet-topology.json, mainnet-alonzo-genesis.json , mainnet-byron-genesis.json, rest-config.json
are you using same config files like me, right ?
or you just use a few of 7 config files ?
I have few because I am using cntools, but it’s fine… upload the new certificate, restart the node, check in glive if you have out/in peers, if yes check if u have tx processed, if yes then now you should start minting blocks again
PS: did u upgraded the nodes to 1.29.0 alonzo, right? I saw the file alonzo… so I guess you did
alright
i have upgraded all of my node such as relay node and block producer node to 1.29.0 on alonzo era
1 Like
Ok, let’s see if now it will mint blocks 
alright
let me try it
U minted 1 block so the issue is fixed 
Next time try the command before and after KES rotation, the new node.cert should have greater value than the old one
value of command cardano-cli text-view decode-cbor --in-file <path>/node.cert | grep int | head -1
Thank you so much with your help, Alex
1 Like