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.

Description of problem:

Hi,

We have a tomcat resource agent configured in our pacemaker cluster like this:

  Resource: Tomcat (class=ocf provider=heartbeat type=tomcat)
   Attributes: tomcat_user=tomcat java_home=/usr/lib/jvm/jre-1.7.0 java_opts="-server -Xmx2048m" catalina_home=/usr/share/tomcat catalina_base=/usr/share/tomcat catalina_tmpdir=/var/cache/tomcat/temp logging_config=/usr/share/tomcat/conf/logging.properties logging_manager=org.apache.juli.ClassLoaderLogManager statusurl=http://localh
ost:8080/app/status 

This used to work fine, but since the upgrade to the latest tomcat package (security update) this no longer works.

Root cause seems to be that /usr/sbin/tomcat (which is used by the resource agent) now uses systemd to start tomcat. 

Regards,

Rik


Version-Release number of selected component (if applicable):


How reproducible:
tomcat-7.0.54-8.el7_2.noarch

Steps to Reproduce:
1. Configure pacemaker resource using the tomcat resource agent
2. Upgrade to latest tomcat package
3.

Actual results:
tomcat fails to start correctly

Expected results:
Tomcat works like before


Additional info: