Well, I actually managed to get a couple workunits uploaded last night. However, do you think a guy could contact the scheduler to report the work? Nope.

11/12/2005 4:52:36 PM||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
11/12/2005 4:52:39 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
11/12/2005 4:52:39 PM|SETI@home|No schedulers responded

Did they somehow mess up the scheduler when they disabled sending new work?

---

* Viking *

Make it a sport to read the front page news.

---

Make it a sport to read the front page news.

Perhaps you didn't read my original post thoroughly... I most certainly do read that regularly. It says "We have turned off work distribution for a bit to allow result uploads to catch up." There is no mention of disabling the schedulers entirely.

---

* Viking *

Ok, let's try this again.
At last count, Seti/BOINC had 617,836 hosts attached. That's computers, not people. Can you imagine what will happen if half of those try to contact the Seti server all at once?

What are the odds you get a "scheduler not responding" message back, instead of a "scheduler responding" message when 100,000 of those try to contact the server all at once?

As the error -106 means it couldn't reach the server. As does Error 500. As does I/O error.

Anyway, since we can't download work from Seti anyway, you can just as well set Seti to No New Work. This will only try to upload work then, not download new work. That'll ease the pressure on the servers already.

If you want to see BOINC in action, Seti Beta is still giving out work. As are a couple of other projects. I hope I don't have to say much about that.

P.S: You can check up on the server status, including scheduler status, here.

---

It's already set to "no new work...."

---

* Viking *