You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm running a 3 node localnet using testground.
I tried to pledge a few sectors, but they failed, ending up in the SealCommitFailed state.
Then at height 540, all the nodes stopped updating.
On the genesis node, I noticed this in the logs for the lotus node:
2020-03-30T23:06:43.015Z WARN rpc jsonrpc/handler.go:225 error in RPC call to 'Filecoin.SyncSubmitBlock': sync to submitted block failed:
github.com/filecoin-project/lotus/node/impl/full.(*SyncAPI).SyncSubmitBlock
/lotus/node/impl/full/sync.go:71
- failed to put synced tipset to chainstore:
github.com/filecoin-project/lotus/chain.(*Syncer).Sync
/lotus/chain/sync.go:428
- MaybeTakeHeavierTipSet failed in PutTipSet:
github.com/filecoin-project/lotus/chain/store.(*ChainStore).PutTipSet
/lotus/chain/store/store.go:243
- All power in the net is gone. You network might be disconnected, or the net is dead!:
github.com/filecoin-project/lotus/chain/store.(*ChainStore).Weight
/lotus/chain/store/weight.go:55
I'll dig through the logs to see if I can find any more clues. I might start the localnet again from scratch to see if I can reproduce (only takes me a few minutes).
Version (run lotus --version):
lotus version 0.3.0+gitf2d90b83.dirty
The text was updated successfully, but these errors were encountered:
computing seal proof failed 2: %!w(*errors.fundamental=&{No cached parameters found for stacked-proof-of-replication-PoseidonHasher-Sha256Hasher-fe437922fe766f61b112750506d6be0e4ad5daa85ff9ce96549d99253ba61cbe 0xc0004be480})
Looks like this is peculiar to my setup with testground. I'll close this.
Describe the bug
I'm running a 3 node localnet using testground.
I tried to pledge a few sectors, but they failed, ending up in the SealCommitFailed state.
Then at height 540, all the nodes stopped updating.
On the genesis node, I noticed this in the logs for the lotus node:
I'll dig through the logs to see if I can find any more clues. I might start the localnet again from scratch to see if I can reproduce (only takes me a few minutes).
Version (run
lotus --version
):lotus version 0.3.0+gitf2d90b83.dirty
The text was updated successfully, but these errors were encountered: