MinerX.3 1.13.2 General Testing and Call Outs #7719
Replies: 18 comments 16 replies
-
|
I am rejecting all deals until the pipeline is clear, which should be Wed 1 Dec am. then will upgrade and accept deals. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
💻 PoSTs work |
Beta Was this translation helpful? Give feedback.
-
|
Just mined a block...
|
Beta Was this translation helpful? Give feedback.
-
|
🤝 Online and offline deals working well |
Beta Was this translation helpful? Give feedback.
-
|
I yolo-ed and now I'm on the new version. lotus-miner version So far windowpost OK Update: winningpost OK!! |
Beta Was this translation helpful? Give feedback.
-
🤝🦭💻 |
Beta Was this translation helpful? Give feedback.
-
|
I'm using I'm guessing that it probably has something to with the I have updated my buffer limits using the steps on this page and the warning messages have now stopped. Might be a good idea for miners to double check their buffer limits. I didn't see any obvious errors with transfers before upping my limits but I'm not sure if it would have had an impact over a longer period of time. NOTE: You may need to restart your miner after updating the limits as doing it on the fly caused Lotus sync issues for me. |
Beta Was this translation helpful? Give feedback.
-
|
Upgraded f01045784 to: |
Beta Was this translation helpful? Give feedback.
-
|
Successfully sealed some new sectors. |
Beta Was this translation helpful? Give feedback.
-
|
workers are upgraded too, seems to be running fine ... Will have the WinPoST check soon and sealing is starting up as we speak. |
Beta Was this translation helpful? Give feedback.
-
|
WinPoST, sealing, etc works fine. No block win yet |
Beta Was this translation helpful? Give feedback.
-
|
No retrieval test yet |
Beta Was this translation helpful? Give feedback.
-
|
Meest NAM (f03488) lotus-miner version lotus version So far wdpost OK |
Beta Was this translation helpful? Give feedback.
-
|
The whole production line is upgraded. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
🦭 |
Beta Was this translation helpful? Give feedback.
-
|
After initial testing: Everything seems fine. 🤝🦭💻 without problems. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Passed windowPoST and a couple of sealed sectors. Everything is normal... I said I would wait for next week on the scheduler optimizations, but then @magik6k just told we can do: |
Beta Was this translation helpful? Give feedback.
-
|
So from here: |
Beta Was this translation helpful? Give feedback.
-
|
all on 1.13.2-rc1, taking deals, wd post in 12:30h - update when results are in |
Beta Was this translation helpful? Give feedback.
-
|
deals work no idea how smilies work here |
Beta Was this translation helpful? Give feedback.
-
|
wd post works |
Beta Was this translation helpful? Give feedback.
-
|
All upgraded to: lotus version 1.13.2-rc1+mainnet+git.52c7fa242 |
Beta Was this translation helpful? Give feedback.
-
|
Finished also the upgrade to v1.13.2-rc1 |
Beta Was this translation helpful? Give feedback.
-
|
🤝 💻 🦭 |
Beta Was this translation helpful? Give feedback.
-
VersionStatus
|
Beta Was this translation helpful? Give feedback.
-
|
I want to report an issue here. I have two AP+PC1 workers. After upgrade to 1.13.2-rc1, one of the workers are normal, but the other worker performance got slow down drastically. Ubuntu 20.04 with latest updates The PC1 worker having problem is with 7F32 CPU. Prior to the upgrade, when running 1.13.0 or prior versions, it runs 6 parallel PC1 jobs and can finishes around 4 hours. With 1.13.2-rc1, it took over 20 hours to do that. Turns out if I added FIL_PROOFS_USE_MULTICORE_SDR=1 to this PC1 worker, the performance per PC1 is not only back but slightly better than 1.13.0 level, however, looks like it only seal max 4 sectors in parallel probably due to the ccx limits. I didn't set FIL_PROOFS_SDR_PARENTS_CACHE_SIZE, not sure if it makes a difference. Does anyone else see PC1 performance differences with SDR=0? |
Beta Was this translation helpful? Give feedback.
-
|
version windowpost OK Update: winningpost OK!! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the report ! but this is MinerX testing. If you want to test any release candidates on your own, always upgrade to the latest tags: We are now on rc7 as you can see :) |
Beta Was this translation helpful? Give feedback.
-
|
Haha he is one of the fellows - but certainly on an older rc lolol |
Beta Was this translation helpful? Give feedback.
-
|
my bad - sorry about that. |
Beta Was this translation helpful? Give feedback.
-
Same old same old. Update your system to lotus v1.13.2-rc1.
❤️ This post if you are participating in this testing round. If you aren't able to join for reasons, please reach out to @ Deep Kapur and me on slack!
Regular Operations
Your daily SP operations should stay ✅ .
Reply with:
🦭 If you have successfully sealed some new sectors.
🤝 If you have successfully made some storage deals.
💻 If you passed your first WindowPoSt.
❗ Create an issue if you think there is a bug, don't forget to attach the logs!
lotus-miner info allif you want to report a bug! If the log files are large, you can upload them inMinerX.3 - v1.13.2 Testing Logsfolder and link it in your issue report/slack message/..New feature and Improvements
Except for worker and scheduler enhancements and retrieval improvements, you should also watch out for:
lotus-shed balancerout, it should help you with multi wallet management, for example between worker and control addresses!lotus-shed msg, it's getting really handy for inspecting msig messages (which contains internal invocations).lotus-shed miner faultsto get a list of faulty sectors and the expiring times.Beta Was this translation helpful? Give feedback.
All reactions