Re: [Keepalived-announce] VRRP parsed invalid IP
Status: Beta
Brought to you by:
acassen
|
From: Igor C. <ig...@en...> - 2016-03-15 02:28:48
|
Doh, found it this:
virtual_routes { 172.29.240.0/24 dev dhcptap0 }
should be:
virtual_routes {
172.29.240.0/24 dev dhcptap0
}
and problem solved.
On Tue, Mar 15, 2016 at 1:10 PM, Igor Cicimov <
ig...@en...> wrote:
> Forgot to mention:
>
> # keepalived -v
> Keepalived v1.2.19 (03/14,2016)
>
> On Tue, Mar 15, 2016 at 11:14 AM, Igor Cicimov <
> ig...@en...> wrote:
>
>> Hi all,
>>
>> I'm seeing the following error messages in the log from keepalived:
>>
>>
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16981]:
>> VRRP_Instance(dnsmasq-dhcptap0) Entering MASTER STATE
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16981]:
>> VRRP_Instance(dnsmasq-dhcptap0) setting protocol VIPs.
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16981]:
>> VRRP_Instance(dnsmasq-dhcptap0) setting protocol Virtual Routes
>>
>> *Mar 15 10:44:06 node01 Keepalived[15918]: VRRP child process(16981)
>> died: RespawningMar 15 10:44:06 node01 Keepalived[15918]: Starting VRRP
>> child process, pid=16991*
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Netlink reflector reports
>> IP 10.20.1.185 added
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Netlink reflector reports
>> IP 192.168.0.185 added
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Netlink reflector reports
>> IP 10.10.1.185 added
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Netlink reflector reports
>> IP 172.29.240.3 added
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Netlink reflector reports
>> IP fe80::497:e4ff:fea3:7bbe added
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Netlink reflector reports
>> IP fe80::e055:6aff:fe54:2363 added
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Netlink reflector reports
>> IP fe80::c004:26ff:febd:ae23 added
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Netlink reflector reports
>> IP fe80::fca9:59ff:fe0e:9ee0 added
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Netlink reflector reports
>> IP fe80::d49c:e3ff:fe4c:13d1 added
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Netlink reflector reports
>> IP fe80::d894:19ff:fe34:91fc added
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Netlink reflector reports
>> IP fe80::e8bd:5aff:fe9f:c122 added
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Netlink reflector reports
>> IP fe80::a850:8aff:fe9b:d779 added
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Registering Kernel netlink
>> reflector
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Registering Kernel netlink
>> command channel
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Registering gratuitous ARP
>> shared channel
>>
>>
>>
>> *Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Opening file
>> '/etc/keepalived/keepalived.conf'.Mar 15 10:44:06 node01
>> Keepalived_vrrp[16991]: VRRP parsed invalid IP track_script. skipping
>> IP...Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: VRRP parsed invalid IP
>> {. skipping IP...Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: VRRP parsed
>> invalid IP dnsmasq-dhcptap0. skipping IP...*
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Initializing ipvs 2.6
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Configuration is using :
>> 67654 Bytes
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: Using LinkWatch kernel
>> netlink reflector...
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: IPVS: Daemon has already
>> run
>> Mar 15 10:44:06 node01 Keepalived_vrrp[16991]: VRRP sockpool:
>> [ifindex(5), proto(112), unicast(1), fd(10,11)]
>>
>>
>> Looks like keepalived crashes and respawns on of the processes which
>> might be related to the above highlighted lines ie possibly some config
>> parsing issue. The relevant part of my config is as follows:
>>
>> vrrp_script dnsmasq-dhcptap0 {
>> script "kill -0 $(< /var/run/dnsmasq/dnsmasq-dhcptap0.pid)"
>> interval 2
>> }
>>
>> vrrp_instance dnsmasq-dhcptap0 {
>> state MASTER
>> priority 102
>> interface vmbr0
>> virtual_router_id 47
>> advert_int 3
>> lvs_sync_daemon_interface eth2
>> nopreempt
>>
>> unicast_src_ip 192.168.0.185
>> unicast_peer {
>> 192.168.0.186
>> }
>>
>> notify_master "/etc/keepalived/dnsmasq.sh start dhcptap0 node02"
>> notify_backup "/etc/keepalived/dnsmasq.sh stop dhcptap0"
>>
>> virtual_ipaddress {
>> 172.29.240.3/24 dev dhcptap0 scope global
>> }
>>
>> virtual_routes { 172.29.240.0/24 dev dhcptap0 }
>>
>> track_script {
>> dnsmasq-dhcptap0
>> }
>> }
>>
>> The idea is to start dnsmasq process attached to dhcptap0 on IP takeover
>> for that interface on the MASTER. Now, the log messages are confusing to
>> me, why would it complain about invalid IP when parsing track_script
>> statement??
>>
>> I'm really stamped and probably missing something obvious, any help with
>> this is appreciated.
>>
>> Thanks,
>> Igor
>>
>>
>
>
> --
> Igor Cicimov | DevOps
>
>
> p. +61 (0) 433 078 728
> e. ig...@en... <http://encompasscorporation.com/>
> w*.* encompasscorporation.com
> a. Level 4, 65 York Street, Sydney 2000
>
--
Igor Cicimov | DevOps
p. +61 (0) 433 078 728
e. ig...@en... <http://encompasscorporation.com/>
w*.* encompasscorporation.com
a. Level 4, 65 York Street, Sydney 2000
|