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: 4
|
![]() |
Author |
|
SafetyGuy
Cruncher Joined: Jan 11, 2006 Post Count: 2 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I am running the client on a Mac 10.6 system. I have a recurring problem of the elapsed time of a project resetting to zero after the Mac has been in screen saver mode. I do not shut down the hard drive in screen save.
It seems to be happening with the Clean Water project more than others. Today I had to abort a task due today that has been running nearly a week. I am running BOINC 7.0.31 (x86) Any help would be appreciated. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Please provide us with more science specific information: Which research exactly? Got a message log for us from the stdoutdae.txt file [BOINC Data directory] where tasks reset and a Result Log of a task that reset [Click on Status link on Result Status page]. Do these tasks [ever] finish by themselves, or are you just aborting them?
BTW, The water projects finished, Clean Water (Aug.19) and Sustainable Water (Oct.17), so those cant have been current observations. |
||
|
SafetyGuy
Cruncher Joined: Jan 11, 2006 Post Count: 2 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Sorry, my bad. The project was The Clean Energy Project - Phase 2. The task I aborted today has the ID E210418_762_C.32.C26H15N3OSSi.01258221.4.set1d06
I searched my Mac and did not see the message log or TXT file you mentioned. The result log gave the task ID I referenced above. The tasks that appear to resetting do not finish that I can recall. I have aborted them when they occur, normally when the due date comes and they have not completed. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The location of BOINC data is printed in message/event log at start up of client.
CEP2 is currently cut off at 12 hours CPU time, so if you see them going beyond 16-17 hours elapsed [depends on when you run BOINC default throttled at 60%], then it's ample time to consider sending them south. If this is a desktop, try setting the activity menu to 100% [Run Always] and see if they then regularly complete. Some system combinations don't like the BOINC way of slowing tasks down [stop-start-stop-start etc] |
||
|
|
![]() |