Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1446708 - Memory leaks when using OpenSCAP
Summary: Memory leaks when using OpenSCAP
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.2.7
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Sanket Jagtap
URL:
Whiteboard:
Depends On:
Blocks: 1435022
TreeView+ depends on / blocked
 
Reported: 2017-04-28 16:22 UTC by Satellite Program
Modified: 2021-09-09 12:16 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1432263
Environment:
Last Closed: 2018-02-21 17:12:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 18926 0 High Closed Memory leaks when using OpenSCAP 2020-11-16 12:51:53 UTC

Comment 2 Sanket Jagtap 2017-09-29 10:06:58 UTC 
Build: Satellite 6.3 snap 17

Verification:
Two hosts , with policy to run every min 


After approx 3 hrs and 154 reports later

ps -aux | grep foreman+
foreman+  4884  0.0  0.3 256216 48000 ?        Sl   Sep26   0:08 ruby /usr/bin/smart_proxy_dynflow_core -d -p /var/run/foreman-proxy/smart_proxy_dynflow_core.pid
foreman+  8434  0.0  1.0 893496 132872 ?       Sl   Sep26   0:52 ruby /usr/share/foreman-proxy/bin/smart-proxy
root     21611  0.0  0.0 112664   972 pts/0    S+   06:01   0:00 grep --color=auto foreman+

The memory utilization seems adequate and foreman-proxy is still up and running

 systemctl status foreman-proxy
● foreman-proxy.service - Foreman Proxy
   Loaded: loaded (/usr/lib/systemd/system/foreman-proxy.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2017-09-26 07:53:28 EDT; 2 days ago
  Process: 8429 ExecStart=/usr/share/foreman-proxy/bin/smart-proxy (code=exited, status=0/SUCCESS)
 Main PID: 8434 (ruby)
   CGroup: /system.slice/foreman-proxy.service
           └─8434 ruby /usr/share/foreman-proxy/bin/smart-proxy

Sep 28 05:00:47 qe-sat6-feature-rhel6.satqe.lab.eng.rdu2.redhat.com sudo[9741]: foreman-proxy : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/puppet cert --ssldir /var/lib/puppet/ssl --clean c....redhat.com
Sep 28 05:29:15 qe-sat6-feature-rhel6.satqe.lab.eng.rdu2.redhat.com sudo[12500]: foreman-proxy : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/puppet cert --ssldir /var/lib/puppet/ssl --clean c...redhat.com
Sep 28 06:27:26 qe-sat6-feature-rhel6.satqe.lab.eng.rdu2.redhat.com sudo[17601]: foreman-proxy : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/puppet cert --ssldir /var/lib/puppet/ssl --clean r...redhat.com
Sep 28 06:54:30 qe-sat6-feature-rhel6.satqe.lab.eng.rdu2.redhat.com sudo[20125]: foreman-proxy : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/puppet cert --ssldir /var/lib/puppet/ssl --clean e...redhat.com
Sep 28 07:40:06 qe-sat6-feature-rhel6.satqe.lab.eng.rdu2.redhat.com sudo[24017]: foreman-proxy : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/puppet cert --ssldir /var/lib/puppet/ssl --clean e...redhat.com
Sep 28 08:05:37 qe-sat6-feature-rhel6.satqe.lab.eng.rdu2.redhat.com sudo[26349]: foreman-proxy : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/puppet cert --ssldir /var/lib/puppet/ssl --clean b...redhat.com
Sep 28 08:13:39 qe-sat6-feature-rhel6.satqe.lab.eng.rdu2.redhat.com sudo[27218]: foreman-proxy : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/puppet cert --ssldir /var/lib/puppet/ssl --clean d...redhat.com
Sep 28 08:27:51 qe-sat6-feature-rhel6.satqe.lab.eng.rdu2.redhat.com sudo[29055]: foreman-proxy : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/puppet cert --ssldir /var/lib/puppet/ssl --clean i...redhat.com
Sep 28 09:37:46 qe-sat6-feature-rhel6.satqe.lab.eng.rdu2.redhat.com sudo[4167]: foreman-proxy : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/puppet cert --ssldir /var/lib/puppet/ssl --clean r....redhat.com
Sep 29 02:33:58 qe-sat6-feature-rhel6.satqe.lab.eng.rdu2.redhat.com sudo[29322]: foreman-proxy : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/puppet cert --ssldir /var/lib/puppet/ssl --clean v...redhat.com
Hint: Some lines were ellipsized, use -l to show in full.
Comment 3 Bryan Kearney 2018-02-21 17:12:03 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/RHSA-2018:0336
Note You need to log in before you can comment on or make changes to this bug.