-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] miner can't receive head change any more after "window post scheduler notifs channel closed". #5813
Comments
I just got the same error. The miner didn't do WindowPoSt after this error, and restarting miner can solve it.
|
The same, restart the miner solve it. The miner was not doing any sealing work. |
Hey! Just wanted to updated everybody in this thread that this issue will be tracked in #8362 going forward. It´s an issue that is on our radar, and one that we really want to find find a fix for, but it´s also one that we would certainly need additional help from everybody.
|
Describe the bug
while "window post scheduler notifs channel closed" show up, miner can't receive head change anymore.
seen other connection errors at the meantime.
restarting miner can resolve it.
2021-03-15T10:59:35.287+0800 ^[[33mWARN^[[0m advmgr sector-storage/sched_worker.go:261 failed to check worker session {"worker": "0d688d6e-7235-4d32-89c9-2a74a6739e86", "error": "RPC client error: sendRequest failed: Post \"http://192.168.0.231:7890/rpc/v0\": context deadline exceeded"} 2021-03-15T10:59:34.615+0800 ^[[33mWARN^[[0m advmgr sector-storage/sched_worker.go:261 failed to check worker session {"worker": "e7a3028e-8bd2-4f29-813c-84ece2787c41", "error": "RPC client error: sendRequest failed: Post \"http://192.168.0.245:7890/rpc/v0\": context deadline exceeded"} 2021-03-15T10:59:35.471+0800 ^[[33mWARN^[[0m storageminer storage/wdpost_sched.go:120 window post scheduler notifs channel closed
Version (run
lotus version
):v1.5.0
To Reproduce
Steps to reproduce the behavior:
don't catch the reproduce way.
Expected behavior
while "notifs channel closed" ,it should "reopen" immediately, rather than MUST restart miner.
Logs
N/A
The text was updated successfully, but these errors were encountered: