1) Message boards : Theory Application : Theory Task doing nothing (Message 42782)
Posted 17 hours ago by computezrmle
Post:
If it happens again you may consider a project reset to ensure you get a fresh theory vdi.
2) Message boards : ATLAS application : Squid proxies may need restart (Message 42780)
Posted 17 hours ago by computezrmle
Post:
This is also in regards to your post in the Theory thread:
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5431&postid=42775


You may first check your access.log and cache.log.
Do you notice error messages that correspond to your issues?

If no, squid is most likely running fine and the issues are caused by something else.

If yes, you should clear the cache and restart fresh.

You may also insert the following line in your squid.conf and do a "squid -k reconfigure".
shutdown_lifetime 3 seconds

This avoids the 60 seconds default delay when you shutdown/restart squid but I'm not 100% sure if changing this timeout requires a squid -k restart. At least Squid will be prepared for the next restart.
3) Message boards : Sixtrack Application : Internet access OK - project servers may be temporarily down. (Message 42771)
Posted 1 day ago by computezrmle
Post:
What can I do on my Windows Vista 32 bit that cannot be upgraded to 64 bit. It has worked since 2011 OK for LHC@Home?

I have Rosetta working OK, for a month but even if I turn all those Rosetta off I now have a totally completed LHC@Home that has been stuck with "Ready to report" for 3 days.

In the week before that I ran 1 Rosetta and I LHC@Home both working properly.and upgrading properly.

Nils Høimyr referred to a CalNet comment in his post:
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5441&postid=42767

That comment clearly states what to do:
"Legacy devices that have not received updates to support newer roots will also likely to be missing other essential security updates and support for standards required by the modern Internet. We strongly encourage decommissioning these devices if their software cannot be upgraded. Non-upgraded, legacy devices should never be exposed to the Internet and special mitigations should be applied to isolate them from neighbor systems."
4) Message boards : Number crunching : Peer certificate cannot be authenticated with given CA certificates (Message 42768)
Posted 1 day ago by computezrmle
Post:
Thanks Nils.


The outage can clearly bee seen in the mcplots graphics.




A: CA cert expired
B: Issue was solved

The figures also show that
- a couple of clients were not affected
- a couple of of users were able to solve it on their side
5) Message boards : Number crunching : Peer certificate cannot be authenticated with given CA certificates (Message 42734)
Posted 1 day ago by computezrmle
Post:
It most likely depends on how your ssl helper apps (openssl ...) deal with expired CA certificates.
In short:
Older ssl clients can't deal with it, newer clients can.

More info can be found here (link copied from the github BOINC forum):
https://www.agwa.name/blog/post/fixing_the_addtrust_root_expiration


Since yesterday the BOINC source tree for version 7.16 includes a ca-bundle.crt where expired certificates have been removed but this file has not (yet?) been included in the master branch.

You can either wait until a recent 7.16 BOINC packet will be available or download the recent ca-bundle.crt from the 7.16 branch:
https://github.com/BOINC/boinc/blob/client_release/7/7.16/curl/ca-bundle.crt


This should primarily work for BOINC.
Other packets, e.g. wget, might be configured to lookup CA certificates elsewhere.
6) Message boards : Number crunching : Peer certificate cannot be authenticated with given CA certificates (Message 42720)
Posted 3 days ago by computezrmle
Post:
I don't have ca-bundle.crt on my Windows 10 computer in BOINC directory. So where do root certificates come from in this case?

It's usually part of the BOINC package.
You may download the recent version from:
https://github.com/BOINC/boinc/blob/master/curl/ca-bundle.crt


What is wierd is that some ATLAS jobs uploaded the results to LHC but the job in BOINC still shows "Ready to report"...

Nothing weird.
Result uploads go to lhcathome-upload.cern.ch via HTTP.
Result reporting goes to lhcathome.cern.ch via HTTPS.
The latter requires the server certificate to be confirmed by the CA certificate chain.
7) Questions and Answers : Windows : Adding LHC@home currently not possible? (Message 42718)
Posted 3 days ago by computezrmle
Post:
I'm not 100% sure but it might be related to the issue caused by an expired CA certificate:
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5441

