Are you putting them in the right app_config.xml file?
I.e., the one in the ..../projects/boinc.bakerlab.org_rosetta directory?

/var/lib/boinc/projects/boinc.bakerlab.org_rosetta]# cat app_config.xml
<app_config>
<project_max_concurrent>3</project_max_concurrent>
</app_config>



------------------------



Yep..for me its in boinc data/projects/boinc.bakerlab.org_rosetta.
<name>rosetta python projects</name>
<app_config>
<project_max_concurrent>1</project_max_concurrent> (it could be 2 but not 3)
</app_config>
And its back to 3 at a time again.

Resource share is at 100%. I'm thinking I will have to bring it back to 50 again.

I do not even have a directory named [b]boinc data/projects/boinc.bakerlab.org_rosetta[/b]
                                             ^
                              ?????  >>>-----| I cannot believe this is a space.
Filesystem            1K-blocks      Used Available Use% Mounted on
/dev/sdb3             122908728  18785860  97856396  17% /var/lib/boinc

My system is running Red Hat Enterprise Linux release 8.5 (Ootpa) and all its Boinc stuff is in /val/lib/boinc. That is a partition all its own on one of my spinning hard drives. It has only the following directories;

[/var/lib/boinc]$ ls -l
drwx------.  2 root  root     4096 Jul  1 15:22   lost+found
drwxrwx--x.  2 boinc boinc    4096 Dec  5 09:46   notices
drwxrwx--x.  6 boinc boinc    4096 Nov 27  2020   projects
drwxrwx--x. 12 boinc boinc    4096 Dec  4 11:56   slots

---

but I am more than three score and ten and I can tell you it gets worse with age. - I am more than XLV and less than LV

For the "Vm job unmanageable errors", you can try this fix:
https://boinc.bakerlab.org/rosetta/forum_thread.php?id=14839&postid=103729#103729

It will probably work as well as going back to VirtualBox 5.2.44, which is easy in Windows, but not so easy in Ubuntu.

---

I'm LXXVIII and feeling it a little on here atm..:/

Rosetta is already using that wrapper version, vboxwrapper_26203_windows_x86_64.exe on windows.

Rosetta is already using that wrapper version, vboxwrapper_26203_windows_x86_64.exe on windows.

I haven't tried it on Windows yet. But maybe you could check the file size to see if they are the same?
(Or maybe Rosetta fixed it themselves? That would be the best fix.)

And they don't seem to have a fixed version for Linux on that website, so I will be using the one from LHC, which is different than the Rosetta one.

PS - The ones you have finished state:

<stderr_txt>
2021-12-05 09:51:08 (26084): Detected: vboxwrapper 26202

So maybe they just changed it?

---

I'm LXXVIII and feeling it a little on here atm..:/

That is an outstanding age. You have acquired a lot of experience by then.

---

I am showing a date modified of 12/3/2021 for the wrapper.
It is odd. The properties of the file and the messages return 26202 but it is named 26203
They didn't change the file properties and version from BOINC? I just downloaded the linked zip from that post and checked it also.

I have it running Cosmology VMs and it is more stable on my old computer. Running 4 work units of 2 cores each on an Intel i7 920. It's running at 100% and not complaining.

I am showing a date modified of 12/3/2021 for the wrapper.
It is odd. The properties of the file and the messages return 26202 but it is named 26203
They didn't change the file properties and version from BOINC? I just downloaded the linked zip from that post and checked it also.

I have it running Cosmology VMs and it is more stable on my old computer. Running 4 work units of 2 cores each on an Intel i7 920. It's running at 100% and not complaining.

With that date, it must be the new version. They probably just modified something in it to make BOINC accept it as the old one.
It might be easier doing that than changing BOINC.

---

I notice the same thing with the wrapper for Atlas tasks.
Logs for my completed tasks there show "Detected: vboxwrapper 26197". File is "vboxwrapper_26198ab7_windows_x86_64"

I'm LXXVIII and feeling it a little on here atm..:/

Makes me feel young

