But it is not a issue for Linux machines because your running the native environment of the task.
Us Windows users are emulating Linux via a Virtual Machine and that seems to be where the problem is at.
The Virtual Disk Image file Checksum code that we get does not seem to match the code the server wants and then we get a code -119 MD5 checksum error.

I have to run VirtualBox on my Ubuntu machines also to do the pythons.

But it does not always work quite the same way as on Windows. It is hopefully a small discrepancy, but we all need someone at Rosetta to look into it, and they never bother to even acknowledge problems. Maybe someone can get the attention of the Admin.

Sid Celery is already sending emails to Baker Lab, but they are a M-F office hours only project.
There is no dedicated IT person that monitors the forums, at least not that we have seen.
The only way they know if there is a problem is if the researcher of this specific project sees a lot of failures in his data. Other than that, your SOL.

You were in a conversation with Mikey who showed you how to isolate python tasks so you could limit the cores. The only thing further (which i don't know the commands for) is to "block" the specific task type. Maybe Mikey can help you with that in that other thread.

Your not alone with this MD5 issue, A windows user in Italy is also having the exact same problem.
So far everything we know to try and make this disappear has failed. So its something back in Seattle on their system that is causing this. Now why some windows machines and not others is a mystery, because I am cranking through these just fine.

You were in a conversation with Mikey who showed you how to isolate python tasks so you could limit the cores. The only thing further (which i don't know the commands for) is to "block" the specific task type. Maybe Mikey can help you with that in that other thread.

Your not alone with this MD5 issue, A windows user in Italy is also having the exact same problem.
So far everything we know to try and make this disappear has failed. So its something back in Seattle on their system that is causing this. Now why some windows machines and not others is a mystery, because I am cranking through these just fine.

I am not sure what you are referring to on MW. If it is "max concurrent" (or "project max concurrent") in an app_config, that causes a problem with excessive downloads. I have posted on it already here.

But that appears to be irrelevant to the present MD5 issue anyway. And I am seeing the same thing on Ubuntu as the Windows users, just a slightly different message.
https://boinc.bakerlab.org/rosetta/results.php?hostid=6143731&offset=0&show_names=0&state=6&appid=

I am trying a new version of BOINC. I was on 7.16.11, the released version from Ubuntu. Now it is 7.16.17 from Locutus-of-Borg.
That solved a problem on QuChemPedIA, but not necessarily here.

Seattle certainly needs to fix it.

---

I am trying a new version of BOINC. I was on 7.16.11, the released version from Ubuntu. Now it is 7.16.17 from Locutus-of-Borg.
That solved a problem on QuChemPedIA, but not necessarily here.

The new BOINC 7.16.17 didn't fix it. It is something they have to do.

---

You were in a conversation with Mikey who showed you how to isolate python tasks so you could limit the cores. The only thing further (which i don't know the commands for) is to "block" the specific task type. Maybe Mikey can help you with that in that other thread.

Your not alone with this MD5 issue, A windows user in Italy is also having the exact same problem.
So far everything we know to try and make this disappear has failed. So its something back in Seattle on their system that is causing this. Now why some windows machines and not others is a mystery, because I am cranking through these just fine.

I am not sure what you are referring to on MW. If it is "max concurrent" (or "project max concurrent") in an app_config, that causes a problem with excessive downloads. I have posted on it already here.

But that appears to be irrelevant to the present MD5 issue anyway. And I am seeing the same thing on Ubuntu as the Windows users, just a slightly different message.
https://boinc.bakerlab.org/rosetta/results.php?hostid=6143731&offset=0&show_names=0&state=6&appid=

I am trying a new version of BOINC. I was on 7.16.11, the released version from Ubuntu. Now it is 7.16.17 from Locutus-of-Borg.
That solved a problem on QuChemPedIA, but not necessarily here.

Seattle certainly needs to fix it.

But it is weird, MD5 shows up on your machine and the Italian machine, but not on mine and not that many others are talking about it. But is it all python tasks or just certain specific strings that are affected?

I also have the MD5 issue on Rosetta Python tasks. Presently it's been a 100% fail rate, error while downloading.

aaaf-IDC_pp-FPR_pp-mNHM_pp-NMBEN3_pp_0_1737815_2_1

<core_client_version>7.16.11</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
  <file_name>AIMNet_vm_v2.vdi</file_name>
  <error_code>-119 (md5 checksum failed for file)</error_code>
  <error_message>MD5 check failed</error_message>
</file_xfer_error>
</message>
]]>

aaaf-IDC_pp-SAR-AIB_pp-NMBEN3_pp_0_1737353_4_0

<core_client_version>7.16.11</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
  <file_name>AIMNet_vm_v2.vdi</file_name>
  <error_code>-119 (md5 checksum failed for file)</error_code>
  <error_message>MD5 check failed</error_message>
</file_xfer_error>
</message>
]]>

aaaf-mAZE_pp-NMALA_pp-mNMVAL_pp-NMBEN3_pp_0_1736941_7_0

<core_client_version>7.16.11</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
  <file_name>AIMNet_vm_v2.vdi</file_name>
  <error_code>-119 (md5 checksum failed for file)</error_code>
  <error_message>MD5 check failed</error_message>
</file_xfer_error>
</message>
]]>

I see you have had good luck with these Python tasks, what's your vBox setup?

Good lord, I just checked my Virtual Box and all the failed tasks apear to still be in there.

I'm using 6.1.12, the version supplied on the BOINC website, with the Oracle VM VirtualBox Extension Pack installed on Windows 10. Visualization extensions have been enabled in the BIOS.
Should I use the latest version (6.1.26) or the one supplied by BOINC? What about extensions, should I install any?

I received an odd message today:

Rosetta@home: Notice from server
VirtualBox is not installed
9/19/2021 6:01:50 PM

It is correct that I do not have VirtualBox installed, and I have not used VirtualBox to run BOINC programs.

---

How can I make it stop? I have been a long time supporter of RH, but will disconnect from the project if it keeps wasting my bandwidth with 2GB failed downloads.

Temporarily STOP REQUESTING NEW WORK FOR THE PROJET by settling NO NEW WORK for Rosetta on your PC(S) in BOINC until the project fixes the problem.

That means you will get no work at all, even though there are just under 13 million Rosetta 4.20 Tasks available.

---

Grant
Darwin NT

I received an odd message today:

Rosetta@home: Notice from server
VirtualBox is not installed
9/19/2021 6:01:50 PM

It is correct that I do not have VirtualBox installed, and I have not used VirtualBox to run BOINC programs.

That was sorted out yesterday.
It started on the 18th & when it did, it stopped those without VirtualBox from getting any Rosetta work- even that which doesn't need VirtualBox. Once they fixed it, there were no more notices about a lack of VirtualBox in Event logs, and work started flowing again- as can be seen in the Graph below.
In particular, the big dip on the 18th.

---

Grant
Darwin NT

There is a researcher in the group that has submitted a large batch of VM jobs that requires Virtual Box. More information is provided at https://boinc.berkeley.edu/wiki/VirtualBox.

This is the first large batch of "rosetta_python_projects" VM jobs but we hope to have more in the future. Since this is our first attempt at using BOINC's VM option, we will undoubtedly run into issues as we scale up. Please be patient as we try to resolve these issues. Our standard rosetta application is still being used but the number of available jobs can fluctuate as it has before depending on the computing demand from our researchers.

The VM app feature allows researchers much more flexibility to run scientific software that otherwise would not be possible on R@h. For example, the "rosetta_python_projects" app allows researchers to run deep learning based structure prediction pipelines including RoseTTAFold and AlphaFold2, and other python based sofware packages like AIMNet which is being used in the current batch of VM jobs to minimize potential microcycle therapeutics.

---

This is the first large batch of "rosetta_python_projects" VM jobs but we hope to have more in the future.

Very good. I have several machines with lots of memory waiting to do them.

BUT: You need to make them selectable from the regular Rosettas.
A simple checkbox would do, but even better would be the ability to select the number downloaded (or running) at at time.
See LHC, or Cosmology, or WCG for examples.

---

It is just an informational message, hoping that you will install VBox to crunch more tasks. Thanks.

There is a researcher in the group that has submitted a large batch of VM jobs that requires Virtual Box. More information is provided at https://boinc.berkeley.edu/wiki/VirtualBox

