Re: Apache not properly restarting for some people with Core Update 181 Release

[Adolf Belka <adolf.belka@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 2592 bytes --]

Hi Charles,

After the patch has been created, it then has to be merged into the 
Core-Update-181 branch. Then that merged branch has to be built via the 
Nightly Builds process and then that newly created iso has to replace 
the existing one in the downloads section.

The patch has been merged and the Nightly Build has been run 
successfully. That new iso is not yet available via the downloads link 
but you can download it now from the Nightly location if you don't want 
to wait for it to become available in the website downloads section.

https://nightly.ipfire.org/core181/2023-11-27%2011:26:00%20+0000-ece94c7e/x86_64/

I have presumed that you are using x86_64. If it is aarch64 then just 
click on Parent Directory to take you back up one level and then on the 
aarch64 directory.

If you check in the changelog.txt file you will see the commit for the 
apache change.

I am sure that the updated iso will be made available via the downloads 
website section before too long.

Regards,
Adolf.


On 28/11/2023 14:27, Charles Brown wrote:
> 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.
> .
>

-- 
Sent from my laptop