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.
Cause: Tomcat failed to start from the resource agent when in SELinux enforced mode.
Consequence: Tomcat failed to start.
Fix: Use runuser instead of su when available.
Result: Tomcat starts fine in SELinux enforced mode.
DescriptionNaoya Hashimoto
2015-08-03 00:08:19 UTC
+++ This bug was initially created as a clone of Bug #1234276 +++
Description of problem:
Tomcat resource agent (ocf:heartbeat:tomcat) never fails to run in SELiux enforcing mode because it uses su command. The cause of the issue and the workaround is the same as the bug #1234276, ocf:heartbeat:pgsql resource agent.
Version-Release number of selected component (if applicable):
- OS: RHEL-7.1 (x86_64)
- Kernel: 3.10.0-229.el7.x86_64
- HA:
corosync-2.3.4-4.el7_1.1.x86_64
pacemaker-1.1.12-22.el7_1.2.x86_64,
pcs-0.9.137-13.el7_1.2.x86_64
resource-agents-3.9.5-40.el7
- DB: postgresql-server-9.2.10-2.el7_1.x86_64
How reproducible:
100%
Steps to Reproduce:
* Enable SELinux and configure HA Cluster using RHHA Add-on, and install tomcat
* Run ocf:heartbeat:tomcat resource agent
Comment 4Oyvind Albrigtsen
2015-11-11 12:31:18 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.
https://rhn.redhat.com/errata/RHBA-2016-2174.html