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 4dxjVV6hx4z332v for ; Thu, 22 Jan 2026 14:04:34 +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 4dxjVR2bnRz2xQW for ; Thu, 22 Jan 2026 14:04:31 +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 4dxjVN6PKQz4h; Thu, 22 Jan 2026 14:04:28 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1769090669; 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=lWBE0pPqmVRrXMUX6oEOr57JwN7Ad3d9rp3Xoa7Brmk=; b=r7YcMcuvP/iedKGJwLCiWCSteAQVJdiEmpYQ2HmHd0lyVyOLQCEB69GQdm9Ziugv4srSTL iWHb+CPjjFUkdhDw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1769090669; 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=lWBE0pPqmVRrXMUX6oEOr57JwN7Ad3d9rp3Xoa7Brmk=; b=Rm9fJnWC6BWB0B6gwONNLjSNsQ1W6OvBcF2Lnc357axh9YAu23ARGQa0bLNKTfKO9q/tVB OWh+cseTveU6OQFtj5XtVhXTcgSKWjKWlhnUghxjjEeDDHkjhFYQazI/SoAFujqJ6D/Z6T nPtUu5V4k9VVXYZEKir0FWexURqLKtbAKPMDHsdCIwx/UvAYqRI6rJ5n7APJHub2e9KAjQ 1uaj0Zw7wWSZOgShCmYfrhxSTh0jKssW9Z644NSnQXgSn9VI1tKtZ573LlO/wpUGN0Dv18 dRpfARXgbBfRGBycXRo7seaDSt4il6c+IDvR9Jb4yMMHlLj5e9AGatzLqmpcQg== Message-ID: <7cf06956-d5b8-4769-b020-144737f1da10@ipfire.org> Date: Thu, 22 Jan 2026 15:04:19 +0100 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 From: Matthias Fischer Subject: Re: Core 199 - collectd - cpufreq-plugin floods syslog To: Adolf Belka Cc: "IPFire: Development-List" References: <112b1abc-5ac6-4e52-8fe8-0112ab8a7607@ipfire.org> Content-Language: en-US In-Reply-To: <112b1abc-5ac6-4e52-8fe8-0112ab8a7607@ipfire.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 22.01.2026 12:02, Adolf Belka wrote: > Hi Matthias, Hi Adolf, thanks for the feedback! Comments below... > On 21/01/2026 21:47, Matthias Fischer wrote: >> 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-2600). 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? > Can't confirm it on my system. I have a new mini with a quad core > celeron. cpufreq-plugin is working fine. No error messages of any kind > in the collectd system logs since I did my CU199 update and all graphs > are displaying fine. The graphs are absolutely ok here, too and if I hadn't take a look at the logs I wouldn't have noticed. The problem with my machine seems to be that the cpufreq-plugin tries to read four *empty* files (concerning the deactivated "HT-cores"). Theses files are empty, and the plugin doesn't like that... But as I wrote, setting the syslog-loglevel to 'err' solved it. The plugin is quiet now and everything else is running fine. ;-) Best Matthias > > Regards, > > Adolf. > >> Best >> Matthias >> >> >