Open andrzejnovak opened 4 years ago
If this issue is still valid, which platform are you using? which voms version?
I'm now seeing more or less the same but without the oid exists
and further. A strace shows that the program (voms-proxy-init Version: 2.1.1 Compiled: Oct 26 2022 07:40:44) is stuck in a loop opening /cvmfs/dirac.egi.eu/dirac/8.0.3/diracos/etc
and never closing it, so it runs out of file descriptors.
problem actually seems to be due to the program being unable to find the correct vomses file for the requested VO.
If I pass the explicit --vomses=/etc/vomses/km3net.org-voms02.scope.unina.it
option, it works.
Yup, the only follow-up I would have is that it's weird that you can pass --vomses
but no --voms_dir
that one has to be exported to an env var, but I need both the get a proxy back without any "errors"
It seems that if the default location for vomses in version 2.1.1 doesn't exist, it hangs instead of fails. If you specify that non-existent location, it does fail correctly. For the cvmfs one, it looks for /cvmfs/dirac.egi.eu/dirac/8.0.3/diracos/etc/vomses
which doesn't exist.
I've have voms installed in conda. Running
voms-proxy-init
get stuck form some reason onOBJ_create
. Strange thing is that terminating it, there is still a valid proxy created.