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 1324594 - keepalived high number of close syscalls
Summary: keepalived high number of close syscalls
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: keepalived
Version: 7.2
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: 7.2
Assignee: Ryan O'Hara
QA Contact: Brandon Perkins
URL:
Whiteboard:
Depends On: 1419049
Blocks: 1394959 1429880
TreeView+ depends on / blocked
 
Reported: 2016-04-06 17:53 UTC by Ryan Howe
Modified: 2020-08-13 08:26 UTC (History)
11 users (show)

Fixed In Version: keepalived-1.3.4-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1429880 (view as bug list)
Environment:
Last Closed: 2017-08-01 19:36:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1323526 0 unspecified CLOSED keepalived-1.2.20 is available 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2017:2169 0 normal SHIPPED_LIVE keepalived bug fix and enhancement update 2017-08-01 18:18:21 UTC

Description Ryan Howe 2016-04-06 17:53:53 UTC
Description of problem:

keepalived is generating a high number of close syscalls, when a third party agent never drops close events and processing this amount of events is causing the high CPU usage and node to crash


Version-Release number of selected component (if applicable):
Openshift 3.1.1.6
keepalived-1.2.13-7.el7.x86_64

How reproducible: Have not reproduced, with 3rd party application.   



Steps to Reproduce:
1.Configure Ipfailover on openshift
2.Configure 3rd party sysdig to openshift

Actual results:
Openshift node crashes 

Expected results:
keepalived to not generate as many syscalls


Additional info:

OpenShift User list
http://lists.openshift.redhat.com/openshift-archives/users/2016-April/msg00045.html

Customer is running sysdig 
http://www.sysdig.org/


http://www.keepalived.org/changelog.html
 keepalived 1.2.20

"Optimise closure of fds before invoking scripts.
  Every time before a script was invoked, closeall() was called,
  which would spin through 1024 file descriptors closing them, even
  though the vast majority were not open, resulting in 1024 system
  calls. To avoid that, open all sockets and file descriptors
  (except fd 0/1/2) with the CLOEXEC flag set, so that the fds will
  be closed by the kernel when the script is exec'd."

Comment 1 Ryan O'Hara 2016-04-11 15:32:04 UTC
Shouldn't the component for this be keepalived?

The patch in question is upstream commit 480b451a6fb98ee1c1476c3478e366666f87fe15.

Comment 31 errata-xmlrpc 2017-08-01 19:36:38 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2169


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