Good morning,
Yes, I can confirm this. This happened on one of the firewalls in our infrastructure.
It seems that the runtime linker cache isn’t up to date at the time Apache is being restarted, and therefore it simply fails to restart.
However, ldconfig is executed before restarting apache, so I am not sure why this is happening.
It is however safe to reboot the affected systems after this point and Apache will come back up just fine.
Best, -Michael
On 25 Nov 2023, at 09:25, Adolf Belka adolf.belka@ipfire.org 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 upgrade so their WUI hangs at the line:-
PAKFIRE UPGR: core-upgrade-181: Upgrading files and running post-upgrading scripts…
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 restart.
In future core updates, if apache is being upgraded and needs to be restarted, maybe it would be useful to add a check that apache did actually successfully restart and if not to try to start it again.
Any other thoughts on this.
Regards, Adolf.
-- Sent from my laptop