From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: [PATCH] apache: Update to 2.4.38 Date: Tue, 05 Feb 2019 20:57:22 +0000 Message-ID: <3F4CDFFE-F1D3-48B3-9D72-AE49E81C4C6B@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2698336630351172385==" List-Id: --===============2698336630351172385== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Well in that case, are you sure that your hardware supports SSE2? > On 5 Feb 2019, at 17:45, Matthias Fischer w= rote: >=20 > Hi, >=20 > On 05.02.2019 18:30, Michael Tremer wrote: >> Why did the reboot fail? >=20 > Good question. >=20 > Boot screen was flooded with "Bus error" messages and several services > failed to start. A lot. 'hostapd', unbound', ... Too much to count. A bus error is a problem accessing memory. > 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! >=20 >> Did you run ldconfig after updating the library? >=20 > 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. >=20 >> To be honest, you could just delete it. It will be deleted with Core Updat= e 128 anyways... >=20 > If I have the nerves, I'll try this on weekend... ;-) >=20 >>> 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 Ope= nSSH 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 (offlin= e). >>>>>> 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 buil= t 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=3Df8d407e5f7ff0= 812beaa6b45eae18b57475aa3d8 >>>>> 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, = too. >>>>>>=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 >=20 --===============2698336630351172385==--