I'm running both Rosetta and Seti, and I'm dead in the water. Seti is having problems uploading and downloading work. But, I figured that Rosetta would still be working. But, nothing. Is there anything that I can do to get at least Rosetta running? Like Suspend Seti?

---

Ah ha! Suspending Seti did the trick. Guess I should have tried it before I asked.

---

Ah ha! Suspending Seti did the trick. Guess I should have tried it before I asked.

:-) It's probably related to "long term debt". While unable to get work from SETI, BOINC has likely been crunching a bigger share of Rosetta than it normally would, and it wants more SETI. By suspending SETI, you have basically negated the effect of that debt (until you resume SETI, at which time it will probably refuse to do any Rosetta work for some time).

You might, at least temporarily, re-order the resources shares - doesn't look like SETI will be working smoothly any time soon.

---

*** Join BOINC@Australia today ***

humm that is definatly intresting... so if the server cant get jobs from projects like seti.. it could actualy be stalling my systems and not leting me get as much effency .. i didnt know that... i may have to remove a few things from some of my computers like BURP who dosnt have any new WU's and Seti thats being well Dead and a few other little projects that are building %age debt and haveing notheing to process


im glad you posted that.. no wonder my credits per day have been droping.. wonder how many other people this is happening to and they dont know about it

---

humm that is definatly intresting... so if the server cant get jobs from projects like seti.. it could actualy be stalling my systems and not leting me get as much effency .. i didnt know that... i may have to remove a few things from some of my computers like BURP who dosnt have any new WU's and Seti thats being well Dead and a few other little projects that are building %age debt and haveing notheing to process

im glad you posted that.. no wonder my credits per day have been droping.. wonder how many other people this is happening to and they dont know about it

I have to wonder if it would be worth while to submit a bug to Boinc where it considers a project suspended if it's done "due diligence" trying to connect (maybe 5 attempts), and failed to get work. It should (of course) continue to try, and "unsuspend" if and when it gets work, but that should help keep people crunching 24/7.

---

Actually, I also believe this MIGHT be because your cache size is too small. Increase your cache size (in small increments, unless you are extremely familiar with it's workings) and it might download a small amount of rosetta for you to crunch, while keeping a bit of the cache open for a possible successful contact with SETI.

IT MAY BE that your cache size is so low that by downloading any new work from anywhere, your client might consider that detrimental to your balancing your resource debt.

IIRC with a recent change, the more long term debt you incur, the larger the required available portion of your cache gets(as a percentage related to your PC's performance). Obviously, you'd need a larger cache if your PC is only moderate in it's performance, compared to something with all the latest hardware.

---

This situation is being looked at ... the "stall" of one project issuing work causing problems on your computer is a hard one. How can the client distinguish this problem from other "normal" problems. There are cases where participant settings and configurations can mimic parts of this problem.

But, the developers are thinking about this. Also, about idle CPUs which can occur for other reasons (Predictor@Home throwing up a diagnostic window comes to mind).

The good thing is that the BOINC "community" has some smart and dedicated people in it that are just as passionate (if not more rabid :)) about getting the science done. John Keck and JM VII, two of the smartest BOINCers (along with Ingleside) are working on this ...

This is where the power of having multiple projects all using the same infrastructure comes in. For example, Bruce in Einstein@Home develops a new tool, it gets added to the baseline and now all projects have this added capability. His new log tool we hope will help us with troubleshooting networking problems.

Anyway, keep a stiff upper lip ... and be patient ... these are not easy problems ...

---