From nobody Tue May 23 00:54:07 2023 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QQG6g6qk3z4Ch00 for ; Tue, 23 May 2023 00:54:19 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yw1-x112f.google.com (mail-yw1-x112f.google.com [IPv6:2607:f8b0:4864:20::112f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QQG6g3vp5z3HFp for ; Tue, 23 May 2023 00:54:19 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-561b50c1856so88905337b3.0 for ; Mon, 22 May 2023 17:54:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684803258; x=1687395258; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=DoByJBLES/QXjrgbG8SGBpHRtQ56ALR0rYC0ZoydsjI=; b=sD77Ew1DuzoaL3B98hoW80Te7eMMdNQauQrWj6/ov48WE+qdX93/rC/3MtCZfnTYJg wRcs5dmh/c4TePsz0JJuTtLmIU34VYjHgtiRxjB3v0gpiyGDSD+yYyyu+nvu9OVt7uk1 RNPl0180j05//FxrStAW4vT4oMY88cOrfphQzVJfvbEHWmdalDNT2+6c4Q6Gk1nHe/86 Z/IIOFyN1tOUK9o9wVRaXF1ppoCbodFz0K/+2u+6+of+pgSpoClcsHx6lvtw9O53qmkf RDiR5G0JB6qCQBBtVnwnLkNLFIiiTbs9ru57/03EzLJhE5Pai2oVMyH6V2Xb4UBOEeO4 DMkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684803258; x=1687395258; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=DoByJBLES/QXjrgbG8SGBpHRtQ56ALR0rYC0ZoydsjI=; b=RowqeRAV5u0RwgNwDmbRuv4pmM58USa3hCJJh93iM2sWVMKjpOdrl+SdOv6hrsvNPQ oaDndr70nE2VxWgJZ96dOKMzFd2oISpJ6vD/t5OnE2dzAQ9eUfIYT5eJ/23xakcwOEml 9zkLXhVFdMOh11sUQYpvXFkFMTlQAMIpygSxFLHGhDzqsVvsHMKivsANQknBY519ab9c hAmN0Tk5zcR21NcciU1XCXTolHy8P2U5LpCEwp5gF9oaeYGT3VsxxxOYfE7wv2RCg/Sk 0ehKQvFJqUtpELmHZv9A4TLEVI0OkOyMHSM/U2jcGJ7Iow/wDxZfKn3/FKQj0334Vjme trUQ== X-Gm-Message-State: AC+VfDyQPKn1f9cWYQrILXnOYTmttxq8NJ7QwG7wFAvliQ24CCzip/yw FiG3sp8/XN2/gSpKFj4HI/Ro23l4kdDKYZCFNTsq2Zz8 X-Google-Smtp-Source: ACHHUZ42Gz6dcXKN10Rb4c4c3z8HZeHsY3togPbRw+40nS0/RmGBuZclZOLIorbckYKOR/mfDxF7icfRshVbOXoJ5b4= X-Received: by 2002:a0d:ca48:0:b0:561:afdd:3830 with SMTP id m69-20020a0dca48000000b00561afdd3830mr11690841ywd.26.1684803258534; Mon, 22 May 2023 17:54:18 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 References: <2340d01b-7c75-045e-7b35-27eff9bed1f7@qeng-ho.org> In-Reply-To: <2340d01b-7c75-045e-7b35-27eff9bed1f7@qeng-ho.org> From: Kevin Oberman Date: Mon, 22 May 2023 17:54:07 -0700 Message-ID: Subject: Re: System reports libelf.so.1 finds libedit.so.8 not proper layout? To: Arthur Chance Cc: "freebsd-questions@freebsd.org" Content-Type: multipart/alternative; boundary="000000000000bdd18b05fc51d3c3" X-Rspamd-Queue-Id: 4QQG6g3vp5z3HFp X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000bdd18b05fc51d3c3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks so much! I'm back up and online. I should have thought of it as I remember how I thought it was a great idea and it was. For the record, something happened to the ld-elf.so.hints file. It contained only lib32 entries. Restored from backup and the system booted up normally. On Mon, May 22, 2023, 00:13 Arthur Chance wrote: > On 22/05/2023 06:18, Kevin Oberman wrote: > > My month-old server has died with a baffling error. It boots to the > > prompt to enter the shell (default: /bin/sh). Entering anything returns= : > > libelf.so.1: /usr/lib32/libedit.20.8: unsupported file layout > > > > As there is no way to enter any command without a shell, I can't > > proceed. This baffles me. > > Have you tried using /rescue/sh (or /rescue/{csh,tcsh) depending on > taste)? The /rescue programs are statically linked so should work. > > -- > We build our computer systems the way we build our cities; over time, > without a plan, on top of ruins. > =E2=80=94 Ellen Ullman > > --000000000000bdd18b05fc51d3c3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks so much! I'm back up and online. I should have= thought of it as I remember how I thought it was a great idea and it was.<= div dir=3D"auto">
For the record, something happ= ened to the ld-elf.so.hints file. It contained only lib32 entries. Restored= from backup and the system booted up normally.

On Mon, May 22, 2023= , 00:13 Arthur Chance <freebsd@qe= ng-ho.org> wrote:
On 22/05= /2023 06:18, Kevin Oberman wrote:
> My month-old server has died with a baffling error. It boots to the > prompt to enter the shell (default: /bin/sh). Entering anything return= s:
> libelf.so.1:=C2=A0 /usr/lib32/libedit.20.8: unsupported file layout >
> As there is no way to enter any command without a shell, I can't > proceed. This baffles me.

Have you tried using /rescue/sh (or /rescue/{csh,tcsh) depending on
taste)? The /rescue programs are statically linked so should work.

--
We build our computer systems the way we build our cities; over time,
without a plan, on top of ruins.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =E2=80=94 Ellen Ullman

--000000000000bdd18b05fc51d3c3--