Re: Feedback on Core Update 155 Testing

[Michael Tremer <michael.tremer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 2172 bytes --]

Hello,

> On 17 Mar 2021, at 09:35, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Dear all,
> 
> 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.
> 
> https://community.ipfire.org/t/feedback-core-update-155-testing/4896
> 
> That symptom triggered my memory (a bit late) and I found the discussion about my sysvinit patch.
> 
> https://lists.ipfire.org/pipermail/development/2021-February/009403.html
> 
> So the fix never got created and it did not revert from the update.
> 
> 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 this.

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 mentioned in the forum post.
> 
> Rebooting gave the following error message in the log.
> 
> /usr/sbin/sshd: /lib/libcrypt.so.1: version `XCRYPT_2.0' not found (required 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 on 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 have 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 related 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 is actively maintained.

Thanks for looking into these problems.

-Michael

> 
> 
> Regards,
> 
> Adolf
> 
> -- 
> Sent from my laptop
>