Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1390613

Summary: The xinetd process using 100% of CPU on OMPv4
Product: Red Hat Enterprise Linux 6 Reporter: Blake Powers <bpowers>
Component: xinetdAssignee: Jan Synacek <jsynacek>
Status: CLOSED INSUFFICIENT_DATA QA Contact: qe-baseos-daemons
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-02 07:33:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Blake Powers 2016-11-01 14:10:58 UTC
Description of problem:
System log files filling up, 100% usage from xinetd on one CPU and 50% from rsyslod and a second CPU. When restarting the xinitd process, following in omp_daemon.log shortly after

---------------------------------------------------------------------------
Oct 26 14:15:57 ompgam xinetd[10912]: xinetd Version 2.3.14 started with libwra!
p loadavg labeled-networking options compiled in.
Oct 26 14:15:57 ompgam xinetd[10912]: Started working: 26 available services
Oct 26 14:20:47 ompgam xinetd[10912]: START: tftp pid=24301 from=135.2.12.198
Oct 26 14:20:47 ompgam xinetd[10912]: file descriptor of service evdo_rpcmdview!
er7061 has been closed
Oct 26 14:20:47 ompgam xinetd[10912]: select reported EBADF but no bad file des!
criptors were found
Oct 26 14:20:47 ompgam xinetd[10912]: 1 descriptors still set
Oct 26 14:20:47 ompgam xinetd[10912]: No active service for file descriptor 25
Oct 26 14:20:47 ompgam xinetd[10912]: 1 descriptors still set
Oct 26 14:20:47 ompgam xinetd[10912]: No active service for file descriptor 25
Oct 26 14:20:47 ompgam xinetd[10912]: 1 descriptors still set
---------------------------------------------------------------------------


the restart
Running the top command shows that xinetd and rsyslogd are using a lot of CPU


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jan Synacek 2016-11-02 07:33:09 UTC
(In reply to Blake Powers from comment #0)
> Description of problem:
> ...
> Version-Release number of selected component (if applicable):
> 
> 
> How reproducible:
> 
> 
> Steps to Reproduce:
> 1.
> 2.
> 3.
> 
> Actual results:
> 
> 
> Expected results:
> 
> 
> Additional info:

All I can do with this amount of information is advice you to try the latest xinetd build from 6.9. If that doesn't help, please provide the above information and a backtrace.