| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Website Support
Thread: wu errors from boinc 6.10.17 |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 9
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
in the last 2 weeks I have been receiving alot of repair wu's from subject boinc version...
----------------------------------------Is the system setup to curtail wu distribution to this client after so many error's??????? [Edit 2 times, last edit by Former Member at Aug 14, 2012 4:46:48 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Very complete. What OS (Win/Lnx/Mac? What science(s)? What type of errors in the 6.10.17 logs [which could include aborts which also log [erroneously] as error? You're not the first one wondering about this client version. Suggestion was made before to upgrade, but if owners don't read, or not willing to action it ends there.
Standard normal: If a client fails at a task it gets a reduced quota. If it fails continuously, it goes down all the way to 1 per day [per science I think is the server 700 rule]. If it succeeds, the quota is doubled, so 1,2,4 etc till max of 120 per core per day [overall for all sciences combined, so to prevent a massive single host stockpiling, and then if it blows, thousands going to the repair cue or No Reply land]. Summation: Can't do much about this. --//-- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
ty sek I will resolve this thread then and just live with them.
here is one of there result's. same situation of this on all projects not just this one.... Result Log Result Name: SN2S_ 2X8L_ 1000020_ 0402_ 0-- <core_client_version>6.10.17</core_client_version> <![CDATA[ <message> too many exit(0)s </message> ]]> |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
"too many exits!"
You still don't say which OS, but suspect an older Linux distro. 8 or 9, possibly 10.04. Yes, that would be the one [and a major "way to busy" issue]. Client set to default 25% and "Run based on prefs" would not incur that. My 11.10 still gets this [with 7.0.27], so after much testing, found the sweet-point to pause BOINC when the non-BOINC momentarily load goes above 35%. Not 100% sure, but think 7.0.28 has now 75% as default [or it is server 700 doing this?]. Too high for my Linuxes when running any of the heavies, and the ultralight HCMD2 :(. The DDDT2 run though exemplary, 99.73% efficiency on average this last run [11.10 + latest 3.0.xx kernel + 7.0.27 client]. Still if a Linux-64 bit Q6600 needs 1.25 CPU hours more for the ''p'' of C-Type than my 8 threaded Octo HT laptop W7-64 laptop (4.75 hours v 3.5 hours), not the best platform to run on (And I've torqued it off last night from that feeder for this reason). --//-- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Today, digging through a long list of PVal/PVer, it struck me as there being rows upon rows of results with normal claim in credit, but zero processing time, getting marked with Error. Low and behold, these no-time / claim correct were all with client 6.10.17. This was with windows wingman! If the message has not reached anyone with client 6.10.17... Time to upgrade, be it 6.10.58 or .60 or those with proxy, 7.0.31 [also WCG Mac proposed for OS-X 10.8 Lion].
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Using random sampling of my wing_doneWUs that did not get a 'Valid' status, a number of those WUs were indicated as using BOINC_v6.10.17. They occurred frequently enough to get my attention alright and, yes, the frequent fault indicated is 'too many exits'. Not sure if Windows only and not sure if CFSW only. Anyways, this was even before the current server issue.
; |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It's just a bump to top for those on 6.10.17, case the point was missed. There is *no* correlation to the server issues, nor a specificity to Windows but to highlight that there seem to be fair numbers still around of this flaky client [on multiple fronts], on windows too.
----------------------------------------[Edit 1 times, last edit by Former Member at Aug 14, 2012 3:18:33 PM] |
||
|
|
pcwr
Ace Cruncher England Joined: Sep 17, 2005 Post Count: 10903 Status: Offline Project Badges: 
|
My old PC is running 6.2.28 and are all valid. I don't intend upgrading this PC to a newer version of BOINC. It did run a newer version than 6.10.58 but always went wrong.
----------------------------------------My Win7 PCs run 6.10.58 these might get upgraded as I only get half the credit on the laptop. Patrick  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Using random sampling of my wing_doneWUs that did not get a 'Valid' status, a number of those WUs were indicated as using BOINC_v6.10.17. They occurred frequently enough to get my attention alright and, yes, the frequent fault indicated is 'too many exits'. Not sure if Windows only and not sure if CFSW only. Anyways, this was even before the current server issue. ; I saw loads of these "too many exits" generated from my wingmen in VINA-based projects too, so it seems it's not a project-specific issue. |
||
|
|
|