Recommended solutions based on your search
Solutions on the web
While I was testing WHIRR-400 I have noticed that the ZooKeeper integration tests are failing on aws-ec2 with the automatically selected AMI but they are working as expected with the Amazon Linux AMI. The tests are also working as expected on cloudservers-us. This makes me think the failure is not related to our code changes and we should look for an external factor as the root cause. As part of this issue we should think about how to improve the automatic AMI selection mechanism in order to make it more robust and less likely to fail due to AMI upgrades and other external changes.
There is a ssh auth problem when creating a hadoop cluster from an EC2 ubuntu instance. I've been using the same configuration file from an EC2 computer an a physical one, everything works fine in the physical one, but I keep getting this error in EC2: Running configuration script on nodes: [us-east-1/i-c7fde5a6, us-east-1/i-c9fde5a8, us-east-1/i-cbfde5aa] <<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException: publickey auth failed <<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException: publickey auth failed The user in the virtual machine is new and with valid .ssh keys. The hadoop config file is (omitting commented lines): whirr.cluster-name=hadoop whirr.instance-templates=1 hadoop-namenode+hadoop-jobtracker,3 hadoop-datanode+hadoop-tasktracker whirr.provider=aws-ec2 whirr.identity=**** whirr.credential=**** whirr.hardware-id=c1.xlarge whirr.image-id=us-east-1/ami-da0cf8b3 whirr.location-id=us-east-1
net.schmizz.sshj.transport.TransportException: Broken transport; encountered EOF