What is "upload", snoekie? If those are "ready to report", then all is fine. They'll clear in time.

And, without a copy of the event/message log if status is "uploading" fails, we cant do little to diagnose. Doubt that though as when there are too many results failing upload, requesting more work is blocked.

--//--

Hello snoekie,
'Uploading' the result is so fast that I usually only see it for the giant CEP2 result. Once the result is uploaded, there is only the unimportant report waiting to be sent back to the Scheduler server. BOINC Manager will show 'Ready To Report' for this last unimportant detail until there is some important reason to connect to the Scheduler, at which time the waiting reports are also sent and the Manager clears the Tasks from their Tab. If 24 hours pass without connecting to the Scheduler, a special connection will be made just to send the reports.

Communication problems normally show up in the Transfers Tab. As Sekerob says, it is difficult to diagnose without knowing which messages are showing up in which Tab. Copying the Messages Tab is usually a good start.

'Ready To Report' has been giving me headaches ever since we started BOINC in 2005. I wish it would be hidden away in some seldom-viewed Tab. Transfers Tab would be perfect.

Lawrence

Hello shanen,
In general, there are no upload problems right now. But we have had to take down the server a few times this month for several hours. Also, CEP2 has one result file that uploads directly to the Harvard server rather than to WCG. So it is best to report which project is having trouble uploading and when the trouble started.

What I would do would be to select the upload in Transfers Tab and press "Retry Now". If that failed, I would reset the router. Routers sometimes get into a wonky state due to voltage fluctuations, solar flares, etc. If "Retry Now" does not work after a router reset, then wait until CEP2 is not running on your computer and Reboot the OS.

And if all that fails, post a lot of information so we have no excuse but to worry about your problem and try to help you.


Lawrence

For the ''too observant'' there can be made use of additional log flags from this manual: http://boinc.berkeley.edu/wiki/Cc_config.xml . Suggest the below to add to the <log_flags> section of the cc_config.xml (in BOINC data dir. May not exist, i.e. has to be created)

<http_xfer_debug>1</http_xfer_debug>
<file_xfer_debug>1<file_xfer_debug>

The logging can be switched off by changing the 1 to 0, and reading in the config via the advanced menu in BOINC Manager.

If you post us the message (msg tab) / event log section (Advanced Menu > Event Log) from where you select the problem file to upload and done the "Retry Now" to where a fail is messaged in the log, it may tell us something. Probably the file was somehow locked on the server side when the transfer got rudely interrupted. That would reset after a while by itself. If it does not clear, collateral damage... abort the task/resul files if it does not do so by itself.

Edit: Like to document this as the techs may want to research a case [what's your client version and OS?]. Cant remember this having been reported for a while, where the server was upgraded to version 700 of BOINC. Lingering bugs that need fixing and all.

Thanks

--//--