Bug 1390613 - The xinetd process using 100% of CPU on OMPv4
Summary: The xinetd process using 100% of CPU on OMPv4
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xinetd
Version: 6.4
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-01 14:10 UTC by Blake Powers
Modified: 2016-11-02 07:33 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-02 07:33:09 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


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