Closed dmacguigan closed 2 years ago
and you CAN write to /scratch/$JOBID
(/scratch/9342753/
in this example)?
Did you have the scratch folder set in the SINGULARITY_BIND env variable before starting up the process? eg on our system we need to bind the partitions to be able to write to.
# in this example the $SCRATCH variable is set in the slurm env to a local disk folder that is deleted after the job completes
export SINGULARITY_BIND="${SCRATCH}:/tmp"
Ah it seems my problem stems from how SLURM sets environmental variables.
Users submitting job scripts with sbatch that run Singularity containers may notice this error:
mktemp: failed to create file via template ‘/scratch/[jobid]/tmp.XXXXXXXXXX’: No such file or directory
With sbatch, the environment variable TMPDIR gets set to be /scratch/[jobid], so when mktemp tries to execute, it looks for /scratch/[jobid], but the singularity container may not have a /scratch directory.
Recommended solution:
At the beginning of the job script, unset TMPDIR to clear that variable, which allows the Singularity container to use whatever directory is the default for it.
Are you using the latest release? Yes
Describe the bug I am using the latest Docker image for funannotate (with Singularity) on a university computing cluster. However, PASA throws the following error message. I have tried the test dataset and my own data, but the issue persists.
From funannotate-train.log:
From pasa-assembly.log
What command did you issue?
Logfiles See attached files. funannotate-train.log pasa-assembly.log
OS/Install Information