From: Michael Tremer <michael.tremer@ipfire.org>
To: Robin Roevens <robin.roevens@disroot.org>
Cc: development@lists.ipfire.org
Subject: Re: [PATCH 1/2] zabbix_agentd: Update to 7.0.11 (LTS)
Date: Wed, 2 Apr 2025 11:23:11 +0100 [thread overview]
Message-ID: <3DF73209-E144-496F-AA51-2FE4BF00C576@ipfire.org> (raw)
In-Reply-To: <6122b079b517c8bad9b0ed6da76c3e5c6a7f7586.camel@disroot.org>
Hello,
> On 31 Mar 2025, at 00:58, Robin Roevens <robin.roevens@disroot.org> wrote:
>
> Hi Michael
>
> Michael Tremer schreef op zo 30-03-2025 om 14:09 [+0100]:
>> Hello,
>>
>>> On 28 Mar 2025, at 23:53, Robin Roevens <robin.roevens@disroot.org>
>>> wrote:
>>>
>>> Hi Michael
>>>
>>> Michael Tremer schreef op vr 28-03-2025 om 13:55 [+0000]:
>>>> Thank you. I merged this.
>>>>
>>> Thanks!
>>>
>>>> Do we need to add an extra note to the change log so that people
>>>> are
>>>> aware of this breaking change?
>>>>
>>> That is not a bad idea, possibly not every IPFire user is active on
>>> the
>>> forum and some thus may have missed the survey. So please do.
>>>
>>> As you will, or maybe already have noticed, I redid/corrected my
>>> last
>>> patch where I set the number of agent forks to 0 on new
>>> installations.
>>> It is now set to 3 in my newest patch, which was the default in
>>> previous Zabbix agent versions.
>>> I will add an upgrade note about that in the IPFire wiki
>>> zabbix_agentd
>>> addon page.
>>> Maybe that is also worth mentioning in the blog post: that users
>>> with
>>> an existing zabbix_agentd installation may also want to lower the
>>> number of forks the agent starts, especially when running it on a
>>> mini
>>> appliance; with a link to that wiki page.
>
> The wiki has been updated with upgrading notes:
> https://www.ipfire.org/docs/addons/zabbix_agentd#upgrade
>
>>
>> I think the Mini appliance is one of the more powerful pieces of
>> hardware that people are using…
> I can't speak about the new appliance. I have still an old mini
> appliance. I don't have resource problems with it during normal
> operations, but it is rather slow on some operations (especially using
> the log viewer and sometimes executing pakfire and such) so I figure,
> the less resources are taken by non-core elements of IPFire, the
> better.
I agree. Neither of the should run out resources. Mainly because they both have a lot of RAM.
The CPU in the old mini appliance is a little bit slow, at least when it comes to single-core performance. The new one is substantially faster.
But regardless of how fast it is, we should have some limits in place so that the agent cannot bring down the entire system.
-Michael
> Robin
>
>>
>> I have merged the patch. Thank you!
>>
>> -Michael
>>
>>> Regards
>>> Robin
>>>
>>>> -Michael
>>>>
>>>>> On 27 Mar 2025, at 22:45, Robin Roevens
>>>>> <robin.roevens@disroot.org>
>>>>> wrote:
>>>>>
>>>>> - Update from version 6.0.33 to 7.0.11
>>>>> - Update of rootfile not required
>>>>>
>>>>> This is a major release update to the next LTS version and
>>>>> breaks
>>>>> compatibility with Zabbix Server 6.x.
>>>>> A survey on the forum resulted in nobody claiming to still use
>>>>> Zabbix Server v6.x.
>>>>>
>>>>> Full changelogs:
>>>>> - https://www.zabbix.com/rn/rn7.0.0
>>>>> - https://www.zabbix.com/rn/rn7.0.1
>>>>> - https://www.zabbix.com/rn/rn7.0.2
>>>>> - https://www.zabbix.com/rn/rn7.0.3
>>>>> - https://www.zabbix.com/rn/rn7.0.4
>>>>> - https://www.zabbix.com/rn/rn7.0.5
>>>>> - https://www.zabbix.com/rn/rn7.0.6
>>>>> - https://www.zabbix.com/rn/rn7.0.7
>>>>> - https://www.zabbix.com/rn/rn7.0.8
>>>>> - https://www.zabbix.com/rn/rn7.0.9
>>>>> - https://www.zabbix.com/rn/rn7.0.10
>>>>> - https://www.zabbix.com/rn/rn7.0.11
>>>>>
>>>>> Signed-off-by: Robin Roevens <robin.roevens@disroot.org>
>>>>> ---
>>>>> lfs/zabbix_agentd | 6 +++---
>>>>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>>>>
>>>>> diff --git a/lfs/zabbix_agentd b/lfs/zabbix_agentd
>>>>> index bd81dba22..dbe2088fb 100644
>>>>> --- a/lfs/zabbix_agentd
>>>>> +++ b/lfs/zabbix_agentd
>>>>> @@ -26,7 +26,7 @@ include Config
>>>>>
>>>>> SUMMARY = Zabbix Agent
>>>>>
>>>>> -VER = 6.0.37
>>>>> +VER = 7.0.11
>>>>>
>>>>> THISAPP = zabbix-$(VER)
>>>>> DL_FILE = $(THISAPP).tar.gz
>>>>> @@ -34,7 +34,7 @@ DL_FROM = $(URL_IPFIRE)
>>>>> DIR_APP = $(DIR_SRC)/$(THISAPP)
>>>>> TARGET = $(DIR_INFO)/$(THISAPP)
>>>>> PROG = zabbix_agentd
>>>>> -PAK_VER = 16
>>>>> +PAK_VER = 17
>>>>>
>>>>> DEPS = fping
>>>>>
>>>>> @@ -48,7 +48,7 @@ objects = $(DL_FILE)
>>>>>
>>>>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>>>>
>>>>> -$(DL_FILE)_BLAKE2 =
>>>>> 6bf65efe59963294699d8fc6b6456167ae035c075f057c6ca85c612cc41f3f8
>>>>> 12b1
>>>>> 4189ed7e03ab2446e751720f8908f8e098fc0fd7335f95251b221b66b674a
>>>>> +$(DL_FILE)_BLAKE2 =
>>>>> 0c6544c64febc51e6fc153863b46e333d9d5564c83f40b71362a15c0533d48e
>>>>> 50e5
>>>>> c340b35b2ca0dd1d776d0452f4aae42dc44d4e0e4b2c5949df02efbc7fc06
>>>>>
>>>>> install : $(TARGET)
>>>>>
>>>>> --
>>>>> 2.49.0
>>>>>
>>>>>
>>>>> --
>>>>> Dit bericht is gescanned op virussen en andere gevaarlijke
>>>>> inhoud door MailScanner en lijkt schoon te zijn.
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Dit bericht is gescanned op virussen en andere gevaarlijke
>>> inhoud door MailScanner en lijkt schoon te zijn.
>>
>>
>>
>>
>
> --
> Dit bericht is gescanned op virussen en andere gevaarlijke
> inhoud door MailScanner en lijkt schoon te zijn.
prev parent reply other threads:[~2025-04-02 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 22:45 Robin Roevens
2025-03-27 22:45 ` [PATCH 2/2] zabbix_agentd: Disable passive checks by default on new installations Robin Roevens
2025-03-28 13:55 ` [PATCH 1/2] zabbix_agentd: Update to 7.0.11 (LTS) Michael Tremer
2025-03-28 23:53 ` Robin Roevens
2025-03-30 13:09 ` Michael Tremer
2025-03-30 23:58 ` Robin Roevens
2025-04-02 10:23 ` Michael Tremer [this message]
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=3DF73209-E144-496F-AA51-2FE4BF00C576@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=robin.roevens@disroot.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