You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behaviour is that the SLURM job starts and each array starts a process opening the singularity image (accessible to all nodes). This is happening 80% of the time
Actual behaviour
Often I get the following error
Failed to get singularity version:
WARNING: Could not lookup the current user's information: user: lookup userid numeric_UID: no such file or directory
FATAL: Couldn't determine user account information: user: lookup userid numeric_UID: no such file or directory
The numeric_UID is my actual numeric UID on the HPC but it is missing the step to get the UID (not numeric).
Example: my UID is user002, my numeric_UID is 1234567.
As far as I understand, the join between the two happens via active directory as the UID is the ID used for all services (including windows)
Steps to reproduce this behavior
I have not been able to fully reproduce this behaviour. it seems a combination of limited network connection to the active directory component, number of users connected and something else not yet identified
Is there a way to catch the behaviour of singularity in the SLURM file? As I can not reproduce it everytime, it is difficult to catch it
Is there a way to set the UID manually? As it would be always the same in this case, it could help
Version of Singularity:
What version of Singularity are you using?
Expected behavior
I am launching singularity from a SLURM file in an HPC setting
Expected behaviour is that the SLURM job starts and each array starts a process opening the singularity image (accessible to all nodes). This is happening 80% of the time
Actual behaviour
Often I get the following error
The
numeric_UID
is my actual numeric UID on the HPC but it is missing the step to get the UID (not numeric).Example: my UID is user002, my numeric_UID is 1234567.
As far as I understand, the join between the two happens via active directory as the UID is the ID used for all services (including windows)
Steps to reproduce this behavior
I have not been able to fully reproduce this behaviour. it seems a combination of limited network connection to the active directory component, number of users connected and something else not yet identified
Any other suggestions would be welcomed
What OS/distro are you running
How did you install Singularity
It is installed as a module on the HPC, not sure how the administrators installed it.
The text was updated successfully, but these errors were encountered: