From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Friedrich Weber <f.weber@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] [PATCH corosync] corosync.service: add patch to reduce log spam in broken network setups
Date: Fri, 04 Apr 2025 11:28:27 +0200 [thread overview]
Message-ID: <s8o1pu86zs6.fsf@proxmox.com> (raw)
In-Reply-To: <9bf859f5-99a2-461a-9ad0-8d983474d2d0@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
next prev parent reply other threads:[~2025-04-04 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 7:59 Friedrich Weber
2025-04-04 8:14 ` Maximiliano Sandoval
2025-04-04 8:55 ` Thomas Lamprecht
2025-04-04 9:18 ` Friedrich Weber
2025-04-04 9:28 ` Maximiliano Sandoval [this message]
2025-04-04 9:40 ` Thomas Lamprecht
2025-04-04 12:43 ` Friedrich Weber
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=s8o1pu86zs6.fsf@proxmox.com \
--to=m.sandoval@proxmox.com \
--cc=f.weber@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.