Virtual IP does not appear after HA boot heartbeat

Source: Internet
Author: User

  #tail  /var/log/messages   configuration are correct, but Nginx error, modify Nginx configuration can be mar 31 09:34:47  FRANKTEST02 IPADDR (ipaddr_192.168.1.150) [11820]: info: /usr/libexec/heartbeat/send_arp -i  200 -r 5 -p /var/run/resource-agents/send_arp-192.168.1.150 eth0  192.168.1.150 auto not_used not_usedmar 31 09:34:47 franktest02 /usr/lib/ OCF/RESOURCE.D//HEARTBEAT/IPADDR (ipaddr_192.168.1.150) [11794]: info:  successmar 31  09:34:47 franktest02 resourcemanager (default) [11659]: info: running /etc/init.d/nginx   startmar 31 09:34:48 franktest02 resourcemanager (default) [11659]: ERROR:  Return code 1 from /etc/init.d/nginxMar 31 09:34:48 FrankTest02  ResourceManager (default) [11659]: crit: giving up resources due to failure  of nginxmar 31&nbSp;09:34:48 franktest02 resourcemanager (default) [11659]: info: releasing resource  group: master 192.168.1.150/24/eth0:0 nginxmar 31 09:34:48 franktest02  resourcemanager (default) [11659]: info: running /etc/init.d/nginx  stopmar  31 09:34:48 franktest02 resourcemanager (default) [11659]: INFO: RUNNING /ETC/HA.D /resource.d/ipaddr 192.168.1.150/24/eth0:0 stopmar 31 09:34:48 franktest02  IPADDR (ipaddr_192.168.1.150) [12022]: info: ip status = ok, ip_cip=mar 31  09:34:48 FRANKTEST02 /USR/LIB/OCF/RESOURCE.D//HEARTBEAT/IPADDR (IPaddr_192.168.1.150) [11996]:  info:  success
#tail  /var/log/messages If you do not start from the server, so start the primary server later to start from the server reason: I think of a problem, I remember the class when I only start the Lord's heartbeat, from the time of the start, The Lord does not start the VIP and Nginx services, because the master has a judgment that the master will work only when everything is ready from the node. Because it wants to ensure ha cluster availability, if the service from the even heartbeat is not turned on, it can only be explained that this is a single point, so it's going to strike! Mar 31 09:13:20 franktest02 resourcemanager (default) [10114]: info: releasing  resource group: master 192.168.1.150/24/eth0:0 nginxMar 31 09:13:20  Franktest02 resourcemanager (default) [10114]: info: running /etc/init.d/nginx   Stopmar 31 09:13:20 franktest02 resourcemanager (default) [10114]: info: running  /etc/ha.d/resource.d/IPaddr 192.168.1.150/24/eth0:0 stopMar 31 09:13:20  FRANKTEST02 IPADDR (ipaddr_192.168.1.150) [10477]: info: ip status = ok, ip_ CIP=MAR 31 09:13:20 FRANKTEST02 /USR/LIB/OCF/RESOURCE.D//HEARTBEAT/IPADDR (IPaddr_ 192.168.1.150) [10451]: info:  successmar 31 09:13:29 franktest02 heartbeat: [9899]: info: local  resource acquisition completed.  (None) mar 31 09:13:29 franktest02 heartbeat :  [9899]: info: local resource transition completed. Mar 31 09:13:50 franktest02 hb_standby (default) [10562]: going standby [ Foreign]. Mar 31 09:13:50 franktest02 heartbeat: [9899]: info: master wants  to go standby [foreign]mar 31 09:14:00 franktest02 heartbeat: [ 9899]: warn: no reply to standby request.  standby request  Cancelled.
[[email protected] ha.d]# ls /etc/sysconfig/network-scripts/   #可以看到有eth1网卡, Ifcfg-eth0   ifdown-eth   ifdown-ppp     ifup-aliases   ifup-isdn   ifup-routes        net.hotplugifcfg-eth1   ifdown-ippp  ifdown-routes  ifup-bnep      ifup-plip   ifup-sit           network-functionsifcfg-lo     ifdown-ipv6  ifdown-sit      ifup-eth      ifup-plusb  ifup-tunnel        network-functions-ipv6ifdown        ifdown-isdn  ifdown-tunnel  ifup-ippp     ifup-post    ifup-wirelessifdown-bnep  ifdown-post  ifup           ifup-ipv6      ifup-ppp    init.ipv6-global from Upper:[[email protected] ha.d]# ip  addr1: lo: <loopback,up,lower_up> mtu 16436 qdisc noqueue state  unknown    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00     inet 127.0.0.1/8 scope host lo    inet6 ::1/128  scope host       valid_lft forever preferred_lft  Forever2: eth0: <broadcast,multicast,up,lower_up> mtu 1500 qdisc pfifo_ Fast state up qlen 1000    link/ether 00:0c:29:03:f8:1f brd  ff:ff:ff:ff:ff:ff    inet 192.168.1.106/24 brd 192.168.1.255  Scope global eth0    inet6 fe80::20c:29ff:fe03:f81f/64 scope link        valid_lft forever preferred_lft forever3: eth1: <broadcast, multicast> mtu 1500 qdisc noop state down qlen 1000     link/ether 00:0c:29:03:f8:29 brd ff:ff:ff:ff:ff:ff[[email protected] ha.d ]# rm -f /etc/sysconfig/network-scripts/ifcfg-eth1  Erase Eth1

Restart master/slave,

#ip  addr1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue  state unknown    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00     inet 127.0.0.1/8 scope host lo    inet6 : : 1/128 scope host       valid_lft forever preferred_lft  forever2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc  pfifo_fast state up qlen 1000    link/ether 00:0c:29:58:45:92  brd ff:ff:ff:ff:ff:ff    inet 192.168.1.110/24 brd 192.168.1.255  scope global eth0    inet 192.168.1.150/24 brd  192.168.1.255 scope global secondary eth0:0    inet6 fe80::20c : 29ff:fe58:4592/64 scope  link       valid_lft forever preferred_lft forever 

But from the upper IP addr, there is still a hint of eth1, but has been removed eth1 this network card should be no problem.

[[Email protected] ha.d]# ip addr1: lo: <loopback,up,lower_up> mtu  16436 qdisc noqueue state UNKNOWN    link/loopback  00:00:00:00:00:00 brd 00:00:00:00:00:00    inet 127.0.0.1/8 scope  host lo    inet6 ::1/128 scope host        valid_lft forever preferred_lft forever2: eth0: <broadcast, multicast,up,lower_up> mtu 1500 qdisc pfifo_fast state up qlen 1000     link/ether 00:0c:29:03:f8:1f brd ff:ff:ff:ff:ff:ff     inet 192.168.1.106/24 brd 192.168.1.255 scope global eth0     inet6 fe80::20c:29ff:fe03:f81f/64 scope link        valid_lft forever preferred_lft forever3: eth1: <broadcast,multicast> mtu 1500 qdisc noop state  down qlen 1000    link/ether 00:0c:29:03:f8:29 brd ff:ff:ff : Ff:ff:ff

PS:HA.CF on the Ucast test with eth0, the line is recommended to use a different network card eth1 or with a serial port to connect two, what is the serial port


Virtual IP does not appear after HA boot heartbeat

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.