From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Apache not properly restarting for some people with Core Update 181 Release Date: Tue, 28 Nov 2023 15:39:15 +0100 Message-ID: <5353fa2b-cc50-4959-bd91-7a62c94a4404@ipfire.org> In-Reply-To: <39f1dd0a-566b-4047-a34b-e6e2f9783525@yahoo.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7930586368736554017==" List-Id: --===============7930586368736554017== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Charles, After the patch has been created, it then has to be merged into the=20 Core-Update-181 branch. Then that merged branch has to be built via the=20 Nightly Builds process and then that newly created iso has to replace=20 the existing one in the downloads section. The patch has been merged and the Nightly Build has been run=20 successfully. That new iso is not yet available via the downloads link=20 but you can download it now from the Nightly location if you don't want=20 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=20 click on Parent Directory to take you back up one level and then on the=20 aarch64 directory. If you check in the changelog.txt file you will see the commit for the=20 apache change. I am sure that the updated iso will be made available via the downloads=20 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=20 > 181.=C2=A0 Each time pakfire upgrade completes, I check the apache script=20 > in /etc/init.d and it is the same as before. > That is, it does not reflect=20 > https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3Dece94c7edfa45b724= ef05b57ff7a8a18c43fb99b > It still shows ... > > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 stop) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 boot_mesg "Stopping Apache daemon..." > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 killproc /usr/sbin/httpd > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 evaluate_retval > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 ;; > > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 restart) > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 boot_mesg "Restarting Apache daemon..." > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 /usr/sbin/apachectl -k restart > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 evaluate_retval > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 ;; > > 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% |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>| 73.61 MB > PAKFIRE UPGR: core-upgrade-181: Decrypting... > PAKFIRE UPGR: core-upgrade-181: Upgrading files and running=20 > post-upgrading scripts... > PAKFIRE UPGR: core-upgrade-181: Finished. > > PAKFIRE INFO: Checking for package updates... > PAKFIRE WARN: No new package upgrades available. > . > --=20 Sent from my laptop --===============7930586368736554017==--