I have a situation where Rosetta seems to think I don't have enough disk space allocated to run the program. The message I get is; 11/16/2007 7:25:09 PM|rosetta@home|Message from server: (there was work but you don't have enough disk space allocated)>. Now I know I have enough space because I have 10gb allocated for Boinc to use and only about 1/10 of that is being used. I have tried numerous remedies such as resetting the project, detaching the project, and even changing the local space size. All of the other projects are running fine, including the climate progect which is a real space hog. I even checked registry to see if I could find anything unusual in there but no luck. I have Rosetta running fine on another machine and the only thing I can think of is that recently my machine locked up and Rosetta could have been running at the time. If anyone can give me any possible solutions I can try to remedy this problem, other than reinstalling Boinc, I would greatly appreciate it. Thanks in advance.

---

are you setting your options through your account on the website or directly in Boinc Manager?

---

are you setting your options through your account on the website or directly in Boinc Manager?

I have tried both options with no effect. Both the Boinc and local preferences have the use at most space set to 10GB but I am running with the local taking precedence.

---

So, use at most 10GB.

...leave at least?

...use at most xx % of total?

When you go to the advanced view, to the Disk tab, how much does it say is being used for Rosetta?

And what is Rosetta's resource share on that machine? (projects tab)

---

Rosetta Moderator: Mod.Sense

28-Nov-2007 23:48:54 [rosetta@home] Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
28-Nov-2007 23:48:59 [rosetta@home] Scheduler request succeeded: got 0 new tasks
28-Nov-2007 23:48:59 [rosetta@home] Message from server: Project encountered internal error: shared memory
28-Nov-2007 23:50:19 [rosetta@home] Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
28-Nov-2007 23:50:24 [rosetta@home] Scheduler request succeeded: got 0 new tasks
28-Nov-2007 23:50:24 [rosetta@home] Message from server: Project encountered internal error: shared memory
????????????????????????

---

28-Nov-2007 23:48:54 [rosetta@home] Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
28-Nov-2007 23:48:59 [rosetta@home] Scheduler request succeeded: got 0 new tasks
28-Nov-2007 23:48:59 [rosetta@home] Message from server: Project encountered internal error: shared memory
28-Nov-2007 23:50:19 [rosetta@home] Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 1 completed tasks
28-Nov-2007 23:50:24 [rosetta@home] Scheduler request succeeded: got 0 new tasks
28-Nov-2007 23:50:24 [rosetta@home] Message from server: Project encountered internal error: shared memory
????????????????????????

---

28-Nov-2007 23:50:24 [rosetta@home] Message from server: Project encountered internal error: shared memory
????????????????????????

Hi (_KoDAk_),

I have received the same message. Site://boincprojectstatus.ath.cx/ says: Scheduler is up but reporting status: Project is down.
From: Message boards : Number crunching : Whats up with Ralph website? You can also see a reaction from:
Keith E. Laidig
Forum moderator
Project administrator
Project developer

Hmmm, the system is down. I'm not on campus today - I'll see if I can get someone there to take a quick look...

-KEL

Have a nice day,
Path7.

Hi, folks.

I have not been supplied with any new work since the website came back on-line. I was already out of work so Rosetta is losing time to other projects.

Anyone know what is happening, please?

Happy crunching!

Mike, it's possible your other projects got enough work that BOINC doesn't think you will have any time to be running Rosetta within your "connect to network every... days" setting.

Please review this thread . It has a number of things to check on your end.

---

Rosetta Moderator: Mod.Sense

Mike, it's possible your other projects got enough work that BOINC doesn't think you will have any time to be running Rosetta within your "connect to network every... days" setting.

Please review this thread . It has a number of things to check on your end.

Thanks, Mod.Sense, I have checked the thread and that seems to be the problem.

01/12/2007 18:07:24|rosetta@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 0 completed tasks
01/12/2007 18:07:29|rosetta@home|Scheduler request succeeded: got 0 new tasks
01/12/2007 18:12:54|lhcathome|Sending scheduler request: To fetch work. Requesting 404171 seconds of work, reporting 0 completed tasks
01/12/2007 18:12:59|lhcathome|Scheduler request succeeded: got 0 new tasks

However, I have not crunched any Rosetta units for 3 days. One was reported as the website reopened but that had finished and uploaded some time before.

Seti & WCG owe time to rosetta and they are still crunching. Even more time is owed to LHC but that appears to be closed at the moment.

I have 2 cores and a 50% allocation to LHC which is not being taken up. The 25% allocation to CPDN is therefore boosted to 50% and is running continuously on one core. The other core is being shared between WCG (nominal 12.5% share) and Seti (nominal 6.25% share) with Rosetta (nominal 6.25% share) getting nothing.

I have 15 units in hand totalling 75 hours and have 5 days set. I normally have about 30-40 units in hand. These figures exclude CPDN. The earliest report deadline is 5 Dec for WCG and 18 Jan for Seti.

There does not seem to be any reason that BOINC should be excluding Rosetta.

...with your major project (50%) not giving new work, BOINC will have a challenge scheduling work. If LHC should come online tomorrow, BOINC would prefer (based on the debts) to get work for LHC (my guess), and so it's still holding out for that to happen. But, as time goes by and that does not happen, it will be adding to Rosetta debt. So it all balances out.

When you run 5 projects like that, it's normal to not always have work for all of them at the same time. From the sounds of it, once WCG gets work completed, BOINC will request work from Rosetta. Try to resist the temptation to try and force BOINC to do something it doesn't want to do. It will likely only confuse things further.

---

Rosetta Moderator: Mod.Sense

...with your major project (50%) not giving new work, BOINC will have a challenge scheduling work. If LHC should come online tomorrow, BOINC would prefer (based on the debts) to get work for LHC (my guess), and so it's still holding out for that to happen. But, as time goes by and that does not happen, it will be adding to Rosetta debt. So it all balances out.

When you run 5 projects like that, it's normal to not always have work for all of them at the same time. From the sounds of it, once WCG gets work completed, BOINC will request work from Rosetta. Try to resist the temptation to try and force BOINC to do something it doesn't want to do. It will likely only confuse things further.

Thanks for the reply. Everything had been working well, with plenty of pending units on all schemes, until Rosetta went down. It obviously took BOINC a long time to re-schedule but they have finally supplied 5 Rosetta units at one time. However nothing else is now being supplied. I presume that they have now realised that Rosetta needs to catch up. Hopefully, when that has happened, everything will return to normal.

...with your major project (50%) not giving new work, BOINC will have a challenge scheduling work. If LHC should come online tomorrow, BOINC would prefer (based on the debts) to get work for LHC (my guess), and so it's still holding out for that to happen. But, as time goes by and that does not happen, it will be adding to Rosetta debt. So it all balances out.

When you run 5 projects like that, it's normal to not always have work for all of them at the same time. From the sounds of it, once WCG gets work completed, BOINC will request work from Rosetta. Try to resist the temptation to try and force BOINC to do something it doesn't want to do. It will likely only confuse things further.

One thing not mentioned in this reply is CPDN. The long run times there often give the scheduler fits. Their tasks will often go in and out of EDF mode until very near the end. You will likely not get CPDN tasks for awhile after the current one due to the extra time that task will get.

---

BOINC WIKI

BOINCing since 2002/12/8