When inside a salloc session, with SLURM_CONF set, trying to use srun stats a socket and then fails to read the config. mattmix@ln0004 ~>salloc salloc: Granted job allocation 8114 mattmix@ln0004 ~>srun uptime srun: s_p_parse_file: file "/proc/22989/fd/5" is empty srun: error: ClusterName needs to be specified srun: fatal: Unable to process configuration file mattmix@ln0004 ~>ls -l /proc/22989/fd/5 lrwx------. 1 mattmix tech 64 Sep 9 14:14 /proc/22989/fd/5 -> socket:[8298873] mattmix@ln0004 ~>echo $SLURM_CONF /proc/22989/fd/5
Created attachment 15818 [details] slur.conf
Matt, You're very likely hitting the same issue as in Bug 9704. I'll just quote my reply from there (Bug 9704 comment 3): >I can reproduce the issue and I have a patch that I'm passing to our QA queue. >Let me know if you're interested in testing it before the review competition. > >However, client tools should work in config-less mode with just DNS entry >configured you may consider running a slurmd daemon on login node. This slurmd >doesn't have to be configured as a computing node in any partition, but will just >keep the files in /run/slurm/conf/slurm.conf up-to-date (after scontrol >reconfigure). This setup will result in a reduced number of RPCs send to >slurmctld, without that every execution of client utilities has to issue >REQUEST_CONFIG RPC to download the configuration before doing its job. Let me know if you want to try the patch before its QA is completed. cheers, Marcin
Marking as a duplicate of bug #9704 *** This ticket has been marked as a duplicate of ticket 9704 ***