I've researched this error & found two discussion threads that attribute this error to a simple timing error: BOINC timing out waiting for results, Not a problem with the actual results.

https://www.google.com/search?q=finish+file+present+too+long&oq=finish+file+present+too+long&aqs=chrome..69i57j69i61l2.2280j0j8&sourceid=chrome&ie=UTF-8

I've lost 5 results because of this error:

http://boinc.bakerlab.org/rosetta/results.php?userid=472655&offset=0&show_names=0&state=6&appid=

I'm not worried about the credits, but it's frustrating to see this much time contributed to the project getting tossed because of a simple timing error.

Any suggestions on how to prevent this in the future? I'm using this machine as my "Daily driver" as my other machines have died & I have other, more pressing issues to attend to.

I'm running BOINC on 100% of the CPUs 100% of the time, which works fine 99.95% of the time.

Thanks!!

Franko

This search works better:

https://www.google.com/search?ei=ApjHW7A955e2BeO1tPAL&q=%22finish+file+present+too+long%22&oq=%22finish+file+present+too+long%22&gs_l=psy-ab.3..0i7i30.967651.971417..972092...0.0..0.54.103.2......0....1..gws-wiz.......0i71j0i22i30.6CEhGn3jHEY

I get the same error message occasionally on one or two project.

I know they claim to have fixed it in some version of BOINC but it has kept occurring randomly for me.

I suspect the issue is so random they will never be able to completely fix it.

Think there was a problem with one batch from CPDN with this. For subsequent batches of the same type they were able to increase the maximum value to allow the tasks to run successfully.

I think we're talking about two different things.

"finish file present too long" is a 10 second limit hard coded into the BOINC client: when the science is all over and done, the science application should write a file to say that it's completed and BOINC can clean up and report it: then the science application should shut itself down and get out of the way so that BOINC can move on to the next job. See https://github.com/BOINC/boinc/blob/f14d96d2be2e5a290177f7b5391b0802fbd3756c/client/app_control.cpp#L127

It's hard to see how changing a batch (data) spec could change how quickly an application shuts down. Dave is more likely to be thinking of EXIT_TIME_LIMIT_EXCEEDED, which is a different beast entirely: that one can certainly be controlled by a project by correcting <rsc_fpops_bound>.

I just discovered 4 new errors:

http://boinc.bakerlab.org/rosetta/results.php?userid=472655&offset=0&show_names=0&state=6&appid=

