Bug 2007272
| Summary: | [REF] Collect Puma Status Data for Satellite6.10 | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jaskaran Singh Narula <janarula> | |
| Component: | sos | Assignee: | Barbora Vassova <bvassova> | |
| Status: | CLOSED MIGRATED | QA Contact: | Miroslav Hradílek <mhradile> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 7.9 | CC: | agk, bmr, bvassova, cww, fkrska, mhradile, momran, plambri, pmoravec, sbradley, theute | |
| Target Milestone: | rc | Keywords: | MigratedToJIRA, OtherQA, Triaged | |
| Target Release: | --- | Flags: | pmoravec:
needinfo?
(bvassova) |
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2011506 2011507 (view as bug list) | Environment: | ||
| Last Closed: | 2023-09-06 11:10:05 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2011506, 2011507 | |||
|
Description
Jaskaran Singh Narula
2021-09-23 13:11:53 UTC
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.
*** Bug 2009794 has been marked as a duplicate of this bug. *** 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)? (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 ) 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. 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. |