mike wrote: > Nikita Michalko wrote: > >> Hi mike, >> >> it seems to be no HA-problem anymore though, but: >> >> Am Montag, 31. Mai 2010 01:29 schrieb mike: >> >> >>> So I've got ldirector up and running just fine and providing ldap high >>> availability to 2 backend real servers on port 389. >>> >>> Here is the output of netstat on both real servers: >>> tcp 0 0 0.0.0.0:389 >>> 0.0.0.0:* LISTEN >>> tcp 0 0 :::389 >>> >>> :::* LISTEN >>> >>> So I used the same director server to create another highly available >>> application jboss running on port 8080. If I look at the director server >>> I see the output of ipvsadm shows both real servers alive and well. >>> >>> [r...@lvsuat1a ha.d]# ipvsadm >>> IP Virtual Server version 1.2.1 (size=4096) >>> Prot LocalAddress:Port Scheduler Flags >>> -> RemoteAddress:Port Forward Weight ActiveConn InActConn >>> TCP esbuat1.vip.intranet.mydom lc >>> -> gasayul9300602.intranet.mydom Tunnel 1 0 0 >>> -> gasayul9300601.intranet.mydom Tunnel 1 1 0 >>> >>> Looks good so far. Now the problem is that I cannot telnet to the VIP on >>> port 8080; I get "connection refused". If I change the ldirectord.cf to >>> listen on port 22, it works perfectly. So this would seem to indicate >>> that I have things set up appropriately on the director server. So I >>> started poking around on the backend real servers and netstat looks like >>> this: >>> >>> [supp...@esbuat1b ~]$ netstat -an | grep 8080 >>> tcp 0 0 172.28.185.13:8080 >>> 0.0.0.0:* LISTEN >>> >>> >>> >> -> which process is running on this port - i.e. >> lsof -i :8080 >> >> >> >>> so comparing this to the netstat above that listens on port 389 I see >>> that perhaps there is an entry missing, perhaps this: >>> tcp 0 0 :::8080 >>> >>> :::* LISTEN >>> >>> So I don't claim to be a "networking" expert and so maybe I've missed >>> something in my setup and this is why port 8080 is having issues. Can >>> anyone provide me with any pointers or where to go to next? After >>> getting the ldap servers working, I figured this would be easy but I'm >>> struggling with this one. >>> >>> >>> _______________________________________________ >>> Linux-HA mailing list >>> Linux-HA@lists.linux-ha.org >>> http://lists.linux-ha.org/mailman/listinfo/linux-ha >>> See also: http://linux-ha.org/ReportingProblems >>> >>> >> HTH >> >> Nikita Michalko >> _______________________________________________ >> Linux-HA mailing list >> Linux-HA@lists.linux-ha.org >> http://lists.linux-ha.org/mailman/listinfo/linux-ha >> See also: http://linux-ha.org/ReportingProblems >> >> >> > Thanks for your response Nikita. > > Here's the process listening on 8080 on server #1 > [r...@esbuat1a ~]# lsof -i :8080 > COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME > java 15511 jboss 184u IPv4 81259 TCP > ESBUAT1A.intranet.mydomain.com:webcache (LISTEN) > > and on server #2 > [r...@esbuat1b ~]# lsof -i :8080 > COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME > java 23474 jboss 194u IPv4 431570 TCP > ESBUAT1B.intranet.mydomain.com:webcache (LISTEN) > > > I should also note that I can telnet directly to the backend servers on > port 8080. > > Any ideas? > > Mike > > > _______________________________________________ > Linux-HA mailing list > Linux-HA@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > >
ok - what we've found is that the application on the backend servers is starting up listening on the ip of the backend server. By changing the app so that it starts up listening on 0.0.0.0 (all interfaces) connectivity goes through successfully. More to come on this later _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
