From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter =?utf-8?q?M=C3=BCller?= <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Core Update 165: Restart Squid during the update
Date: Wed, 23 Mar 2022 09:34:26 +0000
Message-ID: <84091192-0fdf-d0dc-50d4-adc61c289808@ipfire.org>
In-Reply-To: <AF99C213-5D43-49A2-A4F2-66E6C3C490EF@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2502573440735838849=="
List-Id: <development.lists.ipfire.org>

--===============2502573440735838849==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello Adolf,
hello Michael,

thanks for your replies.

Indeed, Core Update 165 does not contain a new version of Squid, and indeed, =
there
is bug #12623 for an issue where the proxy is not being started properly duri=
ng boot.
I was unfortunately never able to reproduce this, or understand from the scan=
ty logs
supplied what went wrong here. :-/

So, whatever went wrong on my testing machine with Squid and Core Update 165,=
 let's
drop this patch - people are urged to reboot their IPFire installations as so=
on as
possible anyways.

Thanks, and best regards,
Peter M=C3=BCller


> Hmm, okay.
>=20
> So when a service is being updated, it should be stopped before the update =
is applied and restarted after the update is done.
>=20
> We usually do that - unless it is forgotten, which happens occasionally. Th=
at should however not break anything.
>=20
> -Michael
>=20
>> On 21 Mar 2022, at 09:01, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi Peter,
>>
>> On 20/03/2022 19:32, Peter M=C3=BCller wrote:
>>> Hello Michael,
>>>
>>> thanks for your reply.
>>>
>>> This is necessary because (a) we ship a new version of Squid with Core Up=
date 165
>>> and (b) not restarting Squid afterwards caused the web proxy to stall on =
my testing
>>> machine.
>> Following is for info.
>>
>> On my vm testbed I have all items running on the Services table and after =
the CU to 165 they were all still running.
>> I have never had a problem with the Web Proxy stopping running after any C=
ore Update.
>>
>> However there have been threads where people have reported occasionally th=
at there web proxy has stopped after a core update but usually a reboot resol=
ved that.
>>
>> Some people have reported, and I think there is still a bug open on this, =
where the web proxy periodically stops working in normal operation and has to=
 be restarted or IPFire has to be rebooted to restart it. Unfortunately those=
 bug/thread originators have not usually provided logs or the logs provided h=
ave not shown any issue.
>>
>> Regards,
>> Adolf.
>>> Thanks, and best regards,
>>> Peter M=C3=BCller
>>>
>>>
>>>> Why is this necessary?
>>>>
>>>>> On 20 Mar 2022, at 10:20, Peter M=C3=BCller <peter.mueller(a)ipfire.org=
> wrote:
>>>>>
>>>>> Fixes: #12810
>>>>>
>>>>> Signed-off-by: Peter M=C3=BCller <peter.mueller(a)ipfire.org>
>>>>> ---
>>>>> config/rootfiles/core/165/update.sh | 1 +
>>>>> 1 file changed, 1 insertion(+)
>>>>>
>>>>> diff --git a/config/rootfiles/core/165/update.sh b/config/rootfiles/cor=
e/165/update.sh
>>>>> index ffb552c80..2c2e6a10c 100644
>>>>> --- a/config/rootfiles/core/165/update.sh
>>>>> +++ b/config/rootfiles/core/165/update.sh
>>>>> @@ -128,6 +128,7 @@ ldconfig
>>>>> # Start services
>>>>> telinit u
>>>>> /etc/rc.d/init.d/firewall restart
>>>>> +/etc/rc.d/init.d/squid restart
>>>>>
>>>>> # Fix ownership of classification file.
>>>>> chown nobody:nobody /usr/share/suricata/classification.config
>>>>> --=20
>>>>> 2.34.1
>>
>> --=20
>> Sent from my laptop
>=20

--===============2502573440735838849==--