Sunsetting Incognito   

(Resolved) Cannot find committee error

#1

Hey @Support,

All of my validators raise “cannot find committee error”. Here is the content of error.log from one of my validators:

2023/07/27 20:59:51 Using network param file for mainnet
2023/07/27 20:59:51 err 5 81b956fc7f180339147a035b1483de0cf141d35fedaafd2038480d39e46aebbe
panic: Cannot find committee from shardID 5 viewHash 81b956fc7f180339147a035b1483de0cf141d35fedaafd2038480d39e46aebbe

goroutine 1 [running]:
github.com/incognitochain/incognito-chain/blockchain.InitShardCommitteeState(0x3, 0x1d51fe8, 0x39e26d, 0x5, 0xc001f72280, 0xc00016a2c0)
        /Users/autonomous/projects/incognito-chain/blockchain/shardbeststate.go:444 +0x3da
github.com/incognitochain/incognito-chain/blockchain.(*BlockChain).RestoreShardViews(0xc00016a2c0, 0x5)
        /Users/autonomous/projects/incognito-chain/blockchain/blockchain.go:767 +0x3f5
github.com/incognitochain/incognito-chain/blockchain.(*BlockChain).InitChainState(0xc00016a2c0)
        /Users/autonomous/projects/incognito-chain/blockchain/blockchain.go:244 +0xb72
github.com/incognitochain/incognito-chain/blockchain.(*BlockChain).Init(0xc00016a2c0, 0xc000647670)
        /Users/autonomous/projects/incognito-chain/blockchain/blockchain.go:121 +0x175
main.(*Server).NewServer(0xc0069b0960, {0x7ffc98b84cf9, 0xc}, 0xc0037d4d80, {0x1d401c8, 0xc000135470}, 0xc0069a49a0, 0x0, {0x7ffc98b84c01, 0x40}, ...)
        /Users/autonomous/projects/incognito-chain/server.go:315 +0x1398
main.mainMaster(0x0)
        /Users/autonomous/projects/incognito-chain/incognito.go:213 +0xdf3
main.main()
        /Users/autonomous/projects/incognito-chain/incognito.go:288 +0x2b6

How can I fix it? Is there any idea?

#2

Hello @abduraman,

I’ve escalated this to the dev team.

1 Like
#3

My current solution is to bootstrap the beacon chain.

Post-mortem :slight_smile:
Probably deno caused it. To my guess, deno task shouldn’t be run immediately after a node exits the committee. Previously I was running deno task manually. ~One week ago, I had set deno task to run every hour via crontab. Probably one of those runs coincided with the condition I mentioned.

3 Likes