Hi

over the last week whenever I go a message saying schedular request completed got 1 new task I get seti downloading and it shows in my transfer tab "download pending(Project backoff:)" it stays in the transfer tab at 0 % for over 24 hours until I abort the transfer
so I have had no work for over a week. all other projects download properly.
Paul

Most of mine that I have used have downloaded ok, it is the past week that something seems to be wrong with the server, so a backup project might be useful. Trying going into your BOINC manager, then tools then atach project you will probable have to register for these however once you have that is it.

---

Paul, it is a problem on the SETI server side. One of the two download server url's is sticking. If you have one stuck in download now you might try doing an ipconfig/flushdns from a command line. This has been helping clear the backup for quite a few people. It would probably be better at this point in time to just wait though since the crew at Seti will be in today and should have it fixed soon.They have been on a long weekend due to Thanksgiving holiday so they let this little problem slide.

---

PROUD MEMBER OF Team Starfire World BOINC

I restarted 2 of my rigs and 1 actually started downloading work. The other, not so much. I ran out of work and wasnt willing to wait on seti so I set a few Primegrid Wu's to running. That should be enough to get me through the download problem

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

I restarted 2 of my rigs and 1 actually started downloading work. The other, not so much. I ran out of work and wasnt willing to wait on seti so I set a few Primegrid Wu's to running. That should be enough to get me through the download problem

I have a lot of "Project Backoff" messages in all my hosts.
If I exit BOINC and restart, in 50% of cases It statrs to download but if not, I have to wait sometimes to retry. Shutdown doesn't works.
I have some hosts far from my office .... what have I to do?
I must wait ..... weeks?

I read this: "The connectivity problem noted yesterday turned out to be one of our switches and not the router. We swapped in a replacement switch today and connectivity was restored. " .... but I think that was not restored 100%.

Bye,
Franz

---

Hi

over the last week whenever I go a message saying schedular request completed got 1 new task I get seti downloading and it shows in my transfer tab "download pending(Project backoff:)" it stays in the transfer tab at 0 % for over 24 hours until I abort the transfer
so I have had no work for over a week. all other projects download properly.
Paul

This prevents 100,000 BOINC clients from constantly hammering the servers for more work.

The very best thing you can do is nothing at all. If you leave everything alone, the BOINC clients will patiently retry until they get work.

If you do as others suggest, you may get work more quickly (especially if there are server issues, as there were this weekend) but you do so by adding to the overall load (adding to the overload during recovery).

---

Hello all,

A lot of my crunchers were starved so I tried the ipconfig /flushdns on the widow boxes - I got
a few tasks and the crunchers are happy munching err crunching away.
BTW you first have to quit BOINC then flush then restart - rinse and repeat until you get a few
work units.

Those of you on Mac there is a command in OS X 10.5 and greater to do the same same thing that command:

dscacheutil -flushcache

Hope this helps.

regards,
-David

---

I had a machine downloading one WU since 11-27-2009 aborted the download and tried to get new WU and they are still stuck. Mac OSX 10.5.8 all updates and BOINC 6.6.38. Tried the OSX cache flush and boinc restart and still no joy. I hope it is fixed on tuesday.

---

If all is not well by Wed. I am quitting this project! 7 days now fits and starts.

If all is not well by Wed. I am quitting this project! 7 days now fits and starts.

I'm certain project staff will take this quite seriously, and work 24/7 to resolve the issues.

Seriously, though, there is quite a bit of discussion on other threads about how to work around the issues.

... and while there are "issues" they aren't show-stoppers. BOINC is designed to work around them -- and if you choose another project and give it just a sliver of your resource share (1:1000 if you wish) it'll keep your computer warm and busy.

---

Hello everyone



I ALSO HAD trouble downloading files from seti. I did a reload on the program and i was able transfer the file from seti. I am running 6.10.17 on a MAC pro running snow lepoard.




regards
fred

---

Hi

over the last week whenever I go a message saying schedular request completed got 1 new task I get seti downloading and it shows in my transfer tab "download pending(Project backoff:)" it stays in the transfer tab at 0 % for over 24 hours until I abort the transfer
so I have had no work for over a week. all other projects download properly.
Paul

This prevents 100,000 BOINC clients from constantly hammering the servers for more work.

The very best thing you can do is nothing at all. If you leave everything alone, the BOINC clients will patiently retry until they get work.

If you do as others suggest, you may get work more quickly (especially if there are server issues, as there were this weekend) but you do so by adding to the overall load (adding to the overload during recovery).

