Message boards :
Theory Application :
Probing /cvmfs/sft.cern.ch... Failed!
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 18 Dec 15 Posts: 1821 Credit: 118,941,347 RAC: 21,472   
|
I remember that on one my PCs on which I tried to crunch Theory long time ago, it did not work (whereas ATLAS and CMS work fine). So, this morning I updated BOINC to the latest version 7.16.11, and the Virtual Box to latest version 6.1.18 (incl. extension pack). However, Theory tasks still fail after some 4 minutes. Excerpt from sderr: 2021-03-31 15:45:54 (3944): Guest Log: 15:45:52 CEST +02:00 2021-03-31: cranky: [INFO] Checking CVMFS. 2021-03-31 15:46:17 (3944): Guest Log: Probing /cvmfs/sft.cern.ch... Failed! 2021-03-31 15:46:17 (3944): Guest Log: 15:46:15 CEST +02:00 2021-03-31: cranky: [ERROR] 'cvmfs_config probe sft.cern.ch' failed. the complete sderr can be seen here: https://lhcathome.cern.ch/lhcathome/result.php?resultid=307705404 Anyone any idea why Theory tasks cannot be crunched on this machine? |
|
Send message Joined: 2 May 07 Posts: 2244 Credit: 173,902,375 RAC: 456
|
When you ping the failed Server cvmfs_config probe sft.cern.ch do you get a good response? |
|
Send message Joined: 18 Dec 15 Posts: 1821 Credit: 118,941,347 RAC: 21,472
|
When you ping the failed Server cvmfs_config probe sft.cern.chpings says: "Ping-Anforderung konnte Host "cvmfs_config" nicht finden. Überprüfen Sie den Namen, und versuchen Sie es erneut" |
|
Send message Joined: 18 Dec 15 Posts: 1821 Credit: 118,941,347 RAC: 21,472
|
however, I now tried this ping query on another machine which does crunch Theory without problems.When you ping the failed Server cvmfs_config probe sft.cern.chpings says: "Ping-Anforderung konnte Host "cvmfs_config" nicht finden. Überprüfen Sie den Namen, und versuchen Sie es erneut" And interestingly enough, the ping result is excactly the same: ... could not find |
 Send message Joined: 15 Jun 08 Posts: 2541 Credit: 254,608,838 RAC: 34,609 |
sft.cern.ch is not a hostname. Instead it's a repository name that never responds to a ping. |
 Magic Quantum Mechanic Send message Joined: 24 Oct 04 Posts: 1176 Credit: 54,887,670 RAC: 5,761  
|
I updated this pc to that new version of VB and I got that same [ERROR] 'cvmfs_config probe sft.cern.ch' failed. This was with a v5.21 Theory over at -dev I didn't try it again and just went back to running Sixtracks |
|
Send message Joined: 18 Dec 15 Posts: 1821 Credit: 118,941,347 RAC: 21,472
|
I updated this pc to that new version of VB and I got that same [ERROR] 'cvmfs_config probe sft.cern.ch' failed.Here, with the old VB version 6.1.0 I had the same problem.as with version 6.1.18 now. Maybe this is not a software problem, but rather a hardware problem. |
 Send message Joined: 9 May 10 Posts: 14 Credit: 3,104,500 RAC: 0 
|
Same problem. Similar config. Any resolution? 
|
|
Send message Joined: 15 Jun 08 Posts: 2541 Credit: 254,608,838 RAC: 34,609 |
Your task lists don't show a Theory task except an old one from 2019. Part of your problem might be that you ask for ATLAS native. Each ATLAS task downloads an EVNT file of up to 420 MB but all of them fail after a few minutes since you didn't install a local CVMFS client: [2021-04-26 20:32:27] Checking for CVMFS [2021-04-26 20:32:27] No cvmfs_config command found, will try listing directly [2021-04-26 20:32:27] ls: cannot access '/cvmfs/atlas.cern.ch/repo/sw': No such file or directory [2021-04-26 20:32:27] Failed to list /cvmfs/atlas.cern.ch/repo/sw You also ask for beta apps (ATLAS native long). Why? This makes no sense as long as you do not even get the normal ones running. |
|
Send message Joined: 23 Jul 05 Posts: 53 Credit: 2,707,793 RAC: 0
|
Your task lists don't show a Theory task except an old one from 2019. Could you point us to the pinned message about how to install a cvmfs client maybe ? I think that since it's named native, people think as I would have done, that it's just download and run... |
|
Send message Joined: 15 Jun 08 Posts: 2541 Credit: 254,608,838 RAC: 34,609 |
There are lots of posts around CVMFS. Some basic information can be found here: https://cvmfs.readthedocs.io/en/stable/ https://cernvm.cern.ch/fs/ https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4840&postid=36880 Additional information can be found here (mostly required): https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5594 https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5473 Beside that this message board has a search function: https://lhcathome.cern.ch/lhcathome/forum_search.php |
|
Send message Joined: 23 Jul 05 Posts: 53 Credit: 2,707,793 RAC: 0
|
those thread are outdated for some parts. the repositories in particular are not working and the wsl2 from the doc is not working either. for the repo root@ubucern:~# cvmfs_config chksetup Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.cern.ch:8000/cvmfs/atlas.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cernvmfs.gridpp.rl.ac.uk:8000/cvmfs/atlas.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1bnl.opensciencegrid.org:8000/cvmfs/atlas.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1fnal.opensciencegrid.org:8000/cvmfs/atlas.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/atlas.cern.ch/.cvmfspublished Warning: failed to access http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/atlas.cern.ch/.cvmfspublished through proxy DIRECT Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.ihep.ac.cn:8000/cvmfs/atlas.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.cern.ch:8000/cvmfs/atlas-condb.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cernvmfs.gridpp.rl.ac.uk:8000/cvmfs/atlas-condb.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1bnl.opensciencegrid.org:8000/cvmfs/atlas-condb.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1fnal.opensciencegrid.org:8000/cvmfs/atlas-condb.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/atlas-condb.cern.ch/.cvmfspublished Warning: failed to access http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/atlas-condb.cern.ch/.cvmfspublished through proxy DIRECT Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.ihep.ac.cn:8000/cvmfs/atlas-condb.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.cern.ch:8000/cvmfs/lhcb.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cernvmfs.gridpp.rl.ac.uk:8000/cvmfs/lhcb.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1bnl.opensciencegrid.org:8000/cvmfs/lhcb.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1fnal.opensciencegrid.org:8000/cvmfs/lhcb.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/lhcb.cern.ch/.cvmfspublished Warning: failed to access http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/lhcb.cern.ch/.cvmfspublished through proxy DIRECT Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.ihep.ac.cn:8000/cvmfs/lhcb.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.cern.ch:8000/cvmfs/alice.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cernvmfs.gridpp.rl.ac.uk:8000/cvmfs/alice.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1bnl.opensciencegrid.org:8000/cvmfs/alice.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1fnal.opensciencegrid.org:8000/cvmfs/alice.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/alice.cern.ch/.cvmfspublished Warning: failed to access http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/alice.cern.ch/.cvmfspublished through proxy DIRECT Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.ihep.ac.cn:8000/cvmfs/alice.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.cern.ch:8000/cvmfs/alice-ocdb.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cernvmfs.gridpp.rl.ac.uk:8000/cvmfs/alice-ocdb.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1bnl.opensciencegrid.org:8000/cvmfs/alice-ocdb.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1fnal.opensciencegrid.org:8000/cvmfs/alice-ocdb.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/alice-ocdb.cern.ch/.cvmfspublished Warning: failed to access http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/alice-ocdb.cern.ch/.cvmfspublished through proxy DIRECT Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.ihep.ac.cn:8000/cvmfs/alice-ocdb.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.cern.ch:8000/cvmfs/grid.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cernvmfs.gridpp.rl.ac.uk:8000/cvmfs/grid.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1bnl.opensciencegrid.org:8000/cvmfs/grid.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1fnal.opensciencegrid.org:8000/cvmfs/grid.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/grid.cern.ch/.cvmfspublished Warning: failed to access http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/grid.cern.ch/.cvmfspublished through proxy DIRECT Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.ihep.ac.cn:8000/cvmfs/grid.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.cern.ch:8000/cvmfs/cms.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cernvmfs.gridpp.rl.ac.uk:8000/cvmfs/cms.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1bnl.opensciencegrid.org:8000/cvmfs/cms.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1fnal.opensciencegrid.org:8000/cvmfs/cms.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/cms.cern.ch/.cvmfspublished Warning: failed to access http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/cms.cern.ch/.cvmfspublished through proxy DIRECT Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.ihep.ac.cn:8000/cvmfs/cms.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.cern.ch:8000/cvmfs/sft.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cernvmfs.gridpp.rl.ac.uk:8000/cvmfs/sft.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1bnl.opensciencegrid.org:8000/cvmfs/sft.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1fnal.opensciencegrid.org:8000/cvmfs/sft.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/sft.cern.ch/.cvmfspublished Warning: failed to access http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/sft.cern.ch/.cvmfspublished through proxy DIRECT Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.ihep.ac.cn:8000/cvmfs/sft.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.cern.ch:8000/cvmfs/geant4.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cernvmfs.gridpp.rl.ac.uk:8000/cvmfs/geant4.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1bnl.opensciencegrid.org:8000/cvmfs/geant4.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1fnal.opensciencegrid.org:8000/cvmfs/geant4.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/geant4.cern.ch/.cvmfspublished Warning: failed to access http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/geant4.cern.ch/.cvmfspublished through proxy DIRECT Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.ihep.ac.cn:8000/cvmfs/geant4.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.cern.ch:8000/cvmfs/na61.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cernvmfs.gridpp.rl.ac.uk:8000/cvmfs/na61.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1bnl.opensciencegrid.org:8000/cvmfs/na61.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1fnal.opensciencegrid.org:8000/cvmfs/na61.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/na61.cern.ch/.cvmfspublished Warning: failed to access http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/na61.cern.ch/.cvmfspublished through proxy DIRECT Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.ihep.ac.cn:8000/cvmfs/na61.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.cern.ch:8000/cvmfs/boss.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cernvmfs.gridpp.rl.ac.uk:8000/cvmfs/boss.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1bnl.opensciencegrid.org:8000/cvmfs/boss.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1fnal.opensciencegrid.org:8000/cvmfs/boss.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/boss.cern.ch/.cvmfspublished Warning: failed to access http://cvmfsrep.grid.sinica.edu.tw:8000/cvmfs/boss.cern.ch/.cvmfspublished through proxy DIRECT Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.ihep.ac.cn:8000/cvmfs/boss.cern.ch/.cvmfspublished and for the wsl part the probing is failing + the repo same problem $ cvmfs_config probe Probing /cvmfs/atlas.cern.ch... Failed! Probing /cvmfs/atlas-condb.cern.ch... Failed! Probing /cvmfs/lhcb.cern.ch... Failed! Probing /cvmfs/alice.cern.ch... Failed! Probing /cvmfs/alice-ocdb.cern.ch... Failed! Probing /cvmfs/grid.cern.ch... Failed! Probing /cvmfs/cms.cern.ch... Failed! Probing /cvmfs/sft.cern.ch... Failed! Probing /cvmfs/geant4.cern.ch... Failed! Probing /cvmfs/na61.cern.ch... Failed! Probing /cvmfs/boss.cern.ch... Failed! and indeed i tried to reach those repo and I got a 404 error. It's not a network problem I've tried from different location |
|
Send message Joined: 23 Jul 05 Posts: 53 Credit: 2,707,793 RAC: 0
|
and also The cvmfs according to the task failing are configured okey but it can't extract files apparently : root filesystem extraction failed: could not extract squashfs data, unsquashfs not found from a real VM ubuntu 20.04.2 any ideas about that? and your: CVMFS_REPOSITORIES="atlas,atlas-condb,grid,cernvm-prod,sft,alice" from your post : https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5594 is not accurated. Apparently it really needs hardcoded domain and not simple variable. At least the chkconfig is complaining about it. still on a a real VM ubuntu and also in wsl I will make an update thread on how to do things later when I finished debug this. |
|
Send message Joined: 23 Jul 05 Posts: 53 Credit: 2,707,793 RAC: 0
|
and also The cvmfs according to the task failing are configured okey okey so resolved the squashfs problem with https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=5611 which I didn't get in my previous search and I don't why it didn't got installed as a requirement but okey. The tasks are loading now, I had a problem with /var/lib/alternatives that was not created and so apparently the "container" couldn't create it because of permissions so I've created it for him. Now there is a task loading but not crunching apparently and I don't know why for the moment so I'm waiting for it to fail so that I know what is wrong with it. |
|
Send message Joined: 23 Jul 05 Posts: 53 Credit: 2,707,793 RAC: 0
|
and also The cvmfs according to the task failing are configured okey now it's the turn of /var/lib/condor, same problem so I did the same thing, will see for the next task. Are there a lot of directories like that ? Seems not normal that boinc user that have been created automatically by the script from apt can't created what it needs.... And it seems to be happening again. Beginning to even know in advance if the atlas.sh is going down or not... This is getting old by the minute. |
|
Send message Joined: 23 Jul 05 Posts: 53 Credit: 2,707,793 RAC: 0
|
okey so for recap for those who like me have been created your VM through a script or to a vm platform like cockpit or even azure or others you are ending up short on folders. So you need to create alternatives condor cs games gssproxy initramfs machines ntp package-list rpcbind rpm-state texmf tpm
[2021-05-28 08:11:34] FATAL: container creation failed: mount /cvmfs/atlas.cern.ch/repo/containers/sw/singularity/x86_64-el7/3.7.3/var/singularity/mnt/session/rootfs/var/lib/package-list->/cvmfs/atlas.cern.ch/repo/containers/sw/singularity/x86_64-el7/3.7.3/var/singularity/mnt/session/underlay/var/lib/package-list error: while mounting /cvmfs/atlas.cern.ch/repo/containers/sw/singularity/x86_64-el7/3.7.3/var/singularity/mnt/session/rootfs/var/lib/package-list: destination /cvmfs/atlas.cern.ch/repo/containers/sw/singularity/x86_64-el7/3.7.3/var/singularity/mnt/session/underlay/var/lib/package-list doesn't exist in container but that's in the cern filesystem itself that nobody should touch since it's handled automatically or "should be" handled automatically ... So what's the solutio nto that if there is even one? |
|
Send message Joined: 15 Jun 08 Posts: 2541 Credit: 254,608,838 RAC: 34,609 |
You may stop requesting any work from the project until a couple of issues are solved. Issue 1: Misconfigured CVMFS [2021-05-28 08:27:11] Probing /cvmfs/lhcb.cern.ch... OK . . . [2021-05-28 08:27:17] Probing /cvmfs/cms.cern.ch... OK . . . [2021-05-28 08:27:20] Probing /cvmfs/geant4.cern.ch... OK [2021-05-28 08:27:21] Probing /cvmfs/na61.cern.ch... OK [2021-05-28 08:27:22] Probing /cvmfs/boss.cern.ch... OK You don't need those repos but configured them. Your settings cause unnecessary internet traffic, delays and misleading error messages like this: Warning: failed to resolve auto proxy for http://cvmfs-stratum-one.cern.ch:8000/cvmfs/atlas.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cernvmfs.gridpp.rl.ac.uk:8000/cvmfs/atlas.cern.ch/.cvmfspublished Warning: failed to resolve auto proxy for http://cvmfs-s1bnl.opensciencegrid.org:8000/cvmfs/atlas.cern.ch/.cvmfspublished You configured CVMFS to use stratum-1-servers instead of openhtc.io. [2021-05-28 08:27:22] 2.8.1.0 33853 0 24628 85431 3 1 533104 4096001 0 130560 0 0 100.000 0 0 http://cernvmfs.gridpp.rl.ac.uk:8000/cvmfs/atlas.cern.ch DIRECT 1 Looks like you didn't follow all recommended CVMFS configuration steps. CVMFS is a read only filesystem. The only folders that really exist on your local computer are /etc/cvmfs/..., the CVMFS cache and /cvmfs which is used as mountpoint. All folders below /cvmfs are virtual folders which are accessed via the fuse automounter. Many of your comments point out that you didn't understand that. Issue 2: Singularity The project team distributes singularity containers that hold the complete environment necessary to run the scientific apps. Those containers are stored on the CVMFS repsitory atlas.cern.ch and exist as compressed (=squashed) version as well as uncompressed. The containers are developed on CentOS and require a local Singularity version that can deal with them. Older Singularity versions or Singularity on other Linux flavours than CentOS are known to cause errors - e.g. access permission errors - but there are lots of excellent posts from other volunteers who describe solutions and workarounds. As an option Singularity from CVMFS may work but that's neither recommended nor guaranteed. It does not only need +1GB/task on your disk, it also requires a compatible kernel/setup of your local OS. |
|
Send message Joined: 23 Jul 05 Posts: 53 Credit: 2,707,793 RAC: 0
|
Then, I m sure it s a stupid question according to your previous comments, but if singularity downloaded from the project itself is useless (because convoying a lot of errors on other distributions) then why is there not a test to to see which distribution is running and according to that allow or prevent the download of singularity ? We don’t care then about the warnings, duly noted. It doesn’t explain why, if those files are really needed, any curl command did not succeed. But okey let’s put that aside for the moment. For the repo nowhere the information was clear as it should have been. So what did I do as common sense, I took the most complete list I could find on the forum which was not from a post that long ago. At least more recently than what you gave yesterday. As I said also, your configuration line was not working. The chkconfig was complaining about it. Proof that your thread about is not totally correct. Or then the tools is not coded properly, one of the two. Don’t understand this phrase You don't need those repos but configured them. For the use of openhtc it’s simple it was apparently unreachable at the time. And again what do we do first, we use the direct link, not a mirror to access something. Especially as a first try and I don’t see how it can actually be a problem on short terms. Your explanation about the misconfiguration, first I don’t see what would I miss. Secondly the folders, that several people have in their error log should I point out, are not in any way referencing to cvmfs since it was in /var/lib and not in /etc/cvmfs For what I understood is that the project make us download an image of the file system it wants to apply and that’s what got uncompressed and then mounted. If then the application is complaining about not having some folder present in cvmfs itself (not the same thing than the previous thing I’ve just described) I don’t’ see how I could interfere with the process to resolve it. And to my knowledge and what I ve read, nobody having those errors have succeeded to find a solution or they stop responding. And at some point across my readings I even spotted you or one of you colleague acinowledged that there was an error in the package delivered so…. And so I guess that even if cvmfs is delivered in all flavors apparently on the page project you only prefer that people ran Centos Vm then ?(which is now deprecated) |
|
Send message Joined: 23 Jul 05 Posts: 53 Credit: 2,707,793 RAC: 0
|
so indeed with singularity installed locally build from source for the specific distribution it is working correctly and it's crunching as we speak. But I still would like an explanation on which misconfiguration I would have done in CVMFS to have those missing folders in /var/lib which according to what I understand doesn't concern CVMFS. And by the same way, that you confirm me or not if CVMFS is there as a filesystem layer to apply an filesystem image downloadede from the project script? Also I would like to know how to make the differences between what I need as a repo and what I don't need because again, your command didn't check out with the embedded tools which I remind you was(from one of your previous post in the links you posted) CVMFS_REPOSITORIES="atlas,atlas-condb,grid,cernvm-prod,sft,alice |
|
Send message Joined: 15 Jun 08 Posts: 2541 Credit: 254,608,838 RAC: 34,609 |
Run the following command as root and post the output here: cvmfs_config showconfig -s |
©2024 CERN