| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 572
|
|
| Author |
|
|
alanb1951
Veteran Cruncher Joined: Jan 20, 2006 Post Count: 1317 Status: Offline Project Badges:
|
Only the newly issued workunits ending with 0 are getting validated, while the ones that were resent after previous errors — those ending with 2 through 4 — remain stuck in pending validation status. I think that's expected behaviour at the moment. See the 2025-10-28 Operational Status report, which someone copied into this thread recently, and note the item starting "Regarding uploads that span the downtime for migration"... Cheers - Al. |
||
|
|
alanb1951
Veteran Cruncher Joined: Jan 20, 2006 Post Count: 1317 Status: Offline Project Badges:
|
Re extremely large estimated run times (and, possibly, extreme credit requests)...
----------------------------------------I've had a look at the new WUs and their parameter files are very similar to those of the retries we're currently seeing -- unsurprisingly, they also take about the same amount of time to run! However, they are being sent out with an estimated floating point operations figure that is nearly 3 times as high as that associated with the retry tasks, with the expected effect on estimated run-time calculations. And, as far as I can tell, that same very high FPOPs estimate was also used for all the test work units. Given the vast variations in run times of those tasks, I suspect that won't have helped the Claimed Credit calculations :-( These new tasks really shouldn't have such a high estimated FPOPs figure, but if/when it gets sorted out there may well be a situation where the estimates are so much lower that claimed credit may drop a long way until things re-stabilize! Cheers - Al. [Edited to rephrase final paragraph.] [Edit 2 times, last edit by alanb1951 at Oct 29, 2025 9:42:00 AM] |
||
|
|
TLD
Veteran Cruncher USA Joined: Jul 22, 2005 Post Count: 856 Status: Offline Project Badges:
|
111 World Community Grid 10/28/2025 9:51:43 AM [error] Can't parse file info in scheduler reply: file name is empty or has '..' 112 World Community Grid 10/28/2025 9:51:43 AM [error] Can't parse file info in scheduler reply: file name is empty or has '..' 113 World Community Grid 10/28/2025 9:51:43 AM [error] Can't parse file info in scheduler reply: file name is empty or has '..' 114 World Community Grid 10/28/2025 9:51:43 AM [error] Can't parse file info in scheduler reply: file name is empty or has '..' 115 World Community Grid 10/28/2025 9:51:43 AM [error] Can't parse file info in scheduler reply: file name is empty or has '..' 116 World Community Grid 10/28/2025 9:51:43 AM [error] Can't parse file info in scheduler reply: file name is empty or has '..' 117 World Community Grid 10/28/2025 9:51:43 AM [error] Can't parse file info in scheduler reply: file name is empty or has '..' 118 World Community Grid 10/28/2025 9:51:43 AM [error] Can't parse file info in scheduler reply: file name is empty or has '..' 119 World Community Grid 10/28/2025 9:51:43 AM [error] Can't parse file info in scheduler reply: file name is empty or has '..' 120 World Community Grid 10/28/2025 9:51:43 AM [error] Can't parse file info in scheduler reply: file name is empty or has '..' 121 World Community Grid 10/28/2025 9:51:43 AM Scheduler request completed: got 5 new tasks 122 World Community Grid 10/28/2025 9:51:43 AM Resent lost task MCM1_9999999_0005_1 123 World Community Grid 10/28/2025 9:51:43 AM Resent lost task MCM1_9999999_0008_1 124 World Community Grid 10/28/2025 9:51:43 AM Resent lost task MCM1_9999999_0006_0 125 World Community Grid 10/28/2025 9:51:43 AM Resent lost task MCM1_9999999_0009_0 126 World Community Grid 10/28/2025 9:51:43 AM Resent lost task MCM1_9999999_0007_0 127 World Community Grid 10/28/2025 9:51:43 AM Project requested delay of 121 seconds 128 World Community Grid 10/28/2025 9:51:43 AM [error] State file error: missing file 129 World Community Grid 10/28/2025 9:51:43 AM [error] State file error: missing input file 130 World Community Grid 10/28/2025 9:51:43 AM [error] Can't handle task MCM1_9999999_0005 in scheduler reply 131 World Community Grid 10/28/2025 9:51:43 AM [error] State file error: missing file 132 World Community Grid 10/28/2025 9:51:43 AM [error] State file error: missing input file 133 World Community Grid 10/28/2025 9:51:43 AM [error] Can't handle task MCM1_9999999_0008 in scheduler reply 134 World Community Grid 10/28/2025 9:51:43 AM [error] State file error: missing file 135 World Community Grid 10/28/2025 9:51:43 AM [error] State file error: missing input file 136 World Community Grid 10/28/2025 9:51:43 AM [error] Can't handle task MCM1_9999999_0006 in scheduler reply 137 World Community Grid 10/28/2025 9:51:43 AM [error] State file error: missing file 138 World Community Grid 10/28/2025 9:51:43 AM [error] State file error: missing input file 139 World Community Grid 10/28/2025 9:51:43 AM [error] Can't handle task MCM1_9999999_0009 in scheduler reply 140 World Community Grid 10/28/2025 9:51:43 AM [error] State file error: missing file 141 World Community Grid 10/28/2025 9:51:43 AM [error] State file error: missing input file 142 World Community Grid 10/28/2025 9:51:43 AM [error] Can't handle task MCM1_9999999_0007 in scheduler reply 143 World Community Grid 10/28/2025 9:51:43 AM [error] State file error: missing task MCM1_9999999_0005 144 World Community Grid 10/28/2025 9:51:43 AM [error] Can't handle task MCM1_9999999_0005_1 in scheduler reply 145 World Community Grid 10/28/2025 9:51:43 AM [error] State file error: missing task MCM1_9999999_0008 146 World Community Grid 10/28/2025 9:51:43 AM [error] Can't handle task MCM1_9999999_0008_1 in scheduler reply 147 World Community Grid 10/28/2025 9:51:43 AM [error] State file error: missing task MCM1_9999999_0006 148 World Community Grid 10/28/2025 9:51:43 AM [error] Can't handle task MCM1_9999999_0006_0 in scheduler reply 149 World Community Grid 10/28/2025 9:51:43 AM [error] State file error: missing task MCM1_9999999_0009 150 World Community Grid 10/28/2025 9:51:43 AM [error] Can't handle task MCM1_9999999_0009_0 in scheduler reply 151 World Community Grid 10/28/2025 9:51:43 AM [error] State file error: missing task MCM1_9999999_0007 152 World Community Grid 10/28/2025 9:51:43 AM [error] Can't handle task MCM1_9999999_0007_0 in scheduler reply This machine will not download WUs. My other machines are receiving WUs. I have tried to reset the project. Had to uninstall and reinstall to get WUs on this machine. ![]() |
||
|
|
MJH333
Senior Cruncher England Joined: Apr 3, 2021 Post Count: 300 Status: Offline Project Badges:
|
My overview page is now saying “Last updated: Oct. 28, 2025 - 23:59 UTC”.
No idea whether the actual stats shown on the overview page have changed, as I haven’t looked at it for ages. Cheers, Mark |
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2346 Status: Offline Project Badges:
|
What a good observation, Mark! Now it says "Last updated: Oct. 29, 2025 - 12:06 UTC” and the graph is showing an uptick on Oct 29 after a long flatliner (31 Aug - 28 Oct). After a runtime of 0 days yesterday it is now showing 16.855 days for me on Oct 29. The API also reports that my total runtime has increased by 16 days, 20 hours, 30 minutes and 45 seconds.
----------------------------------------Adri [Edit 1 times, last edit by adriverhoef at Oct 29, 2025 4:21:30 PM] |
||
|
|
alanb1951
Veteran Cruncher Joined: Jan 20, 2006 Post Count: 1317 Status: Offline Project Badges:
|
The Statistics history pages for projects have also been updated by the noon-time stats run, not that they have much to report...
----------------------------------------However, the three ARP1 pages on the download server still seem to be behind an ACL (not that they'd contain anything new at present...) Cheers - Al. [Edit 1 times, last edit by alanb1951 at Oct 29, 2025 5:03:41 PM] |
||
|
|
Grumpy Swede
Master Cruncher Svíþjóð Joined: Apr 10, 2020 Post Count: 2498 Status: Offline Project Badges:
|
Well, at least we're up and running (ish), but it's still a long long way before everything can be said to be fully operational and OK.
----------------------------------------At least new tasks are sent out, crunched, uploaded, reported, and validated with credit. Not all test tasks have been validated and given credit though, and no tasks from before the "migration", are validated yet. But that will happen later on, if I interpret the posts from the team, on the Operational Status page right. But there's no hurry, as far as I'm concerned. ![]() [Edit 1 times, last edit by Grumpy Swede at Oct 29, 2025 10:03:55 PM] |
||
|
|
Grumpy Swede
Master Cruncher Svíþjóð Joined: Apr 10, 2020 Post Count: 2498 Status: Offline Project Badges:
|
Something we saw several times before the "migration", is back
----------------------------------------BOINC problem: Server can't open database Project requested delay of 3600 seconds [Edit 5 times, last edit by Grumpy Swede at Oct 30, 2025 2:28:34 AM] |
||
|
|
TPCBF
Master Cruncher USA Joined: Jan 2, 2011 Post Count: 2173 Status: Offline Project Badges:
|
Something we saw several times before the "migration", is back Yup, same here. Have a few more WUs to crunch before the first ones start running dry...BOINC problem: Server can't open database Project requested delay of 3600 seconds Ralf |
||
|
|
bfmorse
Senior Cruncher US Joined: Jul 26, 2009 Post Count: 442 Status: Offline Project Badges:
|
I noticed that too.
While I was troubleshooting a new system that was not using all the available cores, I also noticed (before the system database problem showed up) that the device assignments did not seem to be propagating to my new system - It was still functional as DEFAULT even though it APPEARED to be defined as SCHOOL The new system is 8 core and was only using 3 (default config) When I went to attempt to set that system's profile, it did not respond as expected when I clicked on SAVE - it eventually came back and said that the system was doing other things for the next 77 minutes. HOPEFULLY this is just a new, normal, temporary problem and when the current processing finishes its run, things will return to normal - otherwise, will require human intervention. |
||
|
|
|