Re: tomcat7 cluster not communicating [SOLVED]
It was AWS security groups. Bit me. AWS VLAN != Regular VLAN On Fri, Mar 8, 2013 at 2:12 PM, Vince Stewart wrote: > if this is a newly installed system with linux in each virtual machine, > make sure you have registered the IP address (192.168.x.x) in \etc\hosts > files. > > > On Sat, Mar 9, 2013 at 8:42 AM, Zippy Zeppoli wrote: > >> So, I have a tomcat7 cluster on AWS with a cluster configuration that >> works on my local VirtualBox cluster. >> >> Specs: >> - Same config. >> - Firewall turned off on all hosts. >> - unicast instead of multicast >> >> the following commands time out: >> nc -zv member1 8080 >> nc -zv member1 4110 >> >> They are listening however: >> tcp0 0 0.0.0.0:41100.0.0.0:* >> LISTEN >> tcp0 0 0.0.0.0:80800.0.0.0:* >> LISTEN >> >> tcpdump shows over and over SYN's but no replies on all members: >> 18:57:23.762712 IP member1: 52548 > 192.168.10.10.g2tag: Flags [S], >> seq 215397535, win 14600, options [mss 1460,sackOK,TS val 159216257 >> ecr 0,nop,wscale 7], length 0 >> >> >> Connecting to any other port from one member to another works fine, >> for example ssh. >> >> So I can't figure out why network communication works between all >> hosts, tomcat is listening, but trying to connect to the listening >> port fails. >> >> - >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> > > > -- > Vince Stewart - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat7 cluster not communicating
if this is a newly installed system with linux in each virtual machine, make sure you have registered the IP address (192.168.x.x) in \etc\hosts files. On Sat, Mar 9, 2013 at 8:42 AM, Zippy Zeppoli wrote: > So, I have a tomcat7 cluster on AWS with a cluster configuration that > works on my local VirtualBox cluster. > > Specs: > - Same config. > - Firewall turned off on all hosts. > - unicast instead of multicast > > the following commands time out: > nc -zv member1 8080 > nc -zv member1 4110 > > They are listening however: > tcp0 0 0.0.0.0:41100.0.0.0:* > LISTEN > tcp0 0 0.0.0.0:80800.0.0.0:* > LISTEN > > tcpdump shows over and over SYN's but no replies on all members: > 18:57:23.762712 IP member1: 52548 > 192.168.10.10.g2tag: Flags [S], > seq 215397535, win 14600, options [mss 1460,sackOK,TS val 159216257 > ecr 0,nop,wscale 7], length 0 > > > Connecting to any other port from one member to another works fine, > for example ssh. > > So I can't figure out why network communication works between all > hosts, tomcat is listening, but trying to connect to the listening > port fails. > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > -- Vince Stewart
Re: tomcat7 cluster not communicating
I don't think it has anything to do with EC2, but I could be wrong. Like I said before other ports connect fine, and everything is in the same subnet. There's no way for a firewall to interfere as iptables is disabled. It's a VPC with private (different IPs, you can't have duplicate IP's in EC2). On Fri, Mar 8, 2013 at 1:22 PM, Christopher Schultz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Frank, > > On 3/8/13 2:42 PM, Zippy Zeppoli wrote: >> So, I have a tomcat7 cluster on AWS with a cluster configuration >> that works on my local VirtualBox cluster. >> >> Specs: - Same config. - Firewall turned off on all hosts. - unicast >> instead of multicast >> >> the following commands time out: nc -zv member1 8080 nc -zv >> member1 4110 >> >> They are listening however: tcp0 0 0.0.0.0:4110 >> 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:8080 >> 0.0.0.0:* LISTEN >> >> tcpdump shows over and over SYN's but no replies on all members: >> 18:57:23.762712 IP member1: 52548 > 192.168.10.10.g2tag: Flags >> [S], seq 215397535, win 14600, options [mss 1460,sackOK,TS val >> 159216257 ecr 0,nop,wscale 7], length 0 >> >> >> Connecting to any other port from one member to another works >> fine, for example ssh. >> >> So I can't figure out why network communication works between all >> hosts, tomcat is listening, but trying to connect to the listening >> port fails. > > Are you using your EC2 internal IP addresses or external PI addresses? > When you say you have the "same config", I presume that you have > different IP addresses configured, yes? > > - -chris > -BEGIN PGP SIGNATURE- > Version: GnuPG/MacGPG2 v2.0.17 (Darwin) > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iEYEAREIAAYFAlE6VqAACgkQ9CaO5/Lv0PC7zQCffK+OuT2bKd87ziLS3+ICL8II > GjUAoICdZSixj/MTozTEtrlpjJa8W9iw > =xEcb > -END PGP SIGNATURE- > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat7 cluster not communicating
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Frank, On 3/8/13 2:42 PM, Zippy Zeppoli wrote: > So, I have a tomcat7 cluster on AWS with a cluster configuration > that works on my local VirtualBox cluster. > > Specs: - Same config. - Firewall turned off on all hosts. - unicast > instead of multicast > > the following commands time out: nc -zv member1 8080 nc -zv > member1 4110 > > They are listening however: tcp0 0 0.0.0.0:4110 > 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:8080 > 0.0.0.0:* LISTEN > > tcpdump shows over and over SYN's but no replies on all members: > 18:57:23.762712 IP member1: 52548 > 192.168.10.10.g2tag: Flags > [S], seq 215397535, win 14600, options [mss 1460,sackOK,TS val > 159216257 ecr 0,nop,wscale 7], length 0 > > > Connecting to any other port from one member to another works > fine, for example ssh. > > So I can't figure out why network communication works between all > hosts, tomcat is listening, but trying to connect to the listening > port fails. Are you using your EC2 internal IP addresses or external PI addresses? When you say you have the "same config", I presume that you have different IP addresses configured, yes? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEAREIAAYFAlE6VqAACgkQ9CaO5/Lv0PC7zQCffK+OuT2bKd87ziLS3+ICL8II GjUAoICdZSixj/MTozTEtrlpjJa8W9iw =xEcb -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
tomcat7 cluster not communicating
So, I have a tomcat7 cluster on AWS with a cluster configuration that works on my local VirtualBox cluster. Specs: - Same config. - Firewall turned off on all hosts. - unicast instead of multicast the following commands time out: nc -zv member1 8080 nc -zv member1 4110 They are listening however: tcp0 0 0.0.0.0:41100.0.0.0:* LISTEN tcp0 0 0.0.0.0:80800.0.0.0:* LISTEN tcpdump shows over and over SYN's but no replies on all members: 18:57:23.762712 IP member1: 52548 > 192.168.10.10.g2tag: Flags [S], seq 215397535, win 14600, options [mss 1460,sackOK,TS val 159216257 ecr 0,nop,wscale 7], length 0 Connecting to any other port from one member to another works fine, for example ssh. So I can't figure out why network communication works between all hosts, tomcat is listening, but trying to connect to the listening port fails. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
