From: Charles Brown <cab_77573@yahoo.com>
To: development@lists.ipfire.org
Subject: Re: Apache not properly restarting for some people with Core Update 181 Release
Date: Tue, 28 Nov 2023 07:27:39 -0600 [thread overview]
Message-ID: <39f1dd0a-566b-4047-a34b-e6e2f9783525@yahoo.com> (raw)
In-Reply-To: <a013bf20-3660-46e7-9c4c-67da7705e0c2@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]
I have made a couple of attempts to the get the "fixed" update to Core
181. Each time pakfire upgrade completes, I check the apache script in
/etc/init.d and it is the same as before.
That is, it does not reflect
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=ece94c7edfa45b724ef05b57ff7a8a18c43fb99b
It still shows ...
stop)
boot_mesg "Stopping Apache daemon..."
killproc /usr/sbin/httpd
evaluate_retval
;;
restart)
boot_mesg "Restarting Apache daemon..."
/usr/sbin/apachectl -k restart
evaluate_retval
;;
I did indeed actually do the upgrade.
Punched 'mine' back to 180 to make it do the upgrade thing
Did a pakfire update --force, then did pakfire upgrade ...
CORE INFO: Checking for Core-Updates...
CORE UPGR: Upgrading from release 180 to 181
core-upgrade-2.27... 100.00% |=============================>| 73.61 MB
PAKFIRE UPGR: core-upgrade-181: Decrypting...
PAKFIRE UPGR: core-upgrade-181: Upgrading files and running
post-upgrading scripts...
PAKFIRE UPGR: core-upgrade-181: Finished.
PAKFIRE INFO: Checking for package updates...
PAKFIRE WARN: No new package upgrades available.
.
next prev parent reply other threads:[~2023-11-28 13:27 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
2023-11-28 11:22 ` Peter Müller
2023-11-28 13:27 ` Charles Brown [this message]
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=39f1dd0a-566b-4047-a34b-e6e2f9783525@yahoo.com \
--to=cab_77573@yahoo.com \
--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