Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2237152

Summary: Upload ARF reports is causing Foreman Proxy to consume large amount of memory.
Product: Red Hat Satellite Reporter: Hao Chang Yu <hyu>
Component: SCAP PluginAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.13.3CC: ahumbe, aruzicka, lstejska, mhulan, pmendezh, rlavi, snarya
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Performance, PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 16:28:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Hao Chang Yu 2023-09-04 03:10:51 UTC
Description of problem:
Foreman Proxy can consume large amount of memory after uploading certain amount of ARF reports to Foreman.

I can Foreman proxy to use about 2.8GB of memory by simply using 2 clients to upload the ARF reports.
~~~
# ps -aux | grep foreman-proxy
foreman+ 1548024 10.4 13.9 3094828 2812948 ?     Ssl  02:33   1:26 /usr/bin/ruby /usr/share/foreman-proxy/bin/smart-proxy
~~~


How reproducible:
Easy

Steps to Reproduce:
1. Prepare 2 or more Foreman openscap clients and run the below command on them multiple times.
~~~
foreman_scap_client <the policy id>
~~~

2. Observe the memory usage of the Foreman proxy service in the Satellite

Actual results:
Memory usage of the Foreman Proxy keeps increasing



Expected results:
Should use reasonable amount of memory or free up unused memory.


Additional info:
After some investigations. I found that it is the nokogiri that used about 450MB to parse the XML report and never free up the memory. See below:

~~~
MALLOC_ARENA_MAX=2 irb
~~~

~~~
root     1549155 21.6  0.1 111156 28904 pts/0    S+   02:55   0:01 irb
~~~

~~~
irb(main):001:0> conf.echo = false
irb(main):002:0> require 'nokogiri'
irb(main):003:0> data =  `bunzip2 -dc /root/results.xml.bz2`
irb(main):004:0> parsed_xml = ::Nokogiri::XML.parse(data, nil, nil, Nokogiri::XML::ParseOptions.new.norecover)
~~~

~~~
root     1549155 11.4  2.4 606832 495808 pts/0   S+   02:55   0:05 irb
~~~


I think it is not a memory leak because if I remove the references and force GC immediately, it won't free the memory up, but will reuse it.
~~~
irb(main):006:0> parsed_xml = nil
irb(main):007:0> data = nil
irb(main):008:0> GC.start
irb(main):009:0> data =  `bunzip2 -dc /root/results.xml.bz2`
irb(main):010:0> parsed_xml = ::Nokogiri::XML.parse(data, nil, nil, Nokogiri::XML::ParseOptions.new.norecover)
~~~

~~~
root     1549155  3.2  2.7 740104 562444 pts/0   S+   02:55   0:09 irb
~~~

Comment 1 Ron Lavi 2023-09-04 13:04:31 UTC
This might be the reason for the Net::ReadTimeout error in https://bugzilla.redhat.com/show_bug.cgi?id=1893672

Comment 2 Ron Lavi 2023-09-04 13:15:46 UTC
was referring to what was mentioned in the Additional info:
"After some investigations. I found that it is the nokogiri that used about 450MB to parse the XML report and never free up the memory."

Comment 4 Brad Buckingham 2023-10-30 11:29:29 UTC
Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.

Comment 8 Eric Helms 2024-06-06 16:28:52 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.