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, 201
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
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).
-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 mult
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 howeve
