1)
Message boards :
Theory Application :
New native version v300.08
(Message 49146)
Posted 6 Jan 2024 by Aurum Post: Will I still be able to run native ATLAS with this new 300.08 Theory configuration? |
2)
Message boards :
Theory Application :
New native version v300.08
(Message 49139)
Posted 5 Jan 2024 by Aurum Post: undo all changes made for the old method (especially: reenable cgroups v2) How do we do this? Detach LHC and then add it back for a fresh start? |
3)
Message boards :
Theory Application :
New native version v300.08
(Message 49138)
Posted 5 Jan 2024 by Aurum Post: Computers with the old setup still run 300.08 but Linux Mint computers that have newly added LHC will not run Theory using this new method. |
4)
Message boards :
Theory Application :
New native version v300.08
(Message 49136)
Posted 5 Jan 2024 by Aurum Post: Tried on both Linux Mint 20.3 (Ubuntu 20.04) and 21.2 (Ubuntu 22.04). I guess I can't run Theory any more until sudo 1.9.10 gets added to the Ubuntu repository. Found Sudo-Version 1.9.9. This sudo version is lower than 1.9.10. It does not support regular expressions. Hence, sudoers will not be modified. Error running /tmp/prepare_theory_native_environment |
5)
Message boards :
ATLAS application :
Probing /cvmfs/atlas.cern.ch... Failed!
(Message 48806)
Posted 23 Oct 2023 by Aurum Post: /etc/cvmfs/default.local (to be used without a local proxy): # set quota limit between 4000 and 10000 CVMFS_QUOTA_LIMIT=6000 This already appears in my default.conf file as: # 4GB soft limit for the files in CVMFS_CACHE_BASE CVMFS_QUOTA_LIMIT=4000 Should it be in both files or just one and should the values be the same? Also, should this be the only line? /etc/cvmfs/config.d/cvmfs-config.cern.ch.local # usually this is the only option that should be set in this file CVMFS_CONFIG_REPO_REQUIRED=no Mine currently is this and it passed probe: # In order to bootstrap the network connection, we use a DIRECT proxy # for the config repository only if no other proxy has been set. # CVMFS_HTTP_PROXY="${CVMFS_HTTP_PROXY:=DIRECT}" # Usually this is the only option that should be set in this file CVMFS_CONFIG_REPO_REQUIRED=no |
6)
Message boards :
Sixtrack Application :
XBoinc
(Message 48802)
Posted 22 Oct 2023 by Aurum Post: Watched the workshop video and it sounds good. Looking forward to running them. How will it work when it's ready for BOINC crunchers? Will there be a new option to select on Preferences and then we'll get the new executable and its WUs? I suspect the link to github is for internal CERN users and not for us BOINC civilians. |
7)
Message boards :
ATLAS application :
Probing /cvmfs/atlas.cern.ch... Failed!
(Message 48801)
Posted 22 Oct 2023 by Aurum Post: I have one computer that fails the atlas probe. I've deleted all cvmfs and reinstalled it several times. My other computers continue to run atlas fine. Can anyone see what's wrong? Linux Mint 20.3 Ubuntu 20.04: aurum@Rig-05:~$ cvmfs_config probe Probing /cvmfs/atlas.cern.ch... Failed! Probing /cvmfs/atlas-condb.cern.ch... OK Probing /cvmfs/grid.cern.ch... OK Probing /cvmfs/cernvm-prod.cern.ch... OK Probing /cvmfs/sft.cern.ch... Failed! Probing /cvmfs/alice.cern.ch... OK aurum@Rig-05:~$ sudo cvmfs_config showconfig -s atlas.cern.ch && systemctl status autofs.service CVMFS_REPOSITORY_NAME=atlas.cern.ch CVMFS_BACKOFF_INIT=2 # from /etc/cvmfs/default.conf CVMFS_BACKOFF_MAX=10 # from /etc/cvmfs/default.conf CVMFS_BASE_ENV=1 # from /etc/cvmfs/default.conf CVMFS_CACHE_BASE=/var/lib/cvmfs # from /etc/cvmfs/default.conf CVMFS_CACHE_DIR=/var/lib/cvmfs/shared CVMFS_CHECK_PERMISSIONS=yes # from /etc/cvmfs/default.conf CVMFS_CLAIM_OWNERSHIP=yes # from /etc/cvmfs/default.conf CVMFS_CLIENT_PROFILE=single # from /etc/cvmfs/default.conf CVMFS_CONFIG_REPOSITORY=cvmfs-config.cern.ch # from /etc/cvmfs/default.d/50-cern-debian.conf CVMFS_DEFAULT_DOMAIN=cern.ch # from /etc/cvmfs/default.d/50-cern-debian.conf CVMFS_HOST_RESET_AFTER=1800 # from /etc/cvmfs/default.conf CVMFS_HTTP_PROXY='auto;DIRECT' # from /etc/cvmfs/default.local CVMFS_KCACHE_TIMEOUT=2 # from /etc/cvmfs/default.local CVMFS_KEYS_DIR=/etc/cvmfs/keys/cern.ch # from /etc/cvmfs/domain.d/cern.ch.conf CVMFS_LOW_SPEED_LIMIT=1024 # from /etc/cvmfs/default.conf CVMFS_MAX_RETRIES=3 # from /etc/cvmfs/default.local CVMFS_MOUNT_DIR=/cvmfs # from /etc/cvmfs/default.conf CVMFS_NFILES=131072 # from /etc/cvmfs/default.conf CVMFS_PROXY_RESET_AFTER=300 # from /etc/cvmfs/default.conf CVMFS_QUOTA_LIMIT=4000 # from /etc/cvmfs/default.conf CVMFS_RELOAD_SOCKETS=/var/run/cvmfs # from /etc/cvmfs/default.conf CVMFS_REPOSITORIES=atlas,atlas-condb,grid,cernvm-prod,sft,alice # from /etc/cvmfs/default.local CVMFS_SEND_INFO_HEADER=no # from /etc/cvmfs/default.conf CVMFS_SERVER_URL='http://s1cern-cvmfs.openhtc.io/cvmfs/atlas.cern.ch;http://s1ral-cvmfs.openhtc.io/cvmfs/atlas.cern.ch;http://s1bnl-cvmfs.openhtc.io/cvmfs/atlas.cern.ch;http://s1fnal-cvmfs.openhtc.io/cvmfs/atlas.cern.ch' # from /etc/cvmfs/domain.d/cern.ch.conf CVMFS_SHARED_CACHE=yes # from /etc/cvmfs/default.conf CVMFS_STRICT_MOUNT=no # from /etc/cvmfs/default.conf CVMFS_TIMEOUT=5 # from /etc/cvmfs/default.conf CVMFS_TIMEOUT_DIRECT=10 # from /etc/cvmfs/default.conf CVMFS_USE_CDN=yes # from /etc/cvmfs/default.local CVMFS_USE_GEOAPI=yes # from /etc/cvmfs/domain.d/cern.ch.conf CVMFS_USER=cvmfs # from /etc/cvmfs/default.conf aurum@Rig-05:~$ sudo cvmfs_config chksetup Warning: failed to resolve auto proxy for http://s1cern-cvmfs.openhtc.io/cvmfs/atlas.cern.ch/.cvmfspublished etc... |
8)
Message boards :
Theory Application :
How long may Native-Theory-Tasks run
(Message 48579)
Posted 19 Sep 2023 by Aurum Post: It is a bug, a thoughtless inconsiderate bug that could fixed. Patience would be idiotic and wasteful. You clearly did not understand my comments about wasting expensive electricity. |
9)
Message boards :
Theory Application :
Theory Failure Ratio Explodes
(Message 48578)
Posted 19 Sep 2023 by Aurum Post: There was an update to the new version of scientific software yesterday. Can't you remove the defective WUs from the work server queue or must they all fail several times each? |
10)
Message boards :
Theory Application :
How long may Native-Theory-Tasks run
(Message 48576)
Posted 19 Sep 2023 by Aurum Post: Thanks for that explanation. That's a lot of work to expect from a BOINC user to decide if the WU will ever finish.Theory native logs can be checked, e.g for a task running in slot 0 The problem is that I have many where the progress is being reported as over 98% and looking at the end the WU's runRivet.log it says it's completed 63000 out of 100000 events. That should display to us 63% progress and not 98.563%. If progress was reported accurately then folks would let the task s run. But when they see it seem to stall at over 98% for many hours they assume something is wrong and abort the WU. Hopefully CERN will fix this progress reporting bug soon. Expect many aborted tasks in the meantime. The other problem is that these Theory tasks don't checkpoint. I for one am on Time-of-Use electric service and my electric rate increases 10x during peak hours. If I can't suspend and resume from a checkpoint the task will get aborted when I do a daily TOU shutdown. |
11)
Message boards :
Team invites :
Team creation banned by LHC
(Message 47405)
Posted 21 Oct 2022 by Aurum Post: And I just told you I'm not a stupid fool who is going to advertise my email address on a public spam list. It's a shame CERN wants us to donate our money but they're too lazy to implement a trivial fix. |
12)
Message boards :
ATLAS application :
Is ATLAS limited to to 4 WUs per computer?
(Message 47404)
Posted 21 Oct 2022 by Aurum Post: For Windows you need an app_config.xml.The work server has no idea what's in your app_config.xml file. Or has that changed? BTW, I only run Linux. |
13)
Message boards :
ATLAS application :
Is ATLAS limited to to 4 WUs per computer?
(Message 47403)
Posted 21 Oct 2022 by Aurum Post: What is your setting for Max # CPUs?Like I said, one CPU per WU. Or as Preferences phrases it, "Max # of CPUs for this project" = 1. |
14)
Message boards :
CMS Application :
Is there a Native version in the pipeline?
(Message 47400)
Posted 21 Oct 2022 by Aurum Post: Catch-22: You'll never get a lot of users until you have a native app for Linux.That's it, straight question. Is there a native version in development/under consideration/even possible for CMS? I will never install VirtualBox for any reason. Tried that and it's nothing but trouble. |
15)
Message boards :
Team invites :
Team creation banned by LHC
(Message 47398)
Posted 21 Oct 2022 by Aurum Post: I'd invite you to join our team but LHC bans the creation of new teams. I saw some message about an obsolete all BOINC projects team creation but that requires one to post their email address to a public spam list. One would be insane to do that. I wonder why it's such a bother for LHC to allow team creation? |
16)
Message boards :
ATLAS application :
Is ATLAS limited to to 4 WUs per computer?
(Message 47397)
Posted 21 Oct 2022 by Aurum Post: I used to be able to run many ATLAS WUs per computer but now I can only get 4 WUs to DL per computer. I have plenty of memory and can get a full complement of Theory WUs. I run one CPU per WU. I've tried setting Preferences to ATLAS only and limit to 8 WUs or No Limit but the most I ever get is 4 WUs. Is it something I did or did LHC impose this limit? |
17)
Message boards :
ATLAS application :
Native Atlas Guide
(Message 47396)
Posted 21 Oct 2022 by Aurum Post: Does anyone have an up-to-date guide at all? I tried following this one https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4840 but kept getting errors, when I try and run the tasks they fail with a computational error.After some trial 'n error this is what works for me for native ATLAS & Theory apps running Linux Mint 20.3: sudo apt install runc sudo apt install docker.io -y sudo docker pull cvmfs/service wget https://ecsft.cern.ch/dist/cvmfs/cvmfs-release/cvmfs-release-latest_all.deb sudo dpkg -i cvmfs-release-latest_all.deb rm -f cvmfs-release-latest_all.deb sudo apt-get update sudo apt-get install cvmfs -y sudo wget https://lhcathome.cern.ch/lhcathome/download/default.local -O /etc/cvmfs/default.local Open /etc/cvmfs/ as root: In /etc/cvmfs/default.local add "single": ------------------------------------------------------ start of default.conf ------------------------------------------------ CVMFS_CLIENT_PROFILE=single ------------------------------------------------------ end of default.conf ------------------------------------------------ Edit /etc/cvmfs/default.local to this: ------------------------------------------------------ start of default.local ------------------------------------------------ # Must be set: the repositories required for ATLAS/Theory # If "CVMFS_DEFAULT_DOMAIN" is set to "cern.ch" like in /etc/cvmfs/default.d/50-cern.conf simple names will expand to FQRNs, e.g. atlas -> atlas.cern.ch CVMFS_REPOSITORIES="atlas,atlas-condb,grid,cernvm-prod,sft,alice" # Must be set to ensure openhtc.io is used: CVMFS_USE_CDN=yes CVMFS_HTTP_PROXY="auto;DIRECT" # Additional options CVMFS_KCACHE_TIMEOUT=2 CVMFS_MAX_RETRIES=3 ------------------------------------------------------ end of default.local ------------------------------------------------ sudo cvmfs_config setup sudo cvmfs_config reload (May not be needed but it doesn't hurt.) cvmfs_config probe If the probe fails, try to restart autofs with: sudo systemctl restart autofs |
18)
Message boards :
Sixtrack Application :
Team creation disabled
(Message 47276)
Posted 21 Sep 2022 by Aurum Post: This page explains what to do if you want to create a new BOINC-wide team: It's sad that LHC won't allow new teams. I have no need of a BOINC-wide team. |
19)
Message boards :
ATLAS application :
Best number of cores on a 16 core machine to use for ATLAS
(Message 44860)
Posted 2 May 2021 by Aurum Post: what is the best use for a single task?One. |
20)
Message boards :
ATLAS application :
Ubuntu 20.04 support?
(Message 44819)
Posted 25 Apr 2021 by Aurum Post: I have go version 1.15.2, which works fine.You read mind, I was wondering which Go version you used. I've tried Go 1.16.3, 1.14.15 and 1.14.1. None of them worked. I also downgraded Singularity from 3.7.3 to 3.6.4 that you used. Still fails. And all this time wasted just because a muon did a dance. The release notes indicate that Singularity has been upgraded to fix security issues. It's a shame that CERN is so far behind. Maybe he can figure out how to uninstall one version and get another."If you anticipate needing to remove Singularity, it might be easier to install it in a custom directory using the --prefix option to mconfig. In that case Singularity can be uninstalled simply by deleting the parent directory." https://sylabs.io/guides/3.7/admin-guide/installation.html#remove-an-old-version I just deleted my Singularity folder although in rereading the Sylabs instructions that may not have been sufficient. My notes show last year's installation used the --prefix option: sudo mkdir /usr/local/bin/singularity ; / cd /usr/local/bin/singularity ; / sudo wget https://github.com/hpcng/singularity/releases/tag/v3.7.3/singularity-3.7.3.tar.gz ; / tar xvf singularity-3.7.3.tar.gz ; / sudo apt install libarchive-dev ; / ./configure --prefix=/usr/local ; / make ; / sudo make installThis year's instructions say: cd /usr/local/bin export VERSION=3.6.4 && # adjust this as necessary \ sudo wget https://github.com/hpcng/singularity/releases/download/v${VERSION}/singularity-${VERSION}.tar.gz && \ sudo tar -xzf singularity-${VERSION}.tar.gz cd /usr/local/bin/singularity sudo -s ./mconfig && \ make -C builddir && \ make -C builddir installI added cd /usr/local/bin so it wasn't installed in my Home directory as the CERN instructions specify. I would be willing to try a fresh install on a new-build computer that has never been tainted by an LHC@home attachment. But the ambiguity and contradictions have overwhelmed me. https://lhcathome.cern.ch/lhcathome/result.php?resultid=315423475 |
©2024 CERN