Make sure not to have old Lustre.conf file in modprobe.d which may load legacy lnet settings
> > On Feb 1, 2019 at 12:32 PM, <Michael Di Domenico > (mailto:[email protected])> wrote: > > > > yes. turns out there must have been something futzy in the system, i > did and lctl net down, a lustre_rmmod, and then systemctl restart > lnet. things seemed to work after that. seems a strange failure > scenario though > > i can't mount the filesystem still, but i think that's a separate issue > > On Fri, Feb 1, 2019 at 3:29 PM Riccardo Veraldi > <[email protected]> wrote: > > > > Did you install yaml > > and yaml-devel ? > > > > > > On Feb 1, 2019 at 12:20 PM, <Michael Di Domenico> wrote: > > > > i'm trying to start an lnet client, but lnet kicks out the config with > > > > a yaml error > > > > > > > > yaml: > > > > - builder: > > > > errno: -1 > > > > descr: failed to handle token:0 [state=3, rc=-5] > > > > > > > > i've compared the lnet.conf on the server i'm testing with another > > > > that is working, they appaer identical (except for some ip addresses), > > > > but i can't locate a problem. > > > > > > > > is there something i can run that might be a little more vocal about > > > > what's broke? > > > > _______________________________________________ > > > > lustre-discuss mailing list > > > > [email protected] > > > > http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org > > >
_______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
