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.

Bug 746996

Summary: SAP resource agent cannot be used to manage SAP Webdispatcher or TREX instance
Product: Red Hat Enterprise Linux 6 Reporter: Harald Klein <hklein>
Component: resource-agentsAssignee: Chris Feist <cfeist>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: agk, cluster-maint, ddumas, djansa, edamato, fdanapfe, lhh, mgandhi, rdassen
Target Milestone: rcKeywords: OtherQA
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: resource-agents-3.9.2-9.el6 Doc Type: Bug Fix
Doc Text:
Cause: webdispatcher and the TREX service were not monitored in the SAP resource agent script Consequence: webdispatcher and the TREX service are not monitored. Fix: Add webdispatcher and TREX to list of services we check for SAP Result: webdispatcher and TREX are now monitored properly
Story Points: ---
Clone Of: 746992 Environment:
Last Closed: 2012-06-20 14:38:52 UTC Type: ---
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: 756082    
Attachments:
Description Flags
diff for SAPInstance script none

Description Harald Klein 2011-10-18 14:05:48 UTC
+++ This bug was initially created as a clone of Bug #746992 +++

Description of problem:

The resource agent does miss the webdispatcher and the TREX service in the case statement:

[...]
case $SERVICE in
        disp+work|msg_server|enserver|enrepserver|jcontrol|jstart)
[...]


It should look like this:
case $SERVICE in
        disp+work|msg_server|enserver|enrepserver|jcontrol|jstart|TREXDaemon.x|sapwebdisp)

Comment 2 Harald Klein 2011-10-19 07:12:09 UTC
Created attachment 528935 [details]
diff for SAPInstance script

Comment 4 Lon Hohberger 2012-01-17 19:56:15 UTC
*** Bug 749695 has been marked as a duplicate of this bug. ***

Comment 7 Chris Feist 2012-04-30 21:51:46 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: webdispatcher and the TREX service were not monitored in the SAP resource agent script

Consequence: webdispatcher and the TREX service are not monitored.

Fix: Add webdispatcher and TREX to list of services we check for SAP

Result: webdispatcher and TREX are now monitored properly

Comment 11 errata-xmlrpc 2012-06-20 14:38:52 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0947.html