Nothing better than sliding in at the last moment to steal all the glory ;-)

—Jeff

On Wed, Sep 27, 2023 at 07:10 Jan Andersen <j...@comind.io> wrote:

> Hi Jeff,
>
> Yes, that was it! Things are working beautifully now - big thanks.
>
> /jan
>
> On 27/09/2023 15:07, Jeff Johnson wrote:
> > Any chance the firewall is running?
> >
> > You can use `lctl ping ipaddress@lnet` to check if you have functional
> > lnet between machines. Example `lctl ping 10.0.0.10@tcp`
> >
> > —Jeff
> >
> > On Wed, Sep 27, 2023 at 05:35 Jan Andersen <j...@comind.io
> > <mailto:j...@comind.io>> wrote:
> >
> >     However, it is still timing out when I try to mount on the oss. This
> is
> >     the kernel module:
> >
> >     [root@mds ~]# lsmod | grep lnet
> >     lnet                  704512  7
> mgs,obdclass,osp,ptlrpc,mgc,ksocklnd,mdt
> >     libcfs                266240  15
> >
>  
> fld,lnet,fid,lod,mdd,mgs,obdclass,osp,ptlrpc,mgc,ksocklnd,mdt,osd_ldiskfs,lquota,lfsck
> >     sunrpc                577536  2 lnet
> >
> >     But it only listens on tcp6, which I don't use - is there a way to
> for
> >     it to use tcp4?
> >
> >     [root@mds ~]# netstat -nap | grep 988
> >     tcp6       0      0 :::988                  :::*
> >     LISTEN      -
> >
> >     /jan
> >
> >     On 27/09/2023 10:15, Jan Andersen wrote:
> >      > Hi Rick,
> >      >
> >      > Very strange - when I started the vm this morning, 'modprobe lnet'
> >      > didn't return an error - and it seems to have loaded the module:
> >      >
> >      > [root@rocky8 ~]# lsmod | grep lnet
> >      > lnet                  704512  0
> >      > libcfs                266240  1 lnet
> >      > sunrpc                577536  2 lnet
> >      >
> >      > Looking at the running kernel and the kernel source, they now
> >     seem to be
> >      > the same version:
> >      >
> >      > [root@rocky8 ~]# ll /usr/src/kernels
> >      > total 4
> >      > drwxr-xr-x. 23 root root 4096 Sep 26 12:34
> >     4.18.0-477.27.1.el8_8.x86_64/
> >      > [root@rocky8 ~]# uname -r
> >      > 4.18.0-477.27.1.el8_8.x86_64
> >      >
> >      > - which would explain that it now works. Things were a bit hectic
> >     with
> >      > other things yesterday afternoon, and I don't quite remember
> >     installing
> >      > a new kernel, but it looks like I did. Hopefully this is my
> problem
> >      > solved, then - sorry for jumping up and down and making noise!
> >      >
> >      > /jan
> >      >
> >      > On 26/09/2023 18:13, Mohr, Rick wrote:
> >      >> What error do you get when you run "modprobe lnet"?
> >      >>
> >      >> --Rick
> >      >>
> >     _______________________________________________
> >     lustre-discuss mailing list
> >     lustre-discuss@lists.lustre.org <mailto:
> lustre-discuss@lists.lustre.org>
> >     http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
> >     <http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org>
> >
>
_______________________________________________
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Reply via email to