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