Re: [ptp-user] PTP Launcher Fails withJava.lang.reflect.InvocationTarget

[Greg Watson <g.watson@xxxxxxxxxxxx>]

On Dec 19, 2007, at 12:04 PM, Kenneth Evans, Jr. wrote:

Greg,

 

Thanks for your help.

You're welcome. 

 

First, I should say I am new to OpenMPI.  We are set up for MPICH2.  I am an experienced Eclipse user, however, and would like to try Eclipse, including installing Tau.  This is the reason for using OpenMPI.

 

I modified openmpi-default-hostfile, as you suggested, and I can now run on the command line with:

 

mpiexec --prefix /clhome/EVANS/openmpi -n 5 helloWorld

 

(Note: No machine file.)  My .login sets MPICH2 paths.  I can reset the paths on the machine on which I am running, but I need the –prefix for the nodes to work.  The paths are set for OpenMPI in a script that I use to start Eclipse, but I would guess there is still the problem with the nodes that –prefix fixes.  Can this be handled in PTP?

I'm not sure why you need to use --prefix at all? Did you specify a prefix when you ran configure on OpenMPI? That should set up everything correctly so you should just need to use mpirun.

 

It still doesn’t work in Eclipse.  I get the same exception.  There is only one machine (Machinemachine0, no typo) in the drop-down menu in the launch configuration.  Just what is this machine anyway and where is it set?  I would expect a list of nodes like in the openmpi-default-hostfile. 

This machine name comes from a simulator in PTP. It is selected as a fallback when a valid proxy can't be started. When we get things set up correctly you will see all the machines you put in the hostfile.

The launcher seems like the place to put this information.  It also seems like there should be a place for arguments to mpiexec in addition to those for the program.  Perhaps I have missed something.

What other arguments do you need?

 

I tried restarting Eclipse with –clean.  It didn’t help.

 

The file ptp_orte_proxy exists and looks OK.  I did not get errors during sh BUILD.  I added the following lines to BUILD, first:

 

--------------------------------------------------------------------------------

# Added manually to the original since installation is non-standard

export CFLAGS=-I/clhome/EVANS/openmpi/include

export LDFLAGS="-L/clhome/EVANS/openmpi/lib -Wl,-rpath,/clhome/EVANS/openmpi/lib"

--------------------------------------------------------------------------------

 

(BTW the directions on the help page need some line breaks, and this isn’t exactly what I took them to say, but it seems like it should do what I think they indicate is needed.)

Please try running the ptp_orte_proxy program manually and let me know what output you see. I suspect you have a LD_LIBRARY_PATH problem.

--------------------------------------------------------------------------------

 

Looking to the future: I use MPE.  Is there an easy way to point OpenMPI to the version that is already installed?  There is a paragraph about the advantages of using the mpicc wrapper somewhere I looked.  Can the OpenMPI mpicc be fixed to specify MPE with options like “-mpe=log” as in MPICH2 or do I need to use –L and –l?

I'm not an OpenMPI expert, sorry. You'll need to post something to the OpenMPI mailing list.

Regards,

Greg