That explains, thank you for the quick answer.
2013/11/11 Ralph Castain
> IIRC, 1.6.5 defaults to *not* using the tree spawn. We changed it in 1.7
> series because the launch performance is so much better.
>
>
> On Nov 11, 2013, at 8:22 AM, Christoffer Hamberg <
> christoffer.hamb...@gmail.com
IIRC, 1.6.5 defaults to *not* using the tree spawn. We changed it in 1.7 series
because the launch performance is so much better.
On Nov 11, 2013, at 8:22 AM, Christoffer Hamberg
wrote:
> I re-configured the ssh keys now and for some reason it seems to work. But
> what baffles me is that the
I re-configured the ssh keys now and for some reason it seems to work. But
what baffles me is that the same ssh configuration worked for the other
installation (1.6.5) but not for this one.
Thanks for the help!
2013/11/11 Reuti
> Am 11.11.2013 um 10:04 schrieb Christoffer Hamberg:
>
> > (Corre
Am 11.11.2013 um 10:04 schrieb Christoffer Hamberg:
> (Correction; I mixed up the output of the two first examples in my first
> mail, so it fails on the first one)
>
> ubuntu@node0:~$ mpirun --leave-session-attached -mca plm_base_verbose 5 -np 4
> -host node0,node1,node2,node3 hostname
> [node
(Correction; I mixed up the output of the two first examples in my first
mail, so it fails on the first one)
ubuntu@node0:~$ mpirun --leave-session-attached -mca plm_base_verbose 5 -np
4 -host node0,node1,node2,node3 hostname
[node0:01486] mca:base:select:( plm) Querying component [slurm]
[node0:
Add --enable-debug to your configure and run it with the following additional
options
--leave-session-attached -mca plm_base_verbose 5
Let's see where it fails during the launch phase. Offhand, the only thing that
message means to me is that the ssh keys are botched on at least one node. Keep
