From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Core Update 165: Restart Squid during the update
Date: Mon, 21 Mar 2022 15:57:43 +0000 [thread overview]
Message-ID: <AF99C213-5D43-49A2-A4F2-66E6C3C490EF@ipfire.org> (raw)
In-Reply-To: <f718fb49-a8c4-8d66-ce48-10997b34cf83@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2360 bytes --]
Hmm, okay.
So when a service is being updated, it should be stopped before the update is applied and restarted after the update is done.
We usually do that - unless it is forgotten, which happens occasionally. That should however not break anything.
-Michael
> 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ü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
next prev parent reply other threads:[~2022-03-21 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 10:20 Peter Müller
2022-03-20 15:16 ` Michael Tremer
2022-03-20 18:32 ` Peter Müller
2022-03-21 8:55 ` Michael Tremer
2022-03-21 9:01 ` Adolf Belka
2022-03-21 15:57 ` Michael Tremer [this message]
2022-03-23 9:34 ` Peter Müller
2022-03-23 9:35 ` Michael Tremer
2022-03-24 9:15 ` Peter Müller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AF99C213-5D43-49A2-A4F2-66E6C3C490EF@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox