Node haven't been producing blocks for a while

Staking & Delegation Operate a Stake Pool
1

The node hasn’t produced a block for a few hundred minutes, we checked the binary version (pops 1.35.4), log, etc., all metrics seem doing just fine

@Alexd1985

Hey Alex, could you please give some advice on how to troubleshoot? Much appreciated

2

what is the ticker?
what is the output for command? ( adapt the path to node.cert/op.cert)

cardano-cli query kes-period-info --op-cert-file op.cert --mainnet
3

Much appreciated, the node proposed the block soon after I posted this thread

the output for the posted command = all working fine, including:
✓ Operational certificate’s KES period is within the correct KES period interval
✓ The operational certificate counter agrees with the node protocol state counter

1 Like
4

Hi Alex,
Can you tell me if this output looks ok to you? I also haven’t minted a block in some time and wondering why. Is it weird that qKesKesKeyExpiry is null?

{
    "qKesCurrentKesPeriod": 616,
    "qKesEndKesInterval": 653,
    "qKesKesKeyExpiry": null,
    "qKesMaxKESEvolutions": 62,
    "qKesNodeStateOperationalCertificateNumber": 5,
    "qKesOnDiskOperationalCertificateNumber": 5,
    "qKesRemainingSlotsInKesPeriod": 4785575,
    "qKesSlotsPerKesPeriod": 129600,
    "qKesStartKesInterval": 591
}
5

Hi,

It is null because u did not make any blocks with this certificate

Cheers,

6

Thanks Alex, but other than that it look ok? It’s not a cause for it not producing any blocks in a while?

7

I beliebe this is not ok, what is your ticker?
qKesOnDiskOperationalCertificateNumber should be greater by 1 than qKesNodeStateOperationalCertificateNumber (last one used)

8

Thanks for looking at this, ticker is CTL

9

your last block was made with op#5

image
image1508×108 9.78 KB

if u rotated the keys recently (after that period) you must use counter 6

in the end should be something like

"qKesNodeStateOperationalCertificateNumber": 5,
    "qKesOnDiskOperationalCertificateNumber": 6,

The value of the qKesNodeStateOperationalCertificateNumber key indicates the current counter value for your stake pool registered by the blockchain protocol. The value of the qKesOnDiskOperationalCertificateNumber key indicates the counter value of the current operational certificate that your stake pool uses.

For a new operational certificate, the counter value must be exactly one (1) greater than the current value of the qKesNodeStateOperationalCertificateNumber key.

10

Wow, interesting. I think I restored the certificate from a backup which may have caused the issue. What you you suggest that I do to fix this.

  1. I can rotate my Kes Keys again
  2. Edit the certificate and change from 5 to 6?
  3. Perhaps issue a whole new certificate?

I have never encountered this before.

11

issue a new certificate with counter 6

Cheers,

12

Thanks Alex, Is this possible via cntools or do I follow the coincashew instructions?

13

aaa, if you have cntools is fine. is very easy… when you will go to rotate it will ask you for counter number… just type 6 and thats it… check the certificates again (and also restart the BP)

Cheers,

14

Thanks heaps Alex,
I have rotated my keys (I copied the cold.counter file to the bp node so it didn’t ask me for the counter number). Now the display looks like this:

✓ Operational certificate's KES period is within the correct KES period interval
✓ The operational certificate counter agrees with the node protocol state counter
{
    "qKesCurrentKesPeriod": 616,
    "qKesEndKesInterval": 678,
    "qKesKesKeyExpiry": null,
    "qKesMaxKESEvolutions": 62,
    "qKesNodeStateOperationalCertificateNumber": 5,
    "qKesOnDiskOperationalCertificateNumber": 6,
    "qKesRemainingSlotsInKesPeriod": 7997651,
    "qKesSlotsPerKesPeriod": 129600,
    "qKesStartKesInterval": 616
}
1 Like