All solved and now works well! The culprit was the lost line in the
"maui.cfg" file:
JOBNODEMATCHPOLICY EXACTNODE
The default value for this variable is EXACTPROC and, in its presence, Maui
completely ignores the "-l nodes=N:ppn=M" PBS instruction and allocates
the first M available cores
All solved and now works well! The culprit was the lost line in the
"maui.cfg" file:
JOBNODEMATCHPOLICY EXACTNODE
The default value for this variable is EXACTPROC and, in its presence, Maui
completely ignores the "-l nodes=N:ppn=M" PBS instruction and allocates
the first M available cores
Thanks!
In fact there should be a problem with Maui's node allocation setting. I
have checked the $PBS_NODEFILE contents (this is also may be seen with
"qstat -n1"): while the default Torque scheduler correctly allocates one
slot on node1 and another slot on node2, in case of Maui I always see
sounds to me like your maui scheduler didn’t provide any allocated slots on the
nodes - did you check $PBS_NODEFILE?
> On Aug 9, 2017, at 12:41 PM, A M wrote:
>
>
> Hello,
>
> I have just ran into a strange issue with "mpirun". Here is what happened:
>
> I successfully
Hello,
I have just ran into a strange issue with "mpirun". Here is what happened:
I successfully installed Torque 6.1.1.1 with the plain pbs_sched on a
minimal set of 2 IB nodes. Then I added openmpi 2.1.1 compiled with verbs
and tm, and have verified that mpirun works as it should with a small