From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Fischer To: development@lists.ipfire.org Subject: Re: [PATCH] apache: Update to 2.4.38 Date: Tue, 05 Feb 2019 18:45:37 +0100 Message-ID: In-Reply-To: <49ECA0AD-9ED3-45E3-8B69-D7F4A04D7843@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5681230654674502339==" List-Id: --===============5681230654674502339== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, On 05.02.2019 18:30, Michael Tremer wrote: > Why did the reboot fail? Good question. Boot screen was flooded with "Bus error" messages and several services failed to start. A lot. 'hostapd', unbound', ... Too much to count. At last I was happy that I could login - after connecting monitor and keyboard - and copy the old lib back. After that, reboot succeeded and everything ran as before. Doh! > Did you run ldconfig after updating the library? I couldn't because after copying the SSH session crashed immediately. But I fear I didn't tried this his after rebooting. I was just trying to get the thing running again. > To be honest, you could just delete it. It will be deleted with Core Update= 128 anyways... If I have the nerves, I'll try this on weekend... ;-) >> On 5 Feb 2019, at 17:24, Matthias Fischer = wrote: >>=20 >> Hi, >>=20 >> On 04.02.2019 23:20, Michael Tremer wrote: >>> Did you overwrite the library file while it was in use maybe (by the Open= SSH server)? >>=20 >> I must confess: yes. :-( >>=20 >> I did it the same way as I did before - with other updates. >>=20 >> Even a reboot with the new 'libcrypto.so.1.1'-lib failed. >>=20 >> If the running SSH session is the reason, how can I do this update - and >> survive a reboot? >>=20 >> Best, >> Matthias >>=20 >>>> On 1 Feb 2019, at 18:07, Matthias Fischer wrote: >>>>=20 >>>> Hi, >>>>=20 >>>> On 01.02.2019 18:47, Michael Tremer wrote: >>>>>> Right now, '2.4.38' is running here under Core 126. No seen problems >>>>>> with GUI or anything else so far. Log is clean. My only glitch is the >>>>>> d*** 'libcrypto.so.1.1'-lib from sse2. As I wrote, all of my update >>>>>> efforts ended in breaking the system. >>>>>>=20 >>>>>> One last thing I could do - would take some time - is to build under >>>>>> current 'next' and make a test installation on my testmachine (offline= ). >>>>> Hmm, I am slightly confused. >>>>=20 >>>> Understandable. >>>>=20 >>>>> So in Core 128, we are going to ship apache together with OpenSSL 1.1.1= . So that should be fine because the runtime version is the same as the built= version. All older SSL libraries should be removed then. >>>>=20 >>>> Yes - that's what I'm assuming too. >>>>=20 >>>> In commit >>>> https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3Df8d407e5f7ff08= 12beaa6b45eae18b57475aa3d8 >>>> Arne added the missing '/usr/lib/sse2/libcrypto.so.1.1' for i586 which >>>> seems to be the culprit of my problems. They should be solved with this >>>> update. >>>>=20 >>>>> So I suppose if the nightly build works, then the update should work, t= oo. >>>>>=20 >>>>> Right? >>>>=20 >>>> Yes. What I still don't understand: why the manual updates always failed >>>> with "openssl bus error". :-(( >>>>=20 >>>> Best, >>>> Matthias >>>=20 >>>=20 >>=20 >=20 >=20 --===============5681230654674502339==--