search for: socklnd

...gured in /etc/modprobe.conf.local as below. options lnet networks=tcp0(eth0) accept=all For loading lustre module i tried including lustre module in the variable MODULES_LOADED_ON_BOOT using yast2 sysconfig . But still it is not getting loaded. Error from dmesg is as below. LustreError: 1393:0:(socklnd.c:2543:ksocknal_enumerate_interfaces()) Can''t enumerate interfaces: 0 LustreError: 105-4: Error -100 starting up LNI tcp LustreError: 1393:0:(events.c:725:ptlrpc_init_portals()) network initialisation failed Currently this is present in the VM. Kindly suggest. Regards, Prasad -----------...

Hi, I would like to know what TCP/UDP ports should i keep open in my firewall policies on my MGS server such that I can have my MGS server fire-walled. Also if in a event of loss of MGT would it be possible to recreate the MGT without loosing data or bringing the filesystem down (i.e. by using cached information from MDT''s and OST''s) Thanks Anand

Greetings! I am working with Lustre-2.1.2 on RHEL 6.2. First I configured it using the standard defaults over TCP/IP. Everything worked very nicely usnig a real, static --mgsnode=a.b.c.x value which was the actual IP of the MGS/MDS system1 node. I am now trying to integrate it with Pacemaker-1.1.7. I believe I have most of the set-up completed with a particular exception. The "lctl

....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 i...