| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Genome Comparison
Thread: Latest units stuck at 0%? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 83
|
|
| Author |
|
|
Viktors
Former World Community Grid Tech Joined: Sep 20, 2004 Post Count: 653 Status: Offline Project Badges: 
|
We have resumed Genome Comparison on UD and will soon do so on Boinc as well. Please see the following post for more details: posting
Thank you for your patience. |
||
|
|
Robert Heikkinen
Advanced Cruncher Joined: Mar 14, 2013 Post Count: 57 Status: Offline |
Are the problems solved?
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
For UD agents. Awaiting word for BOINC.
|
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: 
|
The BOINC 5.8 client introduced a new feature where the BOINC server can send a message to it telling it to abort a workunit. However, there wasn't any server side code to take advantage of the this new message. We talked to the BOINC developers over the past day and we have implemented a new feature on the server that allows the server to abort a workunit on a client if the workunit has been canceled on the server. We deployed this to our servers about 3 hours ago and we have just finished canceling all of the suspect workunits.
----------------------------------------This means that any member using the BOINC client 5.8 will get a message telling it to abort any workunits that are part of this problem the next time that the client contacts the server. Go ahead and manually force an update to have your client contact the server immediately by going to the advanced view, project tab and selecting World Community Grid and then click on 'Update'. If you have one of the troublesome workunits you will see a message such as: 3/21/2007 4:43:16 PM|World Community Grid|Message from server: Result 10000001-10001441_0 is no longer usable and you will see in the tasks tab that the result is now marked 'Aborted by project'. I should also mention that earlier versions of the BOINC client will still see the message: 3/21/2007 4:43:16 PM|World Community Grid|Message from server: Result 10000001-10001441_0 is no longer usable but the automatic abort will not occur. Users who see this messages should aborted the referenced workunit. [Edit 2 times, last edit by knreed at Mar 22, 2007 2:24:11 AM] |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges:
|
For UD agents. Awaiting word for BOINC. The new builds are running in development and we are waiting for enough results returned to make sure they are ok to run in production. |
||
|
|
Diana G.
Master Cruncher Joined: Apr 6, 2005 Post Count: 3003 Status: Offline Project Badges:
|
You guys are awesome!!! Thanks for all the hard work you do!
---------------------------------------- Diana G.  |
||
|
|
Robert Heikkinen
Advanced Cruncher Joined: Mar 14, 2013 Post Count: 57 Status: Offline |
I´m now rejoining GC and hoping for no further problems..
 |
|||
|
||||
|
Robert Heikkinen
Advanced Cruncher Joined: Mar 14, 2013 Post Count: 57 Status: Offline |
UD is working fine but it goes slower than before..
But whatever!  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Users who see this messages should aborted the referenced workunit. Leaving out how horribly wasteful this is (I don't monitor mine much at all -- it's wasted 48 hours of CPU on this!), how? If I kill boinc and restart it, it just goes and restarts the same useless WU from the beginning. Is the a "correct" way to terminate it and get it to receive another WU from the server? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Users of earlier BOINC clients will see the same message:
3/21/2007 4:43:16 PM|World Community Grid|Message from server: Result 10000001-10001441_0 is no longer usable but the automatic abort will not occur. Users who see this messages should abort the referenced workunit. You have to abort it manually I think, and get new work units. |
||
|
|
|