LHC@home

found this on another thread - it worked for me.

I analyzed the ca-bundle.crt file and found out that AddTrust External Root certificate expired today.
I removed the expired certificate part from the file and now everything works normal for me again.

Here is a guide to a quick fix:
Backup all your sensitive data first, This is only tested on 1 computer so far.
Exit BOINC
Open file manager and go to C:ProgramFilesBOINC or wherever you have installed BOINC.
Make a backup copy of ca-bundle.crt just in case my instuctions screw up something.
Right click on ca-bundle.crt and open it with Notepad
Scroll down to AddTrust External Root, Below this is the expired certificate.
Delete everything from -----BEGIN CERTIFICATE----- to -----END CERTIFICATE----- including the begin and end lines.
Save the file
Start BOINC and try again.

happy crunching

Hi,

I did this and it solved the issue. No need to update BOINC client (but I guess that updating is the prefered long term solution). If you don't want to update then just delete the expired root CA from ca-bundle.crt and it'll be OK.

OK, thanks for the confirm. I'll finish my WCG-tasks (some hours), try to install the apk and will see whether I can attach LHC@home to my phone now.

If you're running 7.16.5, you'll need to uninstall it first. For some reason Android hates you "downgrading" a program and will instead tell you the APK is corrupt! It's lying.

---

OK, thanks for the confirm. I'll finish my WCG-tasks (some hours), try to install the apk and will see whether I can attach LHC@home to my phone now.

If you're running 7.16.5, you'll need to uninstall it first. For some reason Android hates you "downgrading" a program and will instead tell you the APK is corrupt! It's lying.

No, I was running the default BOINC from Google Play v7.4.53.
Meanwhile installed 7.16.3 over the old version. I could attach to LHC@home now, but getting "No tasks are available for SixTrack".

OK, thanks for the confirm. I'll finish my WCG-tasks (some hours), try to install the apk and will see whether I can attach LHC@home to my phone now.

If you're running 7.16.5, you'll need to uninstall it first. For some reason Android hates you "downgrading" a program and will instead tell you the APK is corrupt! It's lying.

No, I was running the default BOINC from Google Play v7.4.53.
Meanwhile installed 7.16.3 over the old version. I could attach to LHC@home now, but getting "No tasks are available for SixTrack".

Works ok here. Fresh install of 7.16.3 on Android 7.0 yesterday. I just suspended all projects except LHC, which currently had one core of four running Sixtrack. It immediately downloaded three more Sixtracks and commenced calculations..

---

Well the certs error seems to have now occurred on my machine (I was not affected the original 2020 May 30 problem). It was working fine until what seemed liked 2021 Jan 15, 0:00 UT....it may have been slightly earlier, 2021 Jan 15, 0:00 CERN time?

After reading all of the various solutions people put out there I am unsure what works..The few that I have tried haven't worked.

Your computer is running lots of outdated software packages that should be upgraded:
Microsoft Windows 7 -> Microsoft Windows 10
BOINC Version 7.8.3 -> BOINC Version 7.16.11
Virtualbox 5.0.18 -> VirtualBox 6.1.16

One advantage of recent packages is that they include recent CA keys.

Your computer is running lots of outdated software packages that should be upgraded:
Microsoft Windows 7 -> Microsoft Windows 10
BOINC Version 7.8.3 -> BOINC Version 7.16.11
Virtualbox 5.0.18 -> VirtualBox 6.1.16

One advantage of recent packages is that they include recent CA keys.

Can you tell me what version of VB is required for LHC? Because I've just joined another project that doesn't like later versions. Will it break LHC if I downgrade?

---

Can you tell me what version of VB is required for LHC? Because I've just joined another project that doesn't like later versions. Will it break LHC if I downgrade?

According to the VirtualBox download page all versions prior to 6.1 are out of support since July 2020:
https://www.virtualbox.org/wiki/Downloads

I suggest to contact the admins of the "new" project and ask them to update their project.
Older versions may run with LHC but there is no guarantee that they are supported after OS/BOINC updates.

Can you tell me what version of VB is required for LHC? Because I've just joined another project that doesn't like later versions. Will it break LHC if I downgrade?

According to the VirtualBox download page all versions prior to 6.1 are out of support since July 2020:
https://www.virtualbox.org/wiki/Downloads

I suggest to contact the admins of the "new" project and ask them to update their project.
Older versions may run with LHC but there is no guarantee that they are supported after OS/BOINC updates.

I'll leave it on the latest one. I ain't risking messing up LHC for a project that can't program properly. They're thinking of making non-VB tasks anyway. I wonder if they haven't paid for the latest compiler? Seems odd to write a new program that only works in an older VB....

---

Can you tell me what version of VB is required for LHC? Because I've just joined another project that doesn't like later versions. Will it break LHC if I downgrade?

According to the VirtualBox download page all versions prior to 6.1 are out of support since July 2020:
https://www.virtualbox.org/wiki/Downloads

