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] <
hoove...@helix.nih.gov> wrote:
> I would guess something about the slurm job exceede
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 wrote:
>
> Hi Evan,
>
> Are there any other details logged for this job?
>
> --nate
>
> On Thu, Jun 1
Hi Evan,
Are there any other details logged for this job?
--nate
On Thu, Jun 15, 2017 at 9:20 AM, evan clark 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 signa
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 you
