Message boards : Number crunching : Client error - compute error
Author | Message |
---|---|
Bruce Downing Send message Joined: 19 Jul 08 Posts: 16 Credit: 8,040,615 RAC: 1,200 |
Several recent tasks have ended with this message but no further explanation. Anything I can do? Thanks, Bruce D. (I also posted this in Q&A) |
Murasaki Send message Joined: 20 Apr 06 Posts: 303 Credit: 511,418 RAC: 0 |
Unfortunately errors can happen sometimes for different reasons. The best thing to do is to post a message in the Rosetta version threads and include a link to the task report that has the error. The project team can look at the problem and see what the solution is. If a lot of people report the same problem in a short time period it may mean that a dodgy batch of work units were sent out and the project team can remove the batch before anyone else wastes any time. The current thread is Minirosetta 1.82 and a report you might write could be: wrote: lr8_score12_run02_rlbd_1bq9_IGNORE_THE_REST_DECOY_12906_795_1 In this case the linked task report holds quite a large amount of data as to what went wrong. Hopefully this will help the project team to find and fix the error. |
mikey Send message Joined: 5 Jan 06 Posts: 1895 Credit: 9,178,827 RAC: 3,166 |
Several recent tasks have ended with this message but no further explanation. Anything I can do? Do you by chance keep units in memory when switching between your projects? Your Account, Computing Preferences "Leave applications in memory while suspended? (suspended applications will consume swap space if 'yes') yes"? Is yours set to no by chance? If so try changing it to yes and see if it stops the problem. Sometimes when people crunch for multiple projects their are problems when coming back to a unit that was swapped away from to crunch on a different unit. Just a thought, another idea might be to make sure your video card drivers are up to date. Have you rebooted the machine in the last month? If not try doing that too. As Muraski said this problem is a very long standing on in Boinc because it can be soooo many different things, Microsoft did not make error codes easy to figure out! |
Message boards :
Number crunching :
Client error - compute error
©2024 University of Washington
https://www.bakerlab.org