On 2007-01-08T18:51:12, KYO <[EMAIL PROTECTED]> wrote:
> Suse Enterprise 10 OS built-in heartbeat version is heartbeat-2.0.5-7.10.
Please apply the available online updates via ZMD, YaST2 Online Update
or manually from support.novell.com; the latest released version is
2.0.7, which actually fixes exactly this problem.
> I'd used the 'hb_gui' tool to configure LSB tomcat. (add a native)
>
> After I added the resource, I click the operation tab, and add status
> interval 120s , timeout 60s.
>
> And then click the Apply button. The screen pops up 'Activation failed'.
You actually should be adding a "monitor" operation; the error to add
this via the GUI will fail due to a bug in the 2.0.5 version we shipped.
It's been fixed for quite a while, as you can imagine ;-) Please,
install the updates, we make them all available for very good reasons.
> (I've add status method in /etc/init.d/tomcat LSB.)
>
> Even if I add operation in the cib.xml of the 'tomcat' LSB primitive
> segment, after reboot, the heartbeat server doesn't start.
You cannot simply edit the XML file manually. The file has checksums et
cetera to protect against such on-disk corruption.
> I think it was fail with the operation tag by hand.
The logs will have, at great length and with way too much detail, told
you what exactly the cluster didn't like about the configuration on
startup ;-)
Sincerely,
Lars
--
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge."
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
