Missed block & Need help

Staking & Delegation Operate a Stake Pool
1

Hello everyone, my pool missed several blocks, which can be seen by the cardano-cli query leadership-schedule

cardano-cli query leadership-schedule --mainnet --genesis ./shelley-genesis.json --stake-pool-id $(cat ./stakepoolid.txt) --vrf-signing-key-file keys/vrf.skey --current

And the output is

     *********
     149604681                   2025-03-05 10:36:12 UTC
     *********

and in the server logs, it seems checked the leadership, and forged a new block, but it was not confirmed on chain finnaly.
Here are the logs :

{"app":[],"at":"2025-03-05T10:36:12.005Z","data":{"chainDensity":4.990638e-2,"credentials":"Cardano","delegMapSize":1325811,"kind":"TraceStartLeadershipCheck","slot":149604681,"utxoSize":10949657},"env":"10.1.4:1f63d","host":"ada-1","loc":null,"msg":"","ns":["cardano.node.LeadershipCheck"],"pid":"676347","sev":"Info","thread":"173"}
{"app":[],"at":"2025-03-05T10:36:12.050Z","data":{"credentials":"Cardano","val":{"kind":"TraceNodeIsLeader","slot":149604681}},"env":"10.1.4:1f63d","host":"ada-1","loc":null,"msg":"","ns":["cardano.node.Forge"],"pid":"676347","sev":"Info","thread":"173"}
{"app":[],"at":"2025-03-05T10:36:12.050Z","data":{"credentials":"Cardano","val":{"block":"16ae3d6b0763af5821277a522a046781c8e8d85149b09497df6dfee412404568","blockNo":11563709,"blockPrev":"a71bfdca12d0dd105b83e1253a94f438960aa634331919f25ecd117c2e13a5d0","kind":"TraceForgedBlock","slot":149604681}},"env":"10.1.4:1f63d","host":"ada-1","loc":null,"msg":"","ns":["cardano.node.Forge"],"pid":"676347","sev":"Info","thread":"173"}
{"app":[],"at":"2025-03-05T10:36:12.051Z","data":{"block":"16ae3d6b0763af5821277a522a046781c8e8d85149b09497df6dfee412404568","blockNo":11563709,"kind":"ChainSyncClientEvent.TraceDownloade
dHeader","peer":{"local":{"addr":"127.0.0.1","port":"6000"},"remote":{"addr":"127.0.0.1","port":"6000"}},"slot":149604681},"env":"10.1.4:1f63d","host":"ada-1","loc":null,"msg":"","ns":["cardano.node.ChainSyncClient"],"pid":"676347","sev":"Info","thread":"220"}
{"app":[],"at":"2025-03-05T10:36:12.051Z","data":{"chainLengthDelta":1,"headers":[{"blockNo":"11563709","hash":"\"16ae3d6b0763af5821277a522a046781c8e8d85149b09497df6dfee412404568\"","kind":"ShelleyBlock","slotNo":"149604681"}],"kind":"TraceAddBlockEvent.AddedToCurrentChain","newTipSelectView":{"chainLength":11563709,"issueNo":3,"issuerHash":"0fd17893d565ed2f7dee0997372c2a5604903df5ee8a4abd215a515b","kind":"PraosChainSelectView","slotNo":149604681,"tieBreakVRF":"60398d7c3aa7261933d24c91f41b4e52dce435d385c3d32d04c7a344538fdc52208420a8670855076e7a5b976b96f87534aec72e2ba81ff7d5c3d5e2d10c93a0"},"newtip":"16ae3d6b0763af5821277a522a046781c8e8d85149b09497df6dfee412404568@149604681","oldTipSelectView":{"chainLength":11563708,"issueNo":7,"issuerHash":"39b60916e5f2ccaad362b09e907d9d85050cbd22b94db9943a17bdd9","kind":"PraosChainSelectView","slotNo":149604678,"tieBreakVRF":"4145d33dc9ab5d30c5544a0c49a98119d83ac70ec5f260527788deb7784e9e0ab354d014a0f3f7e41d5f337de6958248b54f3ae19d2826ec279843bb7f66a22b"}},"env":"10.1.4:1f63d","host":"ada-1","loc":null,"msg":"","ns":["cardano.node.ChainDB"],"pid":"676347","sev":"Notice","thread":"153"}
{"app":[],"at":"2025-03-05T10:36:12.051Z","data":{"credentials":"Cardano","val":{"blockHash":"16ae3d6b0763af5821277a522a046781c8e8d85149b09497df6dfee412404568","blockSize":871,"kind":"TraceAdoptedBlock","slot":149604681,"txIds":[]}},"env":"10.1.4:1f63d","host":"ada-1","loc":null,"msg":"","ns":["cardano.node.Forge"],"pid":"676347","sev":"Info","thread":"173"}

Has anyone encountered similar problems? Thank you very much for your reply.

2

On a related note we’ve made some progress in the New Year about getting more explicit information into the cardano-node log file that indicates whether a “fork battle” has been won or lost: enough to determine the exact reason for our own node switching to a fork that doesn’t have our recently produced block on it. This thread also suggests that this information will eventually be recorded more explicitly someday for operator “convenience” (cc @Terminada):

Since it’s unlikely for a node to have “several blocks” in a row with consistently lost fork or slot battles, in your case I would first try to confirm the nodes in your stake pool are in good enough communication with the Cardano network and each other that your block producing node is always up to date with the current “tip” of the chain and was fully populated with Tx (as hopefully traceable in your BP’s log file) at the time the blocks were missed.

2 Likes
3

Thanks for you reply. I will check the url

BTW, The pool has missed several blocks. I have migrated the node to a very high performance Server. And it would get leadership scheduler soon.
I will keep an eye on the log

4

Double check your relay nodes’ logs. Make sure their chain is extended with the same block your BP has produced.

I’ve had issues in the past with an invalid opcert - it was not caught until being dropped by the relays.

2 Likes
5

Finnaly the problem has been solved. It should be a machine performance problem.
Before this, it should be the problem that op.cert is invalid.