[lustre-discuss] lnet.service reporting failure on start

[Patrick Farrell]

This is correct, and normal.  It’s not really a failure (in the sense of a being a problem), it’s just that you’re using modules that aren’t signed with the key used by your kernel vendor.  In general, if you’re getting third party modules (ie not from your kernel vendor), this happens, because the point of the signing is your kernel vendor verifying/certifying the module is theirs, and, well, it’s not.

A version of this message has probably been present every time you’ve loaded Lustre since you first used a kernel with signing enabled, which I think came in somewhere in the kernels used by RHEL6/SLES11, so some years back.

Nothing to worry about.
________________________________
From: lustre-discuss <lustre-discuss-bounces at lists.lustre.org> on behalf of Shaun Tancheff <stancheff at cray.com>
Sent: Monday, June 24, 2019 4:21:18 PM
To: Kurt Strosahl; lustre-discuss at lists.lustre.org
Subject: Re: [lustre-discuss] lnet.service reporting failure on start


My understanding, in general terms, is that the messages:



[   26.653699] libcfs: loading out-of-tree module taints kernel.

[   26.665567] libcfs: module verification failed: signature and/or required key missing - tainting kernel



Suggests that the libcfs.ko kernel module is not signed.



Note that kernel module signing is different from the rpm package signing.



From: lustre-discuss <lustre-discuss-bounces at lists.lustre.org> on behalf of Kurt Strosahl <strosahl at jlab.org>
Date: Monday, June 24, 2019 at 3:03 PM
To: "lustre-discuss at lists.lustre.org" <lustre-discuss at lists.lustre.org>
Subject: [lustre-discuss] lnet.service reporting failure on start



Good Afternoon,



    I recently stood up a new lustre client, when I run systemctl start lnet.service systemd reports a failure.  However an lnetctl net show displays all the right information and I can reach other nodes with lclt ping.  Further the lustre file system mounts properly.



Looking in dmesg I see right as the lnet service starts to mount the following:



[   26.653699] libcfs: loading out-of-tree module taints kernel.

[   26.665567] libcfs: module verification failed: signature and/or required key missing - tainting kernel

[   26.683188] LNet: HW NUMA nodes: 1, HW CPU cores: 8, npartitions: 2

[   26.725826] alg: No test for adler32 (adler32-zlib)

[   27.674142] Lustre: Lustre: Build Version: 2.10.7



The system is RHEL 7.6 kernel 3.10.0-957.21.2.el7.x86_64

lustre-client-dkms-2.10.7-1.el7.noarch

lustre-client-2.10.7-1.el7.x86_64



Has anyone seen this message or knows what might be causing it, or be able to suggest why systemd is reporting a failure even though it clearly works.



w/r,

Kurt J. Strosahl
System Administrator: Lustre, HPC
Scientific Computing Group, Thomas Jefferson National Accelerator Facility
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20190624/54a3c6db/attachment-0001.html>