[lustre-discuss] Issue with lnet showing network down lustre 2.5.3

[Patrick Farrell]

I would suggest, if you haven't, unloading the modules, uninstalling the RPMs, rebooting, and then reinstalling and trying again.  The simplest explanation is still that something is confused.  That may not help, but it's worth a shot.
________________________________________
From: lustre-discuss [lustre-discuss-bounces at lists.lustre.org] on behalf of Kurt Strosahl [strosahl at jlab.org]
Sent: Thursday, May 28, 2015 9:15 AM
To: Mohr
Cc: lustre-discuss at lists.lustre.org
Subject: Re: [lustre-discuss] Issue with lnet showing network down lustre 2.5.3

Hi,

The problems persisted through a reboot.

w/r,
Kurt

----- Original Message -----
From: "Mohr" <rmohr at utk.edu>
To: "Kurt Strosahl" <strosahl at jlab.org>
Cc: lustre-discuss at lists.lustre.org
Sent: Thursday, May 28, 2015 10:00:27 AM
Subject: Re: [lustre-discuss] Issue with lnet showing network down lustre 2.5.3

> On May 28, 2015, at 9:27 AM, Kurt Strosahl <strosahl at jlab.org> wrote:
>
>   I've encountered an unusual issue when upgrading a lustre client from 1.8.7 to 2.5.3.  The client installed, but when I start the lnet service it does not come up (all the modules load).  When I run a service lnet status it shows the following error:
>
> sudo service lnet status
> cat: /proc/sys/lnet/routes: No such file or directory
> loaded

I have run into situations before where I have upgraded Lustre (or tried to reload the Lustre modules with the system up), but the Lustre entries in /proc were messed up.  It has not happened very often, and in some of the cases, the system still seemed to be working properly.  In order to clear it up, I just had to reboot the node.

--
Rick Mohr
Senior HPC System Administrator
National Institute for Computational Sciences
http://www.nics.tennessee.edu
_______________________________________________
lustre-discuss mailing list
lustre-discuss at lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org