I learn every day, especially on here. :)

I had gone as far to untick all the disk space boxes to give it unlimited use of the disk

The boxes aren't tickable, they require values. And one value in any one of the options overrides the values in any of the other two when it comes to what disk space is actually available.
While people are now able to get & do more Python Tasks, i can see many more people leaving the project anyway.
Rosetta 4.20 Tasks weren't exactly high payers with roughly 340 Credits for 8 hours of work (depending on the system). For the same time frame, Python Tasks only pay out around 130, roughly 2.5 times less.

I had a look at the versions of BM that I have running here@home
MS 7.2.27 no tick box only value box`s
MS 7.8.3 tick and value box`s
MS 7.16.5 tick and value box`s
MS 7.16.20 tick and value box`s {this is the one infected with python`s}
Linux Mint 7.9.3 tick and value box`s {Linux only build}
and had a quick look at yours and they are 7.16.11 with no tick`s !!
Anyone else running different versions of BM , have a look in the preferences/disk and memory tab
Yes , credits for python`s are low even by rosetta standards, and the `difficulties` to run them . . . . .

I had a look at the versions of BM that I have running here@home

I was referring to the web based settings.
If you've only got one system, local Setting are ok. More than one, web based settings make life much easier.

---

Grant
Darwin NT

I am not getting any Rosetta work on any of my machines, and all of them have a Notice that simply states "Virtualbox not installed." Are these two things related?

I am not getting any Rosetta work on any of my machines, and all of them have a Notice that simply states "Virtualbox not installed." Are these two things related?

Yes.
4.2 tasks are done.
The virtualbox tasks are memory hogs and need virtual box 5.x to run properly and you need to enable virtualization on your motherboard to run this.
They will error out on 6.x

I am not getting any Rosetta work on any of my machines, and all of them have a Notice that simply states "Virtualbox not installed." Are these two things related?

Yes.
4.2 tasks are done.
The virtualbox tasks are memory hogs and need virtual box 5.x to run properly and you need to enable virtualization on your motherboard to run this.
They will error out on 6.x

Is that just for now or forever? Because if it is forever, I might as well resign from the project and find another.

---

I am not getting any Rosetta work on any of my machines, and all of them have a Notice that simply states "Virtualbox not installed." Are these two things related?

Yes.
4.2 tasks are done.
The virtualbox tasks are memory hogs and need virtual box 5.x to run properly and you need to enable virtualization on your motherboard to run this.
They will error out on 6.x

Is that just for now or forever? Because if it is forever, I might as well resign from the project and find another.

Rosetta 4.2 tasks are still being supplied but at a very low rate. There is sporadic Robetta work every day or so and we'll probably see a batch or so every now and then from the Rosetta@home/IPD researchers.

---

I am not getting any Rosetta work on any of my machines, and all of them have a Notice that simply states "Virtualbox not installed." Are these two things related?

Yes.
4.2 tasks are done.
The virtualbox tasks are memory hogs and need virtual box 5.x to run properly and you need to enable virtualization on your motherboard to run this.
They will error out on 6.x

Is that just for now or forever? Because if it is forever, I might as well resign from the project and find another.

Rosetta 4.2 tasks are still being supplied but at a very low rate. There is sporadic Robetta work every day or so and we'll probably see a batch or so every now and then from the Rosetta@home/IPD researchers.

It's done as a full time project for non virtual box type tasks.
SiDock is an alternative to RAH.
Strict NON Vbox jobs.
Fast turnover rate of around 2 hrs.
About 17 credits average,

Is that just for now or forever? Because if it is forever, I might as well resign from the project and find another.




Rosetta 4.2 tasks are still being supplied but at a very low rate. There is sporadic Robetta work every day or so and we'll probably see a batch or so every now and then from the Rosetta@home/IPD researchers.




It's done as a full time project for non virtual box type tasks.
SiDock is an alternative to RAH.

SiXock looks more like the WCG open Pandemics work units.

www.worldcommunitygrid.org/research/opn1/overview.s

---