On 01/18/2011 01:09 PM, Gerry Reno wrote: > Joe, thanks for the help. I agree something is firewalling the packets. > > I added an explicit rule for this security group to allow access for > port 24007 to itself. (Shouldn't need this) and it worked. > > ec2-authorize SECURITYGROUP -P tcp -p 24007-24019 -u AWS_USER_ID -o > SECURITYGROUP > GROUP SECURITYGROUP > PERMISSION SECURITYGROUP ALLOWS tcp 24007 > 24019 FROM USER AWS_USER_ID GRPNAME SECURITYGROUP > > > And now the probe is successful: > > On primary: > # sudo gluster peer probe 10.XXX.58.95 > Probe successful Go figure. > So it appears the internal ec2 network is not open within the security > group. Maybe they just meant the internal network is open in the > 'default' security group. Or they only tested it there. Or its possible, with their testing, they have this pre-set, and didn't include it in the notes. I'd suggest sending an RFE to the gluster team, and see if they can update the docs for EC2 on this. -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics Inc. email: landman at scalableinformatics.com web : http://scalableinformatics.com http://scalableinformatics.com/sicluster phone: +1 734 786 8423 x121 fax : +1 866 888 3112 cell : +1 734 612 4615
