Once in a blue moon, I'll get a task that errors in "finish file present too long". If I recall correctly, I've had this happen on another BOINC project, where the calculation became larger than the maximum upload size.
However, this task completed on other computers, so possibly my computer was in error.
http://denis.usj.es/denisathome/workunit.php?wuid=1130197
Hope this helps!
Stderr output
<core_client_version>7.4.36</core_client_version>
<![CDATA[
<stderr_txt>
Operation time:300000.000000
Diferential Time:0.002000
Frequency:50
Initial Time:299000.000000
03:24:14 (9408): called boinc_finish(0)
</stderr_txt>
<message>
finish file present too long
</message>
]]>
/ 
Reply
Quote
jcastroVolunteer developer
Volunteer tester
Project scientist
Send message
Joined: 16 Mar 15
Posts: 218
Credit: 14,859
RAC: 0
Hi!
We are trying to avoid those strange problems. Most of them are in the "client side" but we are also searching to avoid them changing the limits of the server. Some of those problems are caused by closing and opening the application so many time. This first version didn't have checkpoint function so it could be related to it.
I hope this problem would be solved with the next version of the application,
Beste Regards, Joel.
/ Reply
Quote
Still getting them. A lot of these happen when I'm nowhere near the computer to close or open the application.
/ Reply
Quote
jcastroVolunteer developer
Volunteer tester
Project scientist
Send message
Joined: 16 Mar 15
Posts: 218
Credit: 14,859
RAC: 0
Hi!
Seeing other errors in the same host I could think that could be related to the time that this host restarts/closes boinc/ changes project. Maybe changing the time to checkpoint the project could help you to end more tasks.
I have received from the host 3 different error, the one you said, another one related with "Too many exists" and other related to "exceed the time limit" so maybe if you change some parameters to take less work from each project or change between different projects could help you.
Best regards, Joel.
/ Reply
Quote
Still getting them. A lot of these happen when I'm nowhere near the computer to close or open the application.
Upgrade to BOINC 7.6.6
/ Reply
Quote
Thanks for your feedback.
Can you please recommend a set of parameters that you think will work?
Currently I'm switching between applications every 70 minutes.
Minimum work buffer is .1 days, maximum additional buffer is another .1 days.
There is no CPU time restriction.
As for the newest BOINC Beta, I would not feel comfortable switching to that if it might disrupt my other tasks.
/ Reply
Quote
As for the newest BOINC Beta, I would not feel comfortable switching to that if it might disrupt my other tasks.
v7.6.6 is not Beta, it's the recommended BOINC version.
Your problem is recognized as a client issue. It happens to some users more than to others and also some projects suffering more than others.
It has to do with cleaning up the slot directory after a task is ready.
Older versions of BOINC tries to rename an optional non existing file and retried that too often.
BOINC tells you "finish file present - too long", because the temporary finish file placed by BOINC during cleanup stays longer than 10 seconds.
/ Reply
Quote
It was released as the recommended version...today. What a scold! When I posted that, it hadn't been released.
7.4.42 must be such an old version.
Moreover, where in the release notes does it say anything about slot directory bugs getting fixed?
[/quote]
/ Reply
Quote
Moreover, where in the release notes does it say anything about slot directory bugs getting fixed?
Sorry Dayle, that you've wasted so much cpu-cycles and in fact the jobs were ready. Sometimes it's good being ahead of the troops.
Do you really think, that every change in the source code will find its way into release notes.
Sorry, I've to disappoint you in that, but the code change was made on the 17th of June by David Anderson himself and called:
"client: fix bug that caused delay in job cleanup"
with the comment:
"If a job has an output file with <copy_file> and <optional>,
and it doesn't create the file,
then the call to boinc_rename() (to move it to the project dir) fails,
and we back off and retry."
/ Reply
Quote
Updating to the new version of BOINC did nothing.
Several hours of crunching a day are being tossed out the window. It's 90 degrees where I live. So DENIS is going to 0 priority until version 1.06 or whenever this is solved.
/ Reply
Quote
I'm getting the error message "finish file present too long" for some BOINC tasks. The computer is running Ubuntu 16.10, BOINC 7.6.33.
There are two types of error of this kind. The first type is when the error message is near to the beginning of the Stderr output:
<core_client_version>7.6.33</core_client_version>
<![CDATA[
<message>
finish file present too long
</message>
<stderr_txt>
[...]
Tasks of this kind are:
- Task 1016612 of Workunit 468614
- Task 1016615 of Workunit 468620
- Task 1016617 of Workunit 468626
- Task 1016345 of Workunit 474151
- Task 1016350 of Workunit 474153
- Task 1016430 of Workunit 396848
[/url]
The second type of the "finish file present too long" error is when the error message appears at the end of Stderr output:
[...]
Doing CP It:178377992403:41:33 (118753): called boinc_finish
</stderr_txt>
<message>
finish file present too long
</message>
]]>
Task of this kind is:
I also found a similar topic at boinc.berkeley.edu forum.
/ Reply
Quote