Re: nanny "Read Timed Out" Errors
Tapan Thapa <[email protected]> Fri, 6 Nov 2009 09:25:34 +0530
| Newsgroups | gmane.linux.redhat.piranha |
|---|---|
| Message-ID | <[email protected]> |
--===============1178507223== Content-Type: multipart/alternative; boundary=00032555488ee711750477abd0e6 --00032555488ee711750477abd0e6 Content-Type: text/plain; charset=ISO-8859-1 Hello Mike, Now your network and config file looks perfectly ok. As you are using direct routing so your real server (kiwidev4) has two options. 1st - Use iptables to redirect traffic destined by linux director to real server. 2nd - Use arptables_jf method. (yum install arptables_jf). As you told that you can not modify iptables rules as kiwidev4 machine is being used for other purpose as well so you have to use method 2 (arptables_jf). Below are the steps which you need to performed on real server/servers only: 1. Install arptables_jf rpm from redhat distribution cd or from internet into kiwidev4. 2. arptables -A IN -d 192.168.3.40 -j DROP 3. arptables -A OUT -d 192.168.3.40 -j mangle --mangle-ip-s 192.168.3.38 4. service arptables_jf save 5. chkconfig arptables_jf on 6. ifconfig eth0:1 192.168.3.40 netmask 255.255.248.0 broadcast 192.168.3.255 up (For subsequent reboot, you will have to create a file under /etc/sysconfig/network-scripts/ifcfg-eth0:1) and need to put values for vip (192.168.3.40) address. Then restart httpd service in kiwidev4 and let me know if it works. Please also post ipvsadm -L -n output after this... :) Regards Tapan India On Fri, Nov 6, 2009 at 12:23 AM, mojorising <[email protected]> wrote: > Okay. It seems I missed a critical piece of my config file when I > copy/pasted it to you. Sorry about that. > > So here is my ha.cf file now > > [root@omsbuild ~]# cat /etc/sysconfig/ha/lvs.cf > serial_no = 93 > primary = 192.168.3.28 > service = lvs > backup = 0.0.0.0 > heartbeat = 1 > heartbeat_port = 539 > keepalive = 6 > deadtime = 18 > network = direct > debug_level = NONE > virtual test1 { > active = 1 > address = 192.168.3.40 eth0:1 > vip_nmask = 255.255.248.0 > port = 80 > expect = "HTTP" > use_regex = 0 > load_monitor = none > scheduler = lc > protocol = tcp > timeout = 6 > reentry = 15 > quiesce_server = 0 > server kiwidev4 { > address = 192.168.3.38 > active = 1 > port = 80 > weight = 1 > } > } > > > I took out those other machines because I can not change their IPs > (I'm just using them for testing). So in their place, I put a machine > (kiwidev4) that happens to be on the same subnet as the LVS box. > kiwidev4 was always there and active but that part of the config file > was accidentally clipped off from my message. :( > > I can not change those iptables rules at this time because that > kiwidev4 box may be in use for some other testing at the moment. Can > we do this without making the specified changes to iptables? It seems > we shouldn't need to do that. I will eventually be using LVS to > balance traffic to Windows machines as well so I need to be able to do > without iptables for that reason also. > > > Mike > > > On 04/11/2009, Tapan Thapa <[email protected]> wrote: > > Hello Mike, > > > > Now your network status looks good. > > > > But still i can not see any real server on the same network. i.e. > > 192.168.3.x. > > > > As per your lvs.cf, you have configured two real servers. First one is > > server Speedy and second one is server test1 and currently both are not > > active. (active = 0) They should be (active = 1). > > > > And also your real servers are not in right subnet. > > > > Your real server should be on same 192.168.3.x network. > > > > Your example lvs.cf should look like: > > > > serial_no = 93 > > primary = 192.168.3.28 > > service = lvs > > backup = 0.0.0.0 > > heartbeat = 1 > > heartbeat_port = 539 > > keepalive = 6 > > deadtime = 18 > > network = direct > > debug_level = NONE > > virtual test1 { > > active = 1 > > address = 192.168.3.40 eth0:1 > > vip_nmask = 255.255.248.0 > > port = 80 > > expect = "HTTP" > > use_regex = 0 > > load_monitor = none > > scheduler = lc > > protocol = tcp > > timeout = 6 > > reentry = 15 > > quiesce_server = 0 > > server Speedy { > > address = 192.168.3.29 > > active = 1 > > port = 80 > > weight = 1 > > } > > server test1 { > > address = 192.168.3.30 > > active = 1 > > port = 80 > > weight = 1 > > } > > > > Please change the ip address of Speedy server to 192.168.3.29 and test1 > > server to 192.168.3.30 with subnet mask of 255.255.248.0 and restart > > network > > and httpd service. > > > > then fire below mentioned commands in both real servers (Not in lvs > > server): > > > > chkconfig iptables on > > iptables -F > > iptables -t nat -A PREROUTING -p tcp --dport 80 -d 192.168.3.40 -j > REDIRECT > > service iptables save > > > > then please restart pulse service at linux director server (lvs server) > and > > wait for 2 minutes. and then check the status of ipvsadm -L -n command > and > > let me know in case any issues. > > > > > > Regards > > Tapan Thapa > > India > > > > > > > > On Thu, Nov 5, 2009 at 1:25 AM, mojorising <[email protected]> wrote: > > > >> Tapan, sorry for confusing you. I overlooked my virtual IP and > >> accidedntally left it with an IP on the wrong net. This is now > >> corrected. > >> > >> Those real servers on other nets are still in my configuration but > >> they are "down," as they were before. I do have one real server up on > >> the proper net -- 192.168.3.38. > >> > >> > >> My present network interface set-up: > >> > >> eth0 Link encap:Ethernet HWaddr 00:50:56:AE:14:E3 > >> inet addr:192.168.3.28 Bcast:192.168.7.255 Mask:255.255.248.0 > >> inet6 addr: fe80::250:56ff:feae:14e3/64 Scope:Link > >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > >> RX packets:36180876 errors:1122 dropped:1234 overruns:0 > frame:0 > >> TX packets:8729361 errors:0 dropped:0 overruns:0 carrier:0 > >> collisions:0 txqueuelen:1000 > >> RX bytes:72196093 (68.8 MiB) TX bytes:610192805 (581.9 MiB) > >> Interrupt:177 Base address:0x1400 > >> > >> eth0:1 Link encap:Ethernet HWaddr 00:50:56:AE:14:E3 > >> inet addr:192.168.3.40 Bcast:192.168.7.255 > Mask:255.255.248.0 > >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > >> Interrupt:177 Base address:0x1400 > >> > >> > >> A problem is that I am still getting those error messages from nanny: > >> > >> Nov 4 11:06:52 omsbuild nanny[16919]: READ to 192.168.3.38:80 timed > out > >> Nov 4 11:06:53 omsbuild nanny[20548]: READ to 192.168.3.38:80 timed > out > >> Nov 4 11:07:04 omsbuild nanny[16919]: READ to 192.168.3.38:80 timed > out > >> Nov 4 11:07:05 omsbuild nanny[20548]: READ to 192.168.3.38:80 timed > out > >> > >> > >> My lvs.cf file now: > >> > >> serial_no = 93 > >> primary = 192.168.3.28 > >> service = lvs > >> backup = 0.0.0.0 > >> heartbeat = 1 > >> heartbeat_port = 539 > >> keepalive = 6 > >> deadtime = 18 > >> network = direct > >> debug_level = NONE > >> virtual test1 { > >> active = 1 > >> address = 192.168.3.40 eth0:1 > >> vip_nmask = 255.255.248.0 > >> port = 80 > >> expect = "HTTP" > >> use_regex = 0 > >> load_monitor = none > >> scheduler = lc > >> protocol = tcp > >> timeout = 6 > >> reentry = 15 > >> quiesce_server = 0 > >> server Speedy { > >> address = 192.168.18.29 > >> active = 0 > >> port = 80 > >> weight = 1 > >> } > >> server test1 { > >> address = 65.39.179.197 > >> active = 0 > >> port = 80 > >> weight = 1 > >> } > >> > >> > >> > >> Mike > >> > >> > >> On 03/11/2009, Tapan Thapa <[email protected]> wrote: > >> > Hello Mike, > >> > > >> > Thanks for providing helpful information. > >> > > >> > Now as i understood from your configuration, you have two networks on > >> eth0. > >> > > >> > 1. 192.168.3.x (on eth0) > >> > 2. 192.168.0.x (on eth0:1).. (Is it map with any external ip address?) > >> > (Please provide netstat -rn output here.) > >> > > >> > Your one of real server is on completely new network subnet > >> (192.168.18.x) > >> > and your second real server is on public ip 65.39.179.197 and > currently > >> > none > >> > of them are active. > >> > > >> > I don't think this configuration will work. > >> > > >> > Your configuration should be like: > >> > > >> > 1. Any network like 192.168.0.x on (eth0) > >> > 2. Floating IP Address/Virtual IP Address 192.168.0.254 on (eth0:1) > and > >> it > >> > must be map with any pubic ip address in case you want to access this > >> > VIP > >> > from outside of your network. During testing it is not required to map > >> > it > >> > with any public ip address. > >> > 3. Your real server should be on the same network 192.168.0.x (I.e. > >> > 192.168.0.1/2/3). > >> > > >> > If you are planning to use Linux Director in Direct Mode then their > >> > must > >> be > >> > an existing gateway available. > >> > > >> > All real servers and Linux Director should point to their gateway > >> > towards > >> > that router/gateway. > >> > > >> > As far as your listing of port/service question is concern, If your > >> > linux > >> > director works properly, still your linux director will not listen on > >> port > >> > 80 but your load balancing will work. (I was also confused on this for > >> > 2 > >> > days and after 2 days i realize that load balancing is working > although > >> > port > >> > 80 is not listing.) > >> > > >> > Note: Please stick with one configuration as when you post your > >> > problem, > >> > your linux directory was working under Direct mode and now it is > >> > working > >> in > >> > tunnel mode. (I have no experience of tunnel mode but i can help you > on > >> > direct and nat mode.) > >> > > >> > Regards > >> > Tapan Thapa > >> > India > >> > > >> > On Wed, Nov 4, 2009 at 1:16 AM, mojorising <[email protected]> > wrote: > >> > > >> >> Thanks for your offers of help! > >> >> > >> >> I have made some changes since reading your message saying the > servers > >> >> should all be on the same net -- now I have one real server and it is > >> >> on the same network as the load balancer. The output of the ipvsadmn > >> >> command you requested is below. > >> >> > >> >> [root@omsbuild ~]# ipvsadm -L -n > >> >> IP Virtual Server version 1.2.1 (size=4096) > >> >> Prot LocalAddress:Port Scheduler Flags > >> >> -> RemoteAddress:Port Forward Weight ActiveConn InActConn > >> >> TCP 192.168.0.69:80 lc > >> >> > >> >> NIC/IP information: > >> >> > >> >> [root@omsbuild ~]# ifconfig -a > >> >> eth0 Link encap:Ethernet HWaddr 00:50:56:AE:14:E3 > >> >> inet addr:192.168.3.28 Bcast:192.168.7.255 > >> >> Mask:255.255.248.0 > >> >> inet6 addr: fe80::250:56ff:feae:14e3/64 Scope:Link > >> >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > >> >> RX packets:35121740 errors:1120 dropped:1231 overruns:0 > >> >> frame:0 > >> >> TX packets:8682408 errors:0 dropped:0 overruns:0 carrier:0 > >> >> collisions:0 txqueuelen:1000 > >> >> RX bytes:4182471094 (3.8 GiB) TX bytes:606337720 (578.2 > MiB) > >> >> Interrupt:177 Base address:0x1400 > >> >> > >> >> eth0:1 Link encap:Ethernet HWaddr 00:50:56:AE:14:E3 > >> >> inet addr:192.168.0.69 Bcast:192.168.7.255 > >> >> Mask:255.255.248.0 > >> >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > >> >> Interrupt:177 Base address:0x1400 > >> >> > >> >> > >> >> I'm still getting the same errors from nanny even though the real > >> >> server is now on the same net as the load balancer: > >> >> > >> >> Nov 3 10:44:22 omsbuild nanny[16919]: READ to 192.168.3.38:80 timed > >> out > >> >> > >> >> As represented in eth0:1, my virtual server is listening on > >> >> 192.168.0.69:80. If I do netstat, do a port/service check from a > >> >> workstation to that IP or similar, shouldn't I see the load balancer > >> >> listening on 80? Right now, I do not see the load balancer waiting > for > >> >> connections on port 80. > >> >> > >> >> Here is what my lvs.conf file looks like now: > >> >> > >> >> serial_no = 89 > >> >> primary = 192.168.3.28 > >> >> service = lvs > >> >> backup = 0.0.0.0 > >> >> heartbeat = 1 > >> >> heartbeat_port = 539 > >> >> keepalive = 6 > >> >> deadtime = 18 > >> >> network = tunnel > >> >> debug_level = NONE > >> >> virtual test1 { > >> >> active = 1 > >> >> address = 192.168.0.69 eth0:1 > >> >> vip_nmask = 255.255.248.0 > >> >> port = 80 > >> >> expect = "HTTP" > >> >> use_regex = 0 > >> >> load_monitor = none > >> >> scheduler = lc > >> >> protocol = tcp > >> >> timeout = 6 > >> >> reentry = 15 > >> >> quiesce_server = 0 > >> >> server Speedy { > >> >> address = 192.168.18.29 > >> >> active = 0 > >> >> port = 80 > >> >> weight = 1 > >> >> } > >> >> server test1 { > >> >> address = 65.39.179.197 > >> >> active = 0 > >> >> port = 80 > >> >> weight = 1 > >> >> } > >> >> : > >> >> > >> >> > >> >> Mike > >> >> > >> >> > >> >> On 02/11/2009, Tapan Thapa <[email protected]> wrote: > >> >> > Hello Mike, > >> >> > > >> >> > I am not an expert in IPVS but recently i have setup IPVS with the > >> help > >> >> of > >> >> > Piranha and i am quite comfortable with IPVS. > >> >> > > >> >> > Please let me know your Network diagram and also the output of > below > >> >> > mentioned command. > >> >> > > >> >> > ipvsadm -L -n > >> >> > > >> >> > ---------------------------------------- > >> >> > I think your network diagram should be--- > >> >> > > >> >> > Linux Director ----(One NIC)--->First Real Server (One NIC) > >> >> > --->Second Real Server (One > >> NIC) > >> >> > ---------------------------------------------- > >> >> > > >> >> > Your Linux Director and Your real server should be on the same > >> >> > network > >> >> > segment. Please also post your Linux Director's (Where you have > >> >> > installed > >> >> > Piranha) Network cards ip information. > >> >> > > >> >> > > >> >> > Regards > >> >> > Tapan Thapa > >> >> > India > >> >> > > >> >> > On Tue, Nov 3, 2009 at 6:09 AM, mojorising <[email protected]> > >> wrote: > >> >> > > >> >> >> Hello! > >> >> >> > >> >> >> I have set up a test load balancer with IPVS and Piranha-GUI. For > >> some > >> >> >> reason, when I attempt to connect to one of the two web servers I > >> have > >> >> >> set-up via the load balancer's virtual IP, the load balancer does > >> >> >> not > >> >> >> seem to pass those requests on to the real servers. > >> >> >> > >> >> >> The firewall on the Piranha box is off and I can successfully > >> >> >> establish HTTP sessions with netcat and telnet from the Piranha > box > >> as > >> >> >> well as from my workstation. So the web services are running and > >> >> >> connectivity to them is good. > >> >> >> > >> >> >> The error I'm getting in /var/log/messages is (public IP changed > >> >> >> for > >> >> >> privacy): > >> >> >> > >> >> >> Nov 2 14:28:09 omsbuild nanny[13583]: READ to 65.39.169.xxx:80 > >> >> >> timed > >> >> out > >> >> >> Nov 2 14:28:10 omsbuild nanny[13582]: READ to > >> >> >> 192.168.18.29:80timed > >> >> out > >> >> >> > >> >> >> It looks like nanny can't talk to the web servers but I can't > >> >> >> figure > >> >> >> out why. That may not be the only problem I have here but it's > >> >> >> probably one of them. All the other services are up and seem to be > >> >> >> running fine. > >> >> >> > >> >> >> I've googled around quite a bit and checked the documentation but > I > >> >> >> haven't found anything in those places that gets me to a solution. > >> >> >> > >> >> >> Can anyone out there give me a little push in the right direction > >> >> >> as > >> >> >> to what the problem might be? > >> >> >> > >> >> >> > >> >> >> Thank you! > >> >> >> > >> >> >> Mike > >> >> >> > >> >> >> > >> >> >> My lvs.conf file: > >> >> >> > >> >> >> serial_no = 76 > >> >> >> primary = 192.168.3.28 > >> >> >> service = lvs > >> >> >> backup = 0.0.0.0 > >> >> >> heartbeat = 1 > >> >> >> heartbeat_port = 539 > >> >> >> keepalive = 6 > >> >> >> deadtime = 18 > >> >> >> network = direct > >> >> >> debug_level = NONE > >> >> >> virtual test1 { > >> >> >> active = 1 > >> >> >> address = 192.168.0.69 eth0:1 > >> >> >> vip_nmask = 255.255.248.0 > >> >> >> port = 3128 > >> >> >> expect = "HTTP" > >> >> >> use_regex = 0 > >> >> >> load_monitor = none > >> >> >> scheduler = lc > >> >> >> protocol = tcp > >> >> >> timeout = 6 > >> >> >> reentry = 15 > >> >> >> quiesce_server = 0 > >> >> >> server Speedy { > >> >> >> address = 192.168.18.29 > >> >> >> active = 1 > >> >> >> port = 80 > >> >> >> weight = 1 > >> >> >> } > >> >> >> server test1 { > >> >> >> address = 65.39.169.xxx > >> >> >> active = 1 > >> >> >> port = 80 > >> >> >> weight = 1 > >> >> >> } > >> >> >> > >> >> >> _______________________________________________ > >> >> >> Piranha-list mailing list > >> >> >> [email protected] > >> >> >> https://www.redhat.com/mailman/listinfo/piranha-list > >> >> >> > >> >> > > >> >> > >> >> _______________________________________________ > >> >> Piranha-list mailing list > >> >> [email protected] > >> >> https://www.redhat.com/mailman/listinfo/piranha-list > >> >> > >> > > >> > >> _______________________________________________ > >> Piranha-list mailing list > >> [email protected] > >> https://www.redhat.com/mailman/listinfo/piranha-list > >> > > > > _______________________________________________ > Piranha-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/piranha-list > --00032555488ee711750477abd0e6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello Mike,<br><br>Now your network and config file looks perfectly ok.<br>= <br>As you are using direct routing so your real server (kiwidev4) has two = options.<br><br>1st - Use iptables to redirect traffic destined by linux di= rector to real server.<br> 2nd - Use arptables_jf method. (yum install arptables_jf).<br><br>As you to= ld that you can not modify iptables rules as kiwidev4 machine is being used= for other purpose as well so you have to use method 2 (arptables_jf).<br> <br>Below are the steps which you need to performed on real server/servers = only:<br><br>1. Install arptables_jf rpm from redhat distribution cd or fro= m internet into kiwidev4.<br>2. arptables -A IN -d 192.168.3.40 -j DROP<br> 3. arptables -A OUT -d 192.168.3.40 -j mangle --mangle-ip-s 192.168.3.38<br= >4. service arptables_jf save<br>5. chkconfig arptables_jf on<br>6. ifconfi= g eth0:1 192.168.3.40 netmask 255.255.248.0 broadcast 192.168.3.255 up<br> (For subsequent reboot, you will have to create a file under /etc/sysconfig= /network-scripts/ifcfg-eth0:1) and need to put values for vip (192.168.3.40= ) address.<br><br>Then restart httpd service in kiwidev4 and let me know if= it works.<br> <br>Please also post ipvsadm -L -n output after this... :)<br><br>Regards<b= r>Tapan <br>India<br><br><div class=3D"gmail_quote">On Fri, Nov 6, 2009 at = 12:23 AM, mojorising <span dir=3D"ltr"><<a href=3D"mailto:moj0rising@aim= .com">[email protected]</a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, = 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Okay. It seems I = missed a critical piece of my config file when I<br> copy/pasted it to you. Sorry about that.<br> <br> So here is my <a href=3D"http://ha.cf" target=3D"_blank">ha.cf</a> file now= <br> <br> [root@omsbuild ~]# cat /etc/sysconfig/ha/<a href=3D"http://lvs.cf" target= =3D"_blank">lvs.cf</a><br> <div class=3D"im">serial_no =3D 93<br> primary =3D 192.168.3.28<br> service =3D lvs<br> backup =3D 0.0.0.0<br> heartbeat =3D 1<br> heartbeat_port =3D 539<br> keepalive =3D 6<br> deadtime =3D 18<br> network =3D direct<br> debug_level =3D NONE<br> virtual test1 {<br> =A0 =A0 active =3D 1<br> =A0 =A0 address =3D 192.168.3.40 eth0:1<br> =A0 =A0 vip_nmask =3D 255.255.248.0<br> =A0 =A0 port =3D 80<br> =A0 =A0 expect =3D "HTTP"<br> =A0 =A0 use_regex =3D 0<br> =A0 =A0 load_monitor =3D none<br> =A0 =A0 scheduler =3D lc<br> =A0 =A0 protocol =3D tcp<br> =A0 =A0 timeout =3D 6<br> =A0 =A0 reentry =3D 15<br> =A0 =A0 quiesce_server =3D 0<br> </div> =A0 =A0 server kiwidev4 {<br> =A0 =A0 =A0 =A0 address =3D 192.168.3.38<br> <div class=3D"im"> =A0 =A0 =A0 =A0 active =3D 1<br> =A0 =A0 =A0 =A0 port =3D 80<br> =A0 =A0 =A0 =A0 weight =3D 1<br> =A0 =A0 }<br> }<br> <br> <br> </div>I took out those other machines because I can not change their IPs<br= > (I'm just using them for testing). So in their place, I put a machine<b= r> (kiwidev4) that happens to be on the same subnet as the LVS box.<br> kiwidev4 was always there and active but that part of the config file<br> was accidentally clipped off from my message. =A0:(<br> <br> I can not change those iptables rules at this time because that<br> kiwidev4 box may be in use for some other testing at the moment. Can<br> we do this without making the specified changes to iptables? It seems<br> we shouldn't need to do that. I will eventually be using LVS to<br> balance traffic to Windows machines as well so I need to be able to do<br> without iptables for that reason also.<br> <br> <br> Mike<br> <div><div></div><div class=3D"h5"><br> <br> On 04/11/2009, Tapan Thapa <<a href=3D"mailto:[email protected]"= >[email protected]</a>> wrote:<br> > Hello Mike,<br> ><br> > Now your network status looks good.<br> ><br> > But still i can not see any real server on the same network. i.e.<br> > 192.168.3.x.<br> ><br> > As per your <a href=3D"http://lvs.cf" target=3D"_blank">lvs.cf</a>, yo= u have configured two real servers. First one is<br> > server Speedy and second one is server test1 and currently both are no= t<br> > active. (active =3D 0) They should be (active =3D 1).<br> ><br> > And also your real servers are not in right subnet.<br> ><br> > Your real server should be on same 192.168.3.x network.<br> ><br> > Your example <a href=3D"http://lvs.cf" target=3D"_blank">lvs.cf</a> sh= ould look like:<br> ><br> > serial_no =3D 93<br> > primary =3D 192.168.3.28<br> > service =3D lvs<br> > backup =3D 0.0.0.0<br> > heartbeat =3D 1<br> > heartbeat_port =3D 539<br> > keepalive =3D 6<br> > deadtime =3D 18<br> > network =3D direct<br> > debug_level =3D NONE<br> > virtual test1 {<br> > =A0 =A0 active =3D 1<br> > =A0 =A0 =A0address =3D 192.168.3.40 eth0:1<br> > =A0 =A0 vip_nmask =3D 255.255.248.0<br> > =A0 =A0 port =3D 80<br> > =A0 =A0 expect =3D "HTTP"<br> > =A0 =A0 use_regex =3D 0<br> > =A0 =A0 load_monitor =3D none<br> > =A0 =A0 scheduler =3D lc<br> > =A0 =A0 protocol =3D tcp<br> > =A0 =A0 timeout =3D 6<br> > =A0 =A0 reentry =3D 15<br> > =A0 =A0 quiesce_server =3D 0<br> > =A0 =A0 server Speedy {<br> > =A0 =A0 =A0 =A0 address =3D 192.168.3.29<br> > =A0 =A0 =A0 =A0 active =3D 1<br> > =A0 =A0 =A0 =A0 port =3D 80<br> > =A0 =A0 =A0 =A0 weight =3D 1<br> > =A0 =A0 }<br> > =A0 =A0 server test1 {<br> > =A0 =A0 =A0 =A0 address =3D 192.168.3.30<br> > =A0 =A0 =A0 =A0 active =3D 1<br> > =A0 =A0 =A0 =A0 port =3D 80<br> > =A0 =A0 =A0 =A0 weight =3D 1<br> > =A0 =A0 }<br> ><br> > Please change the ip address of Speedy server to 192.168.3.29 and test= 1<br> > server to 192.168.3.30 with subnet mask of 255.255.248.0 and restart<b= r> > network<br> > and httpd service.<br> ><br> > then fire below mentioned commands in both real servers (Not in lvs<br= > > server):<br> ><br> > chkconfig iptables on<br> > iptables -F<br> > iptables -t nat -A PREROUTING -p tcp --dport 80 -d 192.168.3.40 -j RED= IRECT<br> > service iptables save<br> ><br> > then please restart pulse service at linux director server (lvs server= ) and<br> > wait for 2 minutes. and then check the status of ipvsadm -L -n command= and<br> > let me know in case any issues.<br> ><br> ><br> > Regards<br> > Tapan Thapa<br> > India<br> ><br> ><br> ><br> > On Thu, Nov 5, 2009 at 1:25 AM, mojorising <<a href=3D"mailto:moj0r= [email protected]">[email protected]</a>> wrote:<br> ><br> >> Tapan, sorry for confusing you. I overlooked my virtual IP and<br> >> accidedntally left it with an IP on the wrong net. This is now<br> >> corrected.<br> >><br> >> Those real servers on other nets are still in my configuration but= <br> >> they are "down," as they were before. I do have one real= server up on<br> >> the proper net -- =A0 =A0 =A0 192.168.3.38.<br> >><br> >><br> >> My present network interface set-up:<br> >><br> >> eth0 =A0 =A0 =A0Link encap:Ethernet =A0HWaddr 00:50:56:AE:14:E3<br= > >> =A0 =A0 =A0 =A0 =A0inet addr:192.168.3.28 =A0Bcast:192.168.7.255 = =A0Mask:255.255.248.0<br> >> =A0 =A0 =A0 =A0 =A0inet6 addr: fe80::250:56ff:feae:14e3/64 Scope:L= ink<br> >> =A0 =A0 =A0 =A0 =A0UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0M= etric:1<br> >> =A0 =A0 =A0 =A0 =A0 RX packets:36180876 errors:1122 dropped:1234 o= verruns:0 frame:0<br> >> =A0 =A0 =A0 =A0 =A0TX packets:8729361 errors:0 dropped:0 overruns:= 0 carrier:0<br> >> =A0 =A0 =A0 =A0 =A0collisions:0 txqueuelen:1000<br> >> =A0 =A0 =A0 =A0 =A0RX bytes:72196093 (68.8 MiB) =A0TX bytes:610192= 805 (581.9 MiB)<br> >> =A0 =A0 =A0 =A0 =A0 Interrupt:177 Base address:0x1400<br> >><br> >> eth0:1 =A0 =A0Link encap:Ethernet =A0HWaddr 00:50:56:AE:14:E3<br> >> =A0 =A0 =A0 =A0 =A0 inet addr:192.168.3.40 =A0Bcast:192.168.7.255 = =A0Mask:255.255.248.0<br> >> =A0 =A0 =A0 =A0 =A0 UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0= Metric:1<br> >> =A0 =A0 =A0 =A0 =A0Interrupt:177 Base address:0x1400<br> >><br> >><br> >> A problem is that I am still getting those error messages from nan= ny:<br> >><br> >> Nov =A04 11:06:52 omsbuild nanny[16919]: READ to <a href=3D"http:/= /192.168.3.38:80" target=3D"_blank">192.168.3.38:80</a> timed out<br> >> Nov =A04 11:06:53 omsbuild nanny[20548]: READ to <a href=3D"http:/= /192.168.3.38:80" target=3D"_blank">192.168.3.38:80</a> timed out<br> >> Nov =A04 11:07:04 omsbuild nanny[16919]: READ to <a href=3D"http:/= /192.168.3.38:80" target=3D"_blank">192.168.3.38:80</a> timed out<br> >> Nov =A04 11:07:05 omsbuild nanny[20548]: READ to <a href=3D"http:/= /192.168.3.38:80" target=3D"_blank">192.168.3.38:80</a> timed out<br> >><br> >><br> >> My <a href=3D"http://lvs.cf" target=3D"_blank">lvs.cf</a> file now= :<br> >><br> >> serial_no =3D 93<br> >> primary =3D 192.168.3.28<br> >> service =3D lvs<br> >> backup =3D 0.0.0.0<br> >> heartbeat =3D 1<br> >> heartbeat_port =3D 539<br> >> keepalive =3D 6<br> >> deadtime =3D 18<br> >> network =3D direct<br> >> debug_level =3D NONE<br> >> virtual test1 {<br> >> =A0 =A0 active =3D 1<br> >> =A0 =A0 =A0address =3D 192.168.3.40 eth0:1<br> >> =A0 =A0 =A0vip_nmask =3D 255.255.248.0<br> >> =A0 =A0 port =3D 80<br> >> =A0 =A0 expect =3D "HTTP"<br> >> =A0 =A0 use_regex =3D 0<br> >> =A0 =A0 load_monitor =3D none<br> >> =A0 =A0 scheduler =3D lc<br> >> =A0 =A0 protocol =3D tcp<br> >> =A0 =A0 timeout =3D 6<br> >> =A0 =A0 reentry =3D 15<br> >> =A0 =A0 quiesce_server =3D 0<br> >> =A0 =A0 server Speedy {<br> >> =A0 =A0 =A0 =A0 address =3D 192.168.18.29<br> >> =A0 =A0 =A0 =A0 active =3D 0<br> >> =A0 =A0 =A0 =A0 port =3D 80<br> >> =A0 =A0 =A0 =A0 weight =3D 1<br> >> =A0 =A0 }<br> >> =A0 =A0 server test1 {<br> >> =A0 =A0 =A0 =A0 address =3D 65.39.179.197<br> >> =A0 =A0 =A0 =A0 active =3D 0<br> >> =A0 =A0 =A0 =A0 port =3D 80<br> >> =A0 =A0 =A0 =A0 weight =3D 1<br> >> =A0 =A0 }<br> >><br> >><br> >><br> >> Mike<br> >><br> >><br> >> On 03/11/2009, Tapan Thapa <<a href=3D"mailto:tapan.thapa2000@g= mail.com">[email protected]</a>> wrote:<br> >> > Hello Mike,<br> >> ><br> >> > Thanks for providing helpful information.<br> >> ><br> >> > Now as i understood from your configuration, you have two net= works on<br> >> eth0.<br> >> ><br> >> > 1. 192.168.3.x (on eth0)<br> >> > 2. 192.168.0.x (on eth0:1).. (Is it map with any external ip = address?)<br> >> > (Please provide netstat -rn output here.)<br> >> ><br> >> > Your one of real server is on completely new network subnet<b= r> >> (192.168.18.x)<br> >> > and your second real server is on public ip 65.39.179.197 and= currently<br> >> > none<br> >> > of them are active.<br> >> ><br> >> > I don't think this configuration will work.<br> >> ><br> >> > Your configuration should be like:<br> >> ><br> >> > 1. Any network like 192.168.0.x on (eth0)<br> >> > 2. Floating IP Address/Virtual IP Address 192.168.0.254 on (e= th0:1) and<br> >> it<br> >> > must be map with any pubic ip address in case you want to acc= ess this<br> >> > VIP<br> >> > from outside of your network. During testing it is not requir= ed to map<br> >> > it<br> >> > with any public ip address.<br> >> > 3. Your real server should be on the same network 192.168.0.x= (I.e.<br> >> > <a href=3D"http://192.168.0.1/2/3" target=3D"_blank">192.168.= 0.1/2/3</a>).<br> >> ><br> >> > If you are planning to use Linux Director in Direct Mode then= their<br> >> > must<br> >> be<br> >> > an existing gateway available.<br> >> ><br> >> > All real servers and Linux Director should point to their gat= eway<br> >> > towards<br> >> > that router/gateway.<br> >> ><br> >> > As far as your listing of port/service question is concern, I= f your<br> >> > linux<br> >> > director works properly, still your linux director will not l= isten on<br> >> port<br> >> > 80 but your load balancing will work. (I was also confused on= this for<br> >> > 2<br> >> > days and after 2 days i realize that load balancing is workin= g although<br> >> > port<br> >> > 80 is not listing.)<br> >> ><br> >> > Note: Please stick with one configuration as when you post yo= ur<br> >> > problem,<br> >> > your linux directory was working under Direct mode and now it= is<br> >> > working<br> >> in<br> >> > tunnel mode. (I have no experience of tunnel mode but i can h= elp you on<br> >> > direct and nat mode.)<br> >> ><br> >> > Regards<br> >> > Tapan Thapa<br> >> > India<br> >> ><br> >> > On Wed, Nov 4, 2009 at 1:16 AM, mojorising <<a href=3D"mai= lto:[email protected]">[email protected]</a>> wrote:<br> >> ><br> >> >> Thanks for your offers of help!<br> >> >><br> >> >> I have made some changes since reading your message sayin= g the servers<br> >> >> should all be on the same net -- now I have one real serv= er and it is<br> >> >> on the same network as the load balancer. The output of t= he ipvsadmn<br> >> >> command you requested is below.<br> >> >><br> >> >> [root@omsbuild ~]# ipvsadm -L -n<br> >> >> IP Virtual Server version 1.2.1 (size=3D4096)<br> >> >> Prot LocalAddress:Port Scheduler Flags<br> >> >> =A0-> RemoteAddress:Port =A0 =A0 =A0 =A0 =A0 Forward W= eight ActiveConn InActConn<br> >> >> TCP =A0<a href=3D"http://192.168.0.69:80" target=3D"_blan= k">192.168.0.69:80</a> lc<br> >> >><br> >> >> NIC/IP information:<br> >> >><br> >> >> [root@omsbuild ~]# ifconfig -a<br> >> >> eth0 =A0 =A0 =A0Link encap:Ethernet =A0HWaddr 00:50:56:AE= :14:E3<br> >> >> =A0 =A0 =A0 =A0 =A0inet addr:192.168.3.28 =A0Bcast:192.16= 8.7.255<br> >> >> Mask:255.255.248.0<br> >> >> =A0 =A0 =A0 =A0 =A0inet6 addr: fe80::250:56ff:feae:14e3/6= 4 Scope:Link<br> >> >> =A0 =A0 =A0 =A0 =A0UP BROADCAST RUNNING MULTICAST =A0MTU:= 1500 =A0Metric:1<br> >> >> =A0 =A0 =A0 =A0 =A0RX packets:35121740 errors:1120 droppe= d:1231 overruns:0<br> >> >> frame:0<br> >> >> =A0 =A0 =A0 =A0 =A0TX packets:8682408 errors:0 dropped:0 = overruns:0 carrier:0<br> >> >> =A0 =A0 =A0 =A0 =A0collisions:0 txqueuelen:1000<br> >> >> =A0 =A0 =A0 =A0 =A0RX bytes:4182471094 (3.8 GiB) =A0TX by= tes:606337720 (578.2 MiB)<br> >> >> =A0 =A0 =A0 =A0 =A0Interrupt:177 Base address:0x1400<br> >> >><br> >> >> eth0:1 =A0 =A0Link encap:Ethernet =A0HWaddr 00:50:56:AE:1= 4:E3<br> >> >> =A0 =A0 =A0 =A0 =A0inet addr:192.168.0.69 =A0Bcast:192.16= 8.7.255<br> >> >> Mask:255.255.248.0<br> >> >> =A0 =A0 =A0 =A0 =A0UP BROADCAST RUNNING MULTICAST =A0MTU:= 1500 =A0Metric:1<br> >> >> =A0 =A0 =A0 =A0 =A0Interrupt:177 Base address:0x1400<br> >> >><br> >> >><br> >> >> I'm still getting the same errors from nanny even tho= ugh the real<br> >> >> server is now on the same net as the load balancer:<br> >> >><br> >> >> Nov =A03 10:44:22 omsbuild nanny[16919]: READ to <a href= =3D"http://192.168.3.38:80" target=3D"_blank">192.168.3.38:80</a> timed<br> >> out<br> >> >><br> >> >> As represented in eth0:1, my virtual server is listening = on<br> >> >> <a href=3D"http://192.168.0.69:80" target=3D"_blank">192.= 168.0.69:80</a>. If I do netstat, do a port/service check from a<br> >> >> workstation to that IP or similar, shouldn't I see th= e load balancer<br> >> >> listening on 80? Right now, I do not see the load balance= r waiting for<br> >> >> connections on port 80.<br> >> >><br> >> >> Here is what my lvs.conf file looks like now:<br> >> >><br> >> >> serial_no =3D 89<br> >> >> primary =3D 192.168.3.28<br> >> >> service =3D lvs<br> >> >> backup =3D 0.0.0.0<br> >> >> heartbeat =3D 1<br> >> >> heartbeat_port =3D 539<br> >> >> keepalive =3D 6<br> >> >> deadtime =3D 18<br> >> >> network =3D tunnel<br> >> >> debug_level =3D NONE<br> >> >> virtual test1 {<br> >> >> =A0 =A0 active =3D 1<br> >> >> =A0 =A0 address =3D 192.168.0.69 eth0:1<br> >> >> =A0 =A0 vip_nmask =3D 255.255.248.0<br> >> >> =A0 =A0 =A0port =3D 80<br> >> >> =A0 =A0 =A0expect =3D "HTTP"<br> >> >> =A0 =A0 use_regex =3D 0<br> >> >> =A0 =A0 load_monitor =3D none<br> >> >> =A0 =A0 scheduler =3D lc<br> >> >> =A0 =A0 protocol =3D tcp<br> >> >> =A0 =A0 timeout =3D 6<br> >> >> =A0 =A0 reentry =3D 15<br> >> >> =A0 =A0 quiesce_server =3D 0<br> >> >> =A0 =A0 server Speedy {<br> >> >> =A0 =A0 =A0 =A0 address =3D 192.168.18.29<br> >> >> =A0 =A0 =A0 =A0 active =3D 0<br> >> >> =A0 =A0 =A0 =A0 port =3D 80<br> >> >> =A0 =A0 =A0 =A0 weight =3D 1<br> >> >> =A0 =A0 }<br> >> >> =A0 =A0 server test1 {<br> >> >> =A0 =A0 =A0 =A0 =A0address =3D 65.39.179.197<br> >> >> =A0 =A0 =A0 =A0 active =3D 0<br> >> >> =A0 =A0 =A0 =A0 port =3D 80<br> >> >> =A0 =A0 =A0 =A0 weight =3D 1<br> >> >> =A0 =A0 }<br> >> >> :<br> >> >><br> >> >><br> >> >> Mike<br> >> >><br> >> >><br> >> >> On 02/11/2009, Tapan Thapa <<a href=3D"mailto:tapan.th= [email protected]">[email protected]</a>> wrote:<br> >> >> > Hello Mike,<br> >> >> ><br> >> >> > I am not an expert in IPVS but recently i have setup= IPVS with the<br> >> help<br> >> >> of<br> >> >> > Piranha and i am quite comfortable with IPVS.<br> >> >> ><br> >> >> > Please let me know your Network diagram and also the= output of below<br> >> >> > mentioned command.<br> >> >> ><br> >> >> > ipvsadm -L -n<br> >> >> ><br> >> >> > ----------------------------------------<br> >> >> > I think your network diagram should be---<br> >> >> ><br> >> >> > Linux Director ----(One NIC)--->First Real Server= (One NIC)<br> >> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0--->Second Real Server (One<br> >> NIC)<br> >> >> > ----------------------------------------------<br> >> >> ><br> >> >> > Your Linux Director and Your real server should be o= n the same<br> >> >> > network<br> >> >> > segment. Please also post your Linux Director's = (Where you have<br> >> >> > installed<br> >> >> > Piranha) Network cards ip information.<br> >> >> ><br> >> >> ><br> >> >> > Regards<br> >> >> > Tapan Thapa<br> >> >> > India<br> >> >> ><br> >> >> > On Tue, Nov 3, 2009 at 6:09 AM, mojorising <<a hr= ef=3D"mailto:[email protected]">[email protected]</a>><br> >> wrote:<br> >> >> ><br> >> >> >> Hello!<br> >> >> >><br> >> >> >> I have set up a test load balancer with IPVS and= Piranha-GUI. For<br> >> some<br> >> >> >> reason, when I attempt to connect to one of the = two web servers I<br> >> have<br> >> >> >> set-up via the load balancer's virtual IP, t= he load balancer does<br> >> >> >> not<br> >> >> >> seem to pass those requests on to the real serve= rs.<br> >> >> >><br> >> >> >> The firewall on the Piranha box is off and I can= successfully<br> >> >> >> establish HTTP sessions with netcat and telnet f= rom the Piranha box<br> >> as<br> >> >> >> well as from my workstation. So the web services= are running and<br> >> >> >> connectivity to them is good.<br> >> >> >><br> >> >> >> The error I'm getting in /var/log/messages i= s (public IP changed<br> >> >> >> for<br> >> >> >> privacy):<br> >> >> >><br> >> >> >> Nov =A02 14:28:09 omsbuild nanny[13583]: READ to= 65.39.169.xxx:80<br> >> >> >> timed<br> >> >> out<br> >> >> >> Nov =A02 14:28:10 omsbuild nanny[13582]: READ to= <br> >> >> >> 192.168.18.29:80timed<br> >> >> out<br> >> >> >><br> >> >> >> It looks like nanny can't talk to the web se= rvers but I can't<br> >> >> >> figure<br> >> >> >> out why. That may not be the only problem I have= here but it's<br> >> >> >> probably one of them. All the other services are= up and seem to be<br> >> >> >> running fine.<br> >> >> >><br> >> >> >> I've googled around quite a bit and checked = the documentation but I<br> >> >> >> haven't found anything in those places that = gets me to a solution.<br> >> >> >><br> >> >> >> Can anyone out there give me a little push in th= e right direction<br> >> >> >> as<br> >> >> >> to what the problem might be?<br> >> >> >><br> >> >> >><br> >> >> >> Thank you!<br> >> >> >><br> >> >> >> Mike<br> >> >> >><br> >> >> >><br> >> >> >> My lvs.conf file:<br> >> >> >><br> >> >> >> serial_no =3D 76<br> >> >> >> primary =3D 192.168.3.28<br> >> >> >> service =3D lvs<br> >> >> >> backup =3D 0.0.0.0<br> >> >> >> heartbeat =3D 1<br> >> >> >> heartbeat_port =3D 539<br> >> >> >> keepalive =3D 6<br> >> >> >> deadtime =3D 18<br> >> >> >> network =3D direct<br> >> >> >> debug_level =3D NONE<br> >> >> >> virtual test1 {<br> >> >> >> =A0 =A0 active =3D 1<br> >> >> >> =A0 =A0 address =3D 192.168.0.69 eth0:1<br> >> >> >> =A0 =A0 vip_nmask =3D 255.255.248.0<br> >> >> >> =A0 =A0 port =3D 3128<br> >> >> >> =A0 =A0 expect =3D "HTTP"<br> >> >> >> =A0 =A0 use_regex =3D 0<br> >> >> >> =A0 =A0 load_monitor =3D none<br> >> >> >> =A0 =A0 scheduler =3D lc<br> >> >> >> =A0 =A0 protocol =3D tcp<br> >> >> >> =A0 =A0 timeout =3D 6<br> >> >> >> =A0 =A0 reentry =3D 15<br> >> >> >> =A0 =A0 quiesce_server =3D 0<br> >> >> >> =A0 =A0 server Speedy {<br> >> >> >> =A0 =A0 =A0 =A0 address =3D 192.168.18.29<br> >> >> >> =A0 =A0 =A0 =A0 active =3D 1<br> >> >> >> =A0 =A0 =A0 =A0 port =3D 80<br> >> >> >> =A0 =A0 =A0 =A0 weight =3D 1<br> >> >> >> =A0 =A0 }<br> >> >> >> =A0 =A0 server test1 {<br> >> >> >> =A0 =A0 =A0 =A0 address =3D 65.39.169.xxx<br> >> >> >> =A0 =A0 =A0 =A0 active =3D 1<br> >> >> >> =A0 =A0 =A0 =A0 port =3D 80<br> >> >> >> =A0 =A0 =A0 =A0 weight =3D 1<br> >> >> >> =A0 =A0 }<br> >> >> >><br> >> >> >> _______________________________________________<= br> >> >> >> Piranha-list mailing list<br> >> >> >> <a href=3D"mailto:[email protected]">Piran= [email protected]</a><br> >> >> >> <a href=3D"https://www.redhat.com/mailman/listin= fo/piranha-list" target=3D"_blank">https://www.redhat.com/mailman/listinfo/= piranha-list</a><br> >> >> >><br> >> >> ><br> >> >><br> >> >> _______________________________________________<br> >> >> Piranha-list mailing list<br> >> >> <a href=3D"mailto:[email protected]">Piranha-list@r= edhat.com</a><br> >> >> <a href=3D"https://www.redhat.com/mailman/listinfo/piranh= a-list" target=3D"_blank">https://www.redhat.com/mailman/listinfo/piranha-l= ist</a><br> >> >><br> >> ><br> >><br> >> _______________________________________________<br> >> Piranha-list mailing list<br> >> <a href=3D"mailto:[email protected]">[email protected]= </a><br> >> <a href=3D"https://www.redhat.com/mailman/listinfo/piranha-list" t= arget=3D"_blank">https://www.redhat.com/mailman/listinfo/piranha-list</a><b= r> >><br> ><br> <br> _______________________________________________<br> Piranha-list mailing list<br> <a href=3D"mailto:[email protected]">[email protected]</a><br> <a href=3D"https://www.redhat.com/mailman/listinfo/piranha-list" target=3D"= _blank">https://www.redhat.com/mailman/listinfo/piranha-list</a><br> </div></div></blockquote></div><br> --00032555488ee711750477abd0e6-- --===============1178507223== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Piranha-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/piranha-list --===============1178507223==--