| 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: 7
|
|
| Author |
|
|
Richard Mitnick
Veteran Cruncher USA Joined: Feb 28, 2007 Post Count: 583 Status: Offline Project Badges:
|
The following has happened twice in two tasks. The computer is a PIII with 1 1 gig processor and 512megs of DRAM doing nothing but running crunching tasks.
----------------------------------------12/27/2007 5:54:38 PM|World Community Grid|Deferring communication for 1 min 0 sec 12/27/2007 5:54:38 PM|World Community Grid|Reason: Unrecoverable error for result X0000048710636200504111349_0 (The system cannot find the path specified. (0x3) - exit code 3 (0x3)) 12/27/2007 5:54:38 PM|World Community Grid|Computation for task X0000048710636200504111349_0 finished 12/27/2007 5:54:38 PM|World Community Grid|Output file X0000048710636200504111349_0_0 for task X0000048710636200504111349_0 absent I have only given you what I think you want, not the whole day or the other BOINC stuff. Any help or advice will be appreciated. >>RSM |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
My first guess would be a filesystem error. Can you run chkdisk?
If, on the other hand, it's a work unit problem - then we'll know soon enough. |
||
|
|
Richard Mitnick
Veteran Cruncher USA Joined: Feb 28, 2007 Post Count: 583 Status: Offline Project Badges:
|
Hi, thanks, I will run chkdisk, but I can't do it until after 6:00PM EST tomorrow.
----------------------------------------What do you mean about the work unit? Do you mean in other copies from other people? I can tell you that this machine is running Malaria and Spinhenge with no problems. I will let you know the results of the chkdisk run. Thanks. |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
You may want to try and detaching from World Community Grid and then attaching back. I encountered this once with 5.2 version of BOINC on linux. You may also want to upgrade your BOINC client up to the latest version as that error is more than likely not caused by the application.
-Uplinger |
||
|
|
Richard Mitnick
Veteran Cruncher USA Joined: Feb 28, 2007 Post Count: 583 Status: Offline Project Badges:
|
O.K., I ran chkdsk/f. No problems.
----------------------------------------If there is some report I should provide from that, you would need to tell me. I have run chkdsk/f a number of times over the years, it never found any errors, so I never looked for anything beyond. I did update to the WCG-BOINC 5.10.30. My other PIII, which is supposed to be running HCC, is running Dengue. The tasks are shorter. Maybe the BOINC scheduler is telling me something about these machines. I also updated this machine to 5.10.30. Both machines run 132 hrs/wk on whatever WCG gives them, plus two BOINC projects, Malaria and Spinhenge, with which they have no difficulty. So, with all that, maybe the best thing is for me to just watch and see what happens over the next couple of weeks. If there is anything you can say now, or suggestion now, or anything you want from me, like Messages, please let me know. Thanks all. >>RSM |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The error you are getting isn't the most helpful, since it doesn't say which path is causing a problem, and the error can be caused in many ways.
File system errors and malformed work units are the most common, but there are other less well understood causes, too. If this error isn't repeated, then there is nothing more we can do. Thank you for the report. |
||
|
|
Richard Mitnick
Veteran Cruncher USA Joined: Feb 28, 2007 Post Count: 583 Status: Offline Project Badges:
|
So, I think there is progress.
----------------------------------------Both PIII's are on WCG's 5.10.30. Both were detached and later re-attached. Both got HCC tasks way shorter than what I had previously seen. Both PIII's have been put on 24 hour running, so now 168 hrs/wk, up from 132 hrs/wk. We will see what happens now. >>RSM |
||
|
|
|