No, I don't think so.
I have work and is already assigned to me. But I cannot download it.
Results ready to send = 172,766
In this moment the charge of Internet resuorces at berkeley is 1/3 than maximum.
I think it's a bug/malfunction in the connection.
In the log I see:
01.12.2009 09:27:39 SETI@home Temporarily failed download of 30mr07aa.16918.10706.3.10.209: connect() failed
01.12.2009 09:27:39 SETI@home Backing off 23 min 52 sec on download of 30mr07aa.16918.10706.3.10.209


FF

---

A close and restart of the Boinc Manager worked for me. All of my downloads went through.

EDIT: and after saying that, my connection problem has returned. Notice the 7 minute span between successful download and connection problem:

12/1/2009 9:15:31 AM SETI@home Started download of 16no06ac.10738.22976.14.10.55
12/1/2009 9:15:34 AM SETI@home Finished download of 16no06ac.10738.22976.14.10.55
12/1/2009 9:22:46 AM SETI@home Computation for task 03mr07ac.16750.890.9.10.239_0 finished
12/1/2009 9:22:46 AM SETI@home Starting 03mr07ac.30651.72.11.10.126_0
12/1/2009 9:22:46 AM SETI@home Starting task 03mr07ac.30651.72.11.10.126_0 using setiathome_enhanced version 603
12/1/2009 9:22:47 AM SETI@home Sending scheduler request: To fetch work.
12/1/2009 9:22:47 AM SETI@home Requesting new tasks
12/1/2009 9:22:48 AM SETI@home Started upload of 03mr07ac.16750.890.9.10.239_0_0
12/1/2009 9:22:52 AM SETI@home Finished upload of 03mr07ac.16750.890.9.10.239_0_0
12/1/2009 9:22:52 AM SETI@home Scheduler request completed: got 3 new tasks
12/1/2009 9:22:52 AM SETI@home Message from server: No work can be sent for the applications you have selected
12/1/2009 9:22:52 AM SETI@home Message from server: No work is available for Astropulse v5
12/1/2009 9:22:52 AM SETI@home Message from server: You have selected to receive work from other applications if no work is available for the applications you selected
12/1/2009 9:22:52 AM SETI@home Message from server: Sending work from other applications
12/1/2009 9:22:54 AM SETI@home Started download of 16no06ac.11061.22158.16.10.229
12/1/2009 9:22:54 AM SETI@home Started download of 16no06ac.10738.24203.14.10.16
12/1/2009 9:22:57 AM Project communication failed: attempting access to reference site
12/1/2009 9:22:57 AM SETI@home Temporarily failed download of 16no06ac.11061.22158.16.10.229: connect() failed
12/1/2009 9:22:57 AM SETI@home Backing off 1 min 0 sec on download of 16no06ac.11061.22158.16.10.229

---

"Life is a tragedy for those who feel, and a comedy for those who think."

"I never get into an argument that I cannot win."

after three reboots and a number of BOINC restarts, all downloads finally went through.

---

after three reboots and a number of BOINC restarts, all downloads finally went through.

Yes. Yesterday evening (my local time) during the weekley maintenance, someone in Berkeley have turned the right key ... so the music is again good :-)

FF

---

What works for me is a PC reboot.
All other applications work, and browsers etc can access the web.

It's only BOINC that fouls up.
Not S@H, but all my BOINC projects fail to communicate.
Reboot and C@H and S@H will send my results and download new WUs.
There's no LHC work available right now....

If it was just SETI I'd agree it was the router/server/ipconfig stuff.
But since it's both projects for which I have work, I would suspect it's more likely a common factor.

Anything from the Boinc Manager, Windows, my Router, my ADSL modem, my phoneline, my ISP ... but something that isn't Seti :)
Since a reboot always fixes it, my first thought is that it's Windows AP getting in a twist.

---

PAul

[IMG][/IMG]

This prevents 100,000 BOINC clients from constantly hammering the servers for more work.

The very best thing you can do is nothing at all. If you leave everything alone, the BOINC clients will patiently retry until they get work.

If you do as others suggest, you may get work more quickly (especially if there are server issues, as there were this weekend) but you do so by adding to the overall load (adding to the overload during recovery).

No, I don't think so.
I have work and is already assigned to me. But I cannot download it.
Results ready to send = 172,766
In this moment the charge of Internet resuorces at berkeley is 1/3 than maximum.
I think it's a bug/malfunction in the connection.
In the log I see:
01.12.2009 09:27:39 SETI@home Temporarily failed download of 30mr07aa.16918.10706.3.10.209: connect() failed
01.12.2009 09:27:39 SETI@home Backing off 23 min 52 sec on download of 30mr07aa.16918.10706.3.10.209


FF

We're mixing issues.

One is the whole project backoff mechanism, and why it exists.

The other has to do with a failure at SETI@Home, plus an unfortunate but hard to find bug in libcurl -- one that existed for years, but was only found last month.

---