Clustered tomcat-6 resource doesn't start processes as configured TOMCAT_USER in RHEL 6

Solution In Progress - Updated -

Issue

  • The configured Tomcat-6 resources starts correctly but the processes are started as root (there are not started with "su TOMCAT_USER -c" like Tomcat-5 resource do), so all files written (e.g. logs files) are root files.
  • We have tried to declare TOMCAT_USER variable in /etc/sysconfig/tomcat6.conf, in /etc/tomcat6/tomcat6.conf and in the customized tomcat6.conf created for each resource instance but without success.
  • tomcat-6 resource fails to start because the pidfile directory in /var/run/cluster/tomcat-6 doesn't have the right permissions.

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
  • resource-agents prior to release 3.9.2-40.el6
  • One or more tomcat-6 resources in /etc/cluster/cluster.conf
  • TOMCAT_USER configured as a non-root user in the tomcat configuration used by the resource(s)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.