Virtualization and BOINC
BOINC uses virtualization to allow scientists to develop applications on their preferred operating system (usually Linux) and then run them on volunteered Windows and Mac computers. We call these VM apps.

BOINC's virtualization support uses a system called VirtualBox, which is open-source software maintained and distributed by Oracle. For more information about VirtualBox, please see their web site at https://www.virtualbox.org/

To run VM apps, your computer must have VirtualBox installed. Starting with BOINC version 7.2.28, the recommended BOINC installer for Windows includes VirtualBox as well. You can also install VirtualBox separately.

We recommend the VirtualBox version that is included in the recommended BOINC Windows installer, since newer VirtualBox versions do not work correctly for all projects.

If you are running Windows, it is essential that you install a version of BOINC that matches your version of Windows - use 64-bit BOINC on 64-bit versions of Windows, 32-bit BOINC on 32-bit versions of Windows. Otherwise, BOINC will not be able to detect the presence of VirtualBox.

Oh! So it's that thing I've been ignoring for several years... #Doh

Download BOINC + VirtualBox

---

aaaf-IDC_pp-FPR_pp-mNHM_pp-NMBEN3_pp_0_1737815_2_1

<core_client_version>7.16.11</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
  <file_name>AIMNet_vm_v2.vdi</file_name>
  <error_code>-119 (md5 checksum failed for file)</error_code>
  <error_message>MD5 check failed</error_message>
</file_xfer_error>
</message>
]]>

There goes another one. I have yet to encounter a Python task that doesn't error out. Is it something wrong with my setup, or is there a problem with these tasks? I've tried the version bundled with BOINC and the latest version, still 100% error rate.

I feel like I am missing out on some new information or something. Do these new "rosetta_python_projects" run native on Linux? Virtualbox is only needed on Windows and Mac, correct? I was under the impression that all Windows BOINC installations were already containers or VMs on Windows or Macs.

I feel like I am missing out on some new information or something. Do these new "rosetta_python_projects" run native on Linux? Virtualbox is only needed on Windows and Mac, correct? I was under the impression that all Windows BOINC installations were already containers or VMs on Windows or Macs.

The applications page says:

Linux running on an AMD x86_64 or Intel EM64T CPU 1.03 (vbox64)

Same as Windows and MacOS. No mention of a native app.

---

I'm pretty sure it uses VBox regardless of the host OS. I guess that way it can ship with the correct dependancies etc.

---

Interesting. I took a look at the applications page https://boinc.bakerlab.org/rosetta/apps.php and the VirtualBox page https://boinc.berkeley.edu/wiki/VirtualBox but I don't see anything that would indicate a definitive answer. My Linux systems do not have VirtualBox installed. The apps page does indicate they are running on Linux systems but they don't indicate if VirtualBox is or needs to be installed. The same goes for Windows in the apps page.

It was my understanding that Rosetta tasks were already written for Linux environments and so it was just easier to containerize Linux on Windows than re-write everything for Windows or Macs.

I haven't seen anything in my logs about downloading AIMNet_vm_v2.vdi and when I check out my boinc directory, I see minirosetta and 4.20 executables but I don't see anything about vbox64 or python.

I have 671 tasks in progress and I am showing 0 rosetta python tasks. I was just curious if there is anything I need to do to keep my systems up to date so that they can maximize processing capability for Rosetta.

If Virtualbox isn't installed, your system won't download any work units or executables related to the vbox app.

This "1.03 (vbox64)" indicates the need of the pyrosetta app for virtualbox.

---

Hello,

Why could I receive the message "Communication with VM Hipervisor failed"? In the VBox register appears the error
«Failed to create the VirtualBox object!
NS_ERROR_SOCKET_FAIL (0xC1F30200) IPC Daemon socket error.»

I have the Boinc version 7.16.16 and the VirtualBox 6.1.26 r145957 running on Debian GNU/Linux 11 (bullseye) [5.10.0-8-amd64|libc 2.31 (Debian GLIBC 2.31-13)].
The boinc user is added to the vboxusers, vboxguests and libvirt groups.

Any clue about what could be happening? I have no experience with VirtualBox, I installed it just as a Rosetta@home requirement.