Product specifications
Table Of Contents
- Table of Contents
- 1 Introduction
- 2 Feature Overview
- 3 Step-by-Step Cluster Setup and MPI Usage Checklists
- 4 InfiniPath Cluster Setup and Administration
- Introduction
- Installed Layout
- Memory Footprint
- BIOS Settings
- InfiniPath and OpenFabrics Driver Overview
- OpenFabrics Drivers and Services Configuration and Startup
- Other Configuration: Changing the MTU Size
- Managing the InfiniPath Driver
- More Information on Configuring and Loading Drivers
- Performance Settings and Management Tips
- Host Environment Setup for MPI
- Checking Cluster and Software Status
- 5 Using QLogic MPI
- Introduction
- Getting Started with MPI
- QLogic MPI Details
- Use Wrapper Scripts for Compiling and Linking
- Configuring MPI Programs for QLogic MPI
- To Use Another Compiler
- Process Allocation
- mpihosts File Details
- Using mpirun
- Console I/O in MPI Programs
- Environment for Node Programs
- Environment Variables
- Running Multiple Versions of InfiniPath or MPI
- Job Blocking in Case of Temporary InfiniBand Link Failures
- Performance Tuning
- MPD
- QLogic MPI and Hybrid MPI/OpenMP Applications
- Debugging MPI Programs
- QLogic MPI Limitations
- 6 Using Other MPIs
- A mpirun Options Summary
- B Benchmark Programs
- C Integration with a Batch Queuing System
- D Troubleshooting
- Using LEDs to Check the State of the Adapter
- BIOS Settings
- Kernel and Initialization Issues
- OpenFabrics and InfiniPath Issues
- Stop OpenSM Before Stopping/Restarting InfiniPath
- Manual Shutdown or Restart May Hang if NFS in Use
- Load and Configure IPoIB Before Loading SDP
- Set $IBPATH for OpenFabrics Scripts
- ifconfig Does Not Display Hardware Address Properly on RHEL4
- SDP Module Not Loading
- ibsrpdm Command Hangs when Two Host Channel Adapters are Installed but Only Unit 1 is Connected to the Switch
- Outdated ipath_ether Configuration Setup Generates Error
- System Administration Troubleshooting
- Performance Issues
- QLogic MPI Troubleshooting
- Mixed Releases of MPI RPMs
- Missing mpirun Executable
- Resolving Hostname with Multi-Homed Head Node
- Cross-Compilation Issues
- Compiler/Linker Mismatch
- Compiler Cannot Find Include, Module, or Library Files
- Problem with Shell Special Characters and Wrapper Scripts
- Run Time Errors with Different MPI Implementations
- Process Limitation with ssh
- Number of Processes Exceeds ulimit for Number of Open Files
- Using MPI.mod Files
- Extending MPI Modules
- Lock Enough Memory on Nodes When Using a Batch Queuing System
- Error Creating Shared Memory Object
- gdb Gets SIG32 Signal Under mpirun -debug with the PSM Receive Progress Thread Enabled
- General Error Messages
- Error Messages Generated by mpirun
- MPI Stats
- E Write Combining
- F Useful Programs and Files
- G Recommended Reading
- Glossary
- Index

D–Troubleshooting
QLogic MPI Troubleshooting
D-20 IB6054601-00 H
S
See “Compiler Cannot Find Include, Module, or Library Files” on page D-15,
“Compiling on Development Nodes” on page D-16, and “Specifying the Run-time
Library Path” on page D-16 for additional information.
Process Limitation with ssh
MPI jobs that use more than eight processes per node may encounter an ssh
throttling mechanism that limits the amount of concurrent per-node connections
to 10. If you have this problem, a message similar to this appears when using
mpirun:
$ mpirun -m tmp -np 11 ~/mpi/mpiworld/mpiworld
ssh_exchange_identification: Connection closed by remote host
MPIRUN: Node program(s) exitted during connection setup
If you encounter a message like this, you or your system administrator should
increase the value of MaxStartups in your sshd configurations.
Number of Processes Exceeds ulimit for Number of Open
Files
When users scale up the number of processes beyond the number of open files
allowed by ulimit, mpirun will print an error message. The ulimit for the
number of open files is typically 1024 on both Red Hat and SLES systems. The
message will look similar to:
MPIRUN.up001: Warning: ulimit for the number of open files is only
1024, but this mpirun request requires at least <number of files>
open files (sockets). The shell ulimit for open files needs to be
increased.
This is due to limit:
descriptors 1024
The ulimit can be increased; QLogic recommends an increase of
approximately 20 percent over the number of CPUs. For example, in the case of
2048 CPUs, ulimit can be increased to 2500:
ulimit -n 2500
The ulimit needs to be increased only on the host where mpirun was started,
unless the mode of operation allows mpirun from any node.
NOTE:
This limitation applies only if -distributed=off is specified. By default,
with -distributed=on, you will not normally have this problem.