Message boards :
Number crunching :
WU aborted by server (finish file present too long) - why?
Message board moderation
Author | Message |
---|---|
Send message Joined: 28 Mar 10 Posts: 12 Credit: 332,781 RAC: 46 |
Hello, I have strange error. The task #63839471 was aborted by server after 6 hours running with error "finish file present too long". Why? Log:
Task protokol:
|
Send message Joined: 22 Jan 13 Posts: 107 Credit: 804,597 RAC: 48 |
Did your Windows 10 update? I hear there are some problems with the last update. I am seeing this on other forums. It's mostly machines with NVidia cards and you may need to reinstall or update you NVidia driver to fix. My movie https://vimeo.com/manage/videos/502242 |
Send message Joined: 20 Jun 12 Posts: 63 Credit: 94,685 RAC: 0 |
This is BOINC error (bug/feature), not application nor "aborted by server" http://setiathome.berkeley.edu/forum_thread.php?id=78642 http://setiathome.berkeley.edu/forum_thread.php?id=79721 http://setiathome.berkeley.edu/forum_thread.php?id=78498 - ALF - "Find out what you don't do well ..... then don't do it!" :) |
Send message Joined: 28 Mar 10 Posts: 12 Credit: 332,781 RAC: 46 |
Thank you, it's interesting. So, I didn't restart computer at that moment. Something strange. It seems that this error has happened several times before. |
Send message Joined: 20 Jun 12 Posts: 63 Credit: 94,685 RAC: 0 |
From your log: " 21.09.2016 7:02:30 | WUProp@Home | [task] result data_collect_v4_1474189777_61052_0 checkpointed 21.09.2016 7:03:53 | WUProp@Home | [task] task_state=ABORT_PENDING for data_collect_v4_1474189777_61052_0 from request_abort ... 21.09.2016 7:03:57 | WUProp@Home | [task] Process for data_collect_v4_1474189777_61052_0 exited, exit code 0, task state 5 ... 07:03:39 (53416): called boinc_finish " At 07:03:39 the application created boinc_finish_called file and called boinc_finish() - "the last function it calls in application source code and that never returns back to app" http://setiathome.berkeley.edu/forum_thread.php?id=79721&postid=1792646#1792646 (Raistmer is the developer of OpenCL SETI@home applications) For some reason BOINC didn't respond to the boinc_finish() and didn't see the file boinc_finish_called for 14 seconds (till 7:03:53) App exited at 7:03:57 (18 seconds after calling boinc_finish() ) with "exit code 0" = No error I feel this BOINC check/precaution from hanging apps is too aggressive. I think the hard-coded timeout was (is?) 10 seconds (at which point BOINC decides to abort the task). This delay of 14 seconds may be caused by: - Antivirus scan (lock on the files in BOINC Data directory) - High HDD activity (paging, defrag) - Anything that appears to 'hang' the computer for some time I think the hard-coded timeout was increased (to 60 seconds?) in some BOINC version but don't know which. Richard Haselgrove or Ageless should know. - ALF - "Find out what you don't do well ..... then don't do it!" :) |
Send message Joined: 28 Mar 10 Posts: 12 Credit: 332,781 RAC: 46 |
Thanks! Yes, sometimes my computer is unresponsive, because multicore VMs or GPU BOINC tasks are running. |
©2024 Sébastien