> On Mar 25, 2015, at 1:59 PM, Mark Santcroos <mark.santcr...@rutgers.edu> > wrote: > > Hi Ralph, > >> On 25 Mar 2015, at 21:25 , Ralph Castain <r...@open-mpi.org> wrote: >> I think I have this resolved, >> though that I still suspect their is something wrong on that system. You >> shouldn’t have some nodes running munge and others not running it. > > For completeness, it's not "some" nodes, its the MOM (service) nodes that run > it, and the compute nodes don't. > I don't know munge well enough to judge whether it makes sense to have it > there only and not on the compute nodes?
Can’t say for sure, but it seems odd. Munge is supposed to be there to authenticate connections. If you run mpirun on the service nodes, then you’ll have daemons from the compute node connecting back to it. I should think you’d want those connections authenticated in some fashion, but perhaps not? Might be worth pinging the admins just to get an explanation. I’d be curious as to what they say. As things stand, the patch allows us to fall back to our internal authentication (just a simple text string) if the daemon doesn’t have anything else it can use. So it should (hopefully) work. > >> I wonder if someone was experimenting and started munge on some of the >> nodes, and forgot to turn it off afterwards?? > > If the answer to my request for clarification is along the lines of "No!", > then I can ask the admins whats up. > >> Anyway, see if this fixes the problem. >> >> https://github.com/open-mpi/ompi/pull/497 > > Will get back to you later how that works for me. > > Thanks > > Mark > _______________________________________________ > 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/26533.php
