Closed kdeme closed 4 years ago
Also seen on a server:
Feb 11 14:54:38 master-01.aws-eu-central-1a.nimbus.test docker/beacon-node-testnet0-1[999]: /root/nim-beacon-chain/beacon_chain/beacon_node.nim(1161) beacon_node
Feb 11 14:54:38 master-01.aws-eu-central-1a.nimbus.test docker/beacon-node-testnet0-1[999]: /root/nim-beacon-chain/beacon_chain/beacon_node.nim(215) init
Feb 11 14:54:38 master-01.aws-eu-central-1a.nimbus.test docker/beacon-node-testnet0-1[999]: /root/nim-beacon-chain/beacon_chain/block_pool.nim(246) init
Feb 11 14:54:38 master-01.aws-eu-central-1a.nimbus.test docker/beacon-node-testnet0-1[999]: /root/nim-beacon-chain/vendor/nimbus-build-system/vendor/Nim/lib/pure/options.nim(211) get
Feb 11 14:54:38 master-01.aws-eu-central-1a.nimbus.test docker/beacon-node-testnet0-1[999]: [[reraised from:
Feb 11 14:54:38 master-01.aws-eu-central-1a.nimbus.test docker/beacon-node-testnet0-1[999]: /root/nim-beacon-chain/beacon_chain/beacon_node.nim(1161) beacon_node
Feb 11 14:54:38 master-01.aws-eu-central-1a.nimbus.test docker/beacon-node-testnet0-1[999]: /root/nim-beacon-chain/vendor/nim-chronos/chronos/asyncloop.nim(948) waitFor
Feb 11 14:54:38 master-01.aws-eu-central-1a.nimbus.test docker/beacon-node-testnet0-1[999]: /root/nim-beacon-chain/vendor/nim-chronos/chronos/asyncfutures2.nim(423) read
Feb 11 14:54:38 master-01.aws-eu-central-1a.nimbus.test docker/beacon-node-testnet0-1[999]: /root/nim-beacon-chain/vendor/nim-chronos/chronos/asyncfutures2.nim(407) internalCheckComplete
Feb 11 14:54:38 master-01.aws-eu-central-1a.nimbus.test docker/beacon-node-testnet0-1[999]: ]]
Feb 11 14:54:38 master-01.aws-eu-central-1a.nimbus.test docker/beacon-node-testnet0-1[999]: Error: unhandled exception: Can't obtain a value from a `none`
most likely cause: justification happened on an epoch boundary that had no block, so the latest justified block is pointing to a preceding state..
commit cf14b7ac37bbf8dee53e9b79148cfc654efbf188
Encountered by stopping nim-beacon-chain on testnet0 by Ctrl-C press. On resume via
make testnet0
the issue occurred. I've tried to reproduce a few times after a clean, but did not see it occur again.