Indeed the problem was about disk space on one of the computes that the job
used that.
Thank you very much.
which implies that the job failed before creating the output file.
> could you have a problem accessing the working directory on the compute
> nodes? over-quota even? I would certainly e
why not use sacct? squeue is only for queued and running jobs.
$ sacct -j 1277
JobIDJobName PartitionAccount AllocCPUS State ExitCode
-- -- -- -- --
1277 my_lammpsEMERALDz55 12 FA
> why not use sacct? squeue is only for queued and running jobs.
$ sacct -j 1277
JobIDJobName PartitionAccount AllocCPUS State ExitCode
-- -- -- -- --
1277 my_lammpsEMERALDz55 12 F
>From your email it looks like you submitted the job, ran squeue and saw
that it either didn't start or completed very quickly. I'd start with the
job ExitCode info from sacct.
On Wed, Jul 24, 2019 at 4:34 AM Mahmood Naderan
wrote:
> Hi,
> I don't know why no error/output file is generated after
Hi,
I don't know why no error/output file is generated after the job submission.
$ ls -l
total 8
-rw-r--r-- 1 montazeri montazeri 472 Jul 24 12:52 in.lj
-rw-rw-r-- 1 montazeri montazeri 254 Jul 24 12:53 slurm_script.sh
$ cat slurm_script.sh
#!/bin/bash
#SBATCH --job-name=my_lammps
#SBATCH --output
