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: Sat, 09 Dec 2023 13:49:40 +0100 Message-ID: <3eebcabc-e711-4c3e-9dad-b3e14bee6ec0@ipfire.org> In-Reply-To: <64fe469a-deea-4f51-bf6c-011e0af2555b@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5324130507973280857==" List-Id: --===============5324130507973280857== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Arne, I saw that you had done a mod to the update.sh script for the apache and udev= restarts and that the nightly build for the CU181 had run. So I did an update of a CU180 vm that I cloned and the WUI stayed accessible = the whole time. So I can confirm that your fix has solved that problem. Regards, Adolf. On 01/12/2023 13:38, Adolf Belka wrote: > Hi Michael, > > Further update. > > I re-ran a test on a vm but using the pakfire commands from the console (re= quest from someone on the forum). > > It failed again but with a different error message this time. I don't belie= ve this was due to the different upgrade method but I suspect a timing relate= d issue is more likely to be occurring. > > The message in the log was: > > |Stopping Apache daemon... [ OK ] Starting Apache daemon... (98)Address alr= eady in use: AH00072: make_sock: could not bind to address [::]:81 (98)Addres= s already in use: AH00072: make_sock: could not bind to address 0.0.0.0:81 no= listening sockets available, shutting down| > > Regards, > > Adolf. > > > On 01/12/2023 13:13, Adolf Belka wrote: >> Hi Michael, >> >> There have been some people still talking about the WUI hanging after the = update was done so I ran a vm check. >> >> >> I cloned a CU180 system and then ran the update from pakfire. It came to t= he post-upgrade scripts and then it hung for a long time. >> >> I checked via the console and the changes from your patch were in the init= script. >> >> I then ran the status command >> >> /etc/rc.d/init.d/apache status >> /usr/sbin/httpd is not running. >> >> Then did a restart followed by another status >> >> /etc/rc.d/init.d/apache start >> Starting 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=C2=A0=C2=A0 [=C2=A0 OK=C2=A0 ] >> >> /etc/rc.d/init.d/apache status >> httpd is running with Process ID(s) 19645 19644 19643. >> >> >> I then checked for messages in the Core Update 181 log and found the follo= wing >> >> 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=C2=A0=C2=A0 [=C2=A0 OK=C2=A0 ] >> Starting Apache daemon... >> httpd (pid 6165) already running >> >> So the new initscript was run but for some reason it thought that httpd wa= s still running at that time. >> >> So it looks like the initscript patch has been added in to the updater but= is not fixing the problem of Apache not restarting properly. >> >> Should I raise this as a bug or leave it with this email thread? >> >> Regards, >> >> Adolf. >> >> >> On 28/11/2023 16:56, Michael Tremer wrote: >>> Hello Charles, >>> >>> This is correct. The updater should ship the updated script - unless I ma= de a mistake here. >>> >>> I did not change the installation images, which will have the old script,= but we will ship it with the next update again. >>> >>> -Michael >>> >>>> On 28 Nov 2023, at 14:46, Charles Brown wrote: >>>> >>>> I had assumed a pakfire update would do based on Michael's post at ... >>>> https://community.ipfire.org/t/upgrade-to-181-hangs/10634/30 >>>> "A fixed update has been pushed and as soon as all mirror servers have u= pdated, this problem won=E2=80=99t arise any more." >>>> --===============5324130507973280857==--