I have one system running that gets occasional error messages - maybe 1 a day. The system is an old I7 quad CPU running Seti at 100% under Windows. The system is headless with only remote desktop access to interact with it from another Windows system.

So...

What does the error "finish file present too long" mean and what do I need to do to correct the situation? My other Linux system does not generate any errors so far.

Thanks

Error details below
_____________________________________________________
<core_client_version>7.4.42</core_client_version>
<![CDATA[
<message>
finish file present too long
</message>
<stderr_txt>
setiathome_v7 7.00 DevC++/MinGW/g++ 4.5.2
libboinc: 7.1.0

Work Unit Info:
...............
WU true angle range is : 0.011932
Optimal function choices:
--------------------------------------------------------
name timing error
--------------------------------------------------------
v_BaseLineSmooth (no other)
v_vGetPowerSpectrumUnrolled 0.000130 0.00000
sse3_ChirpData_ak8 0.007557 0.00000
v_vTranspose4x16ntw 0.002002 0.00000
AK SSE folding 0.002052 0.00000

Flopcounter: 44703864078065.937000

Spike count: 10
Autocorr count: 0
Pulse count: 4
Triplet count: 4
Gaussian count: 0
06:53:35 (3784): called boinc_finish

</stderr_txt>

This error happens when a task misses its end point, continues running and eventually writes a 'finish file'. The next time BOINC is restarted, BOINC checks the file and sees that the finish file is way too long to be correct, thus ending that file immediately in a 'finish file present too long'.

There's nothing you can do about these. It's the project that should check these tasks out and see what's making them tick wrong.

---