[monsoonstorm]

I have been setting up a proxy on my network, and I also installed seti. Since seti was not installed before the proxy, I don't know if there are just no workunits, or whther I have a problem reaching the server.

Is there any way I can check to see if I am actually communicating with their servers?

This is what I am getting...
2004-08-09 18:31:12 [SETI@home] Sending request to scheduler: http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
2004-08-09 18:31:24 [SETI@home] Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi failed
2004-08-09 18:31:24 [SETI@home] Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi failed
2004-08-09 18:31:24 [SETI@home] No schedulers responded
2004-08-09 18:31:24 [SETI@home] No schedulers responded
2004-08-09 18:31:24 [SETI@home] Deferring communication with project for 52 minutes and 34 seconds
2004-08-09 18:31:24 [SETI@home] Deferring communication with project for 52 minutes and 34 seconds

I saw mentioned that this could be one of various problems. I need to know if I am getting through though!

MonsoonStorm

[djohnson]

Right now I cannot access the seti servers either. There is a note on their front page:

August 7, 2004
The scheduling server is down while we work on a download storage problem. This may take a day or so.

Hopefully it will be up soon because I have some testing I need to do!

[monsoonstorm]

The messages have changed now:

2004-08-10 07:45:46 [SETI@home] Couldn't read master page for SETI@home: error -107
2004-08-10 07:45:46 [SETI@home] Couldn't read master page for SETI@home: error -107
2004-08-10 07:45:46 [SETI@home] Master file fetch failed
2004-08-10 07:45:46 [SETI@home] Master file fetch failed
2004-08-10 07:45:46 [SETI@home] Deferring communication with project for 1 days, 18 hours, 12 minutes, and 6 seconds


I am presuming that this is because the server is down...
I suppose this is good in a way, as I now know that I AM getting through to the server through my proxy

MonsoonStorm