LATeah1018F_1224.0_261507_0.0_0 running at 100%

MCarbone90
MCarbone90
Joined: 2 May 20
Posts: 3
Credit: 122661
RAC: 0
Topic 222375

So, I've run into a similar issue before, and through these issues, I'm learning a little more how BOINC behaves on my computer.

I know that this particular task took almost a full 24 hours to reach completion. However, it has also been sitting at 100% and running for almost 12 hours now. With the remaining estimated time at "---"

In the past couple of days, I've seen a task or two hang at 63% for a few hours only to eventually complete itself.

I suspect that this task is running into a similar issue. Having spent a a full day letting my computer work on this task, I'm reluctant to abort. I'm hoping that by simply leaving it alone that it will eventually complete and upload.

Update: According to activity monitor, the task is no longer taking up CPU processing, additionally, every two minutes it will reset its elapsed time from 9:25:59 to 9:23:00. I've since suspended the task so my iMac may continue working on more tasks.

Holmis
Joined: 4 Jan 05
Posts: 1118
Credit: 1055935564
RAC: 0

Try to let the task run again

Try to let the task run again and if that fails then try to restart Boinc and if that fails then restart the computer. Only if all of these fail (you could try to reboot the computer to skip the other two) should you consider aborting the task.
Sometimes things happen that prevents a task from completing and most of the times one of the three suggestions above will let the task either start over from the beginning or from the latest checkpoint and from there the task will most probably run normally.

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 5850
Credit: 110040297299
RAC: 22410485

MCarbone90 wrote:.... it has

MCarbone90 wrote:
.... it has also been sitting at 100% and running for almost 12 hours now. With the remaining estimated time at "---"

That sounds like it has never written the first checkpoint (ie. has made no progress at all) and that all that is happening is BOINC's 'simulated' progress until the very first checkpoint is written.

To check this, open BOINC Manager in Advanced View and go to the tasks tab.  Select this particular task and click the 'Properties' button.  There will be information which includes the "CPU time since checkpoint", as well as a lot of other stuff.  If the task is not actually clocking up CPU time, try stopping and restarting BOINC.  You may actually need a reboot to get things moving.

EDIT:  I hadn't seen Holmis' reply when I posted mine.

Cheers,
Gary.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.