public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: Tom Rymes <tom@rymes.net>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>,
	"IPFire: Tremer, Michael" <michael.tremer@ipfire.org>
Subject: Re: Core 199 - collectd - cpufreq-plugin floods syslog
Date: Thu, 22 Jan 2026 07:32:14 +0100	[thread overview]
Message-ID: <5b78cf81-b059-43ef-ab33-038ca1579f22@ipfire.org> (raw)
In-Reply-To: <DF703D68-1844-4AE8-849F-01AD1F48242A@rymes.net>

On 22.01.2026 01:49, Tom Rymes wrote:
> Matthias,

Hi Tom,

> I always get your emails to the list, followed by a second message that your emails aren’t appearing on the list. I’m guessing the issue is that you are not receiving a copy of your own e-mails?

Exactly.

This started "some day" - so that I couldn't tell if my mail came through.

On the other hand, I receive mails like yours always *twice*. Funny. One
of these mails comes with a List-ID from <development.lists.ipfire.org>.
Its a bit weird...

> Either way, it always seems to be working properly to me.

Ok - I think, for the moment I can live with that... ;-)

Best
Matthias

> 
> Tom
> 
>> On Jan 21, 2026, at 5:52 PM, Matthias Fischer <matthias.fischer@ipfire.org> wrote:
>> 
>> 2cd try:
>> For reasons unknown to me, my Mails no longer appear on the list, even
>> though I can send them there without any errors.
>> 
>> Therefore: next attempt - plus CC to MT [Hi Michael... ;-) ]
>> 
>> -----------------
>> 
>> Hi,
>> 
>> just in case that this happens to somebody else:
>> 
>> Some days ago I made a fresh install of Core 199 with a new machine and
>> rather old cpu (i7-2700). Runs fine and has more power than the old Duo
>> box. Fits my needs.
>> 
>> But I couldn't disable HT in BIOS - 'htop' finds eight CPUs. Should be
>> no problem - but it is.
>> 
>> The problem came with the 'cpufreq'-plugin, my logs were flooded with
>> warnings:
>> "cpufreq plugin: Reading
>> "/sys/devices/system/cpu/cpu4[5,6,7]/cpufreq/scaling_cur_freq" failed."
>> 
>> Because of the deactivation, 'scaling_cur_freq' was empty, there were
>> complains about CPU 4-7 (the deactivated ones) and in no time my log was
>> filled with about 10000 'collectd'-entries.
>> 
>> My solution was to change the loglevel of the 'Plugin syslog' in
>> 'collectd.conf' from 'info' to 'err'.
>> 
>> Can anyone confirm this behaviour?
>> 
>> Best
>> Matthias
>> 
> 
> 



  reply	other threads:[~2026-01-22  6:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21 22:52 Matthias Fischer
2026-01-22  0:49 ` Tom Rymes
2026-01-22  6:32   ` Matthias Fischer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-21 20:47 Matthias Fischer
2026-01-22 11:02 ` Adolf Belka
2026-01-22 14:04   ` Matthias Fischer

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=5b78cf81-b059-43ef-ab33-038ca1579f22@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=development@lists.ipfire.org \
    --cc=michael.tremer@ipfire.org \
    --cc=tom@rymes.net \
    /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