Date: Mon, 22 May 2023 17:54:07 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: Arthur Chance <freebsd@qeng-ho.org> Cc: "freebsd-questions@freebsd.org" <questions@freebsd.org> Subject: Re: System reports libelf.so.1 finds libedit.so.8 not proper layout? Message-ID: <CAN6yY1sbPA9Uwjorp--xiyRZhfv7F1_XpnqbN10ubCZEqe-EKQ@mail.gmail.com> In-Reply-To: <2340d01b-7c75-045e-7b35-27eff9bed1f7@qeng-ho.org> References: <CAN6yY1vCc23%2BKi9FHb2WVosh0yd707Oj-g1U2WthiG2egz4JDA@mail.gmail.com> <2340d01b-7c75-045e-7b35-27eff9bed1f7@qeng-ho.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <freebsd@qeng-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 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
<div dir=3D"auto">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"><br></div><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.</div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, May 22, 2023=
, 00:13 Arthur Chance <<a href=3D"mailto:freebsd@qeng-ho.org">freebsd@qe=
ng-ho.org</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 22/05=
/2023 06:18, Kevin Oberman wrote:<br>
> My month-old server has died with a baffling error. It boots to the<br=
>
> prompt to enter the shell (default: /bin/sh). Entering anything return=
s:<br>
> libelf.so.1:=C2=A0 /usr/lib32/libedit.20.8: unsupported file layout<br=
>
> <br>
> As there is no way to enter any command without a shell, I can't<b=
r>
> proceed. This baffles me.<br>
<br>
Have you tried using /rescue/sh (or /rescue/{csh,tcsh) depending on<br>
taste)? The /rescue programs are statically linked so should work.<br>
<br>
-- <br>
We build our computer systems the way we build our cities; over time,<br>
without a plan, on top of ruins.<br>
=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<br>
<br>
</blockquote></div>
--000000000000bdd18b05fc51d3c3--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1sbPA9Uwjorp--xiyRZhfv7F1_XpnqbN10ubCZEqe-EKQ>