Lustre 1.6 Operations Manual

22.3.12 Handling/Debugging "Bind: Address already in
use" Error
During startup, Lustre may report a bind: Address already in use error and
reject to start the operation. This is caused by a portmap service (often NFS locking)
which starts before Lustre and binds to the default port 988. You must have port 988
open from firewall or IP tables for incoming connections on the client, OSS, and
MDS nodes. LNET will create three outgoing connections on available, reserved
ports to each client-server pair, starting with 1023, 1022 and 1021.
Unfortunately, you cannot set sunprc to avoid port 988. If you receive this error, do
the following:
■ Start Lustre before starting any service that uses sunrpc.
■ Use a port other than 988 for Lustre. This is configured in /etc/modprobe.conf
as an option to the LNET module. For example:
■
options lnet accept_port=988
Add modprobe ptlrpc to your system startup scripts before the service that
uses sunrpc. This causes Lustre to bind to port 988 and sunrpc to select a different
port.
Note – You can also use the sysctl command to mitigate the NFS client from
grabbing the Lustre service port. However, this is a partial workaround as other
user-space RPC servers still have the ability to grab the port.
22-12 Lustre 1.6 Operations Manual • September 2008