Troubleshooting guide

/var/run/gm_mapper/pid.{board_id}, and the map files are stored in

/var/run/gm_mapper/map.{board_id}.

Further details about the mapper in GM-2 can be found on the following

webpage:

http://www.myri.com/scs/mapper_gm2.html

Refer to the FAQ entry "How can I tell if the GM-2 Mapper has correctly

detected all of the hosts in my Myrinet network?" (http://www.myri.com/cgi-

bin/fom?file=273).

Important note: Stopping the gm_mapper while GM-2 is running is not supported. The

gm_mapper should be left running at all times, and it will not interfere with the

performance of jobs running over Myrinet.

Important note: The gm start script does not configure the IP device. If you wish to run

IP over GM/Myrinet (ethernet emulation), you must configure the device. (Refer to Step

3 of the installation process.)

The ldconfig line in the installation process is optional, and adds the GM library

directory to the system library search path. If you do not do this, individual users will

have to either manage their LD_LIBRARY_PATH environment variable or link their

programs with an -rpath= option for the dynamic linker to locate the GM shared library.

If you wish to have the driver auto-load at boot, you must create appropriate links in the

/etc/rcN directories to the /etc/init.d/gm script, or, for example, use the following

command (for Debian Linux):

update-rc.d gm defaults

or (for RedHat Linux):

chkconfig –add gm

Alternatively, you may start and stop the driver manually using

su root

/etc/init.d/gm start

/etc/init.d/gm stop

su root

/etc/init.d/gm restart

The gm “stop” script performs the following operations: