'mpiexec -idb' fails to start the Intel GUI debugger correctly

Wed, 17 Jun 2009 11:42:09 -0700

Reference Number : DPD200136769

Version : Intel MPI 3.x, Intel C++ Linux compiler 11.x, Intel Fortran Linux compiler 11.x

Operating System : Linux

Problem Description : This is only an issue on Linux systems using Intel® 64 architecture-based processors. On such systems, the IDB debugger included with the Intel C++ and Fortran 11.x compilers runs in GUI mode by default. If you launch an MPI job under the debugger's control, for example, with 'mpiexec -idb -n number_of_processes mpi_application_name', the IDB GUI and a console will come up, but neither can effectively be used to debug the MPI application.

A possible workaround is to rename idb, and then make idb a symbolic link the idbc, the command line IDB.
In the IDB_HOME directory (by default, the location is /opt/intel/Compiler/11.x//bin/intel64), please do:
mv idb idbgui
ln -s idbc idb

As always, be sure to set environment variable IDB_HOME to the location of the IDB binaries, and set MPIEXEC_DEBUG=1 before launching a debugging session.

Resolution Status : This issue may be resolved in a future version of Intel IDB for Linux

[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]

Master node issue

Fri, 23 Jan 2009 12:12:46 -0800

Issue

I have a cluster, which has for example 3 nodes, where the mpd.hosts file contains:

$ cat mpd.hosts
node2
node3

The master node, which is node1 is not listed in the mpd.hosts file. The shell commands:

$ mpdboot -r ssh -n 2 -f ~/mpd.hosts
$ mpiexec -n 4 /bin/hostname

which are issued from node1 reveal the following:

node1
node1
node2
node2

Solution

By design, the master node (i.e., the node where the mpiexec command is launched from) needs to have a daemon running. If you want to run your application on node2 and node3, you can use the -host options with the mpiexec command as follows:

$ mpdboot -r ssh -n 3 -f ~/mpd.hosts
$ mpiexec -n 2 -host node2 /bin/hostname : -n 2 -host node3 /bin/hostname

Or simply to use the -nolocal option for mpiexec as follows:

$ mpdboot -r ssh -n 3 -f ~/mpd.hosts
$ mpiexec -nolocal -n 4 /bin/hostname

This will run the hostname command on nodes node2 and node3 only, even though there are three mpd daemons total.

Intel Software Network articles feed

'mpiexec -idb' fails to start the Intel GUI debugger correctly

Master node issue