Hello Marcin, Thanks for your answer.
debug level is just " debug " and not " debug4 " but it's enough to get this message. I tried to set it to debug4 but as our cluster is very large it's difficult to get all relevant informations and get the error message as well. >This message can just mean that the association beeing iterated is not added >assoc_list in assoc_mgr.c >I think there is nothing to worry about. I don't really understand what you mean by "is not added assoc_list". Do you think it's just a bug without any bad actions ? Thanks again. Best regards, Gerard Centre Informatique de l'Enseignement Superieur > De: "Marcin Stolarek" <stolarek.mar...@gmail.com> > À: "slurm-dev" <slurm-dev@schedmd.com> > Cc: "Gérard Gil" <gerard....@cines.fr> > Envoyé: Lundi 19 Octobre 2015 19:09:05 > Objet: Re: [slurm-dev] Problem using slurm 14.11.9 : > 2015-10-19 18:21 GMT+02:00 < g...@cines.fr > : >> Hello, >> is there someone who can explain such kind of message in slurmctld.log : >> debug: not the right user 2279 != 1761 > Have you enabled debug4 messages? > This message can just mean that the association beeing iterated is not added > assoc_list in assoc_mgr.c > I think there is nothing to worry about. > cheers, > marcin >> Thanks, >> Best regards, >> Gerard Gil >> Departement Calcul Intensif >> Centre Informatique National de l'Enseignement Superieur >> 950, rue de Saint Priest >> 34097 Montpellier CEDEX 5 >> FRANCE >> tel : (334) 67 14 14 14 >> fax : (334) 67 52 37 63 >> web : http://www.cines.fr >>> De: "gil" < g...@cines.fr > >>> À: "slurm-dev" < slurm-dev@schedmd.com > >>> Cc: "gil" < g...@cines.fr > >>> Envoyé: Mercredi 7 Octobre 2015 09:42:31 >>> Objet: Problem using --ntasks (slurm 14.11.9) >>> Hello, >>> we have just upgraded our configuration from SLURM 2.6.9 to SLURM 14.11.9. >>> We are facing a new issue with jobs using --ntasks. >>> The following variables SLURM_NTASKS , SLURM_NPROCS and >>> SLURM_STEP_NUM_TASKS are >>> set with wrong values when the job is submitted using sbatch command : >>> slurm script exemple : >>> #!/bin/bash >>> #SBATCH --nodes=4 >>> #SBATCH --ntasks=7 >>> #SBATCH --ntasks-per-node=2 >>> ... >>> In a "normal" case slurm 2.6.9 we get : >>> SLURM_NTASKS=7 >>> SLURM_NPROCS=7 >>> SLURM_STEP_NUM_TASKS=7 >>> With slurm version 14.11.9 , when the job is submitted with sbatch command >>> we >>> get : >>> SLURM_NTASKS=8 >>> SLURM_NPROCS=8 >>> SLURM_STEP_NUM_TASKS=8 >>> With slurm version 14.11.9 , when the job is submitted with salloc command >>> we >>> get : >>> SLURM_NTASKS=7 >>> SLURM_NPROCS=7 >>> SLURM_STEP_NUM_TASKS=7 >>> The only way we found to workaround the problem is to set these tree >>> variables >>> "by hand" inside the slurm script as the first command before job steps : >>> #!/bin/bash >>> #SBATCH --nodes=4 >>> #SBATCH --ntasks=7 >>> #SBATCH --ntasks-per-node=2 >>> ... >>> SLURM_NTASKS=7 >>> SLURM_NPROCS=7 >>> SLURM_STEP_NUM_TASKS=7 >>> Any idea about this problem ? >>> How can we solve it ? >>> Best Regards, >>> Gerard Gil >>> Departement Calcul Intensif >>> Centre Informatique National de l'Enseignement Superieur >>> 950, rue de Saint Priest >>> 34097 Montpellier CEDEX 5 >>> FRANCE >>> tel : (334) 67 14 14 14 >>> fax : (334) 67 52 37 63 >>> web : http://www.cines.fr
