From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Apache not properly restarting for some people with Core Update 181 Release
Date: Sat, 25 Nov 2023 13:01:45 +0000 [thread overview]
Message-ID: <2CB35814-862A-453A-99DD-F16AB54BE21E@ipfire.org> (raw)
In-Reply-To: <b9323d52-e326-44b2-98ee-e63b027be6f1@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]
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(a)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
>
next prev parent reply other threads:[~2023-11-25 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 9:25 Adolf Belka
2023-11-25 13:01 ` Michael Tremer [this message]
2023-11-28 11:22 ` Peter Müller
2023-11-28 13:27 ` Charles Brown
2023-11-28 14:39 ` Adolf Belka
2023-11-28 14:46 ` Charles Brown
2023-11-28 15:00 ` Adolf Belka
2023-11-28 15:56 ` Michael Tremer
2023-12-01 12:13 ` Adolf Belka
2023-12-01 12:38 ` Adolf Belka
2023-12-09 12:49 ` Adolf Belka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2CB35814-862A-453A-99DD-F16AB54BE21E@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox