search for: socklnd_cb

Dear, everyone We have stuck with the problem that the OSS connect one dead client or one with changed IP address all the time until we reboot the dead client. From the OSS log message, we can get the information as follows: Jul 7 14:45:07 com01 kernel: Lustre: 12180:0:(socklnd_cb.cLustre: 12180:0:(socklnd_cb.c:915:ksocknal_launch_packet()) No usable routes to 12345-202.Lustre: 12180:0:(socklnd_cb.c:915:ksocknal_launch_packet()) No usable routes to 12345-202.122.37.79 at tcp Jul 7 14:45:07 com01 kernel: Lustre: 12180:0:(socklnd_cb.c:915:ksocknal_launch_packet()) No usable r...

...treError: 4567:0:(acceptor.c:442:lnet_acceptor()) Error -11 reading connection request from 192.168.0.13 Feb 22 03:26:04 node4 kernel: LustreError: 4567:0:(acceptor.c:442:lnet_acceptor()) Error -11 reading connection request from 192.168.0.179 Feb 22 03:26:04 node4 kernel: LustreError: 4564:0:(socklnd_cb.c:2160:ksocknal_recv_hello()) Error -11 reading HELLO from 192.168.0.139 Feb 22 03:26:09 node4 kernel: LustreError: 4567:0:(acceptor.c:442:lnet_acceptor()) Error -11 reading connection request from 192.168.0.120 Feb 22 03:26:13 node4 kernel: LustreError: 4567:0:(acceptor.c:442:lnet_acceptor())...

....80 at tcp>: Input/output error The following is in /var/log/messages Jan 15 17:18:15 dint0001 kernel: LustreError: 120-3: Refusing connection from 192.168.135.80 for 192.168.135.80 at tcp<mailto:192.168.135.80 at tcp>: No matching NI Jan 15 17:18:15 dint0001 kernel: LustreError: 3251:0:(socklnd_cb.c:2167:ksocknal_recv_hello()) Error -104 reading HELLO from 192.168.135.80 Jan 15 17:18:15 dint0001 kernel: LustreError: 11b-b: Connection to 192.168.135.80 at tcp<mailto:192.168.135.80 at tcp> at host 192.168.135.80 on port 988 was reset: is it running a compatible version of Lustre and is 1...