<core_client_version>7.12.1</core_client_version>
<![CDATA[
<message>
finish file present too long</message>

I'm backing the "Use at Most" CPU's to 93.75% (30 of 32 threads, 15/16 cores) & setting the project to No New Tasks until I can get this resolved.

I did find messages in the error log:

10/22/2018 7:47:43 AM | Rosetta@home | Task jelva126_mut_5_9tcssm_73_K_0251_0001_0006_fragments_relax_SAVE_ALL_OUT_700558_46_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task jelva118_mut_5_8tcssm_73_K_0251_0001_0008_fragments_relax_SAVE_ALL_OUT_700549_46_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task jelva76_mut_5_4tcssm_73_K_0251_0001_0006_fragments_fold_SAVE_ALL_OUT_700633_96_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task DSIGG99_DEHCFABG_s00880005aa336a56_0002_0001_fragments_fold_SAVE_ALL_OUT_700443_272_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task jelva2_mut_5_10tcssm_61_K_0251_0001_0005_fragments_fold_SAVE_ALL_OUT_700582_96_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task DSIGG62_CDEFGBAH_s006200026a3c1c99_0001_0001_fragments_fold_SAVE_ALL_OUT_700403_280_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task jelva117_mut_5_8tcssm_73_K_0251_0001_0007_fragments_fold_SAVE_ALL_OUT_700548_115_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task DSIGG55_BEDGHCFA_s00450008aa336a56_0002_0001_fragments_fold_SAVE_ALL_OUT_700395_280_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task DSIGG88_DEFGBAHC_s008200032b122311_0001_0001_fragments_fold_SAVE_ALL_OUT_700431_280_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task jelva53_mut_5_2tcssm_73_K_0251_0001_0003_fragments_fold_SAVE_ALL_OUT_700608_140_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task jelva130_mut_5_9tcssm_73_K_0251_0001_0010_fragments_fold_SAVE_ALL_OUT_700563_140_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task TJ54_IGGH_A_B_C_F_G_D_7delE_0251_0001_0004_fragments_fold_SAVE_ALL_OUT_700139_290_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task jelva118_mut_5_8tcssm_73_K_0251_0001_0008_fragments_fold_SAVE_ALL_OUT_700549_140_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task DSIGG60_BGDEHCFA_s005600026a3c1c99_0002_0001_fragments_fold_SAVE_ALL_OUT_700401_299_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task jelva112_mut_5_8tcssm_73_K_0251_0001_0002_fragments_fold_SAVE_ALL_OUT_700543_164_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task jelva21_mut_5_6tcssm_61_K_0251_0001_0007_fragments_fold_SAVE_ALL_OUT_700573_189_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task jelva94_mut_5_6tcssm_73_K_0251_0001_0004_fragments_fold_SAVE_ALL_OUT_700653_188_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task jelva25_mut_5_8tcssm_61_K_0251_0001_0003_fragments_fold_SAVE_ALL_OUT_700577_226_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task DSIGG22_ADEHCFGB_s00150009aa336a56_0001_0001_fragments_fold_SAVE_ALL_OUT_700323_321_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task jelva3_mut_5_10tcssm_61_K_0251_0001_0008_fragments_fold_SAVE_ALL_OUT_700593_226_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task DSIGG240_GDEFCHAB_s015900036a3c1c99_0003_0001_fragments_fold_SAVE_ALL_OUT_700335_321_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task jelva14_mut_5_4tcssm_61_K_0251_0001_0007_fragments_fold_SAVE_ALL_OUT_700565_226_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task jelva53_mut_5_2tcssm_73_K_0251_0001_0003_fragments_fold_SAVE_ALL_OUT_700608_246_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task jelva15_mut_5_4tcssm_61_K_0251_0001_0009_fragments_fold_SAVE_ALL_OUT_700566_247_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task jelva78_mut_5_4tcssm_73_K_0251_0001_0008_fragments_fold_SAVE_ALL_OUT_700635_246_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.
10/22/2018 7:47:43 AM | Rosetta@home | Task TJ73_IGGH_A_B_C_F_G_D_E_8_0251_0008_fragments_fold_SAVE_ALL_OUT_700160_329_0 exited with zero status but no 'finished' file
10/22/2018 7:47:43 AM | Rosetta@home | If this happens repeatedly you may need to reset the project.

Most of the tasks mentioned in the error log do NOT show up here:
http://boinc.bakerlab.org/rosetta/results.php?userid=472655&offset=0&show_names=0&state=6&appid=
But this one does: http://boinc.bakerlab.org/result.php?resultid=1036002868

Please let me know what I can do to help troubleshoot the problem.

Thanks!!

Franko

This appears to be ROSETTA PROJECT RELATED Error and not really a generic BOINC issue.

Since this is a Rosetta Mini v3.78 Task, please copy/paste details you listed here to the Rosetta Number Crunching Forum Under Minirosetta 3.73-3.78 so the Rosetta developers are aware of the problem.

Sorry about the red herring Richard, you are right and I have had, "EXIT_TIME_LIMIT_EXCEEDED" on a testing batch of tasks since I posted here.

Done, thanks!!

Franko

This appears to be ROSETTA PROJECT RELATED Error and not really a generic BOINC issue.

Since this is a Rosetta Mini v3.78 Task, please copy/paste details you listed here to the Rosetta Number Crunching Forum Under Minirosetta 3.73-3.78 so the Rosetta developers are aware of the problem.