From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Feedback on Core Update 155 Testing Date: Wed, 17 Mar 2021 15:52:53 +0000 Message-ID: <568F1C49-2BB0-42B4-9E2D-F9A0F9D23EDA@ipfire.org> In-Reply-To: <4d4c90ac-087e-1e65-f34e-ae7d512e1469@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4419564622690979239==" List-Id: --===============4419564622690979239== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, > On 17 Mar 2021, at 09:35, Adolf Belka wrote: >=20 > Dear all, >=20 > There is feedback on the forum about IPFire not rebooting after update and = needing a soft reset. After that it boots again. I also found the same effect= on my VM testbed system for testing. >=20 > https://community.ipfire.org/t/feedback-core-update-155-testing/4896 >=20 > That symptom triggered my memory (a bit late) and I found the discussion ab= out my sysvinit patch. >=20 > https://lists.ipfire.org/pipermail/development/2021-February/009403.html >=20 > So the fix never got created and it did not revert from the update. >=20 > Sorry for this mess. I will do a new patch to hopefully solve that problem = for adding to Core Update 155, or you can revert sysvinit and I will make the= update for the following Core Update. No worries. I would only blame myself for forgetting to find a solution for t= his. Arne simply created a symlink which temporarily makes things work again until= the next reboot. After that, things are fine. > I also found the same problem with ssh not working after the update as ment= ioned in the forum post. >=20 > Rebooting gave the following error message in the log. >=20 > /usr/sbin/sshd: /lib/libcrypt.so.1: version `XCRYPT_2.0' not found (require= d by /usr/sbin/sshd) [FAIL] This is another one that I fucked up myself :) I do not know why though, because I tested an earlier version of the update o= n my machine and it worked fine. > People on the forum had deleted the /lib/libcrypt.so.1 link, which was made= to /lib/libcrypt-2.32.so and remade it to /usr/lib/libcrypt.so.1 and they ha= ve reported that ssh then works. I have not tried that fix yet. I suppose Arne tested it and committed it. > I checked the OpenSSH update patch I created and I didn't find anything rel= ated to libcrypt or a change of libcrypt location from /lib to /usr/lib This was part of glibc deprecating libcrypt. Therefore I added a fork which i= s actively maintained. Thanks for looking into these problems. -Michael >=20 >=20 > Regards, >=20 > Adolf >=20 > --=20 > Sent from my laptop >=20 --===============4419564622690979239==--