Re: [OMPI users] mca:base:select:( ess) No component selected!

2008-09-25 Thread Ralph Castain
FWIW: doing it this way locks you to bash. What you could do instead is using ompi_prefix, and then add the other libraries via orte_launch_agent. The reason I suggest this is that ompi_prefix will cause the ssh launcher to check which shell is being invoked on the remote end, and

Re: [OMPI users] mca:base:select:( ess) No component selected!

2008-09-24 Thread Will Portnoy
Thank you. I was able to make everything work by using orte_launch_agent and bash's $@ to pass the necessary parameters to orted within my shell script. I needed to add additional paths to my LD_LIBRARY_PATH/PATH variables for other necessary libraries, which is why I was pushing on the

Re: [OMPI users] mca:base:select:( ess) No component selected!

2008-09-24 Thread Ralph Castain
Yes - you don't want to use orte_launch_agent at all for that purpose. What you need to set is an info_key in your comm_spawn command for "ompi_prefix", with the value set to the install path. The ssh launcher will assemble the launch cmd using that info. Ralph On Sep 24, 2008, at 1:28

Re: [OMPI users] mca:base:select:( ess) No component selected!

2008-09-24 Thread Will Portnoy
Yes, your first sentence is correct. I intend to use the unmodified orted, but I need to set up the unix environment after the ssh has completed but before orted is executed. In particular, one of the more important tasks for me to do after ssh connects is to set LD_LIBRARY_PATH and PATH to

Re: [OMPI users] mca:base:select:( ess) No component selected!

2008-09-24 Thread Will Portnoy
Sorry for the miscommunication: The processes are started by my program with MPI_Comm_spawn, so there was no mpirun involved. If you can suggest a test program I can use with mpirun to validate my openmpi environment and install, that would probably produce the output you would like to see. But

Re: [OMPI users] mca:base:select:( ess) No component selected!

2008-09-24 Thread Ralph Castain
Afraid I am confused. This was the entire output from the job?? If so, then that means mpirun itself wasn't able to find a launch environment it could use, so you never got to the point of actually launching an orted. Do you have ssh in your path? My best immediate guess is that you

Re: [OMPI users] mca:base:select:( ess) No component selected!

2008-09-24 Thread Will Portnoy
That was the output with plm_base_verbose set to 99 - it's the same output with 1. Yes, I'd like to use ssh. orted wasn't starting properly with orte_launch_agent (which was needed because my environment on the target machine wasn't set up), so that's why I thought I would try it directly on the

Re: [OMPI users] mca:base:select:( ess) No component selected!

2008-09-24 Thread Ralph Castain
Could you rerun that with -mca plm_base_verbose 1? What environment are you in - I assume rsh/ssh? I would like to see the cmd line being used to launch the orted. What this indicates is that we are not getting the cmd line correct. Could just be that some patch in the trunk didn't get

[OMPI users] mca:base:select:( ess) No component selected!

2008-09-24 Thread Will Portnoy
I'm trying to use MPI_Comm_Spawn with MPI_Info's host key to spawn processes from a process not started with mpirun. This works with the host key set to the localhost's hostname, but it does not work when I use other hosts. I'm using version 1.3a1r19602. I need to use orte_launch_agent to set