|
1)
Message boards :
ATLAS application :
ATLAS native - Configure CVMFS to work with openhtc.io
(Message 39286)
Posted 5 Jul 2019 by Mumps [MM] Post: Volunteers running ATLAS native and/or Theory native are kindly asked to update their local CVMFS configuration. I find a CVMFS_SERVER_URL in /etc/cvmfs/domain.d/cern.ch.conf. Would updating the one found there be appropriate? Or does it need to go in the .local file instead as indicated? And .local will override .conf, so we wouldn't need to remove the line from .conf, correct? Also, this is more important for users not using a local proxy server, correct? Also, has this been updated in the initial files indicated for a fresh install? So, things like the Ubuntu Repository files and the "master" copy of the default.local file downloaded from https://lhcathome.cern.ch/lhcathome/download/default.local |
|
2)
Message boards :
Theory Application :
Issues Native Theory application
(Message 38317)
Posted 19 Mar 2019 by Mumps [MM] Post: Or what is the oldest Ubuntu that it should work with, so I know if I should spend the time installing 16.04 or 18.04 LTS's. Thanks for the confirmation Jim1348. I think I'll give 18.04.2 a quick try, but at least I've installed 16.04 once or twice before so it's nice to know at least that will work. |
|
3)
Message boards :
Theory Application :
Issues Native Theory application
(Message 38312)
Posted 19 Mar 2019 by Mumps [MM] Post: /cvmfs/grid.cern.ch/vc/containers/runc: symbol lookup error: /cvmfs/grid.cern.ch/vc/containers/runc: undefined symbol: seccomp_version $ ldd -v /cvmfs/grid.cern.ch/vc/containers/runc
linux-vdso.so.1 => (0x00007fff8d12a000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007ff8e2cd8000)
libseccomp.so.2 => /usr/lib/x86_64-linux-gnu/libseccomp.so.2 (0x00007ff8e2ab8000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007ff8e28b0000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff8e24e0000)
/lib64/ld-linux-x86-64.so.2 (0x00007ff8e3860000)
Version information:
/cvmfs/grid.cern.ch/vc/containers/runc:
libdl.so.2 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libdl.so.2
libpthread.so.0 (GLIBC_2.3.2) => /lib/x86_64-linux-gnu/libpthread.so.0
libpthread.so.0 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libpthread.so.0
libc.so.6 (GLIBC_2.14) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.4) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6
/lib/x86_64-linux-gnu/libpthread.so.0:
ld-linux-x86-64.so.2 (GLIBC_2.2.5) => /lib64/ld-linux-x86-64.so.2
ld-linux-x86-64.so.2 (GLIBC_2.3) => /lib64/ld-linux-x86-64.so.2
ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => /lib64/ld-linux-x86-64.so.2
libc.so.6 (GLIBC_2.14) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.3.2) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_PRIVATE) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6
/usr/lib/x86_64-linux-gnu/libseccomp.so.2:
libc.so.6 (GLIBC_2.3.4) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6
/lib/x86_64-linux-gnu/libdl.so.2:
ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => /lib64/ld-linux-x86-64.so.2
libc.so.6 (GLIBC_PRIVATE) => /lib/x86_64-linux-gnu/libc.so.6
libc.so.6 (GLIBC_2.2.5) => /lib/x86_64-linux-gnu/libc.so.6
/lib/x86_64-linux-gnu/libc.so.6:
ld-linux-x86-64.so.2 (GLIBC_2.3) => /lib64/ld-linux-x86-64.so.2
ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => /lib64/ld-linux-x86-64.so.2I'll presume that 14.04 LTS doesn't fall under the category of "relatively recent kernel that supports rootless containers" :) But is 16.04 new enough, or should I go right to 18.04? |
|
4)
Message boards :
Theory Application :
Issues Native Theory application
(Message 38306)
Posted 19 Mar 2019 by Mumps [MM] Post: I have attempted to install the cvmfs software on one of my systems, but have been unsuccessful at getting it to work. I have managed to get it to the point the cvmfs_config probe is successful, but it looks like the runc instance offered up from grid.cern.ch requires a newer version of some components than seems to have been back-ported to Ubuntu 14.04. Can somebody confirm if it's expected to work under an Ubuntu 14.04 LTS Operating System? Or what is the oldest Ubuntu that it should work with, so I know if I should spend the time installing 16.04 or 18.04 LTS's. $ sudo cvmfs_config probe Probing /cvmfs/atlas.cern.ch... OK 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... OK $ https://lhcathome.cern.ch/lhcathome/result.php?resultid=219421137 <core_client_version>7.9.3</core_client_version> <![CDATA[ <message> process exited with code 195 (0xc3, -61)</message> <stderr_txt> 23:46:01 (3124): wrapper (7.15.26016): starting 23:46:01 (3124): wrapper (7.15.26016): starting 23:46:01 (3124): wrapper: running ../../projects/lhcathome.cern.ch_lhcathome/cranky-0.0.28 () 04:46:01 2019-03-19: cranky-0.0.28: [INFO] Detected TheoryN App 04:46:01 2019-03-19: cranky-0.0.28: [INFO] Checking CVMFS. 04:46:01 2019-03-19: cranky-0.0.28: [INFO] Checking runc. /cvmfs/grid.cern.ch/vc/containers/runc: symbol lookup error: /cvmfs/grid.cern.ch/vc/containers/runc: undefined symbol: seccomp_version 04:46:01 2019-03-19: cranky-0.0.28: [ERROR] 'runc -v' failed. 23:46:02 (3124): cranky exited; CPU time 0.020000 23:46:02 (3124): app exit status: 0xce 23:46:02 (3124): called boinc_finish(195) </stderr_txt> ]]> |
©2025 CERN