I installed BOINC on one PC, attached to SETI and Rosetta and it's working fine on the Rosetta units.

I then installed BOINC on a second PC, attached to Rosetta (SETI is down at the moment) with the same account but it keeps saying "Communication Deferred" with a 24-hour countdown. I hit Update, and it tries again in like 5 minutes, but then defers for 24 hours again. Tons of work units are available-- what gives?

Jallen.

I installed BOINC on one PC, attached to SETI and Rosetta and it's working fine on the Rosetta units.

I then installed BOINC on a second PC, attached to Rosetta (SETI is down at the moment) with the same account but it keeps saying "Communication Deferred" with a 24-hour countdown. I hit Update, and it tries again in like 5 minutes, but then defers for 24 hours again. Tons of work units are available-- what gives?

Jallen.

Einstein@Home isn't working all that bloody well either. I was able to upload data a couple of hours ago, but now unable.

F. Prefect

---

In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move.....Douglas Adams

Yeah, actually the Rosetta job finished on the first computer and says "Ready to report", but for some weird reason it's gone into a 3-hour "Communication Deferred" thing and won't attempt to communicate until then. This all seems highly inefficient, and if I have to sit around managing it I'll just remove the damned thing. The old SETI@home interface seemed to work really well compared to this. The second computer is still in the midst of its whopping 24-hour "Communication Deferred" wait.

With BOINC, Patience is DEFINATELY a virtue.
Also, A watched BOINC never communicates.
Relax. Let it 'do it's own thing', as they say these days.

Or you could tell us one or two of the message lines before "Communication Deferred" so that someone can advise.

Yeah, actually the Rosetta job finished on the first computer and says "Ready to report", but for some weird reason it's gone into a 3-hour "Communication Deferred" thing and won't attempt to communicate until then.

Uploading and Reporting are two different things, and require different actions on the projects side of things. When a WU/result finishes it's uploaded immediately. Work is reported based upon a calculation you can find in the wiki. Basically, it allows several wus to be reported at once, rather than one at a time. Uploads to seti go directly to the UL fileserver, while reporting requires communication with several servers and is for that reason, hard on the already overstressed servers. This delay in reporting was intentional.

This all seems highly inefficient, and if I have to sit around managing it I'll just remove the damned thing. The old SETI@home interface seemed to work really well compared to this. The second computer is still in the midst of its whopping 24-hour "Communication Deferred" wait.