Either they're working late at Berkely or we may be down for the weekend again.........

http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html

Can't seem to connect to the scheduler.....

2005-05-07 03:08:05 [SETI@home] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-05-07 03:08:05 [SETI@home] No schedulers responded
2005-05-07 03:08:05 [SETI@home] Deferring communication with project for 1 minutes and 0 seconds
2005-05-07 03:09:28 [SETI@home] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-05-07 03:09:28 [SETI@home] No schedulers responded
2005-05-07 03:09:28 [SETI@home] Deferring communication with project for 1 minutes and 0 seconds
2005-05-07 03:10:36 [SETI@home] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-05-07 03:10:36 [SETI@home] No schedulers responded
2005-05-07 03:10:36 [SETI@home] Deferring communication with project for 1 minutes and 0 seconds
2005-05-07 03:11:59 [SETI@home] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-05-07 03:11:59 [SETI@home] No schedulers responded
2005-05-07 03:11:59 [SETI@home] Deferring communication with project for 1 minutes and 0 seconds
2005-05-07 03:13:21 [SETI@home] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-05-07 03:13:21 [SETI@home] No schedulers responded
2005-05-07 03:13:21 [SETI@home] Deferring communication with project for 1 minutes and 31 seconds
2005-05-07 03:15:14 [SETI@home] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-05-07 03:15:14 [SETI@home] No schedulers responded
2005-05-07 03:15:14 [SETI@home] Deferring communication with project for 6 minutes and 19 seconds
2005-05-07 03:21:55 [SETI@home] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-05-07 03:21:55 [SETI@home] No schedulers responded
2005-05-07 03:21:55 [SETI@home] Deferring communication with project for 5 minutes and 3 seconds
2005-05-07 03:27:21 [SETI@home] Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-05-07 03:27:21 [SETI@home] No schedulers responded

I cannot connect to the schedular either.

5/7/2005 6:19:57 AM|SETI@home|Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
5/7/2005 6:19:57 AM|SETI@home|No schedulers responded
5/7/2005 6:19:57 AM|SETI@home|Deferring communication with project for 31 minutes and 45 seconds
5/7/2005 6:26:54 AM|SETI@home|Started upload of 24dc04aa.7646.13234.723592.154_1_0
5/7/2005 6:27:16 AM|SETI@home|Temporarily failed upload of 24dc04aa.7646.13234.723592.154_1_0: -106
5/7/2005 6:27:16 AM|SETI@home|Backing off 58 minutes and 6 seconds on upload of file 24dc04aa.7646.13234.723592.154_1_0

Shops shut at the weekend.

I don't work weekends.

It seems S@H Boinc dont either.

I just make sure I have a WU cach.

50 S@H to go.....

Plenty to keep my CPU toasty hot.

---

Foamy is "Lord and Master".
(Oh, + some Classic WUs too.)

<blockquote>Shops shut at the weekend.

I don't work weekends.

It seems S@H Boinc dont either.
</blockquote>
Just a small comment: Matt Lebofsky has posted today, so he is "working."

I understand that the CNS department is 24/7. They are responsible for Campus connectivity...

... and if the problem is outside the lab, there isn't much "staff" can do besides stare at servers that aren't working very hard.

---

This thread was being posted the same time as the "Cogent Down" thread was being posted, early this morning at 07:40 UTC. Maybe we should keep it all in the "Cogent Down" thread.