In your BOINC folder you may replace ca-bundle.crt with the most recent version from here:
https://github.com/BOINC/boinc/blob/master/curl/ca-bundle.crt
8) Message boards : Number crunching : Peer certificate cannot be authenticated with given CA certificates (Message 42704)
Posted 3 days ago by computezrmle
Post:
According to Sectigo's knowledge base (https://support.sectigo.com/Com_KnowledgeDetailPage?Id=kA03l00000117LT) there shouldn't be an issue if one of the following CA certs is available:
USERTrust RSA Certification Authority: https://crt.sh/?id=1199354
COMODO RSA Certification Authority: https://crt.sh/?id=1720081

Both certs have been issued 2010 and are already included in BOINC's ca-bundle.crt from 2018:
https://github.com/BOINC/boinc/blob/master/curl/ca-bundle.crt

Since BOINC uses curl to send out HTTP requests and curl needs access to the cerificate list it should be checked if for some reason there are remains from older installations (BOINC/curl) that point to outdated certificate lists.
9) Message boards : Number crunching : Peer certificate cannot be authenticated with given CA certificates (Message 42675)
Posted 3 days ago by computezrmle
Post:
You may check if your BOINC client uses the most recent CA certificates.
Locate the file ca-bundle.crt in your BOINC directory and check if the timestamp in line 4 is at least:
## Certificate data from Mozilla as of: Fri Jan 26 21:30:21 2018 GMT

If not ca-bundle.crt has to be replaced with a version from a recent BOINC client.

The file can also be downloaded from:
https://github.com/BOINC/boinc/blob/master/curl/ca-bundle.crt
10) Questions and Answers : Unix/Linux : How is virtualization support determined? (Message 42658)
Posted 5 days ago by computezrmle
Post:
Looks like Theory vbox runs fine.
Congrats!

Just one minor hint.
Your logfiles show that you throttled your CPU usage:
2020-05-28 23:50:02 (66501): Setting CPU throttle for VM. (75%)

This works fine if you run native apps.
If you run vbox apps a couple of processes rely on each other.
In addition longrunners might hit the runtime limit.

To avoid timeout problems CPU throttle should be set to 100%.
11) Message boards : Theory Application : Only errors running Pythia8 with version 8.301 (Message 42651)
Posted 6 days ago by computezrmle
Post:
https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=139064302
===> [runRivet] Mon May 25 06:50:33 UTC 2020 [boinc pp ue 7000 - - pythia8 8.301 dire-default 70000 4]
.
.
.
0 events processed
dumping histograms...
Rivet.Analysis.ATLAS_2010_S8894728: WARN  Need at least 3 bin entries and a non-zero central value to calculate an error on standard deviation profiles (bin 0)
Rivet.Analysis.ATLAS_2010_S8894728: WARN  Need at least 3 bin entries and a non-zero central value to calculate an error on standard deviation profiles (bin 1)
Rivet.Analysis.ATLAS_2010_S8894728: WARN  Need at least 3 bin entries and a non-zero central value to calculate an error on standard deviation profiles (bin 2)
Rivet.Analysis.ATLAS_2010_S8894728: WARN  Need at least 3 bin entries and a non-zero central value to calculate an error on standard deviation profiles (bin 3)
Rivet.Analysis.ATLAS_2010_S8894728: WARN  Need at least 3 bin entries and a non-zero central value to calculate an error on standard deviation profiles (bin 4)
Rivet.Analysis.ATLAS_2010_S8894728: WARN  Need at least 3 bin entries and a non-zero central value to calculate an error on standard deviation profiles (bin 5)
.
.
.
Rivet.Analysis.ATLAS_2010_S8894728: WARN  Need at least 3 bin entries and a non-zero central value to calculate an error on standard deviation profiles (bin 14)
Rivet.Analysis.ATLAS_2010_S8894728: WARN  Need at least 3 bin entries and a non-zero central value to calculate an error on standard deviation profiles (bin 15)
Rivet.Analysis.ATLAS_2010_S8894728: WARN  Need at least 3 bin entries and a non-zero central value to calculate an error on standard deviation profiles (bin 16)
R

