* Core 199 - collectd - cpufreq-plugin floods syslog
@ 2026-01-21 20:47 Matthias Fischer
0 siblings, 0 replies; 3+ messages in thread
From: Matthias Fischer @ 2026-01-21 20:47 UTC (permalink / raw)
To: IPFire: Development-List
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Core 199 - collectd - cpufreq-plugin floods syslog
2026-01-21 22:52 Matthias Fischer
@ 2026-01-22 0:49 ` Tom Rymes
0 siblings, 0 replies; 3+ messages in thread
From: Tom Rymes @ 2026-01-22 0:49 UTC (permalink / raw)
To: Matthias Fischer; +Cc: IPFire: Development-List, IPFire: Tremer, Michael
Matthias,
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?
Either way, it always seems to be working properly to me.
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
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Core 199 - collectd - cpufreq-plugin floods syslog
@ 2026-01-21 22:52 Matthias Fischer
2026-01-22 0:49 ` Tom Rymes
0 siblings, 1 reply; 3+ messages in thread
From: Matthias Fischer @ 2026-01-21 22:52 UTC (permalink / raw)
To: IPFire: Development-List; +Cc: IPFire: Tremer, Michael
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-01-22 0:49 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-01-21 20:47 Core 199 - collectd - cpufreq-plugin floods syslog Matthias Fischer
2026-01-21 22:52 Matthias Fischer
2026-01-22 0:49 ` Tom Rymes
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox