On Tue, May 11, 2010 at 2:55 PM, Florian Haas <[email protected]> wrote: > On 05/11/2010 08:31 PM, Sam Tran wrote: >> I confirm that when using the tickle ack feature with crm the failover >> node doesn't send the tickle acks. >> I added some debugging in the run_tickle_tcp() function and found out >> that $OCF_RESKEY_tickle_dir is actually empty. If I set that variable >> in the function the tickle acks are sent out. So I don't quite >> understand why this variable is empty when the crm configuration seems >> to be correct: > > I'm afraid it's not. :) > >> primitive portblock_unblock ocf:heartbeat:portblock \ >> params protocol="tcp" ip="192.168.8.171" portno="636" >> action="unblock" \ >> op monitor interval="10" timeout="10" depth="0" >> tickle_dir="/tmp/tickle" sync_script="/usr/sbin/csync2 -xvr" > > The way you set those tickle_dir and sync_script params, they only apply > to the monitor operation. Unless I'm gravely misled, please try: > > primitive portblock_unblock ocf:heartbeat:portblock \ > params protocol="tcp" ip="192.168.8.171" portno="636" action="unblock" \ > tickle_dir="/tmp/tickle" sync_script="/usr/sbin/csync2 -xvr" \ > op monitor interval="10" timeout="10" depth="0" >
Florian, You nailed it down. You were absolutely correct. With the right crm configuration the failover node now sends out tickle acks. I now need to find out whether our firewall is blocking them or not. Thank you so much! Sam _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
