Bug 1670451 - unused sssd_kcm service is eating cpu.
Summary: unused sssd_kcm service is eating cpu.
Keywords:
Status: CLOSED DUPLICATE of bug 1645624
Alias: None
Product: Fedora
Classification: Fedora
Component: sssd
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Zidek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-29 14:55 UTC by Paweł Sikora
Modified: 2020-06-04 11:19 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-06-04 11:19:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Paweł Sikora 2019-01-29 14:55:51 UTC
Description of problem:

on the fresh fedora-29-server installation with selected NIS auth metod i'm observing that sssd_kcm service slowly eats cpu. for 3d20h uptime it used 2h20m. i'm not using any kerberos related stuff.

Version-Release number of selected component (if applicable):

sssd-kcm-2.0.0-5.fc29.x86_64

Comment 1 James 2019-05-21 20:16:12 UTC
Seen in sssd-kcm-2.1.0-2.fc30.x86_64. Line from top:

3033 root      20   0  273716  50228   8824 R  92.4   0.6   1300:57 sssd_kcm

Comment 2 Chris Roadfeldt 2019-06-05 16:47:40 UTC
I am experiencing this as well.

sssd-kcm-2.1.0-2.fc30.x86_64

5811 root      20   0  276908  38856   2844 R  99.0   0.5 114:29.79 sssd_kcm

Comment 3 Ben Cotton 2019-10-31 18:59:23 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 James Szinger 2019-11-03 15:23:33 UTC
I'm seeing this with Fedora 30.  Please update the version and keep open.

Comment 5 Al Schapira 2019-11-12 21:31:42 UTC
Also hogging cpu in f30 for me.  How to disable this?

[ads@ADS3 ~]$ uname -a
Linux ADS3 5.3.8-200.fc30.i686 #1 SMP Tue Oct 29 14:52:45 UTC 2019 i686 i686 i386 GNU/Linux
[ads@ADS3 ~]$

Comment 6 Robbie Harwood 2019-11-12 22:08:40 UTC
Al, removing the "sssd-kcm" package should work around the issue.  (You may have to log out and back in.)  This will switch your system back to the KEYRING ccache type.

While we're here though, do note that 32-bit x86 is no longer a supported architecture in Fedora (since fc25).  Consider moving to x86_64 if you can.  https://fedoraproject.org/wiki/Architectures

Comment 7 James 2019-11-20 20:41:21 UTC
Still present in F31, sssd-kcm-2.2.2-3.fc31.x86_64. Don't really know what provoked the high CPU, happened shortly after unlocking the workstation. 

   2053 root      20   0  263868  35336   4112 R  92.4   0.4 198:50.51 sssd_kcm

Comment 8 Ben Cotton 2020-04-30 20:42:12 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 habicht 2020-05-07 09:02:15 UTC
We have this problem too on:

Linux linux.imsmx.intern 5.6.8-200.fc31.x86_64 #1 SMP Wed Apr 29 19:10:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

We are using FreeIPA and Kerberos.

Will this bug move to FC31?

Comment 10 Robbie Harwood 2020-05-07 14:59:10 UTC
Because you have the problem on fc31, it's appropriate for you to move it to fc31.  (I've done so.)

Comment 11 Orion Poplawski 2020-06-01 21:41:27 UTC
Is this a dupe of 1645624 ?

Comment 12 Alexey Tikhonov 2020-06-04 11:19:38 UTC
(In reply to Orion Poplawski from comment #11)
> Is this a dupe of 1645624 ?

It is, thanks.

*** This bug has been marked as a duplicate of bug 1645624 ***


Note You need to log in before you can comment on or make changes to this bug.