reset the project if this happens repeatedly...

Quote:

Seems that dr. Les has borrowed my thread while I was out... Please create a new thread if you have a different problem...

I enjoyed this "gentle description" of the thread hijacking process :). For new posters, please realise that it is considered pretty poor form to take a thread in a completely different direction like Dr Les did. One thing that is immediately lost, is the ability to use the search function on thread titles and get back meaningful information if the content is not relevant to the title. It also makes it much harder to deal with problems efficiently if they are all jumbled together.

Quote:

Thanks HTH, I will try and detach/attach as soon as this wu has finished and see if the nasty msgs disappear.
Sonja

I wouldn't do that if I were you as I don't think it will "fix" things. I'm sure the Wiki mentions that this is a harmless situation that you can safely ignore. I've seen this particular message many times over several different machines and I've never seen the final result not complete and validate. The message should be regarded as information rather than a dire warning.

When you run a BOINC project, there are three general components that may be running and interacting with each other. The thing that does the crunching is the science app and that's all it does - crunch. It's like a ditch digger - it needs something (an operator) to start it, stop it, push it in the right direction and dispose of the spoils. That is the function of the BOINC daemon (boinc.exe). In this particular case the operator (BOINC daemon) is simply reporting that for some unknown reason, the ditch digger stopped working with no pile of spoils to dispose of. The daemon is simply mentioning this as being a bit unusual because the ditch digger didn't give any reason for stopping and was more or less saying that the job was finished successfully (zero exit status). However, the daemon can see that there is another 200m of trench to dig, so it orders the ditch digger to get going again. If there is a real problem then the ditch digger will stop again very quickly and multiple times in a row. The daemon would fill pages of messages about this and send them to you, the site foreman, relaxing in the site office and not paying too much attention. The daemon is using Boinc Manager to send you all these progress reports. You might have a real problem to deal with if the reports are flying thick and fast.

However, if the restarted ditch digger finishes the trench successfully, the site foreman doesn't need to be too concerned. He might go off and play golf for the day, knowing that there could be a pile of rountine reports on his desk that he can mostly ignore. I notice that that particular result did eventually finish and get reported. I presume it got validated.

On another point, Trog Dog picked up the fact that your log snippet contained the line:-

Quote:

Einstein@Home|Got server request to delete file z1_1106.5

- and he suggested that this might be a cause for concern. This is a perfectly normal log entry. When your computer receives work, a large data file is downloaded. As each result is allocated to you, you receive a small set of "instructions" on how to "slice up" the large data file for that particular result. Eventually the data file will be exhausted and no more instructions for that particular data file are going to be sent to you. The server is simply telling the client that the file is now finished with and can be deleted once all current results have been sent back. The server will always be sending this message while there is still work in progress. The message simply means there wont be any more work for that data file. It can look like the server is sending a batch of work and then immediately deleting it all so I can understand the concern :).

Cheers,