From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4dxWSr1SSwz2y1f for ; Thu, 22 Jan 2026 06:32:28 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4dxWSm4Fj2z2xXH for ; Thu, 22 Jan 2026 06:32:24 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4dxWSk13v9z2r9; Thu, 22 Jan 2026 06:32:21 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1769063542; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=AwuLGF3WXNyoVTMfGC75dS3+87+n0hU0dKUCnEjtu5U=; b=h3YLDarlVRPQdDp5aF7F3hUAUexBnpCFi5Giv6thx10OQR7zgB8AHB1i0II6MsrzvhrdJq jtGjJOx3Ox0+eSDw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1769063542; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=AwuLGF3WXNyoVTMfGC75dS3+87+n0hU0dKUCnEjtu5U=; b=Md5MgAcQAkwK1UafdhY/N0CbKLgdz/OwLqdrzg0mSpsOfcT8R+m+FIK/c6ZfSDvYD0v21j 5Tifkw8PgIq/Cwf9rIYU06yQnFRwSOdpluEy9L/ZzoftKVUDQr9O6HOSGSaQ8Co7J8BLC0 OEG0nij+rwNHoWjP3dSNFi7vCXMT1pLfDNupGplWDMjJIr84U66GmOaBEl/nObz2aIe0Il rR7BfRy7dySNGO1KE7ZbeF8EYnKOEe84qKTam+WCHDoF9VVL07clgK93kUYTGGoo0xD7w/ mha52vRDudS7ocwpdL14gW1CTCLeHXQoOwds4T1il+2i2PbrA8KNt3UXXF3JTg== Message-ID: <5b78cf81-b059-43ef-ab33-038ca1579f22@ipfire.org> Date: Thu, 22 Jan 2026 07:32:14 +0100 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: Core 199 - collectd - cpufreq-plugin floods syslog To: Tom Rymes References: Content-Language: en-US Cc: "IPFire: Development-List" , "IPFire: Tremer, Michael" From: Matthias Fischer In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 . 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 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 >> > >