[Pacemaker] Tomcat won't start (status timed out) SOLVED

[David Quenzler]

FIXED the incorrect java_home variable
RESTARTED the cluster

On 10/22/10, Andrew Beekhof <andrew at beekhof.net> wrote:
> On Fri, Oct 22, 2010 at 3:48 PM, David Quenzler <quenzler at gmail.com> wrote:
>> Team,
>>
>> ocf:heartbeat:IPaddr params ip=<my_ip> works like a charm.  Resource is
>> UP.
>>
>> ocf:heartbeat:tomcat requires catalina_home and java_home. OK I
>> supplied those along with the recommended timeouts: op start
>> timeout="60s" op stop timeout="60s"
>>
>> tomcat will not start (status=Timed Out)
>> It looks like the OCF tomcat script *is* being called
>
> maybe it just needs longer than 60s?
>
>>
>> /var/log/tomcat.log doesn't show much.  Can I increase the verbosity
>> of logging to that file?
>
> possibly, but not from within pacemaker.
> presumable there is a tomcat config file that controls this
>
>> /var/log/messages shows a few things:
>>
>> Processing failed op tomcat_start_0 : unknown exec error
>> tomcat has failed INFINITY times on x, forcing away, failed INFINITY times
>> on y
>> tomcat cannot run anywhere
>>
>> Am I missing additional configuration?  Has anyone seen this before?
>>
>> Thanks
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs:
>> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs:
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>