LHC@home

This feature is for Windows pcs (that are the absolute majority)

For me no problems so far.

I am suddenly having this same problem again. Failing to connect these same services.

How is this possible running 4 core CMS tasks hundreds of times?


I was just looking around to see how they are running here.

Do you have in Boincmanager -> Filetransfer for this Atlas-Tasks transfers which are open?

for this host, as can be seen, 5 ATLAS tasks are shown as being in process:
https://lhcathome.cern.ch/lhcathome/results.php?hostid=10815905

since yesterday, I have had a few tasks on different PCs which successfully produced a HITS file and were uploaded okay, but ended up with "confirmation error" ("Bestätigungsfehler") - example see here:
https://lhcathome.cern.ch/lhcathome/result.php?resultid=411294133

any idea what's behind this ?

If you use the suggested CVMFS configuration supplementary repositories are mounted automatically when an app requires them.

I got same invalid results for a bunch of my tasks too. (Example)

I think the real problem is this line:

> CVMFS is not available at /cvmfs/atlas-nightlies.cern.ch/repo/sw/logs/lastUpdate

atlas-nightlies.cern.ch is not in the configured sites, so it's not mounted. Do we need an update for our cvmfs config, or perhaps this is a batch of jobs not meant to send out to volunteers?

If you use the suggested CVMFS configuration supplementary repositories are mounted automatically when an app requires them.
The errors currently shown point out a misconfigured ATLAS batch rather than a local issue.

Permanently adding those supplementary repositories to the base configuration just wastes resources on the client, the server and along the whole network route.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
These long runners are really a problem and the project should avoid to send them to volunteers.
The problem is not only that they run that long, but they produce big upload files exceeding the
max_nbytes project setting of 2000000000 bytes (1.8626 GB) for the HITS-result file and BOINC will not upload that file.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

It seems that the 3800 event files are the ones that are failing with that error. The tasks have produced HITS files over 2 GB in size shown by your stderr.

Uploading a 1.12GB HITS-file from a 1950 events-task: LHC@home GQZKDmAlCP5nsSi4apGgGQJmABFKDmABFKDm4ySLDmFhIKDmAjaRan_0_r1821662343_ATLAS_hits 1172589,63 K