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.
Description of problem:
our central loghost is routinely dumping out
Aug 15 09:45:11 log02 rsyslogd-2163: last message repeated 1662 times
Aug 15 09:45:11 log02 rsyslogd-2163:epoll_ctl failed on fd 136, id 0/0x7ff1d401fc10, op 1 with File exists
: File exists [try http://www.rsyslog.com/e/2163 ]
Version-Release number of selected component (if applicable):
rsyslog-5.8.10-2.el6.x86_64
How reproducible:
that's a good question - we don't quite know how to reproduce it
It just happens pretty often recently. It only started following the rhel 6.3 upgrade.
Actual results:
it emits this message - specifically the last line which is not in syslog format and causes our log parser/analyzer to complain
Expected results:
it should not emit the message or rather should not have the problem causing the msg.
Comment 2RHEL Program Management
2012-12-14 08:02:39 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
We are seeing similar messages appear when there is an unusually high load on a rsyslog server that aggregates from several nodes. Its a RHEL6.4 system with kernel version is 2.6.32-279.19.1.el6.x86_64 and rsyslog-5.8.10-6.el6.x86_64.
rsyslogd-2163: epoll_ctl failed on fd 984, id 0/0x7f26e8377c40, op 1 with File exists: File exists [try http://www.rsyslog.com/e/2163 ]
Have any fixes for this bug proved successful?
Comment 12RHEL Program Management
2013-10-14 04:50:53 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This is fixed in the version rsyslog-5.8.10-8.el6_4.x86_64. Please upgrade to it or onwards.
Also increase per user max open fd limit which is by default set to 1024 in RHEL.
/etc/security/limits.conf
~~~
root soft nofile 4096
root hard nofile 10240
~~~
As Susant has written, increasing the maximum number of file descriptors can be a viable workaround.
An updated package should be available in el6.5.
The upstream patch that should fix the cause for the "epoll_ctl" message is this:
http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=bea499dcb2747d1f5b42eae4978cfe86a37dc957
But there's some other problem:
The side-effect seems to be that the daemon takes CPU utilization to 100% until a file descriptor frees up.
I need to investigate this further.
I will confirm your findings Tomas. I have this same core issue (epoll_ctl), and updating to rsyslog-5.8.10-8.el6_4.x86_64 does seem to "fix" the original problem, but it does cause the CPU usage to spike.
Because our instance is an HPC environment, we already had max open set higher than default in /etc/security/limits.conf
---
* soft nofile 32000
* hard nofile 100000
---
The original issue, as reported, has been already fixed in rsyslog-5.8.10-8 as noted in an earlier comment. This is the relevant patch:
rsyslog-5.8.10-bz862517.patch
Thus, I'm closing this bz.
There is a related issue, uncovered by the abovementioned patch, with spikes of CPU usage. I've filed it separately as bug #1077238.