For jobs submitted with sbatch, their stdout or stderr is normally directed/saved to a file with the name slurm-$SLURM_JOBID.out e.g. slurm-58228.out But, you can override this in your batch script by providing the --output & --error sbatch options e.g. #SBATCH --output /path/to/job-dir/slurm.out #SBATCH --error /path/to/job-dir/slurm.out
In your script(that you attached earlier), you've already specified the output file(--output=res.txt) which slurm will direct stdout & stderr to. Have a look at it, you'll find something in it. As for the execve() error, it might be caused by a mount option(noexec) that prevents users from directly executing binaries/scripts on the mounted filesystem. Can you please provide us with your slurm.conf file? On Mon, Apr 11, 2016 at 7:25 AM, Naajil Aamir <[email protected]> wrote: > Hi there Im getting this error when i try to run this job. > slurmd[Hostname]: execve(): Pathtoexecutable: Permission denied > I have two nodes, one is the masternode (ctld) while the other one it the > slurmd. The uid is same across the group. and Ive set the permissions of > the script as well as the executable to 777. > I have attatched the jobscript > > if i run it as it is I get (I run using srun myjob.sh) > slurmd[fypclient-OptiPlex-330]: execve(): myjob.sh: Permission denied > > if i run srun hostname directly the hostname of my slurmd node is returned > back > I I run using sbatch, no output is shown, just says submitted job id > > Can any one please help in why it is not able to access the myjob,sh > Thanks in advance > -- *James Oguya*
