Are others seeing "no work" messages in response to work requests? Or 12/28/2005 7:32:35 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu] messages? I didn't see similar posts in my quick skim of thread titles. Wanted to see what others were experiencing before looking further on my end, as otherwise my network and servers seem to be normal.

Thanks,

Robert

---

yup, I have been getting that also

---

Are others seeing "no work" messages in response to work requests? Or 12/28/2005 7:32:35 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu] messages? I didn't see similar posts in my quick skim of thread titles. Wanted to see what others were experiencing before looking further on my end, as otherwise my network and servers seem to be normal.

There's an outage every Wednesday while maintenence is done on the database. And there's always a congested period for a few hours after it comes back up as the accumulated work tries to get done. So some "can't connect" message during those periods aren't unusual. If it's still going on several hours from now or tomorrow, it's worth troubleshooting, but otherwise it's probably outage-related.

Cheers,
Brian

---

If you think education is expensive, try ignorance.

Are others seeing "no work" messages in response to work requests? Or 12/28/2005 7:32:35 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu] messages? I didn't see similar posts in my quick skim of thread titles. Wanted to see what others were experiencing before looking further on my end, as otherwise my network and servers seem to be normal.

There's an outage every Wednesday while maintenence is done on the database. And there's always a congested period for a few hours after it comes back up as the accumulated work tries to get done. So some "can't connect" message during those periods aren't unusual. If it's still going on several hours from now or tomorrow, it's worth troubleshooting, but otherwise it's probably outage-related.

Cheers,
Brian

---

I am getting the same message

12/28/2005 7:38:44 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
12/28/2005 7:38:45 PM|SETI@home|Temporarily failed download of 18fe05aa.28993.19794.273584.1.116: system I/O

---

Are others seeing "no work" messages in response to work requests? Or 12/28/2005 7:32:35 PM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu] messages? I didn't see similar posts in my quick skim of thread titles. Wanted to see what others were experiencing before looking further on my end, as otherwise my network and servers seem to be normal.

Thanks,

Robert

================
I have same problem; some machines on network have just stopped d/l work. All except my macintosh...just keeps crunching and u/l and d/l units.

Dr. Bob

---

Robert L. Hanson, Ed.D.

There's an outage every Wednesday while maintenance is done on the database. And there's always a congested period for a few hours after it comes back up as the accumulated work tries to get done. So some "can't connect" message during those periods aren't unusual. If it's still going on several hours from now or tomorrow, it's worth troubleshooting, but otherwise it's probably outage-related.

That may not be true in this case. The recovery from the outage went outstanding well for the first two hours. My machines had no trouble at all uploading results and reporting results. A few even got validated quickly.

There was the usual "Started", Counldn't connect", "Temporarily failed" messages for less than an hour, but that cleared up with download only taking 10 seconds for the next hour.

The problems seemed to start about two hours into the recovery when my machines started coming out of backoff on requesting new work. The first requests all resulted in "No work from project". But that was not unusual because the number of seconds of work being requested was less than the time it takes those machines to do a WU. Then ten minutes later the second round of requests for work with seconds larger than the run time also got "No work from project"?

This was followed by a long series of "Started download of #", followed about 18 seconds latter by a "Couldn't connect to hostname" error and a "Temporarily failed download of #". After about 20 minutes of this, the results downloaded.

The Cricket graphs show there was a drop in download traffic during this 20 minute period. The project may have ran out of work, but the Server status page did not indicate such a problem.

So there was some sort of "glitch" in the process causing a "No work from project". It could have been something the staff at Berkeley was doing or the servers could have been backlogged and not able to move work from the "Ready to Send" queue. But that seems to have cleared now.

That may not be true in this case. The recovery from the outage went outstanding well for the first two hours. My machines had no trouble at all uploading results and reporting results. A few even got validated quickly.
<snip>
The Cricket graphs show there was a drop in download traffic during this 20 minute period. The project may have ran out of work, but the Server status page did not indicate such a problem.

So there was some sort of "glitch" in the process causing a "No work from project". It could have been something the staff at Berkeley was doing or the servers could have been backlogged and not able to move work from the "Ready to Send" queue. But that seems to have cleared now.

If it's cleared, then no problem, these sorts of transient incidents are fairly common. The regular outage will produce the "can't connect" messages, but with the other messages that were posted ("system I/O"), there's obviously something else going on. Nothing major, let's hope. If it continues or recurs, posting the error messages (and a few lines of the log before the error message) can help troubleshoot what's happening.

Happy crunching!

---

If you think education is expensive, try ignorance.