You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@whirr.apache.org by Sebastian Schoenherr <se...@uibk.ac.at> on 2013/04/19 17:54:55 UTC
Custom Ami Problem Whirr 0.8.1
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
Re: Custom Ami Problem Whirr 0.8.1
Posted by Imad Qureshi <im...@yahoo.com>.
Hi sorry for posting this message here but I am running into same issue.
I can create a cluster using
one of the publicly available AMI but cannot using my custom AMI (RHEL).
I have set bootstrap-user
also.
Any idea? Port 22 is open in my security group.
Re: Custom Ami Problem Whirr 0.8.1
Posted by Sebastian Schoenherr <se...@uibk.ac.at>.
Hi all,
With the update to Whirr 0.8.2 I'm able to start a custom AMI without
problems.
This config file worked for me. Since it's based on ubuntu,
whirr.login-user is set to ubuntu
Thanks for the great work!
Seb
whirr.cluster-name = clusterCustomAmi
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 = cloudgene
whirr.provider = aws-ec2
whirr.image-id = us-east-1/my-custom-ami
whirr.login-user = ubuntu
whirr.hardware-id = m1.large
whirr.hadoop.install-function = install_cdh_hadoop
whirr.hadoop.configure-function = configure_cdh_hadoop
whirr.max-startup-retries = 2
whirr.client-cidrs = 0.0.0.0\/0
whirr.env.REPO = cdh3u5
On 19.04.2013 18:30, Sebastian Schoenherr wrote:
> Again me,
> I forgot to set the bootstrap-user to ubuntu, which is necessary for
> custom AMIs (whirr.bootstrap-user=ubuntu).
>
> Still have a connection issue:
>
> 2013-04-19 18:13:36,733 DEBUG [jclouds.compute] (user thread 5) >>
> running [sudo /tmp/init-bootstrap-hadoop-datanode_hadoop-tasktracker
> start] as ubuntu@184.72.78.208
> 2013-04-19 18:14:30,206 ERROR
> [net.schmizz.sshj.transport.TransportImpl] (reader) Dying because -
> java.net.SocketTimeoutException: Read timed out
>
> Login is possible.
> Any help is very much appreciated,
> Seb
>
>
>
> On 19.04.2013 17:54, Sebastian Schoenherr wrote:
>> 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
>
>
Re: Custom Ami Problem Whirr 0.8.1
Posted by Sebastian Schoenherr <se...@uibk.ac.at>.
Again me,
I forgot to set the bootstrap-user to ubuntu, which is necessary for
custom AMIs (whirr.bootstrap-user=ubuntu).
Still have a connection issue:
2013-04-19 18:13:36,733 DEBUG [jclouds.compute] (user thread 5) >>
running [sudo /tmp/init-bootstrap-hadoop-datanode_hadoop-tasktracker
start] as ubuntu@184.72.78.208
2013-04-19 18:14:30,206 ERROR [net.schmizz.sshj.transport.TransportImpl]
(reader) Dying because - java.net.SocketTimeoutException: Read timed out
Login is possible.
Any help is very much appreciated,
Seb
On 19.04.2013 17:54, Sebastian Schoenherr wrote:
> 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
--
Sebastian Schoenherr
PhD student in Bioinformatics
Institute of Computer Science
Division of Genetic Epidemiology
sebastian.schoenherr@uibk.ac.at
http://dbis-informatik.uibk.ac.at
http://www.i-med.ac.at/genepi/