On May 23, 2011, at 4:08 PM, Joshua Randall wrote: > Scott, > > I compiled and ran your test program (with a few small errors > corrected):
I am surprised it was only a few small errors since it was written in my email client... ;-) > > Running it is successful: >> jrandall@begbie:/tmp$ ./omxtestself >> iconnect completed with status Success > > > However, I'm not really sure what this is testing -- it seems like it > is only opening one endpoint, looking up that endpoint address, and > then trying to connect to it. I thought the failure I was observing > was that when the client (on one endpoint) tried to connect to the > server (on another endpoint?) on the same host. Am I mistaken about > that? Yes, and they should be in different processes too. Good catch. > In any case, I've tried to extend your test to cover that > scenario: > >> <snip> > > This results in: > >> jrandall@begbie:/tmp$ OMX_CONNECT_POLLALL=1 ./omxtestself2 >> OMX: Forcing connect polling all endpoints to enabled >> iconnect completed with status Success >> iconnect to nic_id from hostname completed with status Success >> > (it does not exit, but seems to loop forever in the final mx_test loop) Hmmm. Not sure what to make of it not returning. Can you print out the value of result? > I'm not sure that I'm doing this right, and have actually also > implemented it as two separate test programs, one for each endpoint > and that has exactly the same issue. I'll pass this test case along > to the Open-MX people and see if they can point out what is wrong. > > Thanks! > > Josh. Ok, you wrote it as two apps and it connects or does not connect? You may also want to set MX_VERBOSE=3 in your environment or something like that to see if Open-MX is complaining internally. They may also have a separate OMX_VERBOSE environment flag. Check their docs. Scott Scott _______________________________________________ Pvfs2-users mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
