Unable to Create VOMS Proxy

[Andrew42]

When trying to run the command voms-proxy-init -voms cms on both coffea-opendata.casa and coffea.casa, I get a segfault.

The error output looks like the following:

[user:~]$ voms-proxy-init -voms cms -valid 192:00 --debug
Unspecified proxy version, settling on version 4 (RFC)
PCI extension info: 
 Path length: -1
 Policy language not specified.
 Policy file not specified.
Number of bits in key :2048
Files being used:
 CA certificate file: none
 Trusted certificates directory : /etc/grid-security/certificates
 Proxy certificate file : /tmp/x509up_u6440
 User certificate file: /home/cms-jovyan/.globus/usercert.pem
 User key file: /home/cms-jovyan/.globus/userkey.pem
Output to /tmp/x509up_u6440
Enter GRID pass phrase:
Your identity: /DC=ch/DC=cern/OU=Organic Units/OU=Users/CN=awightma/CN=792680/CN=Andrew Wightman
error:12000079:random number generator::Cannot open file:crypto/rand/randfile.c:106Filename=/home/cms-jovyan/.rnd
Cannot open fileFilename=/home/cms-jovyan/.rnd
Function: 
Using configuration file /home/cms-jovyan/.glite/vomses
Using configuration file /usr/local/etc/vomses
Segmentation fault (core dumped)

At first we thought it was an issue with locating the configuration file /usr/local/etc/vomses, which didn't exist initially, so we copied it from /etc/vomses, however, this didn't fix the issue. We then tried manually creating the .rnd file via touch and later via openssl rand -out $HOME/.rnd -hex 256. This fixed the error message about the random number generator, but the command still segfaulted in the same location.

[oshadura]

@clundst @jthiltges do you have any idea what could be wrong? We switched using Alma8 from Ubuntu and it looks like something is still missing in configuration.
Also segfault doesn't help, even though I have gdb available in the image :-)

This is reproducible easily with coffee2024 image setup.

[clundst]

If I specify a vomses file I avoid the segmentation fault, it looks like it's trying a vomses file that doesn't exist.

voms-proxy-init -voms cms -valid 192:00 --debug --vomses /etc/vomses