b.org>, lustre-discuss@lists.lustre.org
> Sent: Thursday, October 12, 2017 5:02:47 PM
> Subject: Re: [lustre-discuss] exec start error for
lustre-2.10.1_13_g2ee62fb
>
> Google suggests that this error message has been associated with a
missing “hashpling” in some
t;Chris Horn" <ho...@cray.com>
> To: "David Rackley" <rack...@jlab.org>, lustre-discuss@lists.lustre.org
> Sent: Thursday, October 12, 2017 5:02:47 PM
> Subject: Re: [lustre-discuss] exec start error for lustre-2.10.1_13_g2ee62fb
>
> Google suggests that this
That was it! Thanks for the help.
- Original Message -
From: "Chris Horn" <ho...@cray.com>
To: "David Rackley" <rack...@jlab.org>, lustre-discuss@lists.lustre.org
Sent: Thursday, October 12, 2017 5:02:47 PM
Subject: Re: [lustre-discuss] exec start err
Google suggests that this error message has been associated with a missing
“hashpling” in some cases. The lustre_routes_config script has “# !/bin/bash”,
and I wonder if that space before the “!” isn’t the culprit?
Just a guess. You might try to remove that space from the lustre_routes_config
Greetings,
I have built lustre-2.10.1_13_g2ee62fb on 3.10.0-693.2.2.el7.x86_64 RHEL
Workstation release 7.4 (Maipo).
After installation of kmod-lustre-client-2.10.1_13_g2ee62fb-1.el7.x86_64.rpm
and lustre-client-2.10.1_13_g2ee62fb-1.el7.x86_64.rpm the lnet startup fails.
The error reported
