| 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: 49
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
;) 6.1.12 (just looked) is somehow even recommended, I saw that somewhere on this site that they’re going to switch soon. You are mistaken. 6.1.12 is a new alpha release. It will never be made recommended. BOINC uses odd minor versions for alpha releases, then goes to an even minor number when they have a release candidate. After months of beta testing, one of the beta builds will be promoted to the recommended stable version. What does top show? Is the application picking up from the last checkpoint, finishing, then exiting without being detected by BOINC? |
||
|
|
mirabilos
Cruncher Joined: Mar 25, 2008 Post Count: 37 Status: Offline Project Badges:
|
6.1.12 is a new alpha release Okay, but the problem seems to be the faah* app, not boinc… What does top show? Is the application picking up from the last checkpoint, finishing, then exiting without being detected by BOINC? No, the app is running:
top:
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello mirabilos,
BOINC 5.10.45 is the most recent stable release. I don't know what to look for on Linux but this is very poor: 02-Apr-2008 22:40:58 [---] Preferences limit memory usage when active to 119.77MB 02-Apr-2008 22:40:58 [---] Preferences limit memory usage when idle to 179.66MB You should set your preferences so that BOINC can always use 179.66MB, even when active. Lawrence |
||
|
|
mirabilos
Cruncher Joined: Mar 25, 2008 Post Count: 37 Status: Offline Project Badges:
|
Use no more than: XXX % of memory while computer in use
----------------------------------------Changing XXX from 50 to 75, that should do the trick? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well, something is wrong. There are 4 zombie processes, and no active WCG process. Try the stable version. It may not help, but it will give a reference point for further enquiries.
Since I'm unable to attach a debugger, there's not a lot more I can do. Do ask Pav for advice, though. And I will let the WCG techs know about your problem, but they won't be able to devote a great deal of time to this. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Use no more than: XXX % of memory while computer in use Changing XXX from 50 to 75, that should do the trick? When the limit is reached, you should see a "waiting for memory" message. I don't see that in your log anywhere. Increase the limit, but it won't solve your problem. |
||
|
|
mirabilos
Cruncher Joined: Mar 25, 2008 Post Count: 37 Status: Offline Project Badges:
|
Interestingly enough, after:
----------------------------------------– allowing for more RAM – --project … update – --result … suspend – --result … resume it works again:
and
|
||
|
|
mirabilos
Cruncher Joined: Mar 25, 2008 Post Count: 37 Status: Offline Project Badges:
|
Since I'm unable to attach a debugger We can do something about that. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It could be that the suspend/resume caused the work unit to pick up at the last checkpoint (again). It is likely to return to zombie state when the work unit completes (again).
Let's wait and observe whether that happens. |
||
|
|
mirabilos
Cruncher Joined: Mar 25, 2008 Post Count: 37 Status: Offline Project Badges:
|
Yes, it stalls again.
----------------------------------------I’ll build a 5.x boinc client then. |
||
|
|
|