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.
Having the reports grouped by the the executable this way is not very useful for analysis, as it doesn't actually show which processes are growing most, please provide more granular information, similar to what's requested here https://bugzilla.redhat.com/show_bug.cgi?id=1368103#c6. From the current report, I can only see the ruby set of processes growing, but there are a lot of different process in there.
Thanks, it helps a bit, but I would like to ask for more details if possible:
1. restart foreman-tasks
2. start collecting periodically the `ps aux` output (let's say every minute, if possible)
3. perform the reproducing steps (I assume it's reproducible easily)
4. once the memory grew significantly, run `foreman-rake foreman_tasks:export_tasks tasks=all days=1`
to share what kind of tasks were there
5. I would be also interested into qpid stats:
qpid-stat --ssl-certificate=/etc/pki/katello/qpid_client_striped.crt -b amqps://localhost:5671 -e
qpid-stat --ssl-certificate=/etc/pki/katello/qpid_client_striped.crt -b amqps://localhost:5671 -g
qpid-stat --ssl-certificate=/etc/pki/katello/qpid_client_striped.crt -b amqps://localhost:5671 -c
I'm closing this issue, as the original case when opening the issue was closed and there were additional bugs filed identifying specific usages that lead to the memory growth. The reason for closing is avoiding misunderstandings when dealing with several independent issues in one BZ. For future bugs regarding similar memory issues, please see
https://access.redhat.com/site/solutions/2785811
to see possible causes of the issues, as well as info how to collect data for faster analysis and provide additional information, when any of the existing bug mentioned there doesn't correspond to the system behavior and a new BZ needs to be filed.