Mailing List Archive

Re: [Linux-HA] HA both the nodes are showing as active
I think u have to configure ping node
Check this one
http://www.linux-ha.org/ConfigureIpfail


Il giorno 09/ago/2012, alle ore 20:53, p srinivas <srinivaspatnana@gmail.com> ha scritto:

> On my HA setup both the nodes area taking ownership. Can some one please
> help me on this how to resolve this issue?
>
> Thanks,
> Patnana.
>
>
> [root@HA-NODE1 ~]# rpm -qa | grep heartbeat
>
> heartbeat-pils-2.1.4-11.el5
>
> heartbeat-2.1.4-11.el5
>
> heartbeat-stonith-2.1.4-11.el5
>
> Active Node::
> ----------------
> [root@HA-NODE1 ~]# ifconfig
> eth0 Link encap:Ethernet HWaddr 00:0C:29:4D:05:29
> inet addr:10.0.29.82 Bcast:10.0.255.255 Mask:255.255.0.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:346879 errors:0 dropped:0 overruns:0 frame:0
> TX packets:13678 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:29670931 (28.2 MiB) TX bytes:4804084 (4.5 MiB)
>
> eth0:0 Link encap:Ethernet HWaddr 00:0C:29:4D:05:29
> inet addr:10.0.154.164 Bcast:10.0.255.255 Mask:255.255.0.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:1570424 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1570424 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:343211575 (327.3 MiB) TX bytes:343211575 (327.3 MiB)
> Passive Node::
> ----------------------
> [root@HA-NODE2 ~]# ifconfig
> eth0 Link encap:Ethernet HWaddr 00:0C:29:2D:E1:79
> inet addr:10.0.29.83 Bcast:10.0.255.255 Mask:255.255.0.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:356943 errors:0 dropped:0 overruns:0 frame:0
> TX packets:23179 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:31977443 (30.4 MiB) TX bytes:4267333 (4.0 MiB)
>
> eth0:0 Link encap:Ethernet HWaddr 00:0C:29:2D:E1:79
> inet addr:10.0.154.164 Bcast:10.0.255.255 Mask:255.255.0.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:892500 errors:0 dropped:0 overruns:0 frame:0
> TX packets:892500 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:140286823 (133.7 MiB) TX bytes:140286823 (133.7 MiB)
>
> HA-NODE1
> ---------------
> Aug 8 12:56:55 HA-NODE1 heartbeat: [4763]: info: Local status now set to:
> 'active'
> Aug 8 12:56:55 HA-NODE1 heartbeat: [4763]: info: Starting child client
> "/usr/lib64/heartbeat/ipfail" (0,0)
> Aug 8 12:56:55 HA-NODE1 heartbeat: [5148]: info: Starting
> "/usr/lib64/heartbeat/ipfail" as uid 0 gid 0 (pid 5148)
> Aug 8 12:56:56 HA-NODE1 heartbeat: [4763]: info: Status update for node
> ha-node2: status active
> Aug 8 12:56:56 HA-NODE1 harc[5191]: [5197]: info: Running
> /etc/ha.d/rc.d/status status
> Aug 8 12:56:56 HA-NODE1 heartbeat: [4763]: WARN: Client [ipfail] pid 5148
> failed authorization [client failed authorization]
> Aug 8 12:56:56 HA-NODE1 heartbeat: [4763]: ERROR:
> api_process_registration_msg: cannot add client(ipfail)
> Aug 8 12:56:56 HA-NODE1 ipfail: [5148]: ERROR: Cannot sign on with
> heartbeat
> Aug 8 12:56:56 HA-NODE1 ipfail: [5148]: ERROR: REASON:
> Aug 8 12:56:56 HA-NODE1 heartbeat: [4763]: WARN: Managed
> /usr/lib64/heartbeat/ipfail process 5148 exited with return code 1.
> Aug 8 12:56:56 HA-NODE1 heartbeat: [4763]: ERROR: Respawning client
> "/usr/lib64/heartbeat/ipfail":
> Aug 8 12:56:56 HA-NODE1 heartbeat: [4763]: info: Starting child client
> "/usr/lib64/heartbeat/ipfail" (0,0)
> Aug 8 12:56:57 HA-NODE1 heartbeat: [5204]: info: Starting
> "/usr/lib64/heartbeat/ipfail" as uid 0 gid 0 (pid 5204)
> Aug 8 12:56:57 HA-NODE1 heartbeat: [4763]: WARN: Client [ipfail] pid 5204
> failed authorization [client failed authorization]
> Aug 8 12:56:57 HA-NODE1 heartbeat: [4763]: ERROR:
> api_process_registration_msg: cannot add client(ipfail)
> Aug 8 12:56:57 HA-NODE1 ipfail: [5204]: ERROR: Cannot sign on with
> heartbeat
>
> HA-NODE2
> --------------
> Aug 8 12:56:54 HA-NODE2 heartbeat: [4753]: info: Local status now set to:
> 'up'
> Aug 8 12:56:55 HA-NODE2 heartbeat: [4753]: info: Link 10.0.0.1:10.0.0.1 up.
> Aug 8 12:56:55 HA-NODE2 heartbeat: [4753]: info: Status update for node
> 10.0.0.1: status ping
> Aug 8 12:56:55 HA-NODE2 heartbeat: [4753]: info: Link ha-node1:eth0 up.
> Aug 8 12:56:56 HA-NODE2 heartbeat: [4753]: info: Status update for node
> ha-node1: status active
> Aug 8 12:56:56 HA-NODE2 heartbeat: [4753]: info: Comm_now_up(): updating
> status to active
> Aug 8 12:56:56 HA-NODE2 heartbeat: [4753]: info: Local status now set to:
> 'active'
> Aug 8 12:56:56 HA-NODE2 heartbeat: [4753]: info: Starting child client
> "/usr/lib64/heartbeat/ipfail" (0,0)
> Aug 8 12:56:56 HA-NODE2 heartbeat: [4921]: info: Starting
> "/usr/lib64/heartbeat/ipfail" as uid 0 gid 0 (pid 4921)
> Aug 8 12:56:56 HA-NODE2 heartbeat: [4753]: WARN: Client [ipfail] pid 4921
> failed authorization [client failed authorization]
> Aug 8 12:56:56 HA-NODE2 heartbeat: [4753]: ERROR:
> api_process_registration_msg: cannot add client(ipfail)
> Aug 8 12:56:56 HA-NODE2 heartbeat: [4753]: WARN: Managed
> /usr/lib64/heartbeat/ipfail process 4921 exited with return code 1.
> Aug 8 12:56:56 HA-NODE2 ipfail: [4921]: ERROR: Cannot sign on with
> heartbeat
> Aug 8 12:56:56 HA-NODE2 heartbeat: [4753]: ERROR: Respawning client
> "/usr/lib64/heartbeat/ipfail":
> Aug 8 12:56:56 HA-NODE2 ipfail: [4921]: ERROR: REASON:
> Aug 8 12:56:56 HA-NODE2 heartbeat: [4753]: info: Starting child client
> "/usr/lib64/heartbeat/ipfail" (0,0)
> Aug 8 12:56:56 HA-NODE2 harc[4919]: [4941]: info: Running
> /etc/ha.d/rc.d/status status
>
>
> [root@HA-NODE1 ~]# cat /etc/ha.d/ha.cf
> keepalive 5
> deadtime 120
> warntime 5
> initdead 130 # depend on your hardware
> udpport 694
> ping 10.0.0.1
> mcast eth0 239.239.239.239 694 1 0
> auto_failback off
> node HA-NODE1
> node HA-NODE2
> respawn root /usr/lib64/heartbeat/ipfail
> use_logd yes
>
> [root@HA-NODE1 ~]# cat /etc/hosts
> # Do not remove the following line, or various programs
> # that require network functionality will fail.
> 127.0.0.1 localhost.localdomain localhost
> 10.0.29.82 HA-NODE1.qa-dc.net HA-NODE1
> 10.0.29.83 HA-NODE2.qa-dc.net HA-NODE2
>
>
> [root@HA-NODE1 ~]# cat /etc/ha.d/authkeys
> auth 2
> 2 crc
>
> [root@HA-NODE1 ~]# cat /etc/ha.d/haresources
> HA-NODE1 10.0.154.164 httpd nodentwd
> _______________________________________________
> Linux-HA mailing list
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/