message execution failed: exit 16, reason: invalid deadline 4 at epoch 1692587, expected 3

[nujz]

Checklist

• This is not a security-related bug/issue. If it is, please follow please follow the security policy.
• This is not a question or a support request. If you have any lotus related questions, please ask in the lotus forum.
• This is not a new feature request. If it is, please file a feature request instead.
• This is not an enhancement request. If it is, please file a improvement suggestion instead.
• I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
• I am running the Latest release, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
• I did not make any code changes to lotus.

Lotus component

• lotus daemon - chain sync
• lotus miner - mining and block production
• lotus miner/worker - sealing
• lotus miner - proving(WindowPoSt)
• lotus miner/market - storage deal
• lotus miner/market - retrieval deal
• lotus miner/market - data transfer
• lotus client
• lotus JSON-RPC API
• lotus message management (mpool)
• Other

Lotus Version

Daemon:  1.14.1+mainnet+git.63a6b1c2b.dirty+api1.5.0
Local: lotus version 1.14.1+mainnet+git.63a6b1c2b.dirty

Daemon:  1.14.2+mainnet+git.73ec177d0.dirty+api1.4.0
Local: lotus-miner version 1.14.2+mainnet+git.73ec177d0.dirty

Describe the Bug

2022-04-04T23:17:50.806+0800	ERROR	storageminer	storage/wdpost_run.go:892	estimating gas	{"error": "estimating gas used: message execution failed: exit 16, reason: invalid deadline 4 at epoch 1692587, expected 3 (RetCode=16)"}
2022-04-04T23:17:50.824+0800	ERROR	storageminer	storage/wdpost_run.go:186	submit window post failed: pushing message to mpool:
    github.com/filecoin-project/lotus/storage.(*WindowPoStScheduler).submitPoStMessage
        /root/go/src/new_rust/storage/wdpost_run.go:854

  - GasEstimateMessageGas error: estimating gas used: message execution failed: exit 16, reason: invalid deadline 4 at epoch 1692587, expected 3 (RetCode=16)

Logging Information

1

Repo Steps

No response

[rjan90]

Hey @nujz!

Thanks for the ticket. The message error: invalid deadline 4 at epoch 1692587, expected 3 (RetCode=16) means basically that the proof landed on-chain too late. It was supposed to be a proof for a deadline 3, but at the time you posted it the network is expecting proofs for deadline 4.

I can see that the error message is a bit confusing, but it´s not an issue per se, rather we need to debug why you sent the message so late to the chain. Typical things include computing the windowPost took to long, stuck in mpool (need to set up an control address), out of sync.

Converting it to an discussion so we can debug more!

[nujz]

1. Yes. The control address has no enough balance.

[rjan90]

Okay! That explains it. Top-up the balance on your control-address and you should be good by next deadline 😄! You can always run lotus-miner proving check --slow <partition number> to make sure that the sectors in the deadline are okay!

[nujz]

The control address has no enough balance for a long time. The other days were fine

[rjan90]

Yeah, when your control address is out of funds, it will fall back and send the message from the worker-address, and you are therefor at risk of the message being stuck behind others.

[nujz]

Okay, thanks. I'll try this.