have a look in:
dmesg
/var/log/messages
/var/log/syslog
Configure manually the IP and check it, because the zen service is starting
the ip but the operative system or the hypervisor (if zenlb is a vm) is
powering off the eth0, maybe duplicated ip
Regards
2015-06-23 17:34 GMT+02:00 Anthony Hare <h...@epcits.com>:
> Hello,
>
>
>
> No, I don’t have any cluster on the test setup.. In my production, I am
> getting one of the virtual interfaces to drop now as well..
>
>
>
> root@zenlb2:~# /etc/init.d/zenloadbalancer start
>
> update global.conf file done...
>
> Starting Zen Load Balancer...
>
> * Running Interfaces:
>
> * Running interface eth0
>
> IF: eth0 IP: 10.201.7.82 NETMASK: 255.255.255.0 GATEWAY: 10.201.7.1
>
> OK
>
> * Running interface eth1
>
> IF: eth1 IP: 10.201.8.6 NETMASK: 255.255.255.0 GATEWAY: 10.201.8.1
>
> OK
>
> * Running interface eth0:1
>
> IF: eth0:1 IP: 10.201.7.83 NETMASK 255.255.255.0
>
> OK
>
> * Running Farms:
>
>
>
> DEFAULT GW: 10.201.8.1 dev eth1
>
> root@zenlb2:~# ifconfig
>
> eth0 Link encap:Ethernet HWaddr 00:50:56:93:49:df
>
> inet6 addr: fe80::250:56ff:fe93:49df/64 Scope:Link
>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>
> RX packets:219618 errors:0 dropped:901 overruns:0 frame:0
>
> TX packets:8781 errors:0 dropped:0 overruns:0 carrier:0
>
> collisions:0 txqueuelen:1000
>
> RX bytes:17059902 (16.2 MiB) TX bytes:1707552 (1.6 MiB)
>
>
>
> eth1 Link encap:Ethernet HWaddr 00:50:56:93:67:bb
>
> inet addr:10.201.8.6 Bcast:10.201.8.255 Mask:255.255.255.0
>
> inet6 addr: fe80::250:56ff:fe93:67bb/64 Scope:Link
>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>
> RX packets:34570 errors:0 dropped:118 overruns:0 frame:0
>
> TX packets:14004 errors:0 dropped:0 overruns:0 carrier:0
>
> collisions:0 txqueuelen:1000
>
> RX bytes:3999703 (3.8 MiB) TX bytes:2699966 (2.5 MiB)
>
>
>
> lo Link encap:Local Loopback
>
> inet addr:127.0.0.1 Mask:255.0.0.0
>
> inet6 addr: ::1/128 Scope:Host
>
> UP LOOPBACK RUNNING MTU:16436 Metric:1
>
> RX packets:84 errors:0 dropped:0 overruns:0 frame:0
>
> TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
>
> collisions:0 txqueuelen:0
>
> RX bytes:4200 (4.1 KiB) TX bytes:4200 (4.1 KiB)
>
>
>
>
>
> Was up for a bit and then I lose eth0 again..
>
>
>
> Reply from 10.201.7.82: bytes=32 time=1832ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=71ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=22ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=18ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=23ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=26ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=14ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=16ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=13ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=19ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=29ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=26ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=36ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=18ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=13ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=13ms TTL=62
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
>
>
> A
>
>
>
>
>
>
>
> *From:* Mathieu Chateau [mailto:mathieu.chat...@lotp.fr]
> *Sent:* Monday, June 22, 2015 10:24 PM
> *To:* zenloadbalancer-support
> *Subject:* Re: [Zenloadbalancer-support] Losing ip from NIC
>
>
>
> Hello,
>
>
>
> any VRRP/cluster ? Maybe switch see mac address twice and block port?
>
>
>
> If zen is stopped on node, do you loose also network?
>
>
> Cordialement,
> Mathieu CHATEAU
> http://www.lotp.fr
>
>
>
> 2015-06-23 1:53 GMT+02:00 Anthony Hare <h...@epcits.com>:
>
> Hello,
>
>
>
> I have a test box that I am running ver 3.05 on a vm. I have two nics for
> the host and I keep losing eth0, I can configure it and it keeps the ip
> shortly and then dies.. During this time, eth1 has no issues..
>
>
>
> Mon Jun 22 16:37:01 PDT 2015 - - - - running '/sbin/ip rule del from
> 10.201.7.82 table table_eth0'
>
> Mon Jun 22 16:37:01 PDT 2015 - - - - running '/sbin/ip route add
> 10.201.7.0/24 dev eth0 src 10.201.7.82 table table_eth0'
>
> Mon Jun 22 16:37:01 PDT 2015 - - - - running '/sbin/ip rule add from
> 10.201.7.82 table table_eth0'
>
> Mon Jun 22 16:37:01 PDT 2015 - - - - sending '/usr/bin/arping -c 2 -A
> -I eth0 10.201.7.82'
>
> Mon Jun 22 16:40:05 PDT 2015 - 10.201.8.6 - 10.232.26.20 - admin - running
> '/sbin/ifconfig eth0 10.201.7.82 netmask 255.255.255.0'
>
> Mon Jun 22 16:40:05 PDT 2015 - 10.201.8.6 - 10.232.26.20 - admin - running
> '/sbin/ip rule del from 10.201.7.82 table table_eth0'
>
> Mon Jun 22 16:40:05 PDT 2015 - 10.201.8.6 - 10.232.26.20 - admin - running
> '/sbin/ip route add 10.201.7.0/24 dev eth0 src 10.201.7.82 table
> table_eth0'
>
> Mon Jun 22 16:40:05 PDT 2015 - 10.201.8.6 - 10.232.26.20 - admin - running
> '/sbin/ip rule add from 10.201.7.82 table table_eth0'
>
> Mon Jun 22 16:44:02 PDT 2015 - 10.201.8.6 - 10.232.26.20 - admin - running
> '/sbin/ifconfig eth0 10.201.7.82 netmask 255.255.255.0'
>
> Mon Jun 22 16:44:02 PDT 2015 - 10.201.8.6 - 10.232.26.20 - admin - running
> '/sbin/ip rule del from 10.201.7.82 table table_eth0'
>
> Mon Jun 22 16:44:02 PDT 2015 - 10.201.8.6 - 10.232.26.20 - admin - running
> '/sbin/ip route add 10.201.7.0/24 dev eth0 src 10.201.7.82 table
> table_eth0'
>
> Mon Jun 22 16:44:02 PDT 2015 - 10.201.8.6 - 10.232.26.20 - admin - running
> '/sbin/ip rule add from 10.201.7.82 table table_eth0'
>
> root@zenlb2:/usr/local/zenloadbalancer/logs# cat
> /usr/local/zenloadbalancer/
>
> app/ backups/ config/ license.txt logs/ www/
>
> root@zenlb2:/usr/local/zenloadbalancer/logs# cat
> /usr/local/zenloadbalancer/config/
>
> campbellpem.pem fwmarks.conf global.conf if_eth0_conf
> if_eth1_conf zencert.pem zlb-start zlb-stop
>
> root@zenlb2:/usr/local/zenloadbalancer/logs# cat
> /usr/local/zenloadbalancer/config/if_eth0_conf
>
> eth0::10.201.7.82:255.255.255.0:up:10.201.7.1:
>
> root@zenlb2:/usr/local/zenloadbalancer/logs# ifconfig eth0
>
> eth0 Link encap:Ethernet HWaddr 00:50:56:93:49:df
>
> inet6 addr: fe80::250:56ff:fe93:49df/64 Scope:Link
>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>
> RX packets:4123 errors:0 dropped:0 overruns:0 frame:0
>
> TX packets:325 errors:0 dropped:0 overruns:0 carrier:0
>
> collisions:0 txqueuelen:1000
>
> RX bytes:299564 (292.5 KiB) TX bytes:44712 (43.6 KiB)
>
>
>
> Reply from 10.201.7.82: bytes=32 time=1ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=1ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=2ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=3ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=1ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=4ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=1ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=2ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=3ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=2ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=1ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=2ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=2ms TTL=62
>
> Reply from 10.201.7.82: bytes=32 time=1ms TTL=62
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
> Request timed out.
>
>
>
> Any ideas why? The production is having issues running on one of the
> nodes and keeping an ip as well…
>
>
>
>
>
> Thx,
> A
>
>
>
> ------------------------------------------------------------------------------
> Monitor 25 network devices or servers for free with OpManager!
> OpManager is web-based network management software that monitors
> network devices and physical & virtual servers, alerts via email & sms
> for fault. Monitor 25 devices for free with no restriction. Download now
> http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
> _______________________________________________
> Zenloadbalancer-support mailing list
> Zenloadbalancer-support@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
>
>
>
> ------------------------------------------------------------------------------
> Monitor 25 network devices or servers for free with OpManager!
> OpManager is web-based network management software that monitors
> network devices and physical & virtual servers, alerts via email & sms
> for fault. Monitor 25 devices for free with no restriction. Download now
> http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
> _______________________________________________
> Zenloadbalancer-support mailing list
> Zenloadbalancer-support@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
>
--
Load balancer distribution - Open Source Project
http://www.zenloadbalancer.com
Distribution list (subscribe): zenloadbalancer-support@lists.sourceforge.net
------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
Zenloadbalancer-support mailing list
Zenloadbalancer-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
