Hello!
I've some problem with my BOINC client.
I always have got error messages, when my client tries to send data to SETI. The messages is always one of the following:
Attempting to communicate with [setiboincdata.ssl.berkeley.edu] timed out
OR
2005. 12. 11. 7:10:28|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 504
OR
2005. 12. 11. 7:10:28|SETI@home|No schedulers responded
OR
2005. 12. 08. 1:29:15||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]

I have firewall (as standalone server), with NAT (network address translation), without any restriction for outbound traffic. I tried to use BOINC with and without proxy, but doesn't works with SETI@HOME..

(I had no any problem with Einsten@home project with and without proxy.)

Do anyone has any suggestion?

---

Take a look at any of the many recent upload/download threads here.
The download server is off, the upload server is crushed flat under the load.

This is almost certainly your problem.

---

maybe because so many Seti-Classic user changed to Seti 1 in this days (at the last possible Point...) the Berkeley server are mutch more used as in the normal way.
Allso the have problems making a server backup, and some new server troubles are happend - nobody knows what and how to fix at the moment.
Maybe there are other troubles allso.

Things like that You allways can read in the Technical News:
http://setiathome.berkeley.edu/tech_news.php

It seems like Your machine is Okay and the attidudes are well done!

If You have questions by handling BOINC feel free to visit:
http://www.crunching-family.wins.info

The "Crunching Family" is a european Info- and Helpteam (...for the german speaking area, but You can ask -Forum: HILFE- allso in english!) about the distributed computing (BOINC)
I think (...just me!) the longest date the SETI-server will having problems is the early January, it's mutch earlyer i hope!!!)!
Use an other project for a while, if You are'nt patient with SETI.

Regards
Miko

---

http://altes-beckhaus.com - my home & job
http://crunching-family.at - my team

Take a look at any of the many recent upload/download threads here.
The download server is off, the upload server is crushed flat under the load.

This is almost certainly your problem.

This is most likely not the answer, Berkeley uses Cogent as an ISP and here is the the webpage that shows the amount of data going thru the pipe:
http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html
The pipe is not full, there is something else wrong.

---

Take a look at any of the many recent upload/download threads here.
The download server is off, the upload server is crushed flat under the load.

This is almost certainly your problem.

This is most likely not the answer, Berkeley uses Cogent as an ISP and here is the the webpage that shows the amount of data going thru the pipe:
http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html
The pipe is not full, there is something else wrong.

It's not the download server which is off, but the feeder which tells the servers that there's work to download.
Not the internet pipeline, but the ability of the servers to handle connections that are being attempted.

The fine folk at the Lab are well aware of the problems, and working to resolve them. But this kind of mess doesn't happen instantly, and can't be fixed overnight. Relax, the work will eventually get moved where it belongs. In the mean time, your other projects will keep your computer busy, or for those who are SETI-exclusive, the computer will get a rest.

MJ

---