I suggest to contact the admins of the "new" project and ask them to update their project.
Older versions may run with LHC but there is no guarantee that they are supported after OS/BOINC updates.

@computezrmle, you avoided answering the question and just cast shade at the other project.
Their project is in development and, for this beta period, are not able to use VBox 6.1.x and later under Windows X only.

Do LHC WU's work properly under VBox ver 5.2.44?

Because I am going back to 5.2.44 and will run ATLAS on that version.
LHC doesn't appear to be calling on any new features of VBox that haven't been supported since ver 4.x

Can you tell me what version of VB is required for LHC?

I returned work two days ago on VBox 5.2.42 (Ubuntu 18.04.5).
https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10671473

Can you tell me what version of VB is required for LHC?

I returned work two days ago on VBox 5.2.42 (Ubuntu 18.04.5).
https://lhcathome.cern.ch/lhcathome/show_host_detail.php?hostid=10671473

Thankyou Jim.
Question answered.

I suggest to contact the admins of the "new" project and ask them to update their project.
Older versions may run with LHC but there is no guarantee that they are supported after OS/BOINC updates.

Cosmology@Home is running with Virtualbox 5.2.44 only.
For me LHC@Home in Windows run also with 5.2.44, but also with 6.1.12 from Boinc-Mainpage. (Boinc 7.16.11).

I suggest to contact the admins of the "new" project and ask them to update their project.
Older versions may run with LHC but there is no guarantee that they are supported after OS/BOINC updates.

Cosmology@Home is running with Virtualbox 5.2.44 only.
For me LHC@Home in Windows run also with 5.2.44, but also with 6.1.12 from Boinc-Mainpage. (Boinc 7.16.11).

IIRC, Cosmology@Home is also using Boot2Docker inside their VM's
Reviewing the GitHub page gives some insight as to why there might be issues under VBox 6.x. (such as the project was developed with 5.x VBox and deprecated before properly tested under VBox 6).
https://github.com/boot2docker/boot2docker

There is a Test for Docker with CentOS7 for Atlas.
This is in a very early Stage.

My intention was to avoid a discussion that is now about to start:
"My tasks run under VBox a.c.f"
"Mine need g.c.h"
"No, the best is still x.y.z"

As already mentioned it's clearly stated at the VBox page (meanwhile for half a year) that older versions are no longer supported.
Of course, older versions may still work fine but every OS update (Windows, Linux, ...) includes a risk that it doesn't work any more.

Nobody will force a volunteer to upgrade but nobody should expect that a project develops for outdated components as long as the official ones work fine for most participants.


Hence, it is not a nice behaviour to launch a new project now that forces already outdated software components.

BTW:
Although Cosmology@Home (which is not the new project mentioned above) seems to be dead since Dec 2020 they had computers performing fine with VBox 6.1.x, on Windows as well as on Linux.

My intention was to avoid a discussion that is now about to start:
"My tasks run under VBox a.c.f"
"Mine need g.c.h"
"No, the best is still x.y.z"

As already mentioned it's clearly stated at the VBox page (meanwhile for half a year) that older versions are no longer supported.
Of course, older versions may still work fine but every OS update (Windows, Linux, ...) includes a risk that it doesn't work any more.

Nobody will force a volunteer to upgrade but nobody should expect that a project develops for outdated components as long as the official ones work fine for most participants.


Hence, it is not a nice behaviour to launch a new project now that forces already outdated software components.

BTW:
Although Cosmology@Home (which is not the new project mentioned above) seems to be dead since Dec 2020 they had computers performing fine with VBox 6.1.x, on Windows as well as on Linux.

It's quite clear to me the new version is what should be used. Just because 5 works at LHC now doesn't mean it will in the future. Why would anybody write a new program requiring Boot2Docker when it's deprecated? Any project that can't keep up will simply not be run on my machines.

---

Although Cosmology@Home (which is not the new project mentioned above) seems to be dead since Dec 2020 they had computers performing fine with VBox 6.1.x, on Windows as well as on Linux.

In Windows 10pro Virtualbox 5.2.44

Hence, it is not a nice behaviour to launch a new project now that forces already outdated software components.

I can agree with that.

I can also see how this happened as when you search for Boinc2Docker (which uses Boot2Docker) you find a startup solution that will save a new project from reinventing the wheel, but it's not obvious that the work is based on, is now deprecated.

After the first 2 days of releasing this WU, and seeing the issues, Kryptos@Home recognized their mistake, apologized, and are planning on creating native apps.

I do not see intent to harm the user base here.
The project is also short term to solve a single cryptographic message and the solution might be found tomorrow or 6 months from now. I'm sure they do not want to sink thousands of hours of development time into something that might be done any day.


BTW, if you know of a more up-to-date, turnkey solution for new BOINC projects, let them know.
If you are developing a turnkey BOINC project product; here's your chance for a sale.