Generally speaking...

When a WU is completed on a client, in the TASKS tab it is listed under STATUS as "Ready to report".

The client contacts the project upload-server & starts to transfer the result file(s). This shows up under TRANSFER tab. As well as various actions on the MESSAGES tab (started upload, defering, etc)

When the transfer is completed, the line-item on the TRANSFER tab is cleared. And 'Finished upload of...' is written to MESSAGES tab.

***But on TASKS tab, the item is still be listed under status as "Ready to report" until (assumptions follow) client contacts scheduler?-server to report upload completed which shows on MESSAGES tab as "Reporting X tasks"; "Schedule RPC succeeded..."

**Question: Is this generally correct?

Every once in a while, I'll see a WU that has completed upload, but "Ready to report" on TASK tab, Status is NEVER cleared.

I'm not concerned that that line-item on TASKS tab may take a while to clear, but after many days I start to wonder.
**Question: Once WU results file is uploaded, but before item cleared on TASKS tab, if client is permanently killed (uninstalled, detached, even WU aborted) does that negatively impact the WU or tracking of WUs?

---

You are generally correct.

The data is uploaded to the server as a simple file, then later it is reported to the database that the file was uploaded and where it was stored. In most cases this separation makes the system more reliable since they can be retried independently. However in the case you mention where a client is permanently killed, the result can put into limbo. The data file is there but the server does not know about it.

---

BOINC WIKI

BOINCing since 2002/12/8

However in the case you mention where a client is permanently killed, the result can put into limbo. The data file is there but the server does not know about it.

Thanks for comfirmation!

If the client NEVER reports to server that results file was successfully uploaded, can that be corrected/resolved on the server side?


I **LOVE** BOINC's fault tolerant design of "Set it, & forget it!"
I have 3 clients that I only access every 1 or 2 years, and they just keep plugging along!!

---

Hi Heflin
I hope that you're not running cpdn on a computer that hasn't been looked at for a few years.

There are several people 'in this boat' who have BOINC version 4.19, and are just downloading models and not processing them.
This is because, for about a year and a half, the latest models need a BOINC version 5.* to work. There's a growing list of people being found with hundreds to thousands of models just sitting on their 'forget about it' computers.

cpdn

IF cpdn is the 'BBC Climate Change Experiment', then those clients are not attached to that project. I'm surprised cpdn doesn't check the version before providing a WU.

I do monitor/check on the project's web site that these remote machines are being issued WUs and returning WUs that are accepted. So far, the only issue has been client machines being turned off for long periods of time which most projects & BOINC seem to handle very well.

---

BBC is a separate project from CPDN (although it was run by the same people).

They've already tried the setting to restrict the Boinc manager version, but it doesn't seem to help.

---