[slurm-users] Slurmctld 18.08.1 and 18.08.3 segfault
Kilian Cavalotti
kilian.cavalotti.work at gmail.com
Tue Nov 13 22:39:47 MST 2018
Hi Bill,
On Tue, Nov 13, 2018 at 5:35 PM Bill Broadley <bill at cse.ucdavis.edu> wrote:
> (gdb) bt
> #0 _step_dealloc_lps (step_ptr=0x555787af0f70) at step_mgr.c:2092
> #1 post_job_step (step_ptr=step_ptr at entry=0x555787af0f70) at step_mgr.c:4720
> #2 0x000055578571d1d8 in _post_job_step (step_ptr=0x555787af0f70) at step_mgr.c:270
> #3 _internal_step_complete (job_ptr=job_ptr at entry=0x555787af04a0,
> step_ptr=step_ptr at entry=0x555787af0f70) at step_mgr.c:311
> #4 0x000055578571d35c in job_step_complete (job_id=7035546, step_id=4294967295,
> uid=uid at entry=0, requeue=requeue at entry=false,
> job_return_code=<optimized out>) at step_mgr.c:878
> #5 0x00005557856f0522 in _slurm_rpc_step_complete (msg=0x7f06a93d2e20,
> running_composite=<optimized out>) at proc_req.c:3863
There are a couple mentions of the same backtrace on the bugtracker,
but that was a long time ago (namely
https://bugs.schedmd.com/show_bug.cgi?id=1557 and
https://bugs.schedmd.com/show_bug.cgi?id=1660, for Slurm 14.11). Weird
to see that popping up again in 18.08.
Cheers,
--
Kilian
More information about the slurm-users
mailing list