I've increased resource share to Einstein to help SETI catch up...

---

-Aardvark

Excuse me if I am asking something obvious here - not quite as computer literate as the rest of you. I have a laptop with SETI, LHC & EINSTEIN, and a desktop downstairs with SETI and PREDICTOR. Both the S@H files are hung up with Uploading/Downloading bottlenecks. Now at the same time none of the rest of the BOINC projects will send me a WU. They can be tricked by resetting, but as soon as they upload a finished unit they forget to send me any more. They used to work unattended. Is this a SETI related problem? Should I just dump the finished SETI WUs and let the others return to normal?

---

Excuse me if I am asking something obvious here - not quite as computer literate as the rest of you. I have a laptop with SETI, LHC & EINSTEIN, and a desktop downstairs with SETI and PREDICTOR. Both the S@H files are hung up with Uploading/Downloading bottlenecks. Now at the same time none of the rest of the BOINC projects will send me a WU. They can be tricked by resetting, but as soon as they upload a finished unit they forget to send me any more. They used to work unattended. Is this a SETI related problem? Should I just dump the finished SETI WUs and let the others return to normal?

I suspended SETI and LHC took off. I have 17 SETI work units to upload and 17 to down load. I have not had a good SETI transfer since before the database reorg last week. I hope that I can get them uploaded before the 17th as that is the deadline.

---

Excuse me if I am asking something obvious here - not quite as computer literate as the rest of you. I have a laptop with SETI, LHC & EINSTEIN, and a desktop downstairs with SETI and PREDICTOR. Both the S@H files are hung up with Uploading/Downloading bottlenecks. Now at the same time none of the rest of the BOINC projects will send me a WU. They can be tricked by resetting, but as soon as they upload a finished unit they forget to send me any more. They used to work unattended. Is this a SETI related problem? Should I just dump the finished SETI WUs and let the others return to normal?

From reading the threads, I'd say it's related to SETI@Home in that there's a problem connecting to S@H that isn't happening with other projects, but it seems to be somewhere short of S@H itself. An accepted workaround is to use a proxy server: Here is a site with lists of possible proxies, I think you'd have to experiment and see which one works for you. On my home setup, I leave BOINC without the proxy connection connected except when I check it and see waiting up/down-loads. Then activate the proxy, update/retry the pending work, and unselect the proxy until the next time. Checking twice a day, with multiple projects and a .2 day connect setting, finds me always with a S@H work unit still processing, along with the others.

Let us know if you need more help, you can find much more information in the Wiki, linked in my signature.

MJ

---

With this availability we had, initially, one project that was hosted and live. SETI@Home, shortly after that we started having some of the other projects move into open beta. Now, we are in production mode on 5 projects, with additional applications for several of those projects in testing (CPDN: Sulfur something, SETI@Home: AstroPulse and SETI@Home extended/advanced/or whatever we are going to call it).

Minor nit. It is six projects in production. SETI, LHC, Einstein, Predictor, CPDN and SZTAKI (Hungarian).

---

BOINC WIKI

Excuse me if I am asking something obvious here - not quite as computer literate as the rest of you. I have a laptop with SETI, LHC & EINSTEIN, and a desktop downstairs with SETI and PREDICTOR. Both the S@H files are hung up with Uploading/Downloading bottlenecks. Now at the same time none of the rest of the BOINC projects will send me a WU. They can be tricked by resetting, but as soon as they upload a finished unit they forget to send me any more. They used to work unattended. Is this a SETI related problem? Should I just dump the finished SETI WUs and let the others return to normal?

I suspended SETI and LHC took off. I have 17 SETI work units to upload and 17 to down load. I have not had a good SETI transfer since before the database reorg last week. I hope that I can get them uploaded before the 17th as that is the deadline.

I saw a post by another cruncher and tried his advise and it worked. Go to tools on the manager, click on tools, then options, then Http, enter 128.32.18.173 port 80 and you should be able to up and down load manually.....Doing this will stop up and download of the other projects so after you finish with Seti uncheck the connect via proxy......

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

With this availability we had, initially, one project that was hosted and live. SETI@Home, shortly after that we started having some of the other projects move into open beta. Now, we are in production mode on 5 projects, with additional applications for several of those projects in testing (CPDN: Sulfur something, SETI@Home: AstroPulse and SETI@Home extended/advanced/or whatever we are going to call it).

Minor nit. It is six projects in production. SETI, LHC, Einstein, Predictor, CPDN and SZTAKI (Hungarian).

Umm actually it is 7 or 8 depending on if you count the japanesse projects seperately or as one.

On that note there is a chance these projects will be able to use the 5.xx clients when they come around. They currently require a special 3.xx client.

---

BOINC WIKI

BOINCing since 2002/12/8

Thanks for the ideas! I tried changing the proxy but the SETI logjam is too solid, and nothing happened. Suspending SETI has allowed all the other BOINC programs to run happily all night. Even suspended, I see in the MESSAGES file that SETI still is trying to up/download on a regular basis, but isn't getting through. At least my computers are doing something useful while S@H is getting the backlog straightened out.

---

Again ....... I'm gonna do the only thing I can do to help....SUSPEND SETI....do No work, don't ask for none and don't send none back. Do other projcts instead. It really is the ONLY WAY it can catch up now......we must stop getting and sending back work.....all if us.....it cannot cope right now!

---

I thought about disconnecting our grid from the project (we only have SETI clients for Solaris, so I can't just switch to another project) but that wouldn't really fix anything ... what would happen next time this situation arises ?

So I decided it's probably best to keep S@H at a realistic level and the guys at Berkeley can see whether the fixes they are putting in place will actually make a difference to the current, real world load the project is currently experiencing.

If they don't see a significant drop in the queue once they've 'fixed' it then they are going to be aware much sooner that the setup probably won't cope with any significant increase in demand in the near future.

---

I have not suspended seti but I have reduced my resource share for seti to help ease the load until this can be sorted out.

---

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

And God said"Let there be light."But then the program crashed because he was trying to access the 'light' property of a NULL universe pointer.