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.
DescriptionTakayuki Nagata
2022-04-08 04:02:30 UTC
Description of problem:
When system is shutdown/rebooted, the following message is shown since oracle processes are terminated before stopping the oracle resource.
Apr 6 10:34:53 node1 oracle(ins_pkg-oracle-INS)[675071]: INFO: Oracle instance INS already stopped
Version-Release number of selected component (if applicable):
resource-agents-4.1.1-98.el8_5.2.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Configure pacemaker cluster with oracle resource
2. Start cluster service
3. Shutdown/reboot the system.
Actual results:
Oracle processes are are terminated before stopping the oracle resource as follows.
Apr 6 10:34:53 node1 systemd[1]: session-c3.scope: Killing process 7540 (ora_pmon_ins) with signal SIGTERM.
Apr 6 10:34:53 node1 systemd[1]: session-c3.scope: Killing process 7544 (ora_clmn_ins) with signal SIGTERM.
Apr 6 10:34:53 node1 systemd[1]: session-c3.scope: Killing process 7548 (ora_psp0_ins) with signal SIGTERM.
Apr 6 10:34:53 node1 systemd[1]: session-c3.scope: Killing process 7552 (ora_vktm_ins) with signal SIGTERM.
:
Apr 6 10:34:53 node1 systemd[1]: session-c3.scope: Killing process 35942 (ora_w009_ins) with signal SIGTERM.
Apr 6 10:34:53 node1 systemd[1]: session-c3.scope: Killing process 37693 (ora_m003_ins) with signal SIGTERM.
Apr 6 10:34:53 node1 systemd[1]: session-c3.scope: Killing process 1170709 (ora_m004_ins) with signal SIGTERM.
Apr 6 10:34:53 node1 systemd[1]: Stopping Session c3 of user oracle.
:
Apr 6 10:34:53 node1 pacemakerd[2137]: notice: Caught 'Terminated' signal
:
Apr 6 10:34:53 node1 oracle(ins_pkg-oracle-INS)[675071]: INFO: Oracle instance INS already stopped
Expected results:
The oracle resource can stop the processes correctly.
Additional info:
This would probably benefit from a closer look at the sosreports via the support case. This does not appear to be a problem with the resource agents. The logs presented in comment 0 show that systemd is killing the oracle processes before pacemaker and the resource agents even attempt to stop oracle.
"su - $ORACLE_OWNER -s /bin/sh -c ..." creates processes under a new .scope unit. I think that the cause of this issue is the unit, and I think that adding dependencies to the unit could fix the issue.
Comment 4RHEL Program Management
2023-09-22 19:36:19 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 5RHEL Program Management
2023-09-22 19:38:35 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. You can also visit https://access.redhat.com/articles/7032570 for general account information.