I know this one's been asked many times but I haven't seen an answer to it yet - other than 'just leave it, it'll sort itself out. The SETI app on my maching has been stuck on 'Communication deferred'. These are the most recent messages. The last entry says 'scheduler request succeeded' but it's still stuck on 'Communication deferred'. What am I missing?

28/03/2006 16:35:28|boincsimap|Scheduler request to http://boinc.bio.wzw.tum.de/boincsimap_cgi/cgi succeeded
28/03/2006 16:35:30|boincsimap|Started download of 60301207.008409
28/03/2006 16:35:46|boincsimap|Finished download of 60301207.008409
28/03/2006 16:35:46|boincsimap|Throughput 89975 bytes/sec
28/03/2006 16:35:47||request_reschedule_cpus: files downloaded
28/03/2006 16:44:48||request_reschedule_cpus: process exited
28/03/2006 16:44:48|boincsimap|Computation for result 60301207.011920_1 finished
28/03/2006 16:44:48|boincsimap|Starting result 60301208.024517_1 using simap version 507
28/03/2006 16:44:50|boincsimap|Started upload of 60301207.011920_1_0
28/03/2006 16:45:06|boincsimap|Finished upload of 60301207.011920_1_0
28/03/2006 16:45:06|boincsimap|Throughput 20667 bytes/sec
28/03/2006 16:55:26||request_reschedule_cpus: project op
28/03/2006 16:55:30|boincsimap|Sending scheduler request to http://boinc.bio.wzw.tum.de/boincsimap_cgi/cgi
28/03/2006 16:55:30|boincsimap|Reason: Requested by user
28/03/2006 16:55:30|boincsimap|Reporting 1 results
28/03/2006 16:55:35|boincsimap|Scheduler request to http://boinc.bio.wzw.tum.de/boincsimap_cgi/cgi succeeded
28/03/2006 16:56:06||request_reschedule_cpus: result op
28/03/2006 16:56:06|boincsimap|Pausing result 60301208.024517_1 (removed from memory)
28/03/2006 16:56:07|boincsimap|Starting result 60301207.008409_0 using simap version 507
28/03/2006 16:56:08||request_reschedule_cpus: process exited
28/03/2006 16:56:09||request_reschedule_cpus: result op
28/03/2006 16:56:10|Predictor @ Home|Resuming result bprion_8_152134_2 using mfoldB125 version 428
28/03/2006 16:56:10|boincsimap|Pausing result 60301207.008409_0 (removed from memory)
28/03/2006 16:56:15||request_reschedule_cpus: result op
28/03/2006 16:56:39||request_reschedule_cpus: project op
28/03/2006 16:56:41|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
28/03/2006 16:56:41|SETI@home|Reason: Requested by user
28/03/2006 16:56:41|SETI@home|Requesting 8640 seconds of new work
28/03/2006 16:57:03||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
28/03/2006 16:57:06|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
28/03/2006 16:57:06|SETI@home|No schedulers responded
28/03/2006 16:58:06|SETI@home|Fetching master file
28/03/2006 16:58:11|SETI@home|Master file download succeeded
28/03/2006 16:58:16|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
28/03/2006 16:58:16|SETI@home|Reason: Requested by user
28/03/2006 16:58:16|SETI@home|Requesting 8640 seconds of new work
28/03/2006 16:58:37||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
28/03/2006 16:58:41|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
28/03/2006 16:58:41|SETI@home|No schedulers responded
28/03/2006 16:59:41|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
28/03/2006 16:59:41|SETI@home|Reason: Requested by user
28/03/2006 16:59:41|SETI@home|Requesting 8640 seconds of new work
28/03/2006 17:00:11|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded

---

Home Page:
March 27, 2006
We need to continue cleaning up after several server issues over the weekend. We won't be sending out any new work until we clear up some disk space.

---

My movie https://vimeo.com/manage/videos/502242

Here is the actual text from the boinc wiki on the "error code -106" error.

A failure to read/write from the Disk Drive, or in the case of network transmissions, a failure to send and receive data.

A failure to send and receive data to and from a Project Server generally means that during the transmission to or from the Project Server, or a router along the way has reset the TCP connection between the BOINC Client Software and the Project Server. This can happen for a number of different reasons, such as the Project Server being overloaded, or packets being lost in route.

Note:
This is probably the most common error after an outage of the Project.

While checking the server status page I see nearly two and a half million results waiting to be deleted. This sounds like a problem at Berkeley. Of course when I checked just now the stats hadn't been upgraded in 5 hours now, so the real numbers are probably quite a bit different.

As there are many causes of this error, it's almost impossible to say what causes it at any particular time, however Berkeley's servers have been giving quite a bit of trouble lately and so has the network connection.

---

Jim

Some people plan their life out and look back at the wealth they've had.
Others live life day by day and look back at the wealth of experiences and enjoyment they've had.

Home Page:
March 27, 2006
We need to continue cleaning up after several server issues over the weekend. We won't be sending out any new work until we clear up some disk space.

OK. Thanks guys.

---