Bob-
Guessing from the private key file you might be running as ubuntu which
could be doing something weird somewhere. A bug for sure, so logs would
be handy, but might have an easy workaround if you can run as a
different user locally (could be whirr, or could go with something else
to disambiguate in the log files).
--A
On 10/04/2012 22:05, Andrei Savu wrote:
Can you post the relevant stack trace? Or log records?
-- Andrei
On Tue, Apr 10, 2012 at 11:55 PM, Bob Briski <[email protected]
<mailto:[email protected]>> wrote:
Alright, this problem is happening again. Here's my properties file:
whirr.cluster-name=sqoop
whirr.cluster-user=whirr
whirr.instance-templates=1 hadoop-namenode+hadoop-jobtracker,6
hadoop-datanode+hadoop-tasktracker
whirr.hadoop.install-function=install_cdh_hadoop
whirr.hadoop.configure-function=configure_cdh_hadoop
whirr.provider=aws-ec2
whirr.identity=${env:AWS_ACCESS_KEY_ID}
whirr.credential=${env:AWS_SECRET_ACCESS_KEY}
whirr.hardware-id=m1.large
whirr.image-id=us-east-1/ami-3f6ca156
whirr.location-id=us-east-1
whirr.private-key-file=/home/ubuntu/.ssh/id_rsa
whirr.public-key-file=${whirr.private-key-file}.pub
whirr.firewall-rules=3306
