[lustre-discuss] exec start error for lustre-2.10.1_13_g2ee62fb
David Rackley
rackley at jlab.org
Fri Oct 13 05:50:29 PDT 2017
That was it! Thanks for the help.
----- Original Message -----
From: "Chris Horn" <hornc at cray.com>
To: "David Rackley" <rackley at jlab.org>, lustre-discuss at 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 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 script and try to restart lnet with systemctl.
Chris Horn
On 10/12/17, 3:39 PM, "lustre-discuss on behalf of David Rackley" <lustre-discuss-bounces at lists.lustre.org on behalf of rackley at jlab.org> wrote:
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 is:
-- Unit lnet.service has begun starting up.
Oct 12 13:21:53 kernel: libcfs: loading out-of-tree module taints kernel.
Oct 12 13:21:53 kernel: libcfs: module verification failed: signature and/or required key missing - tainting kernel
Oct 12 13:21:53 kernel: LNet: HW NUMA nodes: 1, HW CPU cores: 20, npartitions: 1
Oct 12 13:21:53 kernel: alg: No test for adler32 (adler32-zlib)
Oct 12 13:21:53 kernel: alg: No test for crc32 (crc32-table)
Oct 12 13:21:54 kernel: LNet: Using FMR for registration
Oct 12 13:21:54 lctl[135556]: LNET configured
Oct 12 13:21:54 kernel: LNet: Added LNI 172.17.1.92 at o2ib [8/256/0/180]
Oct 12 13:21:54 systemd[135576]: Failed at step EXEC spawning /usr/sbin/lustre_routes_config: Exec format error
-- Subject: Process /usr/sbin/lustre_routes_config could not be executed
-- Defined-By: systemd
-- Support: https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.freedesktop.org_mailman_listinfo_systemd-2Ddevel&d=DwIGaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=YRHhjew1k3Uquj64NMeoZQ&m=7w3NFNrR4nh8bmAIIuotD49Y2GvHoyAo981ZUHbvgg0&s=kxN1qf1rXRld4fZDxONppI9l8fdxJMzBaBeyDdejaEM&e=
--
-- The process /usr/sbin/lustre_routes_config could not be executed and failed.
--
-- The error number returned by this process is 8.
Oct 12 13:21:54 systemd[1]: lnet.service: main process exited, code=exited, status=203/EXEC
Oct 12 13:21:54 systemd[1]: Failed to start lnet management.
-- Subject: Unit lnet.service has failed
-- Defined-By: systemd
-- Support: https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.freedesktop.org_mailman_listinfo_systemd-2Ddevel&d=DwIGaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=YRHhjew1k3Uquj64NMeoZQ&m=7w3NFNrR4nh8bmAIIuotD49Y2GvHoyAo981ZUHbvgg0&s=kxN1qf1rXRld4fZDxONppI9l8fdxJMzBaBeyDdejaEM&e=
--
-- Unit lnet.service has failed.
--
-- The result is failed.
Any ideas?
_______________________________________________
lustre-discuss mailing list
lustre-discuss at lists.lustre.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.lustre.org_listinfo.cgi_lustre-2Ddiscuss-2Dlustre.org&d=DwIGaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=YRHhjew1k3Uquj64NMeoZQ&m=7w3NFNrR4nh8bmAIIuotD49Y2GvHoyAo981ZUHbvgg0&s=opi5sgY77yi4mGI8B6DTWf48swoFn6Ifqkz1ThO763s&e=
More information about the lustre-discuss
mailing list