Re: [OMPI users] General question about running single-node jobs.

2014-09-30 Thread Lee-Ping Wang
Hi Ralph, Thanks. I'll add some print statements to the code and try to figure out precisely where the failure is happening. - Lee-Ping On Sep 30, 2014, at 12:06 PM, Ralph Castain wrote: > > On Sep 30, 2014, at 11:19 AM, Lee-Ping Wang wrote: > >>

Re: [OMPI users] General question about running single-node jobs.

2014-09-30 Thread Ralph Castain
On Sep 30, 2014, at 11:19 AM, Lee-Ping Wang wrote: > Hi Ralph, > >>> If so, then I should be able to (1) locate where the port number is >>> defined in the code, and (2) randomize the port number every time it's >>> called to work around the issue. What do you think?

Re: [OMPI users] General question about running single-node jobs.

2014-09-30 Thread Lee-Ping Wang
Hi Ralph, >> If so, then I should be able to (1) locate where the port number is defined >> in the code, and (2) randomize the port number every time it's called to >> work around the issue. What do you think? > > That might work, depending on the code. I'm not sure what it is trying to >

Re: [OMPI users] General question about running single-node jobs.

2014-09-30 Thread Ralph Castain
On Sep 30, 2014, at 10:49 AM, Lee-Ping Wang wrote: > Hi Ralph, > > Thank you. I think your diagnosis is probably correct. Are these sockets > the same as TCP/UDP ports (though different numbers) that are used in web > servers, email etc? Yes > If so, then I should

Re: [OMPI users] General question about running single-node jobs.

2014-09-30 Thread Lee-Ping Wang
Hi Ralph, Thank you. I think your diagnosis is probably correct. Are these sockets the same as TCP/UDP ports (though different numbers) that are used in web servers, email etc? If so, then I should be able to (1) locate where the port number is defined in the code, and (2) randomize the

Re: [OMPI users] still SIGSEGV for Java in openmpi-1.9a1r32807 on Solaris

2014-09-30 Thread Ralph Castain
Don't know about the segfault itself, but I did find and fix the classpath logic so the app is found. Might help you get a little further. On Sep 29, 2014, at 10:58 PM, Siegmar Gross wrote: > Hi, > > yesterday I installed openmpi-1.9a1r32807 on my

Re: [OMPI users] OpenMPI 1.8.3 build without BTL

2014-09-30 Thread Lee-Ping Wang
Hi Jeff and Ralph, Thanks. I'm really a novice user - and in cases like this one I don't really know what I'm doing. In this case, I just wanted to get my application to run without throwing strange error messages and quitting. :) That said, I would much rather learn about the components of

Re: [OMPI users] OpenMPI 1.8.3 build without BTL

2014-09-30 Thread Jeff Squyres (jsquyres)
How can you run MPI jobs at all without any BTLs? That sounds weird -- this is not a case for which we designed the code base. All that being said, you're getting compile errors in the OMPI build because of two things: - you selected to build static - you didn't disable enough stuff

[OMPI users] still SIGSEGV for Java in openmpi-1.9a1r32807 on Solaris

2014-09-30 Thread Siegmar Gross
Hi, yesterday I installed openmpi-1.9a1r32807 on my machines with Sun C 5.12 and gcc-4.9.1. Unfortunately my small Java program still breaks with a segmentation fault. tyr java 109 ompi_info | grep -e MPI: Open MPI: 1.9a1r32807 tyr java 110 mpijavac InitFinalizeMain.java warning:

Re: [OMPI users] OpenMPI 1.8.3 build without BTL

2014-09-30 Thread Ralph Castain
ompi_info is just the first time when an executable is built, and so it always is the place where we find missing library issues. It looks like someone has left incorrect configure logic in the system such that we always attempt to build Infiniband-related code, but without linking against the

Re: [OMPI users] General question about running single-node jobs.

2014-09-30 Thread Ralph Castain
I don't know anything about your application, or what the functions in your code are doing. I imagine it's possible that you are trying to open statically defined ports, which means that running the job again too soon could leave the OS thinking the socket is already busy. It takes awhile for