Silent Errors (No Output or Error Files)

If your job ends without any error nor any output file, start your investigation by checking the following.

No permissions to write in the destination directory

You must have the write  permissions on the destination directory to allow Slurm to create the output files in it.

Reminder: by default, if you don't specify anything through -o  and -e options, Slurm creates slurm-<job id>.o  and slurm-<job id>.e  files in the directory where the command (generally sbatch) is launched.

To check that you have the write permission on a directory, use ls -ld  command

Code Block (bash)

login@maestro-submit ~ $ ls -ld ./bacteria
drwxr-x--- 1 user1 UnitName 0 May 26 12:30 ./bacteria/

On the above example, user1 hasn't given write permissions to other members of the unix group UnitName, since, for the second triplet (r-x) in the first column drwxr-x--- , there is no w  in second position. r-x   means that members of the group can list the content of the bacteria  directory but can not create or remove any file inside it.

No space remaining on the directory

If the storage space where the files are supposed to be written is full, of course they won't be created. Check the remaining on that space using myquota

Code Block (bash)

login@maestro-submit ~ $ myquota -u <login>

Filesystem (2023-08-03 16:50)                 Type     Size     Used    Avail   Use%
/pasteur/appa/homes/<login>                    user  100.00G    7.23G   92.77G   7.2%
/pasteur/zeus/projets/p01/project1         project    1.00T   49.65G  974.35G   4.8%
/pasteur/zeus/projets/p02/project2         project   10.00T   10.00T       0B 100.0%

Filesystem (2023-08-03 02:00)                 Type     Size     Used    Avail   Use%
/pasteur/appa/scratch/proj2scratch           group        -  503.39G        -      -

As you can see, project2  storage space is full (0 bytes available, 100% used), there is no space left to write anything, including the Slurm error file.