Thanks everyone for your message.
Of course, it is not Belgium !!
But it stay very very irritating. I can not open a permanent link to
Seti, due to setting of my proxy server. I open the gateway one hour each week.
Of course, not on tuesday.
The computers have also 10 days cache WU. It will say that when the connection fail, the computers have not enough work till the next week !!!

---

4/24/2007 4:50:23 PM||Access to reference site failed - check network connection or proxy configuration.

This indicates that there's a problem with your network connection, not SETI.

---

This is my most recent error. Hmmmm

4/24/2007 4:45:15 PM||Project communication failed: attempting access to reference site
4/24/2007 4:45:19 PM|SETI@home|Scheduler request failed: couldn't connect to server
4/24/2007 4:45:19 PM|SETI@home|Deferring communication for 1 hr 26 min 35 sec
4/24/2007 4:45:19 PM|SETI@home|Reason: scheduler request failed
4/24/2007 4:50:23 PM||Access to reference site failed - check network connection or proxy configuration.

It is a time of patience be needed. Soon we will be multibeaming like maniacs. And later on in the works we will be pulsating with joy over the thrilling Astrouplse WU.

We are just like kids waiting and complaining about waiting to our parents Matt and Eric when it is thursday and the candyday is on saturday.

BTW, try increasing the amount of WUs cached. Set contact to three days and update. I have around 30 WUs all the time.

Carl

Perhaps because SETI do not like Belgium ??? Joke !!!

Eh, stop waffling! Either they don't like Belgium or they do. Personally, I think there's something rotten in Denmark though... ;-)



Seriously though, sorry for your pain. All of us are having issues related to the moving of lab equipment and the reduction in the replication/quorum amounts...

Brian

IMHO, from what I gather from tech threads etc...These aren't problems, it's throttling and reconfiguration in preparation for transfer to new multibeam data.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

After version5.8.14 . I are only problems.
My connection speed ( real up at 512kbps, down at 4500kbps , yes 4.5Mbps) it are only problem.
The server status do not show problem, all server seem to be active. But when all the computers ( above 10.000, ten thousand ) try to connect, it are always the same error message. See here below. Of course, they never try to connect at the same time. But I do not want spend my time to go on each computer to check if all is correct working. I am tired. I will remove me from the project. I was full agree, but it give me now much more time to check the status. What happen with SETI ???
Of course, I have try with my "test" computer ( other connection, other configuration, other speed. But the same proble appear !!! Perhaps because SETI do not like Belgium ??? Joke !!!

Here a example. Of course, I can give thousand of similar, with different times !!!

You are not alone, I have noticed a number of times today when message indicated that host was down, but showed no outage.
Perhaps they are under a zombie attack;)

---

When we finally figure it all out, all the rules will change and we can start all over again.

