What is the working directory for slurmd?  I suspect slurmstepd would fork
there, perhaps there is some issue with it?

----
Doug Jacobsen, Ph.D.
NERSC Computer Systems Engineer
National Energy Research Scientific Computing Center <http://www.nersc.gov>
dmjacob...@lbl.gov

------------- __o
---------- _ '\<,_
----------(_)/  (_)__________________________


On Fri, Sep 15, 2017 at 9:04 AM, Gyro Funch <gyromagne...@gmail.com> wrote:

>
> Thank you for the responses, Doug and Andy.
>
> There is a /tmp directory on all of the compute nodes and the
> permissions seem okay (drwxrwxrwt).
>
> Running as root, I find:
> $ cd /tmp
> $ srun -N5 whoami
> root
> slurmstepd: error: Unable to get current working directory: No such
> file or directory
> root
> slurmstepd: error: Unable to get current working directory: No such
> file or directory
> root
> slurmstepd: error: Unable to get current working directory: No such
> file or directory
> root
> slurmstepd: error: Unable to get current working directory: No such
> file or directory
> root
>
>
> I also tried
> $ cd /home/slurm
> $ sudo -u slurm srun -N5 whoami
> slurm
> slurmstepd: error: Unable to get current working directory: No such
> file or directory
> slurm
> slurmstepd: error: Unable to get current working directory: No such
> file or directory
> slurm
> slurmstepd: error: Unable to get current working directory: No such
> file or directory
> slurm
> slurmstepd: error: Unable to get current working directory: No such
> file or directory
> slurm
>
>
> Thanks.
>
> -gyro
>
> On 9/15/2017 9:19 AM, Andy Riebs wrote:
> > Actually, it looks like /tmp is missing on the compute nodes?
> >
> > On 09/15/2017 11:12 AM, Doug Meyer wrote:
> >> Re: [slurm-dev] slurmstepd error
> >> Your path is either erroneous in your submission or inaccessible
> >> by the client.
> >> Welcome to slurm!
> >>
> >> Doug
> >>
> >>
> >> On Sep 15, 2017 8:10 AM, "Gyro Funch" <gyromagne...@gmail.com
> >> <mailto:gyromagne...@gmail.com>> wrote:
> >>
> >>
> >>     Hi,
> >>
> >>     I am a new user of slurm (17.02.7) and just installed and
> >>     configured
> >>     it on a small compute cluster.
> >>
> >>     In testing, I ran into the following situation:
> >>
> >>     -----
> >>
> >>     $ cd /tmp
> >>     $ srun -N5 hostname
> >>     compute-4
> >>     slurmstepd: error: Unable to get current working directory: No
> >>     such
> >>     file or directory
> >>     compute-2
> >>     slurmstepd: error: Unable to get current working directory: No
> >>     such
> >>     file or directory
> >>     compute-1
> >>     slurmstepd: error: Unable to get current working directory: No
> >>     such
> >>     file or directory
> >>     compute-0
> >>     slurmstepd: error: Unable to get current working directory: No
> >>     such
> >>     file or directory
> >>     compute-3
> >>
> >>     -----
> >>
> >>     Does anyone know why the 'Unable to get current working directory'
> >>     error arises and how to fix it.
> >>
> >>     Thank you for your help.
> >>
> >>     Kind regards,
> >>     gyro
> >>
> >>
> >
>

Reply via email to