Getting Help

If you have a bug report and/or patch for Open MPI, you should probably subscribe to the Open MPI developer's list and post it there. Open MPI uses Trac for its bug tracking (see the "Bug Tracking" link in the left-hand navigation), but only developers are allowed to open new tickets (mainly as an artifact of our SVN+Trac authentication system; it's never been a big enough issue for us to figure out how to issue non-developer/Trac-only accounts).

If you have a problem or question, it is highly recommended that you execute the following steps in order. Many people have similar problems with configuration and initial setup of Open MPI -- it is possible that your question has already been answered.

1. Check the Open MPI FAQ. We generally take the approach that if the same question comes up multiple times, we put it on the FAQ.

2. Check the mailing list archives. Use the "search" features to check old posts and see if others have asked the same question and had it answered.

3. If you do not find a solution to your problem in the above resources, send the following information to the Open MPI user's mailing list (see the mailing lists page for more information) -- please compress the files before sending them! Note that the mailing lists have a 100kb limit on messages to prevent from sending enormous, uncompressed datatsets.

   • Remember: the more information you include in your report, the better. E-mails simply stating, "It doesn't work!" are not helpful; we need to know as much information about your environment as possible in order to provide meaningful assistance. The best way to get help is to provide a "recipie" for reproducing the problem. This will allow the Open MPI developers to see the error for themselves, and therefore be able to fix it.

   • For run-time problems:
     1. Check the FAQ first. Really. This can save you a lot of time; many common problems and solutions are listed there.
     2. The config.log file from the top-level Open MPI directory, if available (please compress!).
     3. The output of the "ompi_info --all" command.
     4. A detailed description of what is failing. The more details that you provide, the better. E-mails saying "My application doesn't work!" will inevitably be answered with requests for more information about exactly what doesn't work; so please include as much information detailed in your initial e-mail as possible. We strongly recommend that you include the following information:
        • The exact command used to run your application.
        • Any relevant MCA parameters that were set (or unset) when you ran (from either the command line, environment, parameter file, etc.).
        • The value of the PATH and LD_LIBRARY_PATH environment variables (did you set them correctly to point to all relevant executables, the Open MPI libraries, and any required support libraries, such as libraries required for high-speed networks such as InfiniBand and/or Myrinet?).
     5. Please include information about your network:
        • For Myrinet-based networks, include the information listed in this FAQ entry.
        • For InfiniBand-based networks, include the information listed in this FAQ entry.
        • For TCP-based networks, include the output of the ifconfig command on all relevant nodes. Note that some Linux distributions do not put ifconfig in the default PATH of normal users; look for it in /sbin/ifconfig or /usr/sbin/ifconfig.

   • For compile problems:
     1. All output (both compilation output and run time output, including all error messages)
     2. Output from when you ran "./configure" to configure Open MPI (please compress!)
     3. The config.log file from the top-level Open MPI directory (please compress!)
     4. Output from when you ran "make" to build Open MPI (please compress!)
     5. Output from when you ran "make install" to install Open MPI (please compress!)

   To capture the output of the configure and make steps you can use the script command or the following technique if using a csh style shell:

   shell% ./configure {options} |& tee config.out shell% make all |& tee make.out shell% make install |& tee make-install.out

   or if using a Bourne style shell:

   shell$ ./configure {options} 2>&1 | tee config.out shell$ make all 2>&1 | tee make.out shell$ make install 2>&1 | tee make-install.out

   To compress all the files listed above, we recommend using the tar and gzip commands. For example (using a csh-style shell):

   shell% mkdir $HOME/ompi-output shell% cd /path/to/ompi-1.3 shell% ./configure |& tee $HOME/ompi-output/configure.out #...lots of output... shell% cp config.log share/include/ompi_config.h $HOME/ompi-output shell% make all |& tee $HOME/ompi-output/make.out #...lots of output... shell% make install |& tee $HOME/ompi-output/make-install.out #...lots of output... shell% cd $HOME shell% tar cvf ompi-output.tar ompi-output #...lots of output... shell% gzip ompi-output.tar

   Then send the resulting ompi-output.tar.gz file to the mailing list.

   If you are using an sh-style shell:

   shell$ mkdir $HOME/ompi-output shell$ cd /path/to/ompi-1.3 shell$ ./configure 2>&1 | tee $HOME/ompi-output/configure.out #...lots of output... shell$ cp config.log share/include/ompi_config.h $HOME/ompi-output shell$ make all 2>&1 | tee $HOME/ompi-output/make.out #...lots of output... shell$ make install 2>&1 | tee $HOME/ompi-output/make-install.out #...lots of output... shell$ cd $HOME shell$ tar cvf ompi-output.tar ompi-output #...lots of output... shell$ gzip ompi-output.tar

   Then send the resulting ompi-output.tar.gz file to the mailing list.

Make today an Open MPI day!