-
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
PC tickets expire, seems new ticket is already expired at retrieval time #4865
Comments
Just wanted to chime in here with more ticket expired bugs. Got a lot of sectors with ticket expired after they have been stuck in mpool due to base fee's being higher over the weekend. If you don't replace gas, and it takes too long for the messages to get on chain from "PreCommitWait" & "CommitWait", the tickets will expire and the sectors start looping. And there is no other way than removing the sectors to clean it up.
|
I've got my tickets expired too https://filecoinproject.slack.com/archives/CEGN061C5/p1605723685085300 |
I had the same issue with v1.2.1: |
This happened again with v1.2.2 , the sector in question can not be removed or update-state to sector log |
@karalabe have you tried abort jobs of sectors after run remove command #5081 (comment) |
My miner ran into this multiple times, and still happening. I am troubleshooting what the root causes are. For now, here are some information to share: (in the following case, it's related to sector 656), initially it looked like caused by worker overloaded. But later got moved to other worker for PC1, and PC2, no success. Kept doing loops and back to PC1.
2020-12-24T07:51:47.207-0800 WARN stores stores/index.go:204 sector {8399 656} redeclared in c90229a6-e411-4c34-8417-95494c70db9f 2020-12-25T13:00:20.208-0800 WARN sectors storage-sealing/fsm.go:511 sector 656 got error event sealing.SectorSealPreCommit1Failed: ticket expired: ticket expired: seal height: 348153, head: 354120 |
Same issue here Event Log:
|
I am also experiencing a similar issue with a sector stuck on repeating PreCommit1. I am trying to see if I can complete the sealing process on other sectors. Is there anyone to prevent it or manually correct this problem? lotus-miner sealing jobsID Sector Worker Hostname Task State Time lotus versionDaemon: 1.4.2+mainnet+git.d1abc3cb5.dirty+api1.1.0 lotus-miner sectors status 3SectorID: 3 Miner.log Thank You |
this should be resolve in lotus v1.9.0 and up - Please open a new ticket if you are running into this issue on the latest version of lotus! |
All my sectors during the weekend got stuck in PC2 due to some new GPU scheduling bug in 1.1.3. I've reconfigured things to not have concurrent GPU handling, after which PC2 seems to have worked, but all the sectors started looping between PC2->PC1->PC2, etc. First two time it said the sector ticket expired. Two bugs though:
The text was updated successfully, but these errors were encountered: