Hi,
For an update we tried one case please find it below:
We tried by adding below script to kill the namd3 process in our epilog
script.
# To kill remaining processes of job.
#
if [ $SLURM_UID = 1234 ] ; then
STUCK_PID=`${SLURM_BIN}scontrol listpids $SLURM_JOB_ID | awk
'{print $1}' | gr
Hi,
Also forgot to mention the process is still running when user do scancel
and epilog does not clean if one job finished when doing multiple job
submission.
We tried to use unkillable option but did not work. The process still
remains the same until killing it manually.
On Tue, 25 Apr 2023 at
Hi,
We are facing one issue in my environment and the behaviour looks strange
to me. It is specifically associated with the namd3 application.
The issue is narrated below and I have made some of the cases.
I am trying to understand the way to kill the processes of the namd3
application submitted
