From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pve-devel-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 5DDEB1FF189 for <inbox@lore.proxmox.com>; Fri, 4 Apr 2025 11:29:15 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7040E1AB7C; Fri, 4 Apr 2025 11:29:00 +0200 (CEST) References: <20250404075957.80057-1-f.weber@proxmox.com> <s8oa58w72hl.fsf@proxmox.com> <84420a11-0b5f-443f-99b3-bd517725a31c@proxmox.com> <9bf859f5-99a2-461a-9ad0-8d983474d2d0@proxmox.com> User-agent: mu4e 1.10.8; emacs 30.1 From: Maximiliano Sandoval <m.sandoval@proxmox.com> To: Friedrich Weber <f.weber@proxmox.com> Date: Fri, 04 Apr 2025 11:28:27 +0200 In-reply-to: <9bf859f5-99a2-461a-9ad0-8d983474d2d0@proxmox.com> Message-ID: <s8o1pu86zs6.fsf@proxmox.com> MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.096 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [freedesktop.org] Subject: Re: [pve-devel] [PATCH corosync] corosync.service: add patch to reduce log spam in broken network setups X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com> Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>, Thomas Lamprecht <t.lamprecht@proxmox.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com> Friedrich Weber <f.weber@proxmox.com> writes: > If I read the journald.conf docs [1] right, the default interval is 30s > and the burst value is 10000 multiplied by a factor depending on the > free disk space, I guess 4-6 on reasonable setups -- this is a lot of > messages, but as you mention probably fine for limiting really noisy > services. I was more thinking about this from a technical support > point-of-view, where I'd fear that having extreme corosync logspam over > days or weeks would cause the actually interesting stuff to be rotated > away more quickly than I'd like. :) > > But as we have no idea how many broken setups are out there, this is all > somewhat hypothetical, so I'm also fine with not applying this -- if we > get many user reports seeing logspam I guess we can still do this. > > [1] > https://www.freedesktop.org/software/systemd/man/latest/journald.conf.html#RateLimitIntervalSec= I am starting to lean towards not limiting this here. However, I have seen multiple instances at our support portal where logs are rotated rather quickly and useful messages are lost. _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel