Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionJaskaran Singh Narula
2021-09-23 13:11:53 UTC
Description of problem:
After Puma is introduced in Satellite 6.9/6.10 there is no file that captures puma status by default.
Having that info for Satellite6 is crucial:
- This is important to check how many requests are pending on puma's workers and requests on them.
Version-Release number of selected component (if applicable):
sos-3.9-4.el7_9.noarch
How reproducible:
100%
Steps to Reproduce:
1. Have Sat6.9/6.10 installed and run sosreport
2. Check collected:
- No file captures the output of commands:
----
# scl enable tfm 'puma-status /usr/share/foreman/tmp/puma.state'
----
Actual results:
No puma-status collected.
Expected results:
Stauts should be collected under foreman.
Hi Mike,
do you think it will be possible to add equivalent of "passenger-status --show=requests" for puma? I believe that will be more useful for support delivery.
If you are not the right person can you please let me know who to ask?
PR _without_ the equivalent of "passenger-status --show=requests" proposed.
Showing the particular pending requests is however seen as an important debugging information that we are losing by passenger->puma migration. E.g. in case 503 responses, we need to know what pending rquests block the httpd/puma/foreman for how long. We can deduce something from incomplete requests in production.log ("Started" log appears but no "Completed" log yet), but that requires some extra scripting.
(In reply to Pavel Moravec from comment #8)
> Bara, does it make sense to add this bug to the 7.9 errata alongside with
> the foreman tasks bug (7.9 clone of 2043102 that I cant find)?
(the 7.9 cloned bug of 2043102 is https://bugzilla.redhat.com/show_bug.cgi?id=2043103 )
Comment 12RHEL Program Management
2023-09-06 11:09:37 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 13RHEL Program Management
2023-09-06 11:10:05 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 "RHEL-" 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.
Comment 14Red Hat Bugzilla
2024-01-05 04:25:04 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days