|
Message boards : Number crunching : Trickle up message Pending and 5 completed tasks "Ready to Report"
Message board moderation
Author | Message |
---|---|
Send message Joined: 15 Feb 12 Posts: 2 Credit: 1,422,611 RAC: 0 |
Hello all, i have had 5 HadAM4 at N144 resolution tasks stuck into "Ready to Report" for weeks now, after they completed at 100% and uploaded successfully. Also the Trickle up message Pending and Comm deferred refuses to go away, can i clear it myself or not? I have two other longer N216 tasks currently running and connectivity seems OK what is going on? |
![]() Send message Joined: 7 Aug 04 Posts: 2187 Credit: 64,822,615 RAC: 5,275 |
This may be a certificate issue problem. At the end of September 2021, Windows boinc versions before 7.16.20 had a certificate list that expired. Linux updates the certificate list periodically outside of boinc. However, if you are running an old version of a Linux distribution that no longer gets updates, boinc may be reading the old list and not able to properly communicate with cpdn for trickles, downloading new tasks or reporting completed ones. It looks like you are running an older, likely non-updating version of linux, and are running boinc 7.2.42, probably downloaded from the Berkeley boinc site? If that's the case, your boinc directory is wherever you extracted the boinc installation file to. You may be able to: 1. shut down boinc 2. rename the ca-bundle.crt in the boinc directory to something else 3. download this file https://boinc.berkeley.edu/ca-bundle.crt and copy it into your boinc installation directory. 4. restart boinc If that doesn't work, boinc is reading the ca-bundle.crt from somewhere other than the boinc directory and you can use some method to search for where that is, and replace it with the new one. You may have to be root user to do that. Good luck. |
Send message Joined: 15 Feb 12 Posts: 2 Credit: 1,422,611 RAC: 0 |
Thank you geophi, this was the cause and the fix worked beautifully, and was explained perfectly. The older certificate had many expired entries, while the newly downloaded one is current, worked like a charm, thank you again, issue resolved. |
![]() Send message Joined: 7 Aug 04 Posts: 2187 Credit: 64,822,615 RAC: 5,275 |
You may not read this, but almost universally, not running cpdn tasks on hyperthreads/SM threads is a good idea. If a 4 core, 8 thread PC runs 4 tasks at a time, instead of 8 tasks at a time, you will finish more tasks per unit time. In the olden days when tasks weren't as cache and memory intensive, one could get more done when using at least some of the hyperthreads as well. That's not the case any more. |
![]() Send message Joined: 15 May 09 Posts: 4558 Credit: 19,039,635 RAC: 18,944 |
You may not read this, but almost universally, not running cpdn tasks on hyperthreads/SM threads is a good idea. If a 4 core, 8 thread PC runs 4 tasks at a time, instead of 8 tasks at a time, you will finish more tasks per unit time. In the olden days when tasks weren't as cache and memory intensive, one could get more done when using at least some of the hyperthreads as well. That's not the case any more. I would add to what George has said that unless you have a lot of RAM you may find it worth cutting back even more. I have 4GB/real core and running five or six real cores depending on the application type seems to be the sweet spot. I am possible going to up memory to 64GB at some point and go from DDR4 PC 2800 to PC3200 at the same time and suspect this will make a significant difference. |
©2025 cpdn.org