No. "ALL" does not count. I remembered that I have to manually specify the range.
On Mon, Aug 17, 2015 at 6:06 PM, Roman Shaposhnik <[email protected]> wrote: > On Mon, Aug 17, 2015 at 5:40 PM, Xiaojian Zhou <[email protected]> wrote: > > This error msg actually is not the root cause of the issue. To avoid the > > error msg, you can modify sysctl.conf of your instance to add 2 lines: > > # unicast buffer size > > net.core.rmem_max = 2096304 > > net.core.wmem_max = 2096304 > > Thanks for the suggestion, but I am actually not running it on Linux > (or UNIX for that matter). > > > 2) You might not open enough ports for tcp and udp. That could be the > real > > root cause. To do that, you can either turn the ports (1024-65535) from > AWS > > GUI interface or via following commands: > > aws ec2 authorize-security-group-ingress --group-id > your_security_group_id > > --protocol tcp --port 22 --cidr 0.0.0.0/00 > > aws ec2 authorize-security-group-ingress --group-id > your_security_group_id > > --protocol tcp --port 1024-65535 --cidr 0.0.0.0/00 > > aws ec2 authorize-security-group-ingress --group-id > your_security_group_id > > --protocol udp --port 1024-65535 --cidr 0.0.0.0/00 > > Hm. That's a good point, but the security group I'm running it > from has ALL the ports open so I guess it shouldn't be a problem > then, right? > > Thanks, > Roman. >
