From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Re: Apache not properly restarting for some people with Core Update 181 Release Date: Tue, 28 Nov 2023 11:22:00 +0000 Message-ID: In-Reply-To: <2CB35814-862A-453A-99DD-F16AB54BE21E@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2160071085931784394==" List-Id: --===============2160071085931784394== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Adolf, hello Michael, thank you for discussing this and the insight. Although this seems to have a different root cause, it reminds me of various update problems we've been trying to solve in https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3Dd0ba077ed3851346b1d= d6d82867103df8446aea8 (which we never fully traced back, but ever since, no reports of such faulty behavior have surfaced again). I was just wondering if it makes sense to run a "sync" before updating the linker cache as well. It wouldn't have fixed the Apache restart issue, but maybe makes things a little bit more robust otherwise? Thanks, and best regards, Peter M=C3=BCller > Good morning, >=20 > Yes, I can confirm this. This happened on one of the firewalls in our infra= structure. >=20 > It seems that the runtime linker cache isn=E2=80=99t up to date at the time= Apache is being restarted, and therefore it simply fails to restart. >=20 > However, ldconfig is executed before restarting apache, so I am not sure wh= y this is happening. >=20 > It is however safe to reboot the affected systems after this point and Apac= he will come back up just fine. >=20 > Best, > -Michael >=20 >> On 25 Nov 2023, at 09:25, Adolf Belka wrote: >> >> Hi All, >> >> There has been a thread in the forum:- >> >> https://community.ipfire.org/t/upgrade-to-181-hangs/10634/1 >> >> where four people have reported that apache has not restarted during the u= pgrade so their WUI hangs at the line:- >> >> PAKFIRE UPGR: core-upgrade-181: Upgrading files and running post-upgrading= scripts=E2=80=A6 >> >> but their pakfire logs showed that the upgrade continued successfully. One= person has done the upgrade on 14 systems. 3 went without any problem but 11= hung after the above line. >> >> IPFire has continued working fine behind the scenes so no big interruption= to their operation but clearly for some systems apache did not properly rest= art. >> >> In future core updates, if apache is being upgraded and needs to be restar= ted, maybe it would be useful to add a check that apache did actually success= fully restart and if not to try to start it again. >> >> Any other thoughts on this. >> >> Regards, >> Adolf. >> >> --=20 >> Sent from my laptop >> >=20 --===============2160071085931784394==--