On 10 June 2014 00:29, Richard Haselgrove <[email protected]> wrote:
> Ironically, the topic of tasks which make 0% progress - BOINC thinks > they're running, and elapsed time continues to accrue, but I guess CPU time > doesn't rise - cropped up at LHC as well recently. > > > http://lhcathomeclassic.cern.ch/sixtrack/forum_thread.php?id=3843&postid=26583 > Hmm. It's a bit unclear if the app's process still existed or had it exited. Saying it doesn't show in top could mean that with 0% CPU usage it doesn't fit in the screen along with the actually running processes. If the process still existed it would be a bug in the app, either in the project's code or BOINC API. If the process had exited then it's a bug in the client. If this is happening somewhat often and if it looks like a client bug OP could try running BOINC with <task_debug> set. Then every time BOINC starts a new task the process' ID is printed to logs. If a process gets stuck like that that process ID could then be used to see if BOINC is monitoring the right process. I've been running with <task_debug> ever since I reported the case of BOINC (apparently) losing track of task's process. So far all I've gotten is ton of logs... -Juha _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
