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: 1903 bytes --]

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 the 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 initscript.

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...                  [  OK  ]

/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 following

Stopping Apache daemon...                  [  OK  ]
Starting Apache daemon...
httpd (pid 6165) already running

So the new initscript was run but for some reason it thought that httpd was 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 made 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 <cab_77573(a)yahoo.com> 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 updated, this problem won’t arise any more."
>>