Orderer going into panic "panic: Failed to retrieve block" , after respawning and reconnecting with the other orderers #raft #tls #fabric-orderer #kubernetes


Vijaya Bhaskar
 

Following is the brief overview,

the network is running on 2 kubernetes clusters. we have 3 orderers (2 in east US cluster and one in India cluster). we are using skupper to establish connection across clusters by exposing the service-names directly on azure kubernetes cluster.
I removed the skupper and re installed it. this caused the connection between clusters to drop for sometime and no transactions were made on the network.
I am seeing that the orderer3 which is in the india cluster is restarting again and again with the following error. the other 2 orderers are working fine.
2022-11-26 07:40:12.653 UTC [certmonitor] trackCertExpiration -> INFO 00d The server TLS certificate will expire on 2023-06-21 14:45:00 +0000 UTC
2022-11-26 07:40:12.653 UTC [certmonitor] trackCertExpiration -> INFO 00e The client TLS certificate will expire on 2023-06-21 14:45:00 +0000 UTC
2022-11-26 07:40:13.475 UTC [orderer.commmon.multichannel] ConfigBlock -> PANI 00f Failed to retrieve block blockNum=18446744073709551615 error="Entry not found in index"
panic: Failed to retrieve block
 
goroutine 1 [running]:
go.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc0001656b0, {0xc0004e0900, 0x2, 0x4})
/go/src/github.com/hyperledger/fabric/vendor/go.uber.org/zap/zapcore/entry.go:230 +0x486
go.uber.org/zap.(*SugaredLogger).log(0xc0000100d8, 0x4, {0xe6386a?, 0x2a?}, {0x0?, 0x2?, 0x3?}, {0xc00054be60, 0x4, 0x4})
/go/src/github.com/hyperledger/fabric/vendor/go.uber.org/zap/sugar.go:234 +0x13b


Param
 

Hi,
Based on the error messages, I suspect that the file ledger directory(FileLedger.Location = "/var/hyperledger/production/orderer") is corrupted or not initialized completely.
Please check whether this directory location is complete(accessible).

Thanks
Param