No new logfile entry since Mon May 25 06:55 UTC
12) Message boards : ATLAS application : Validate error on all tasks, and short run time with 1 core only (Message 42645)
Posted 6 days ago by computezrmle
Post:
... until someone tells me what's happened.

Just look around and read other posts.
The answer might already be there:
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5438&postid=42630
13) Message boards : Sixtrack Application : please, remove non-optimized application SixTrack for 32 bit systems (Message 42643)
Posted 6 days ago by computezrmle
Post:
You may insert the following line in the <options> section of your "cc_config.xml":
<no_alt_platform>1</no_alt_platform>

Then reload the client configuration.

See:
https://boinc.berkeley.edu/wiki/Client_configuration
14) Questions and Answers : Unix/Linux : How is virtualization support determined? (Message 42635)
Posted 6 days ago by computezrmle
Post:
You may at first sort out problems that are caused by the interface FreeBSD <-> VirtualBox.
Hence you may create your own VM and run linux as guest.
Check if internet access is possible from that guest.

It makes no sense to run a VM from LHC as long as basic problems are not sorted out.
15) Message boards : Theory Application : Theory Task doing nothing (Message 42622)
Posted 7 days ago by computezrmle
Post:
It's usually a minor problem to run many tasks concurrently but it can become a problem if they change their status.
This happens if you start/restart your BOINC client or even at shutdown when lots of data has to be saved to disk.
Modern computers with lots of cores are more affected as they run more tasks concurrently.

Nobody can really tell what's the best combination on your computer. You'll have to try it out.
16) Message boards : Theory Application : Theory Task doing nothing (Message 42620)
Posted 7 days ago by computezrmle
Post:
Indeed.
Starting, pausing and restarting too many vbox tasks concurrently can result in an overloaded disk IO.
You may try to limit at least the number of concurrent ATLAS starts as each of them copies a few GB.
17) Message boards : ATLAS application : three 1-core tasks possible with 16GB RAM? (Message 42607)
Posted 10 days ago by computezrmle
Post:
... the same old server bug. I don't understand that it can't be fixed.

I agree.
Very old, very nasty and it has been reported very often, e.g. by Erich.
18) Message boards : ATLAS application : three 1-core tasks possible with 16GB RAM? (Message 42606)
Posted 10 days ago by computezrmle
Post:
The project server calculates 2 memory values, both based on the well known RAM formula.


memory_size_mb is used when a fresh VM is initialized.
This value can be modified using an app_config.xml

rsc_memory_bound is used by the BOINC client to decide if there's enough free RAM to start a task.
This value can't be modified by the client.


If at your web preferences #cores (per task) is set to unlimited or a high value and you run a 1-core setup it may result in a situation where the BOINC client thinks too much RAM is already in use.
19) Message boards : Theory Application : High Memory usage? (Message 42601)
Posted 10 days ago by computezrmle
Post:
22:43:04 EDT -04:00 2020-05-22: cranky-0.0.32: [INFO] ===> [runRivet] Sat May 23 02:43:02 UTC 2020 [boinc ppbar zinclusive 1800 -,-,50,130 - madgraph5amc 2.6.6.atlas nlo2jet 100000 12]

Looks like it has been the same event generator (madgraph5amc) that caused the trouble here:
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5323
20) Message boards : Theory Application : Tasks run 4 days and finish with error (Message 42583)
Posted 11 days ago by computezrmle
Post:
Just change your view.
Scientists define thousands of parameter sets that they want to be simulated.
At that time they don't know how the tasks generated from that parameter sets behave.
Most of the tasks deliver valuable results.
A few don't and scientists check if the successful tasks answer their questions.
If not they will investigate why and modify the parameters or applications and generate new parameter sets.


Next 20


©2020 CERN