Am Dienstag, 2. Dezember 2008 13:07 schrieb Joerg Streckfuss:
> Hi list,
>
> Im using heartbeat-2.99.2-6.1 with pacemaker-1.0.1-3.1 in a testsetup for a
> firewall cluster. This setup has two nodes each with two physical
> interfaces eth0 and eth1.
>
> I configured two resources of the typ IPaddr2 and one MailTo resource to
> get an Email when a failover occurs. I put these resources into one group
> to ensure that the resources will always run on one node.
>
> The problem is each time when I force a failover the resource MailTo
> produces the following report in /var/log/ha-log and unfortunately no email
> will be send.
>
> <snip>
> RA
> output:(MailTo-admin:start:stderr)
> /usr/lib/ocf/resource.d//heartbeat/MailTo: line 86: -s: command not found
> </snip>
>
> For me it looks like MailTo has no valid $MAILCMD.
>
> Here is my xml snippet.
>
> <group id="group-firewall">
> <primitive id="IPaddr2-10.1.1.1" class="ocf" type="IPaddr2"
> provider="heartbeat"> <operations>
>       <op id="op-IPaddr2-10.1.1.1" name="monitor" interval="3s"
> timeout="3s" role="Started" on-fail="restart"/> </operations>
>    <instance_attributes id="IPaddr2-10.1.1.1-inst-attrs">
>             <nvpair id="IPaddr2-10.1.1.1-ip" name="ip" value="10.1.1.1"/>
>             <nvpair id="IPaddr2-10.1.1.1-nic" name="nic" value="eth0"/>
>             <nvpair id="IPaddr2-10.1.1.1-cidr" name="cidr_netmask"
> value="24"/> <nvpair id="IPaddr2-10.1.1.1-iflabel" name="iflabel"
> value="VIP"/> </instance_attributes>
>    </primitive>
> <primitive id="IPaddr2-192.168.2.50" class="ocf" type="IPaddr2"
> provider="heartbeat"> <operations>
>       <op id="op-IPaddr2-192.168.2.50" name="monitor" interval="3s"
> timeout="3s" role="Started" on-fail="restart"/> </operations>
>    <instance_attributes id="IPaddr2-192.168.2.50-inst-attrs">
>       <nvpair id="IPaddr2-192.168.2.50-inst-attr-ip" name="ip"
> value="192.168.2.50"/> <nvpair id="IPaddr2-192.168.2.50-inst-attr-nic"
> name="nic" value="eth1"/> <nvpair id="IPaddr2-192.168.2.50-inst-attr-cidr"
> name="cidr_netmask" value="24"/> <nvpair
> id="IPaddr2-192.168.2.50-inst-attr-iflabel" name="iflabel" value="VIP"/>
> </instance_attributes>
> </primitive>
> <primitive id="MailTo-admin" class="ocf" type="MailTo"
> provider="heartbeat"> <instance_attributes id="MailTo-inst-attrs">
>       <nvpair id="MailTo-inst-email" name="email"
> value="[EMAIL PROTECTED]"/> <nvpair id="MailTo-inst-subject"
> name="subject" value="Heartbeat Takeover occurs"/> </instance_attributes>
> </primitive>
> </group>

Hi,

does the command 'mail' exist on your computer? It it configured? Can you send 
mails manually using 'mail'

> In additionen, when ping packets from my configured pingd on the prefered
> maste node stay away, the duration for a complete failover takes about 75
> seconds. This is a long time and not reasonable for a firewall cluster.
> I tried to set the monitor option interval from pingd to 3 seconds. But
> this changed nothing. The interval for ping packets remains at 10 seconds.
> Are there better places, like adding another resource to monitor the link
> status of the network interfaces to achieve a faster failover? I believe
> IPaddr2 won't check network link status, right?

IPaddr does not check reachability in the net.
There is a parameter in the ha.cf called deadping. It is 30s by default. So 
changes in the reachability take 30s + damping time to get active. Set this 
paramter to 10s (or lower) according to your needs. You will have to restart 
heartbeat.

Greetings,
-- 
Dr. Michael Schwartzkopff
MultiNET Services GmbH
Addresse: Bretonischer Ring 7; 85630 Grasbrunn; Germany
Tel: +49 - 89 - 45 69 11 0
Fax: +49 - 89 - 45 69 11 21
mob: +49 - 174 - 343 28 75

mail: [EMAIL PROTECTED]
web: www.multinet.de

Sitz der Gesellschaft: 85630 Grasbrunn
Registergericht: Amtsgericht München HRB 114375
Geschäftsführer: Günter Jurgeneit, Hubert Martens

---

PGP Fingerprint: F919 3919 FF12 ED5A 2801 DEA6 AA77 57A4 EDD8 979B
Skype: misch42
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to