Hi

Running Seti@Home. "Temporarily failed upload" for about 2 days now.

Website says the servers are available.

Have rebooted BOINC Manager and computer. Einstein@Home seems to be working fine.

Any suggestions?

Thinqr

SETI-specific problems are best addressed on the SETI boards, but as they are incredibly slow right now, I'll tell you the summary from there; SETI's servers are "slammed", with all the new users, and there are network problems in parts of the U.S. West Coast adding to the problem. In order to keep people from being out of work, they have put the priority on the download servers; uploads are a lower priority issue. Until the network problems are resolved, and SETI has had at least a few hours of "clean" time to catch up, you're likely to have trouble uploading. I suspect it may be a day or two. The best thing to do is just let the exponential backoff and retrys do their job. Einstein may get a bit "ahead", but BOINC will compensate, SETI will catch up, and then everyone will be complaining that BOINC isn't asking for work from Einstein! :-)

---

To add more to Bill's observation.

SETI@Home is the "test bed" for the "high end" of the BOINC System. It has the most participants, the highest data rates, most hosts, etc. With this comes stress and in many cases shows some issues with BOINC that may need attention.

This is one of the reasons that BOINC was built in the first place. If SETI@Home is unavailable (though BOINC I feel has a better life track record than Classic) the other projects can take up the slack. So, for example in the last week or so,

SETI@Home has up-download problems
SZTAKI Desktop Grid has stopped issuing work
Predictor@Home has had work issue problems
CPDN's sites tripped off line
LHC@Home fiinished the study (no new work)

THrough that list of problems none of my computers really noticed a problem. THey all had work, and if they could not get it from one place they got it from another.

So, history says that there is at least a 2 day period before the system will be responsive and not back-logged after the problems have all been corrected!

---