Upload issues?

[denim]

Anyone else having an issue once the tasks are completed to upload? (Same issue with PrimaB, but no issue with PG or WCG for example)

[John P. Myers]

Are you using <report_results_immediately>1</report_results_immediately> in your cc_config? If not it can delay uploads by hours.

[denim]

Are you using <report_results_immediately>1</report_results_immediately> in your cc_config? If not it can delay uploads by hours.

I haven't touched the app config. Even when trying to manually click on update, the completed WU's remain.

[denim]

Ok, now it is Rosetta, PrimaB, and SETI won't upload from my work machine.

PG and WCG is good though.

[Al]

Ok, now it is Rosetta, PrimaB, and SETI won't upload from my work machine.

PG and WCG is good though.

It's Tuesday at SETI, scheduled downtime.

[denim]

Capture.jpg

[denim]

It's Tuesday at SETI, scheduled downtime.

Ok, phew. Now I just have to figure out why for Rosetta and primaB.

[Mumps]

Well, "Ready to Report" means the upload was at least completed. So the project at least knows you completed the WU.

What shows up in the log when you hit the Update button for those projects? My systems I have running Rosetta aren't showing any issues.

[denim]

Well, "Ready to Report" means the upload was at least completed. So the project at least knows you completed the WU.

What shows up in the log when you hit the Update button for those projects? My systems I have running Rosetta aren't showing any issues.

The Rosetta and PrimaB sites shows servers are good, but my event log is saying:

Scheduler request failed: failure when receiving data from the peer
Project communication failed: attempting access to reference site
Internet access ok - project servers may be temporarily down.

[Egilman]

The Rosetta and PrimaB sites shows servers are good, but my event log is saying:

Scheduler request failed: failure when receiving data from the peer
Project communication failed: attempting access to reference site
Internet access ok - project servers may be temporarily down.

That's a BOINC client error not a project error...
Scheduler request failed:, means Boinc was unable to perform the task; failure when receiving data from the peer, is the description of the error and this would appear to be a network issue.

Project communication failed:, means Boinc is explaining in the log what the issue is; attempting access to reference site, is Boinc telling you what it's doing to narrow the issue down.


Internet access ok - project servers may be temporarily down, Is Boinc communicating that it is connected to the internet, (usually by checking if it can reach Google.com) so the issue isn't a hardware issue preventing communication.

I would reboot the machine..... Something is not allowing that Boinc instance from communicating with the project server...