RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 842564 - High CPU and slow response on Red Hat using Kerberos
Summary: High CPU and slow response on Red Hat using Kerberos
Keywords:
Status: CLOSED DUPLICATE of bug 845125
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: krb5
Version: 6.3
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Nalin Dahyabhai
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-24 08:48 UTC by Jamie Morrison
Modified: 2012-08-09 16:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-09 16:07:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jamie Morrison 2012-07-24 08:48:50 UTC 
Description of problem: When using Kerberos authentication, slow performance and high CPU utilisation may be seen when performing Kerberos operations, such as creating a keytab using the net process or authenticating an NFSv4 mount using rpc.svcgssd. 


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

pam_krb5-2.3.11-9.el6.x86_64
krb5-libs-1.9-33.el6.x86_64
krb5-workstation-1.9-33.el6.x86_64
selinux-policy-3.7.19-155.el6_3.noarch
selinux-policy-targeted-3.7.19-155.el6_3.noarch
libselinux-2.0.94-5.3.el6.x86_64


How reproducible:

Install and configure kerberos and run the following commands:

 - net ads join
 - net ads keytab create
 - net ads keytab add

or try to authenticate an NFSv4/Kerberos export.

Occurs when /etc/sysconfig/selinux SELINUX= set to enforcing or permissive, but not disabled.


Actual results:

# time net ads keytab add nfs -U username
real    1m50.321s
user    1m29.677s
sys     0m8.704s

Expected results:

# time net ads keytab add nfs -U username
real    0m4.402s
user    0m0.020s
sys     0m0.012s


Additional info:

Seen in top:

PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 2176 root      20   0  183m 5872 4612 R 99.9  0.1   2:20.60 net

PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 3392 root      20   0  533m 498m 1540 R 99.7  6.4   0:08.55 rpc.svcgssd

This also causes extremely slow boot or non-bootable system.

strace reveals a lot od SELinux traffic.
Comment 2 Karel Srot 2012-08-09 12:12:08 UTC 
I am curious whether this is related to bug 845125. 

Jamie,
are you able to retest it with SELinux disabled?
Comment 3 Jamie Morrison 2012-08-09 12:22:48 UTC 
Looks similar. Could be libkrb5 and its selinux integration.

SELINUX=disabled resolves the issue.

SELINUX=enforcing or even SELINUX=permissive and the issue still exists.
Comment 4 Karel Srot 2012-08-09 16:07:31 UTC 
Thank you. Closing this one as a duplicate.

*** This bug has been marked as a duplicate of bug 845125 ***
Note You need to log in before you can comment on or make changes to this bug.