Posts by Keith Myers
|
1)
Posted 3 days ago by 
Keith Myers
Post: The Asteroids gpu app is much less productive compared to the cpu app when deployed across a multi-core cpu. Why most of us don't bother with the gpu app and just run the cpu app. |
|
2)
(Message 9352)
Posted 20 days ago by
Keith Myers
Post: I don't put much trust in "theoreticals? Better data is achieved by actually deploying the hardware in an actual Boinc cruncher and see whether the applications can actually get any advantage from the new crunching hardware. |
|
3)
(Message 9315)
Posted 17 Dec 2025 by
Keith Myers
Post: Since it appears that the project is ignoring your Blackwell gpus exclusion in cc_config.xml if I understand your statement, I would go to the option of removing the detection report in the coproc_info.xml file and lock the file down as immutable so the client can't rewrite it anymore. |
|
4)
(Message 9291)
Posted 25 Nov 2025 by
Keith Myers
Post: Thanks so much Keith! No, not directly. The work_fetch_debug flag in the Event Log options can provide a clue to how much debt each project has to any other. But the output is extremely large, detailed and hard to suss out one individual parameter in all the other junk it exposes. Normally you only turn it on for just a couple of scheduler connections since it will swamp the log if left enabled. The other logging flag that is useful is rr_simulation. It does something similar to work_fetch_debug but doesn't swamp the output as much. Between the two, if you dig into the output you can see somewhat the relation between projects and their priorities to getting and running work on the host. I'd try rr_simuation first. |
|
5)
(Message 9287)
Posted 23 Nov 2025 by
Keith Myers
Post: Yes, this occurs because of the Boinc client REC (Recent Estimated Credit) algorithm that always runs in the client. The client tries to balance all your projects credits based on the average credits accrued across all your projects and resource shares. In the case where one project has a long spell of work completed and credited, when another project starts getting work again, that project needs to 'repay the credit debt' owed to the other recently run project. This then appears to override the clients resource shares and runs the long dormant project exclusively for a while and this observation is commented on frequently by new crunchers that their resource shares are not being observed correctly. There is one tweak the cruncher can use to ameliorate this effect with a cc_config.xml default option called <rec_half_life_days>10.000000</rec_half_life_days> in the file. If you change the REC averaging period from the default ten days to a single day, the credit debt can be repaid much sooner and the client will return to observing your resource shares more closely much sooner. So edit the cc_config.xml file for this parameter in the <options> section by changing it to <rec_half_life_days>1.000000</rec_half_life_days> |
|
6)
(Message 9271)
Posted 7 Nov 2025 by
Keith Myers
Post: You have a security certificate issue with the project. Either upgrade your client to a newer version or manually download the latest ca-cert.bundle from Boinc and install it |
|
7)
(Message 9243)
Posted 4 Oct 2025 by
Keith Myers
Post: Yes, your suspended tasks are the issue. BOINC doesn't like being perturbed by user manipulations. It considers the suspended tasks a priority since they are likely close if not not already in EDF mode but Boinc can't do anything about that since you manually suspended that work. Either abort the suspended work or unsuspend them and set NNT for those projects so Boinc can get back to round-robin scheduling of all your projects according to your weights. Then you can get your turn at the Asteroid work. |
|
8)
(Message 9239)
Posted 2 Oct 2025 by
Keith Myers
Post: It looks like you just started running that app on that host. Boinc can't and doesn't calculate accurate estimated completion times for tasks until 11 verified tasks for the app have been seen by BOINC. You only have 5 tasks verified so far. Once the 11th task is reported, the client will show an accurate APR rate for the app and your estimated times will begin to show accuracy to actual runtimes. |
|
9)
(Message 9212)
Posted 29 Sep 2025 by
Keith Myers
Post: I'm not seeing stats at FreeDC. Skillz told me he wasn't going to make any changes on the old code for the old website. He would make the change on the new website when he gets it finally production ready. |
|
10)
(Message 9203)
Posted 29 Sep 2025 by
Keith Myers
Post: Asteroids app developer has tried to contact the server admin but has never received any response or acknowledgement of said contact. So no response from admin yet. So we continue to be stuck with no way to contact project, report tasks or request more without using the workaround. And no external stats site can show any stats either still of completed work or updated stats. |
|
11)
(Message 9195)
Posted 27 Sep 2025 by
Keith Myers
Post: Check for a double entry in the dpkg-reconfigure app list. Remove a duplicate GEANT TLS RSA 1 |
|
12)
(Message 9192)
Posted 27 Sep 2025 by
Keith Myers
Post: Read the thread https://asteroidsathome.net/boinc/forum_thread.php?id=1154 for your fix solution. |
|
13)
(Message 9191)
Posted 27 Sep 2025 by
Keith Myers
Post: My Windows systems are receiving and completing tasks is the "certificate" issue only Linux related ? Yes. Linux and Mac. |
|
14)
(Message 9190)
Posted 27 Sep 2025 by
Keith Myers
Post:
There is only ONE server here at Asteroids. It runs ALL processes on the Supermicro X11SW-TF (1 x Intel Xeon Silver 4214 2.20 GHz, 256 (4 x 64) GB RAM, 8 x 2TB HDD SAS 10K rpm (RAID6) OS Debian Jessie) server. The reason that browsers work is because it uses a different protocol that manages comms with the primary certificate compared to the client needing to use different protocols provided by the intermediate certificate which is not installed into the server yet. |
|
15)
(Message 9189)
Posted 27 Sep 2025 by
Keith Myers
Post: I posted a bug report and request at BoincStats for them to apply the intermediate certificate fix. No reply so far. Over at FreeDC, the admin stated he won't be applying any fixes to the current website and database until he can move everything over to the new code and new website. So, no stats from there either until the website changeover. No timeline given for that event yet. |
|
16)
(Message 9164)
Posted 25 Sep 2025 by
Keith Myers
Post: Read this forum message and follow the instructions. https://asteroidsathome.net/boinc/forum_thread.php?id=1154&postid=9135 Then after adding the certificate, your host will be able to contact the project again for new work. |
|
17)
(Message 9128)
Posted 19 Sep 2025 by
Keith Myers
Post: The server admin has to fix the secondary certificate issue on his side. Nothing can be done but wait it out. |
|
18)
(Message 9115)
Posted 11 Sep 2025 by
Keith Myers
Post: Seems like they are rapidly refilling tasks now after the server upgrade. 800K now available as i post. |
|
19)
(Message 9100)
Posted 17 Aug 2025 by
Keith Myers
Post: No, this project has been continously active since late 2022 when it came back online. |
|
20)
(Message 9097)
Posted 16 Aug 2025 by
Keith Myers
Post: Are you going to implement a separate science database along with the working database so we don't have 8 months of old data still in our accounts to load every web page visit? |
Next 20