Project

General

Profile

Actions

Bug #18926

closed

Memory leaks when using OpenSCAP

Added by Ondřej Pražák over 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
High
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Description of problem:

A user is noticing that foreman-proxy is dying and we suspected it was due to the large amount of clients being checked by the OpenSCAP plugin. I tried to reproduce locally and saw the same issue.

How reproducible:

100%

Steps to Reproduce:
1. Set up a system with one host, an OpenSCAP policy and attach the policy to the host.
2. Set OpenSCAP to scan the host every minute

Actual results:

Memory usage balloons until the OOM killer terminates foreman-proxy

Expected results:

Memory usage remains relatively constant.


Related issues 1 (0 open1 closed)

Related to OpenSCAP - Bug #20164: smart_proxy_openscap leaks memoryClosedOndřej Pražák06/29/2017Actions
Actions #1

Updated by Ondřej Pražák over 7 years ago

  • Subject changed from Memory leaks when using OpenSCAP to Memory leaks when using OpenSCAP
  • Target version set to 115
Actions #2

Updated by The Foreman Bot over 7 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Ondřej Pražák
  • Pull request https://github.com/theforeman/smart_proxy_openscap/pull/47 added
Actions #3

Updated by Ondřej Pražák over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #4

Updated by Marek Hulán over 7 years ago

  • Translation missing: en.field_release set to 232
Actions #5

Updated by Ondřej Pražák over 7 years ago

  • Related to Bug #20164: smart_proxy_openscap leaks memory added
Actions

Also available in: Atom PDF