HP-MPI User's Guide (11th Edition)

Debugging and troubleshooting
Troubleshooting HP-MPI applications
Chapter 6206
• Application binaries are available on the necessary remote hosts and
are executable on those machines
•The -sp option is passed to mpirun to set the target shell PATH
environment variable. You can set this option in your appfile
• The .cshrc file does not contain tty commands such as stty if you
are using a /bin/csh-based shell
Starting on Windows
When starting multihost applications using Windows CCS:
• Don't forget the -ccp flag.
• Use UNC paths for your file names. Drives are usually not mapped
on remote nodes.
• If using the AutoSubmit feature, make sure you are running from a
mapped network drive and don't specify file paths for binaries.
HP-MPI will convert the mapped drive to a UNC path and set
MPI_WORKDIR to your current directory. If you are running on a local
drive, HP-MPI cannot map this to a UNC path.
• Don't submit any scripts or commands which require a command
window. These commands usually fail when trying to 'change
directory' to a UNC path.
• Don't forget to quote any filenames or commands with paths that
have spaces. The default HP-MPI install location includes spaces:
"C:\Program Files (x86)\Hewlett-Packard\HP-MPI\bin\mpirun"
OR
"%MPI_ROOT%\bin\mpirun"
When starting multihost applications using appfiles on Windows
2003/XP, make sure that:
• HP-MPI Remote Launch service is registered and started on all
remote nodes. Check this by accessing the list of Windows services
through Administrator Tools -> Services. Look for the 'HP-MPI
Remote Launch' service.
• HP-MPI is installed in the same location on all remote nodes. All
HP-MPI libraries and binaries must be in the same MPI_ROOT.