Question for the list:
I have a small, aircooled pc server, which is running fine, but the log gets filled with a series of messages saying the package, and each of 8 cpus is throttled because of thermal issues. Then, within the same second according to the timestamps, it reports everything is OK and throttling is off. This happens once every minute.
In reality, when I try performance tests, I believe the processor is actually spending measurable time in the throttled condition.
I have installed lmsensors, and am monitoring temps as frequently as the reported throttling occurs, but I never see any high cpu temps. I see them vary, based on load, but never high enough to be alarmed, or to be throttled.
I did a lot of googling, and I see some intel issues in some lenovo laptops, and a potential fix. I did the following:
dnf copr enable abn/throttled dnf install -y throttled
but I get this output: Error: Problem: conflicting requests - nothing provides python3-configparser needed by throttled0.7-1.x86_64
I have no guess what to do about this.
Thanks, -chuck
On Sun, Aug 9, 2020 at 1:40 PM Chuck Campbell campbell@accelinc.com wrote:
... dnf copr enable abn/throttled dnf install -y throttled
but I get this output: Error: Problem: conflicting requests
- nothing provides python3-configparser needed by throttled0.7-1.x86_64
I have no guess what to do about this.
Well, that dependency is being invoked by this third party package, abn/throtted from the COPR collection of Fedora... I have no idea what repos it might be in
At Sun, 9 Aug 2020 14:16:21 -0700 CentOS mailing list centos@centos.org wrote:
On Sun, Aug 9, 2020 at 1:40 PM Chuck Campbell campbell@accelinc.com wrote:
... dnf copr enable abn/throttled dnf install -y throttled
but I get this output: Error: Problem: conflicting requests
- nothing provides python3-configparser needed by throttled0.7-1.x86_64
I have no guess what to do about this.
Well, that dependency is being invoked by this third party package, abn/throtted from the COPR collection of Fedora... I have no idea what repos it might be in
Right. Some third party repos and/or varous out-of-band "repos" use different package naming / origanizations. *Fedora* often uses "incompatable" package naming WRT RHEL/CentOS. I guess when RedHat migrates a package set from Fedora, there is sometimes package renaming and reorganization. Esp. for things like Perl, PHP, and Python packages (often these are noarch packages), so when you go back to a Fedora repo for something RedHat did not pick up, you end up with this sort of problem (been there, done that). Often the only cure is to grab the .src.rpm(s) and rebuild it(them), after manually installing the various dependencies one by one (including rebuilding them as well, as needed). Often, the low-level .src.rpms build easily enough, so it becomes mostly a bit of tedium.
The OP, is probably going to have to install rpmbuild and set up a RPM Build tree.
-
Chuck Campbell -
John Pierce -
Robert Heller