I get a 'no finished file' error for every project every now and then. What could this be?

4/5/2005 10:24:21 PM|climateprediction.net|Result 1y18_300111689_0 exited with zero status but no 'finished' file
4/5/2005 10:24:21 PM|climateprediction.net|If this happens repeatedly you may need to reset the project.
4/5/2005 10:24:21 PM|SETI@home|Result 27dc04aa.19468.3057.298580.184_2 exited with zero status but no 'finished' file
4/5/2005 10:24:21 PM|SETI@home|If this happens repeatedly you may need to reset the project.
4/5/2005 10:24:21 PM|ProteinPredictorAtHome|Result t0239E_1_53296_2 exited with zero status but no 'finished' file
4/5/2005 10:24:21 PM|ProteinPredictorAtHome|If this happens repeatedly you may need to reset the project.
4/5/2005 10:24:21 PM|ProteinPredictorAtHome|Restarting result t0239E_1_53296_2 using mfoldB125 version 4.28

---

-----

try disabling "Boinc Network access".

Does this help? Check Slots for "No Heartbeat" message

tony

I get these messages every now and again. I did a search of the forums, checked out what others were doing, and basically was told just to ignore them. The work units still end up finishing properly (at least mine do) and doesn't seem to cause any errors other than seeing that random message. I'll be interested in hearing other opinions about this.

Dig

---

> I get these messages every now and again. I did a search of the forums,
> checked out what others were doing, and basically was told just to ignore
> them. The work units still end up finishing properly (at least mine do) and
> doesn't seem to cause any errors other than seeing that random message. I'll
> be interested in hearing other opinions about this.

It may be one of those odd timing things, where the file is created and uploaded before the BOINC Software gets around to closing the Science Application, as it is closing the S-App it "sees" no finish file because it has already been sent.

I would suspect that this is more common on DSL/Cable modem systems if this were the case.

---

my machines do this sometimes as well.
mine generally happen DURING crunching or when switching applications (both stopping the particular unit or starting again). rarely did this cause a complete restart of the WU, just dropped back to the last write to disk.

i really need to get ramdrives setup, but i've always had troubles with them...

---

S@h Berkeley's Staff Friends Club