Hi guys,
I've some problems starting a custom AMI with Whirr.
This is what I've done:
I started this EBS Ubuntu AMI (ami-d0f89fb9) with Whirr. After the
instance was launched successfully, I created a new custom EBS AMI with
the AWS Management Console (Right click on the running instance, "Create
EBS AMI"). Launching this new AMI (no changes in the config file) yields
to a freeze in the output at this point:
>> running
InitScript{INSTANCE_NAME=bootstrap-hadoop-datanode_hadoop-tasktracker}
on node(us-east-1/i-66de3f0c)
Log says:
2013-04-19 17:43:33,002 ERROR [jclouds.ssh] (user thread 4) <<
(root:rsa[fingerprint(66:14:46:3a:74:cf:f1:ff:45:ab:70:82:93:7c:a0:d3),sha1(32:3e:ff:7d:68:3e:7d:96:96:61:04:af:43:1e:50:32:43:b8:c5:5a)]@54.242.30.84:22)
error acquiring SFTPClient() (out of retries - max 7): Invalid packet:
indicated length 1349281121 too large
java.lang.IllegalStateException: Invalid packet: indicated length
1349281121 too large
Any hints? Any option I forget to set for custom AMIs?
Cheers and thanks for your help,
Seb
Config file:
whirr.cluster-name = myCluster
whirr.private-key-file = xxx
whirr.public-key-file = xxx
whirr.identity = xxx
whirr.credential = xxx
whirr.instance-templates = 1 hadoop-namenode+hadoop-jobtracker,1
hadoop-datanode+hadoop-tasktracker
whirr.cluster-user = someUser
whirr.provider = aws-ec2
whirr.image-id = us-east-1/ami-1ec4a577
whirr.hardware-id = m1.large
whirr.max-startup-retries = 2
whirr.client-cidrs = 0.0.0.0\/0
whirr.env.REPO = cdh3u5
