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
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Connect all workers to lotus-miner (200+ of them)
Run lotus-miner sectors pledge
Find out all workers stay idle.
Run lotus-miner sealing sched-diag.
Process hangs indefinitely
I press ctrl+z.
There are 2 PIDs for lotus-miner.
lotus-miner does nothing no matter how long I wait.
lotus-miner stop doesn't work either. The processes have to be killed.
Expected behavior
NO JAMMING when calling sealing jobs list, sealing workers list, and sealing sched-diag. Please!
Jamming after running these commands seems to be the byproduct of sched deadlocking not the cause.
Screenshots
Version (run lotus version): 0.5.7+git.b8bbbf3e
(Compiled on latest mater and applied PR #3445.
Additional context
Sched has never been reliable from testnet phase 2 (when I started mining).
I've suffered from deadlocking issue for a long long time. Version 0.5.7 is bad enough to finally make me file a bug report.
The most reliable one I've tried was version 0.5.3. 0.5.7 is worst I've ever used.
The text was updated successfully, but these errors were encountered:
hyunmoon
changed the title
Scheduler deadlocking very badly
Scheduler deadlocking
Sep 1, 2020
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
lotus-miner sectors pledge
lotus-miner sealing sched-diag
.lotus-miner
.lotus-miner
does nothing no matter how long I wait.lotus-miner stop
doesn't work either. The processes have to be killed.Expected behavior
NO JAMMING when calling
sealing jobs list
,sealing workers list
, andsealing sched-diag
. Please!Jamming after running these commands seems to be the byproduct of sched deadlocking not the cause.
Screenshots
Version (run
lotus version
):0.5.7+git.b8bbbf3e
(Compiled on latest mater and applied PR #3445.
Additional context
Sched has never been reliable from testnet phase 2 (when I started mining).
I've suffered from deadlocking issue for a long long time. Version 0.5.7 is bad enough to finally make me file a bug report.
The most reliable one I've tried was version 0.5.3. 0.5.7 is worst I've ever used.
The text was updated successfully, but these errors were encountered: