On Mon, Dec 15, 2008 at 12:27 PM, Noah Miller <[email protected]> wrote:
> Hi -
>
> I'm just setting up an active-passive cluster running 2.1.4 on CentOS
> 5.2. For the most part, everything is working, but there's one
> primitive/service I'm trying to "clusterize" that is just not playing
> nicely. It is Sangoma's wanrouter service (for their IP telephony
> cards). I can set it up as a generic lsb service like this:
>
> <primitive class="lsb" id="wanrouter" provider="heartbeat" type="wa$
> <operations>
> <op id="wanrouter_mon" interval="120s" name="monitor" timeout="120s"/>
> </operations>
> </primitive>
Woops! That xml should read:
<primitive class="lsb" id="wanrouter" provider="heartbeat" type="wanrouter">
<operations>
<op id="wanrouter_mon" interval="120s" name="monitor" timeout="120s"/>
</operations>
</primitive>
> Heartbeat successfully starts wanrouter with this config, but is
> unable to stop it. When I try, the log says only this:
>
> Dec 15 12:01:39 asterisk1 crm_resource: [27122]: WARN: unpack_rsc_op:
> Processing failed op wanrouter_stop_0 on asterisk1: Error
>
> The wanrouter logs seem to show that the service does, in fact, stop
> successfully, but heartbeat seems to think the stop has failed, and
> shows it as an orphaned resource. Naturally, this causes all sorts of
> problems.
>
> I'm not sure what I can do to troubleshoot this. Can I jack up the
> verbosity on the logging? Do I need to explicitly state start and
> stop operations?
>
> Any ideas are welcome.
>
> Thanks,
> Noah Miller
>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
