If slurm accounting is configured, `sacct` might reveal more. You might also check the slurmd logs on the execution host where the job ran. --nate On Thu, Jun 15, 2017 at 11:47 AM, Hoover , David (NIH/CIT) [E] < hooverdm@helix.nih.gov> wrote:
I would guess something about the slurm job exceeded some allocated resource (memory, cpu, time) and slurm killed the job.
David Hoover HPC @ NIH
On Jun 15, 2017, at 11:28 AM, Nate Coraor <nate@bx.psu.edu> wrote:
Hi Evan,
Are there any other details logged for this job?
--nate
On Thu, Jun 15, 2017 at 9:20 AM, evan clark <eclark28@fau.edu> wrote:
Has anyone ever encountered an error such as this when running galaxy with slurm and submitting files for upload and unzip.
slurmstepd: get_exit_code task 0 died by signal
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/