[LinuxFailSafe] failsafe does not failover
cqcai
cqcai@163.com
Tue, 25 Mar 2003 16:29:09 +0800
something strange, when two IP_address resource start successful, and
i can use ifconfig -a to see them.
but the log says this:
Tue Mar 25 06:47:19.432 <N ha_cilog script 11796:0 Unknown:0> Tue Mar 25
06:47:19 <N IP_address-exclusive script 11661:0> 192.168.1.2 exclusive
status: NOT RUNNING
Tue Mar 25 06:47:19.474 <N ha_cilog script 11800:0 Unknown:0> Tue Mar 25
06:47:19 <N IP_address-exclusive script 11660:0> 192.168.1.3 exclusive
status: NOT RUNNING
Tue Mar 25 07:34:51.622 <N ha_cilog script 12220:0 Unknown:0> Tue Mar 25
07:34:51 <N IP_address-start script 12136:0> IP_address: start - 192.168.1.2
Tue Mar 25 07:34:51.662 <N ha_cilog script 12223:0 Unknown:0> Tue Mar 25
07:34:51 <N IP_address-start script 12135:0> IP_address: start - 192.168.1.3
Tue Mar 25 07:34:51.881 <N ha_cilog script 12263:0 Unknown:0> Tue Mar 25
07:34:51 <N IP_address-start script 12136:0> 192.168.1.2 not configured
on any interface
Tue Mar 25 07:34:51.935 <N ha_cilog script 12267:0 Unknown:0> Tue Mar 25
07:34:51 <N IP_address-start script 12135:0> 192.168.1.3 not configured
on any interface
what about "not configured on any interface" ?
regards
Padmanabhan Sreenivasan wrote:
>cqcai wrote:
>
>>When i run test in cmgr to test the IP_address resource 192.168.1.1, get
>>error information:
>>
>>cmgr> test resource 192.168.1.1 of resource_type IP_address in cluster test
>>qcai.wiregate.com: Connection refused
>>Failure: Connection to qcai.wiregate.com from qcai.wiregate.com failed
>>Suggestion: (1) Ensure node 'qcai.wiregate.com' has superuser access
>>from qcai.wiregate.com
>>Suggestion: (2) Ensure address 'qcai.wiregate.com' is valid.
>>Error:
>>Notice: overall exit status:failed, tests failed:1, total tests executed:1
>>Cluster diagnostics failed
>>test command failed
>>
>>But i can ping 192.168.1.1, and it doesn't display in ifconfig -a, it's
>>strangely.
>>
>>ifd_qcai log:
>>Mon Mar 24 01:59:41.908 <W ha_ifd ifd 22315:0 ifd_net.c:681> CI_FAILURE,
>>lo is neither broadcast, point-to-point, nor loopback
>>Mon Mar 24 01:59:41.908 <I0 ha_ifd ifd 22315:0 ifd_main.c:346> ha_ifd
>>monitoring network interfaces
>>Mon Mar 24 03:11:41.934 <W ha_ifd ifd 22315:0 ifd_net.c:913> CI_FAILURE,
>>found no interface for ip address 192.168.1.1
>>
>
>Did you configure 192.168.1.1 IP address as a resource? Did you
>specify the ethernet interface without the alias number
>(example: eth0)?
>
>Paddy
>
>>Mon Mar 24 03:11:41.934 <W ha_ifd ifd 22315:0 ifd_net.c:916> CI_FAILURE,
>>Check IP_address 192.168.1.1 resource configuration. Check if interface
>>name is valid.
>>
>>script_qcai log:
>>Mon Mar 24 03:11:35.326 <N ha_cilog script 23418:0 Unknown:0> Mon Mar 24
>>03:11:35 <N IP_address-exclusive script 23375:0> IP_address: exclusive -
>>192.168.1.1
>>Mon Mar 24 03:11:35.484 <N ha_cilog script 23440:0 Unknown:0> Mon Mar 24
>>03:11:35 <N IP_address-exclusive script 23375:0> 192.168.1.1 not
>>configured on any interface
>>Mon Mar 24 03:11:35.574 <N ha_cilog script 23444:0 Unknown:0> Mon Mar 24
>>03:11:35 <N IP_address-exclusive script 23375:0> 192.168.1.1 exclusive
>>status: NOT RUNNING
>>Mon Mar 24 03:11:40.335 <N ha_cilog script 23450:0 Unknown:0>
>>/usr/lib/failsafe/policies/ordered: 1 ordered NO ONE Auto_Recovery
>>Auto_Failback UNIX qcai UNIX
>>Mon Mar 24 03:11:41.785 <N ha_cilog script 23496:0 Unknown:0> Mon Mar 24
>>03:11:41 <N IP_address-start script 23453:0> IP_address: start - 192.168.1.1
>>Mon Mar 24 03:11:41.914 <N ha_cilog script 23518:0 Unknown:0> Mon Mar 24
>>03:11:41 <N IP_address-start script 23453:0> 192.168.1.1 not configured
>>on any interface
>>Mon Mar 24 03:11:42.035 <N ha_cilog script 23532:0 Unknown:0> Mon Mar 24
>>03:11:41 <N IP_address-start script 23453:0> ip address 192.168.1.1
>>cannot be configured
>>Mon Mar 24 03:11:42.124 <N ha_cilog script 23535:0 Unknown:0> Mon Mar 24
>>03:11:42 <N IP_address-start script 23453:0> Check ha_ifd logs on this
>>node for more information
>>
>>/etc/hosts:
>>127.0.0.1 qcai.wiregate.com qcai localhost.localdomain
>>localhost
>>192.168.0.143 qcai.wiregate.com qcai
>>192.168.1.143 pub_qcai.wiregate.com pub_qcai
>>192.168.1.1 test1.wiregate.com test1
>>
>>192.168.0.13 webserver.wiregate.com webserver
>>192.168.1.13 pub_webserver.wiregate.com pub_webserver
>>192.168.1.3 test3.wiregate.com test3
>>
>>192.168.0.21 UNIX.wiregate.com UNIX
>>192.168.1.21 pub_UNIX.wiregate.com pub_UNIX
>>192.168.1.2 test2.wiregate.com test2
>>
>>Lars Marowsky-Bree wrote:
>>
>>>On 2003-03-20T14:57:45,
>>> cqcai <cqcai@163.com> said:
>>>
>>>> { 192.168.1.143 = <tree>
>>>> { BroadcastAddress = "192.168.1.255" }
>>>> { interfaces = "eth0:0" }
>>>>
>>>This is totally wrong. You do not name the interface "eth0:0"; just tell it to
>>>use "eth0" and it will pick a free alias number automatically.
>>>
>>>Sincerely,
>>> Lars Marowsky-Brée <lmb@suse.de>
>>>
>>_______________________________________________
>>LinuxFailSafe mailing list
>>LinuxFailSafe@lists.community.tummy.com
>>http://lists.community.tummy.com/mailman/listinfo/linuxfailsafe
>>
>_______________________________________________
>LinuxFailSafe mailing list
>LinuxFailSafe@lists.community.tummy.com
>http://lists.community.tummy.com/mailman/listinfo/linuxfailsafe
>