After version5.8.14 . It are only problems.
My connection speed ( real up at 512kbps, down at 4500kbps , yes 4.5Mbps) it are only problems.
The server status do not show problem, all servers seem to be active. But when my computers ( above 10,000, ten thousand ) try to connect, it are always the same error message. See here below. Of course, they never try to connect at the same time. But I do not want spend my time to go on each computer to check if all is correct working. I am tired.
I will remove me from the project. I was full agree, but it give me now much more time to check the status. What happen with SETI ???
Of course, I have try with my "test" computer ( other connection, other configuration, other speed. But the same problem appear !!! Perhaps because SETI do not like Belgium ??? Joke !!!
The problem is now about 3 weeks old !!!

Here a example. Of course, I can give thousand of similar, with different times !!!

23/04/2007 23:17:08||Starting BOINC client version 5.8.16 for windows_intelx86
23/04/2007 23:17:08||log flags: task, file_xfer, sched_ops
23/04/2007 23:17:08||Libraries: libcurl/7.16.0 OpenSSL/0.9.8a zlib/1.2.3
23/04/2007 23:17:08||Data directory: C:\\Program Files\\BOINC
23/04/2007 23:17:08||Processor: 2 GenuineIntel Intel(R) Pentium(R) 4 CPU 3.00GHz [x86 Family 15 Model 4 Stepping 1] [fpu tsc sse sse2 mmx]
23/04/2007 23:17:08||Memory: 1023.48 MB physical, 2.86 GB virtual
23/04/2007 23:17:08||Disk: 47.46 GB total, 38.12 GB free
23/04/2007 23:17:08|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 3302999; location: home; project prefs: home
23/04/2007 23:17:08||General prefs: from SETI@home (last modified 2007-04-11 06:58:57)
23/04/2007 23:17:08||Host location: home
23/04/2007 23:17:08||General prefs: using separate prefs for home
23/04/2007 23:17:08|SETI@home|Restarting task 27ja04ab.15458.15537.486066.3.173_2 using setiathome_enhanced version 515
23/04/2007 23:17:08|SETI@home|Restarting task 27ja04ab.15458.15537.486066.3.147_2 using setiathome_enhanced version 515
23/04/2007 23:17:08|SETI@home|Sending scheduler request: To fetch work
23/04/2007 23:17:08|SETI@home|Requesting 1348956 seconds of new work
23/04/2007 23:17:30||Project communication failed: attempting access to reference site
23/04/2007 23:17:31||Access to reference site succeeded - project servers may be temporarily down.
23/04/2007 23:17:33|SETI@home|Scheduler request failed: couldn't connect to server
23/04/2007 23:17:33|SETI@home|Deferring communication for 17 min 6 sec
23/04/2007 23:17:33|SETI@home|Reason: scheduler request failed
23/04/2007 23:19:53|SETI@home|Sending scheduler request: Requested by user
23/04/2007 23:19:53|SETI@home|Requesting 1349052 seconds of new work
23/04/2007 23:20:15||Project communication failed: attempting access to reference site
23/04/2007 23:20:16||Access to reference site succeeded - project servers may be temporarily down.
23/04/2007 23:20:18|SETI@home|Scheduler request failed: couldn't connect to server
23/04/2007 23:20:18|SETI@home|Deferring communication for 38 min 25 sec
23/04/2007 23:20:18|SETI@home|Reason: scheduler request failed
23/04/2007 23:22:53|SETI@home|Sending scheduler request: Requested by user
23/04/2007 23:22:53|SETI@home|Requesting 1349289 seconds of new work
23/04/2007 23:23:53|SETI@home|Scheduler RPC succeeded [server version 509]
23/04/2007 23:23:53|SETI@home|Deferring communication for 11 sec
23/04/2007 23:23:53|SETI@home|Reason: requested by project
23/04/2007 23:23:55|SETI@home|[file_xfer] Started download of file 30se04aa.7255.9216.422146.3.103
23/04/2007 23:23:55|SETI@home|[file_xfer] Started download of file 30se04aa.7255.9216.422146.3.102
23/04/2007 23:24:08|SETI@home|Sending scheduler request: To fetch work
23/04/2007 23:24:08|SETI@home|Requesting 1254867 seconds of new work
23/04/2007 23:24:13|SETI@home|Scheduler RPC succeeded [server version 509]
23/04/2007 23:24:13|SETI@home|Deferring communication for 11 sec
23/04/2007 23:24:13|SETI@home|Reason: requested by project
23/04/2007 23:24:13|SETI@home|Deferring communication for 1 min 0 sec
23/04/2007 23:24:13|SETI@home|Reason: no work from project
23/04/2007 23:24:13|SETI@home|Scheduler RPC succeeded [server version 509]
23/04/2007 23:24:13|SETI@home|Deferring communication for 11 sec
23/04/2007 23:24:13|SETI@home|Reason: requested by project
23/04/2007 23:24:13|SETI@home|Deferring communication for 1 min 0 sec
23/04/2007 23:24:13|SETI@home|Reason: no work from project
23/04/2007 23:24:24|SETI@home|[file_xfer] Finished download of file 30se04aa.7255.9216.422146.3.103
23/04/2007 23:24:24|SETI@home|[file_xfer] Throughput 12519 bytes/sec
23/04/2007 23:24:24|SETI@home|[file_xfer] Started download of file 27ja04ab.15458.15728.215926.3.204
23/04/2007 23:24:32|SETI@home|[file_xfer] Finished download of file 30se04aa.7255.9216.422146.3.102
23/04/2007 23:24:32|SETI@home|[file_xfer] Throughput 9989 bytes/sec
23/04/2007 23:24:32|SETI@home|[file_xfer] Started download of file 30se04aa.7255.9216.422146.3.109
23/04/2007 23:24:57|SETI@home|[file_xfer] Finished download of file 27ja04ab.15458.15728.215926.3.204
23/04/2007 23:24:57|SETI@home|[file_xfer] Throughput 11077 bytes/sec
23/04/2007 23:24:58|SETI@home|Starting 27ja04ab.15458.15728.215926.3.204_0
23/04/2007 23:24:58|SETI@home|Starting task 27ja04ab.15458.15728.215926.3.204_0 using setiathome_enhanced version 515
23/04/2007 23:25:10|SETI@home|[file_xfer] Finished download of file 30se04aa.7255.9216.422146.3.109
23/04/2007 23:25:10|SETI@home|[file_xfer] Throughput 9883 bytes/sec
23/04/2007 23:36:54|SETI@home|Sending scheduler request: Requested by user
23/04/2007 23:36:54|SETI@home|(not requesting new work or reporting completed tasks)
23/04/2007 23:37:44|SETI@home|Scheduler RPC succeeded [server version 509]
23/04/2007 23:37:44|SETI@home|Deferring communication for 11 sec
23/04/2007 23:37:44|SETI@home|Reason: requested by project
23/04/2007 23:38:29|SETI@home|Sending scheduler request: Requested by user
23/04/2007 23:38:29|SETI@home|(not requesting new work or reporting completed tasks)
23/04/2007 23:38:51||Project communication failed: attempting access to reference site
23/04/2007 23:38:52||Access to reference site succeeded - project servers may be temporarily down.
23/04/2007 23:38:54|SETI@home|Scheduler request failed: couldn't connect to server
23/04/2007 23:38:54|SETI@home|Deferring communication for 1 min 0 sec
23/04/2007 23:38:54|SETI@home|Reason: scheduler request failed
23/04/2007 23:39:55|SETI@home|Sending scheduler request: Requested by user
23/04/2007 23:39:55|SETI@home|(not requesting new work or reporting completed tasks)
23/04/2007 23:40:17||Project communication failed: attempting access to reference site
23/04/2007 23:40:18||Access to reference site succeeded - project servers may be temporarily down.
23/04/2007 23:40:20|SETI@home|Scheduler request failed: couldn't connect to server
23/04/2007 23:40:20|SETI@home|Deferring communication for 1 min 0 sec
23/04/2007 23:40:20|SETI@home|Reason: scheduler request failed
23/04/2007 23:41:20|SETI@home|Sending scheduler request: Requested by user
23/04/2007 23:41:20|SETI@home|(not requesting new work or reporting completed tasks)
23/04/2007 23:42:15|SETI@home|Scheduler RPC succeeded [server version 509]
23/04/2007 23:42:15|SETI@home|Deferring communication for 11 sec
23/04/2007 23:42:15|SETI@home|Reason: requested by project

---