[Lustre-discuss] failed to start lustre: problem with port 988

neutron neutronsharc at gmail.com
Sat Nov 29 22:14:20 PST 2008


hi all,

 I m using  Lustre 2.6.18-53.1.13.el5_lustre.1.6.4.3smp.    I sometime
ran into a problem when starting lustre FS.   For example, I  usually
failed to start an OSS with some error messages appear in
/var/log/messages, like:

------------------
Nov 30 01:04:31 wci66 kernel: Lustre: Added LNI 172.16.0.67 at o2ib [8/64]
Nov 30 01:04:31 wci66 kernel: Lustre: Added LNI 172.16.0.67 at tcp [8/256]
Nov 30 01:04:31 wci66 kernel: LustreError:
7288:0:(linux-tcpip.c:554:libcfs_sock_listen()
) Can't create socket: port 988 already in use
Nov 30 01:04:31 wci66 kernel: LustreError: 122-1: Can't start acceptor
on port 988: port
already in use
Nov 30 01:04:32 wci66 kernel: Lustre: Removed LNI 172.16.0.67 at o2ib
Nov 30 01:04:33 wci66 kernel: Lustre: Removed LNI 172.16.0.67 at tcp
Nov 30 01:04:33 wci66 kernel: LustreError:
7204:0:(events.c:654:ptlrpc_init_portals()) ne
twork initialisation failed
Nov 30 01:04:33 wci66 modprobe: WARNING: Error inserting ptlrpc
(/lib/modules/2.6.18-53.1
.13.el5_lustre.1.6.4.3smp/kernel/fs/lustre/ptlrpc.ko): Input/output error
Nov 30 01:04:33 wci66 kernel: mdc: Unknown symbol ldlm_prep_enqueue_req
Nov 30 01:04:33 wci66 kernel: mdc: Unknown symbol ldlm_resource_get
------------------------

It seems that Lustre modules need port 988 but the port is already
used by others.  But at that time "netstat -nap"  shows no proc is
using that port.
Is Lustre statically bound to the port 988?  Or is there anywhere I
can change the configuration so that Lustre doesn't rely on a
statically fixed port?   Thanks.



More information about the lustre-discuss mailing list