Got a PM reply from Toni:

Oh gosh, thanks ...

:-)

Got a PM reply from Toni:

Hey Richard, thanks for raising this with admins.
Much appreciated!

So hopefully we will be back up and running shortly :). Thanks for bring it to Toni's attention.

Will someone tell us when the FUBAR has finished???

---

The problem is still not resolved...

Michael.

---

President of Rechenkraft.net - Germany's first and largest distributed computing organization.

Got a PM reply from Toni:

Hey Richard, thanks for raising this with admins.
Much appreciated!

What surprises me though is that no one from GPUGRID found out by themselves :-(

I aborted all my gpu wu's to let someone with windows run them. Was hoping the certificate would be renewed by now so I could finish the ones I had time invested that I suspended before they failed. No such luck :-(. Barley enough calander time left to finish them anyway.

Toni responded in this thread: http://www.gpugrid.net/forum_thread.php?id=4925&nowrap=true#51834

We are aware of the problem. We'd like to do a major version upgrade rather than continue fixing the old one. For the time being, I'm deprecating the app for linux so crunching goes on on Windows rather than erroring out.

So it looks like time to find a new project for the majority of my machines. Only have 1 that still runs M$

---

I came back from the Pent to this. :( Thought my computers borked.

So does anyone want to explain how a BOINC wrapper works? The docs don't really say anything about the mechanics involved.

What pre-requisites are there?

Anyone running a BOINC wrapper on other projects and care to elaborate?

LHC@home uses a boincwrapper. All Windows, MAC OSX and other Linux distros can run their programs written in Scientific Linux. You must have VirtualBox installed.
Tullio

---

LHC@home uses a boincwrapper. All Windows, MAC OSX and other Linux distros can run their programs written in Scientific Linux. You must have VirtualBox installed.
Tullio

Nope that's even more separation from the client including OS and environment variables like specific libc versions. In the case of LHC they give the choice of VBox or setting up CVFMS and Singularity on your own which is included in vbox.vdi file

https://boinc.berkeley.edu/trac/wiki/WrapperApp

If you DON'T want want to include progress % complete, check pointing, GPU device # within your app then the wrapper can do that.

Don't expect it to be as efficient as there is now another layer between the exe doing the calculations and hardware.

So we can no longer run this BOINC GPU Project under BOINC version 7.9.3 on Ubuntu 18.04.2 LTS [4.15.0-51-generic|libc 2.27 (Ubuntu GLIBC 2.27-3ubuntu1)] Running NVIDIA GeForce GTX 1080 Ti (4095MB) driver: 390.11?

So we can no longer run this BOINC GPU Project under BOINC version 7.9.3 on Ubuntu 18.04.2 LTS [4.15.0-51-generic|libc 2.27 (Ubuntu GLIBC 2.27-3ubuntu1)] Running NVIDIA GeForce GTX 1080 Ti (4095MB) driver: 390.11?

Correction:
We can not run this BOINC GPU Project (GPUGrid) on any Linux distro for a who-knows-how-long time period.

I bet it won't be long before we get Linux WUs again. In the mean time there's asteroids, einstein, milkyway & seti to keep one busy.

---

So does anyone want to explain how a BOINC wrapper works? The docs don't really say anything about the mechanics involved.

From what I understand its a wrapper program they put around their normal (non-BOINC) science app that is used to invoke it. No pre-reqs. No need for vbox. That way the wrapper handles the BOINC interaction and allows the use of non-BOINC app.

See https://boinc.berkeley.edu/trac/wiki/WrapperApp for docs.

---

BOINC blog

Thanks, I had already read that document and was and still am confused. I gather it is not a VM. So assume you don't need virtualization on the cpu?

Why does BOINC offer versions of BOINC+Virtual Box if this mechanism does not require VBox?

Does VBox do more or less than a wrapper? What are the limitations of a wrapper compared to VBox?

Does the application wrapped in a wrapper have to be native code for the platform? With a VM you could run an app not native to the platform.

Thanks, I had already read that document and was and still am confused. I gather it is not a VM. So assume you don't need virtualization on the cpu?

Why does BOINC offer versions of BOINC+Virtual Box if this mechanism does not require VBox?

Does VBox do more or less than a wrapper? What are the limitations of a wrapper compared to VBox?

Does the application wrapped in a wrapper have to be native code for the platform? With a VM you could run an app not native to the platform.

The wrapper does not need VBox. It's just another interface to perform BOINC related functions while the project's 'math.exe' or w/e is doing the crunching ONLY performs calculations.

VBox can set up the entire OS environment to satisfy all the specifics needed to crunch. If a project needs extra programs that do not typically come with an OS or are normally installed by people then that can be included in the vbox image. Again as LHC as the example, Singularity and CVFMS are included in the image. They can also make 1 vbox image for Windows and Linux Host OSs

Is the BOINC wrapper a memory hog like virtualbox???

---