Re: [PATCH] Core Update 165: Restart Squid during the update

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

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

Hi Peter,

On 20/03/2022 19:32, Peter Müller wrote:
> Hello Michael,
>
> thanks for your reply.
>
> This is necessary because (a) we ship a new version of Squid with Core Update 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 
Core Update.

However there have been threads where people have reported occasionally 
that there web proxy has stopped after a core update but usually a 
reboot resolved 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 have not shown any issue.

Regards,
Adolf.
> Thanks, and best regards,
> Peter Müller
>
>
>> Why is this necessary?
>>
>>> On 20 Mar 2022, at 10:20, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>>
>>> Fixes: #12810
>>>
>>> Signed-off-by: Peter Müller <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/core/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
>>> -- 
>>> 2.34.1

-- 
Sent from my laptop