| 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: 3
|
|
| Author |
|
|
steffen_moeller
Cruncher Joined: Dec 3, 2005 Post Count: 44 Status: Offline |
Hi,
on my NFS directory I unpacked several versions of BOINC (5.4,5.6 and 5.8.2) from boinc.berkeley.edu. Each has its separate directory. When there is a machine idling at the weekend, I may then go and crunch for FAAH for some 40 hours ( -> about 10 WUs per machine) and kill them the latest Monday morning. The assignment of the machine however is not fixed for any such directory. Starting with 5.8.2, I have now observed no CPU benchmark to be performed when starting ./run_client. Even worse: the latest work unit is submitted without being completed. Two questions: * Bug or feature? * Can you detect such Workunits for more than their short analysis time, e.g. faah1232_d107n939_x2BPZ_02_0, and what happens to them? Many thanks Steffen |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I don't think that's a supported configuration. Strange problems are almost inevitable.
Why do you have three versions of BOINC? |
||
|
|
steffen_moeller
Cruncher Joined: Dec 3, 2005 Post Count: 44 Status: Offline |
I don't think that's a supported configuration. Strange problems are almost inevitable. That the machines running on a folder are exchanged is indeed rather rare. But others may do this, too, and if there is a problem that disturbs the projects, then this certainly must be fixed asap. The exchange of the client host is so easy to check that I did not expect any problem from that end. The user (me) does not change. Neither does the version of boinc for a particular WU. There is never more than one machine running per folder at any time. Why do you have three versions of BOINC? I always took the latest that was available at the time and did not want to ruin the WU that was running or partially done before. Though the problem would occur if I only ran the 5.8.2, too. A single WU never sees different versions of the BOINC client. The exchange of machines running on a workunit makes a problem from what you say. To me this is a bug and I should report it to the BOINC developers, then. |
||
|
|
|