Okay I am not real bright on this stuff but I have been having upload/download problems for a while. I have ti set to automatically do this but my Bionic has been idle for three days! I have tried to initiate the process manually but still get this:
2/3/2007 9:23:11 AM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
2/3/2007 9:23:11 AM||Couldn't connect to hostname [setiboincdata.ssl.berkeley.edu]
2/3/2007 9:23:11 AM|SETI@home|Temporarily failed download of 17my00aa.25969.15888.572166.3.136: system I/O
2/3/2007 9:23:11 AM|SETI@home|Backing off 2 hours, 16 minutes, and 49 seconds on download of file 17my00aa.25969.15888.572166.3.136
2/3/2007 9:23:11 AM|SETI@home|Temporarily failed download of 07jn00aa.7719.3090.61078.3.59: system I/O
2/3/2007 9:23:11 AM|SETI@home|Backing off 22 minutes and 54 seconds on download of file 07jn00aa.7719.3090.61078.3.59

Could all you smarter people out there make me less stupid on this. Thanks

---

Hi Randy....I've been having the same problem for the past 5 days, until yesterday when it finally stopped all work...I just had a 'pile' of WU's seemingly stuck in the "Transfers" box....not getting here all the way and thus not available to start running. And I had run out of cache. I know there are issues going on in Cali right now and I know it is very frustrating for them. Anyway I decided that with no work I might just as well shut 'er down (not involved with any other projects yet) and save on my electric bill for a couple days...lol. Anyway prior to shut down I decided to run my system 'cleanup disc' once through to clean various caches and the drives of any privacy, regist. errors, junk etc. Then did a complete shutdown. BUT I couldn't resist going back to run SETI again a few minutes later (I'm addicted). Low and behold the darn thing finished all the downloads stuck in the "Transfers" box and started happily crunching again..and has been doing so for the past 20 hrs. Go figure.

PS. I should mention that my system had been online for 3wks nonstop...(not even a restart)....and crunching when SETI was available. My system may have picked up errors etc during that time, and by running my cleanup disc and shuting down, it may have cleaned out those hung up errors...who knows.

---

yeap same here. A pc reboot fixed one but others does not seem to fix.
Maybe time to bump up the queue days.

---

Thanks folks I will try the disc cleanup and see what that does for me, I tend to leave my computer on at all times and it runs this SETI whenever I am not using it so this osunds like it might be the problem.

---

I had the same problems... then i downloaded the latest boinc client 5.8.8 and everything worked fine...

Download here

---

After occasional problems all last week everything has been fine since yesterday morning. Two machines cleared up Saturday night ... :->

I had the same problems to last week. I check the serverstatus of BOINC and i see ( even today) the folowing message:

sah_splitter1 penguin Not Running
sah_splitter2 kryten Not Running
sah_splitter3 kosh Not Running
sah_splitter4 klaatu Not Running



I don't now exactly what that means but maybe this have something to do with it?

---

Jimmy.B

I had the same problems to last week. I check the serverstatus of BOINC and i see ( even today) the folowing message:

sah_splitter1 penguin Not Running
sah_splitter2 kryten Not Running
sah_splitter3 kosh Not Running
sah_splitter4 klaatu Not Running



I don't now exactly what that means but maybe this have something to do with it?

The splitters make the results (wus) that are sent to us. Them being down would result in "no new work" after the cached results at seti run out.

I have not been able to connect to SETI in almost 2 weeks. Anyone else still having problems?

---

Jockstocks.com

I have not been able to connect to SETI in almost 2 weeks. Anyone else still having problems?

no problems here - using BOINC v 5.8.11 w/ chicken SSE2 etc and last night got 15 units

no major problems here - except some half hour outages now and then...

/edit

@ ldzppln: seems your machines got work all right...

/edit

---

mic.

no major problems here - except some half hour outages now and then...

/edit

@ ldzppln: seems your machines got work all right...

/edit

I've been getting these messages for days on end now:

2/12/2007 7:18:32 PM|SETI@home|Started upload of file 18my00aa.25368.32224.953400.3.248_3_0
2/12/2007 7:18:53 PM||Project communication failed: attempting access to reference site
2/12/2007 7:18:54 PM|SETI@home|Temporarily failed upload of 18my00aa.25368.32224.953400.3.248_3_0: http error
2/12/2007 7:18:54 PM|SETI@home|Backing off 3 hours, 45 minutes and 5 seconds on upload of file 18my00aa.25368.32224.953400.3.248_3_0
2/12/2007 7:18:55 PM||Access to reference site succeeded - project servers may be temporarily down.
2/12/2007 7:20:32 PM|SETI@home|Started upload of file 20ap00aa.5520.1217.467332.3.120_1_0
2/12/2007 7:20:53 PM||Project communication failed: attempting access to reference site
2/12/2007 7:20:54 PM||Access to reference site succeeded - project servers may be temporarily down.
2/12/2007 7:20:54 PM|SETI@home|Temporarily failed upload of 20ap00aa.5520.1217.467332.3.120_1_0: http error
2/12/2007 7:20:54 PM|SETI@home|Backing off 2 hours, 37 minutes and 53 seconds on upload of file 20ap00aa.5520.1217.467332.3.120_1_0
2/12/2007 7:22:28 PM|SETI@home|Started download of file 06mr00ab.19273.114.798576.3.167
2/12/2007 7:22:50 PM||Project communication failed: attempting access to reference site
2/12/2007 7:22:50 PM|SETI@home|Temporarily failed download of 06mr00ab.19273.114.798576.3.167: http error
2/12/2007 7:22:50 PM|SETI@home|Backing off 1 hours, 8 minutes and 12 seconds on download of file 06mr00ab.19273.114.798576.3.167
2/12/2007 7:22:51 PM||Access to reference site succeeded - project servers may be temporarily down.
2/12/2007 8:00:30 PM|SETI@home|Started upload of file 18my00aa.25368.28705.267324.3.11_2_0
2/12/2007 8:00:51 PM||Project communication failed: attempting access to reference site
2/12/2007 8:00:52 PM|SETI@home|Temporarily failed upload of 18my00aa.25368.28705.267324.3.11_2_0: http error
2/12/2007 8:00:52 PM|SETI@home|Backing off 38 minutes and 53 seconds on upload of file 18my00aa.25368.28705.267324.3.11_2_0
2/12/2007 8:00:53 PM||Access to reference site succeeded - project servers may be temporarily down.
2/12/2007 8:04:24 PM|SETI@home|Started upload of file 07jn00aa.20200.26481.947138.3.215_0_0
2/12/2007 8:04:45 PM||Project communication failed: attempting access to reference site
2/12/2007 8:04:46 PM|SETI@home|Temporarily failed upload of 07jn00aa.20200.26481.947138.3.215_0_0: http error
2/12/2007 8:04:46 PM|SETI@home|Backing off 28 minutes and 10 seconds on upload of file 07jn00aa.20200.26481.947138.3.215_0_0
2/12/2007 8:04:47 PM||Access to reference site succeeded - project servers may be temporarily down.
2/12/2007 8:19:05 PM|SETI@home|Started upload of file 10ap00ab.2527.8322.336096.3.145_2_0
2/12/2007 8:19:27 PM||Project communication failed: attempting access to reference site
2/12/2007 8:19:28 PM|SETI@home|Temporarily failed upload of 10ap00ab.2527.8322.336096.3.145_2_0: http error
2/12/2007 8:19:28 PM|SETI@home|Backing off 41 minutes and 58 seconds on upload of file 10ap00ab.2527.8322.336096.3.145_2_0
2/12/2007 8:19:29 PM||Access to reference site succeeded - project servers may be temporarily down.
2/12/2007 8:20:28 PM|SETI@home|Started download of file 19ap00aa.8521.14545.48580.3.172
2/12/2007 8:20:50 PM||Project communication failed: attempting access to reference site
2/12/2007 8:20:50 PM|SETI@home|Temporarily failed download of 19ap00aa.8521.14545.48580.3.172: http error
2/12/2007 8:20:50 PM|SETI@home|Backing off 43 minutes and 2 seconds on download of file 19ap00aa.8521.14545.48580.3.172
2/12/2007 8:20:51 PM||Access to reference site succeeded - project servers may be temporarily down.

---

Jockstocks.com

I haven't been able to send a completed work unit in since February 2nd.

---

Jockstocks.com

I haven't been able to send a completed work unit in since February 2nd.

I would suggest the following for starters: flush your dns and check your firewall settings.

---

Account frozen...

I haven't been able to send a completed work unit in since February 2nd.

I would suggest the following for starters: flush your dns and check your firewall settings.

Still didn't resolve the issue. I am having the same problem. No telling how long it's been like this though as the server reboots on Sundays anyway.

I have not been able to connect to SETI in almost 2 weeks. Anyone else still having problems?

I'm still in Northern California; I upgraded my Dad's system from BOINC 5.4.11 to BOINC 5.8.11 with Chicken's SSE3 with Graphics yesterday. All is running fine; both cores crunching away, happily.

Dual Core Dell Dimension 8400

P4 3.2 GHZ (x2)

1 GB RAM

Win XP Pro SP2 with all updates as of yesterday.

Again, no issues.

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

I haven't been able to send a completed work unit in since February 2nd.

I would suggest the following for starters: flush your dns and check your firewall settings.

I got the same problem, not sure if it starts at Feb 2nd, but should be around early Feb.

I haven't been able to send a completed work unit in since February 2nd.

The suggestions of flushing your DNS cache weren't far off; however, that's just one part of the solution.

BOINC itself keeps a DNS cache (one of the components that's used to transfer HTTP stuff, curl, does). So just flushing your DNS cache ("net stop dnscache" then "net start dnscache" in start/run or a command prompt) won't work as-is.

Instead, you'll have to either reboot your PC (which resets all caches anyway) or instead, restart BOINC - if you're running it as a service, "net stop boinc / net start boinc" does the trick, otherwise just close the manager and re-open it.

Then you should be able to communicate with the BOINC servers fine again.

One problem that may remain with WUs you tried to DOWNload til then; those downloads may still fail. Try a result upload to see if it works again (smaller filesize, below 30K vs. ~350K for a download).

Downloads that will not work even after this procedure can safely be cancelled.

HTH,
Simon.

---

Donate to SETI@Home via PayPal!

Optimized SETI@Home apps + Information

The suggestions of flushing your DNS cache weren't far off; however, that's just one part of the solution.

BOINC itself keeps a DNS cache (one of the components that's used to transfer HTTP stuff, curl, does). So just flushing your DNS cache ("net stop dnscache" then "net start dnscache" in start/run or a command prompt) won't work as-is.

Instead, you'll have to either reboot your PC (which resets all caches anyway) or instead, restart BOINC - if you're running it as a service, "net stop boinc / net start boinc" does the trick, otherwise just close the manager and re-open it.

Then you should be able to communicate with the BOINC servers fine again.

One problem that may remain with WUs you tried to DOWNload til then; those downloads may still fail. Try a result upload to see if it works again (smaller filesize, below 30K vs. ~350K for a download).

Downloads that will not work even after this procedure can safely be cancelled.

HTH,
Simon.

I've been unable to upload since the third (and have two expired WUs on the 11th and four about to expire). I've tried every trick above, plus a few I won't even mention here and still can U/L or D/L to any box. I'm thinking the cable provider may cache the DNS somewhere on their end?

---

Stewie: So, is there any tread left on the tires? Or at this point would it be like throwing a hot dog down a hallway?

Fox Sunday (US) at 9PM ET/PT

Man did I snooze through this one.

I just noticed my machines down.

---