I've been using BOINC successfully for a long time. One of my most recent tasks, though, is not transferring. On the Tasks tab, it says 100% complete, and has a dash in the "Remaining (estimated)" column. But on the Transfer tab, there's no indication that it has tried to transfer this task. It just keeps running rather than trying to transfer. Since then, one of my other tasks for a different project has completed successfully, and a different task for this project is running fine so far. But this one seems to be stuck.

Any idea what's wrong or what I can do to fix it?

I'm using BOINC 7.0.27 (x86) on Ubuntu 12.04. The task in question is a climateprediction.net task (their page currently mentions no downtime). I suspect if there were some way to tell the task to try uploading, it would upload properly. Instead, it seems stuck. Any help would be appreciated.

Does anyone have any ideas on this? It still sits there saying "100%" but not attempting an upload no matter what I do. I'm tempted to just delete the task and hope for the best with future tasks. But my computer spent a long time processing it, so I'd hate to have all of that go to waste.

How to graciously end a CPDN 'stuck' task, I do not know, or for that matter any task. Often the restart of a client kicks obstinate tasks of many projects back in motion. Suggest you ask the question over at the CPDN forums. We're ill equipped here... the occasional visit of a CPDN expert is chance. Far as I know the CPDN tasks still trickle pieces up until the end, about every 3-6 hours [Long time not done one]. Is it still doing that? It's visible in the message/event log.

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

While it certainly is BOINC its duty to upload tasks, it is not its duty to finish them before the task is done. That's something that the science application does, or in this case the ClimatePrediction application.

If that one continues to run when it's been on 100% for some time, even when you've exited & restarted the BOINC client (you did try that?) or rebooted the computer (you tried that?), then you'll have to report this on the CPDN forums, as then it's something their developers will have to look into.

---

I've tried exiting BOINC and restarting my computer. When I reboot, the task still says 100% and is still trying to run instead of uploading. And now one of my SETI tasks says "Ready to report" but is not uploading either.

Apparently a new version of BOINC for Linux just came out today. I'll download that and see if that helps. If not, I'll ask over at CPDN. If you have any suggestions in the meantime about the "Ready to report" task, I'm open to suggestions. Thanks!

I have participated in BOINC a good number of year, but I recently realized my completed tasks are not transferring. This has been since I got a new Mac a couple years ago. I run Mac OS 10.6.8. I would love to get these completed tasks (obviously there's quite a few of them) to transfer.

I have participated in BOINC a good number of year, but I recently realized my completed tasks are not transferring. This has been since I got a new Mac a couple years ago. I run Mac OS 10.6.8. I would love to get these completed tasks (obviously there's quite a few of them) to transfer.

This is the Boinc (Development) Forum, you can't upload completed Wu's here as it isn't a project, all projects have their own servers, without knowing which projects you can't upload to we can't really help,

Please have a read of this thread and supply some info, like a Boinc version, the Boinc startup and upload failures from the Message Tab, or Event Log.

Claggy

I have the same problem with results not being uploaded [Linux 7.0.29 (x86)] . My projects are:

The Lattice Project
rosetta@home
World Community Grid
fightmalaria@home
malariacontrol.net

None of them upload results automatically from what I can tell, so my problem is not project related. Several times a day I need check on BOINC and to go to the advanced-GUI Projects tab, select each project individually in the list, and hit the associated "Update" button for them to phone back home and push those results back to the individual project, otherwise they just accumulate. I find this very odd because they have absolutely no problem with collecting work units to do, they just don't return the results back to the project.

My only non-standard settings is to boost the CPU utilization as high as comfortable and to limit the hours for the "Network usage allowed" between 06:00 and 20:00, because the network here gets turned off during off hours and monitored heavily. Ideally I would like BOINC to store up enough work units prior to 20:00 to last through the night and upload them at 6:00am, but it does not appear to be uploading at all.

Is there a logfile which contains upload/download information that I can check? Are my network allowed hours I specified not formatted correctly (e.g. leading zero in the am setting), or is there a difference in GMT/EST?

I can't believe that BOINC doesn't upload finished tasks immediately (as long as the network is available). Are those tasks really marked as "Uploading" in the status column of the Tasks tab or are they "Ready to report"?

If the latter, they are already uploaded, just not reported to the database. That will happen at the next work request or after 24 hours, whatever comes first.

Gruß,
Gundolf

One doesn't upload tasks waiting to upload with the Update button, but with the Retry Now button in the Transfers tab. Which makes me believe you're seeing what Gundolf told you, that these tasks are already uploaded but waiting to be reported.

The upload mechanism is two-fold in BOINC:
1. Once a task is finished, the result data is uploaded from your computer to a disk at the server.
2. Then it needs to be reported to the database that your computer finished this task and when it uploaded the result data. Because reporting tasks uses the database, and because reporting 50 tasks takes as much overhead as reporting a single task, projects prefer that you report as many as possible at the same time.

Therefore, finished tasks are reported at or around:
1) 24 hours before deadline.
2) Connect Every X before deadline.
3) 24 hours after task completion.
4) Immediately if the upload completes later than either 1, 2, or 3 upon completion of the task.
5) On a trickle up message.
6) On a trickle down request.
7) On a server scheduled connection. Used, but I am not certain by which project.
8) On a request for new work.
9) When the user pushes the update button.
10) On a request from an account manager.
11) Report immediately every task, if "No new Task" is set.
12) Report immediately if CPU or network time-of-day override starts in the next 30 minutes. (BOINC 7.0)
13) When minimum work buffer is reached. (BOINC 7.0)

---

What cache settings are you using on Boinc 7.0.29?

Boinc 7 has a new scheduler, it'll wait until the amount of work in the cache has fallen below the Minimum value before it'll ask for work again, so if you have a big additional value set you'll probably get this behaviour,

Where with Boinc 6 you would set 0.1 + 3 days, with Boinc 7 you should set 3 + 0.1 days.

Claggy