From: Matthias Fischer <matthias.fischer@ipfire.org>
To: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Core 199 - collectd - cpufreq-plugin floods syslog
Date: Wed, 21 Jan 2026 21:47:59 +0100 [thread overview]
Message-ID: <bd11ec78-3558-4d05-ba1b-cd5cab15faea@ipfire.org> (raw)
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
next reply other threads:[~2026-01-21 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 20:47 Matthias Fischer [this message]
2026-01-22 11:02 ` Adolf Belka
2026-01-22 14:04 ` Matthias Fischer
2026-01-21 22:52 Matthias Fischer
2026-01-22 0:49 ` Tom Rymes
2026-01-22 6:32 ` 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=bd11ec78-3558-4d05-ba1b-cd5cab15faea@ipfire.org \
--to=matthias.fischer@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