Make sure the gid_range is set to a range in which none of your system's
users have group-ids. Otherwise it will kill the wrong things.
On Thu, Nov 15, 2018 at 6:10 PM wrote:
> Hay, William wrote on 11/14/18 04:21:
> > Do you have ENABLE_ADDGRP_KILL set? Can be helpful in killing processes
> l
Hay, William wrote on 11/14/18 04:21:
Do you have ENABLE_ADDGRP_KILL set? Can be helpful in killing processes left
behind when a job exits.
We don't have that set yet. I will try setting ENABLE_ADDGRP_KILL=TRUE
in the execd_params for the global configuration and see if it helps.
Thanks
__
Reuti wrote on 11/14/18 04:53:
Which version of MPICH are you using? Maybe it's not tightly integrated.
It's MPICH 3.2.1 which I believe is tightly integrated.
Thanks
___
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/
Hi,
> Am 14.11.2018 um 01:06 schrieb ad...@genome.arizona.edu:
>
> We have a cluster with gridengine 6.5u2 and noticing a strange behavior when
> running MPI jobs. Our application will finish, yet the processes continue to
> run and use up the CPU. We did configure a parallel environment for
On Tue, Nov 13, 2018 at 05:06:51PM -0700, ad...@genome.arizona.edu wrote:
> We have a cluster with gridengine 6.5u2 and noticing a strange behavior when
> running MPI jobs. Our application will finish, yet the processes continue
> to run and use up the CPU. We did configure a parallel environment
probably it is the Maker which does not have proper handling of signals?
Maybe you can try to use a script to run the job, rather than run
binary directly, to see if it can work. Also you can add some signal
handling commands in your script to check...
Best,
Feng
On Tue, Nov 13, 2018 at 7:07 PM
