Ok. FYI: > aprun munge -n munge: Error: Unable to access "/var/run/munge/munge.socket.2": No such file or directory Application 23792792 exit codes: 6 Application 23792792 resources: utime ~0s, stime ~1s, Rss ~27304, inblocks ~35, outblocks ~58
> On 25 Mar 2015, at 17:29 , Ralph Castain <r...@open-mpi.org> wrote: > > Yeah, what’s happening is that mpirun is picking one security mechanism for > authenticating connections, but the backend daemons are picking another, and > hence we get the conflict. The weird thing here is that you usually don’t see > this kind of mismatch for the very reason you are hitting - it becomes > difficult to resolve authentications. > > Let me ponder a bit. We can resolve it easily enough, but I want to ensure we > don’t do it by creating a security hole. > >> On Mar 25, 2015, at 9:25 AM, Mark Santcroos <mark.santcr...@rutgers.edu> >> wrote: >> >> >>> On 25 Mar 2015, at 17:06 , Ralph Castain <r...@open-mpi.org> wrote: >>> >>> OHO! You have munge running on the head node, but not on the backends! >> >> Ok, so I now know that munge is ... :) >> >> It's running on the MOM node (not on the head node): >> >> daemon 18800 0.0 0.0 118476 3212 ? Sl 01:27 0:00 >> /usr/sbin/munged --key-file /opt/munge/munge.key --num-threads 8 >> >> Any tests you would like me to perform? >> >> _______________________________________________ >> users mailing list >> us...@open-mpi.org >> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users >> Link to this post: >> http://www.open-mpi.org/community/lists/users/2015/03/26524.php > > _______________________________________________ > users mailing list > us...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users > Link to this post: > http://www.open-mpi.org/community/lists/users/2015/03/26525.php
