Sorry for the super long delay. I don't know how this one got lost...
I run like this all the time. Unfortunately, it is not as simple as I
would like. Here is what I do:
1. Log into the machine using ssh -X
2. Run mpirun with the following parameters:
-mca pls rsh (This makes sure that Open MPI uses the rsh/ssh launcher.
It may not be necessary depending on your setup)
-mca pls_rsh_agent "ssh -X" (To make sure X information is forwarded.
This might not be necessary if you have ssh setup to always forward X
--debug-daemons (This ensures that the ssh connections to the backed
nodes are kept open. Otherwise, they are closed and X information cannot
be forwarded. Unfortunately, this will also cause some debugging output
to be printed, but right now there is no other way :( )
So, the complete command is:
mpirun -np 4 -mca pls rsh -mca pls_rsh_agent "ssh -X" --debug-daemons
xterm -e gdb my_prog
I hope this helps. Let me know if you are still experiencing problems.
> For debugging i usually run each process in a separate X-window.
> This works well if i set the DISPLAY variable to the computer
> from which i am starting my OpenMPI application.
> This method fails however, if i log in (via ssh) to my workstation
> from a third computer and then start my OpenMPI application,
> only the processes running on the workstation i logged into can
> open their windows on the third computers. The processes on
> the other computers cant open their windows.
> This is how i start the processes
> mpirun -np 4 -x DISPLAY run_gdb.sh ./TestApp
> where run_gdb.sh looks like this
> #!/bin/csh -f
> echo "Running GDB on node `hostname`"
> xterm -e gdb $*
> exit 0
> The output from the processes on the other computer:
> xterm Xt error: Can't open display: localhost:12.0
> I there a way to tell OpenMPI to forward the X windows
> over yet another ssh connection?
> users mailing list