whirr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrei Savu <savu.and...@gmail.com>
Subject Re: Starting HBASE Cluster - Unending whirr - IllegalStateException: The permission '72.205.25.214/32-1-2181-2181' has already been authorized on the specified group
Date Thu, 22 Dec 2011 21:12:32 GMT
Looks like a serios issue. This exception should not bubble up so much. You
can workaround it by cleaning up your account by hand - I know this is less
than ideal.

Just to be clear: are you using 0.7.0?

On Thu, Dec 22, 2011 at 11:03 PM, David Medinets
<david.medinets@gmail.com>wrote:

> While this error does seem benign, the whirr command does not return
> back to the command prompt. That's the part that worries me. If I can
> help to debug this issue please let me know. In case it matters, I am
> running from the command-line on Ubuntu oneiric 11.10.
>
> Here is my hbase-ec2.properties file:
>
> whirr.cluster-name=hbase
> whirr.instance-templates=1
> zookeeper+hadoop-namenode+hadoop-jobtracker+hbase-master,2
> hadoop-datanode+hadoop-tasktracker+hbase-regionserver
> whirr.provider=aws-ec2
> whirr.identity=${env:AWS_ACCESS_KEY_ID}
> whirr.credential=${env:AWS_SECRET_ACCESS_KEY}
>
> whirr.hardware-id=m1.small
> whirr.image-id=us-east-1/ami-6936fb00
>
> whirr.hbase.tarball.url=
> http://archive.apache.org/dist/hbase/hbase-0.89.20100924/hbase-0.89.20100924-bin.tar.gz
>
> Here is the command that I use to start the cluster:
>
> $ whirr launch-cluster --config hbase-ec2.properties
>
> And here is the output:
>
> Bootstrapping cluster
> Configuring template
> Starting 1 node(s) with roles [zookeeper, hadoop-namenode,
> hadoop-jobtracker, hbase-master]
> Configuring template
> Starting 2 node(s) with roles [hadoop-datanode, hadoop-tasktracker,
> hbase-regionserver]
> Nodes started: [[id=us-east-1/i-a44e96c6, providerId=i-a44e96c6,
> group=hbase, name=null, location=[id=us-east-1b, scope=ZONE,
> description=us-east-1b, parent=us-east-1, iso3166Codes=[US-VA],
> metadata={}], uri=null, imageId=us-east-1/ami-6936fb00, os=[name=null,
> family=ubuntu, version=10.04, arch=paravirtual, is64Bit=false,
>
> description=ubuntu-images-us/ubuntu-lucid-10.04-i386-server-20110930.manifest.xml],
> state=RUNNING, loginPort=22, privateAddresses=[10.192.50.239],
> publicAddresses=[107.21.72.159], hardware=[id=m1.small,
> providerId=m1.small, name=null, processors=[[cores=1.0, speed=1.0]],
> ram=1740, volumes=[[id=null, type=LOCAL, size=10.0, device=/dev/sda1,
> durable=false, isBootDevice=true], [id=null, type=LOCAL, size=150.0,
> device=/dev/sda2, durable=false, isBootDevice=false]],
> supportsImage=Not(is64Bit())], loginUser=ubuntu, userMetadata={}]]
> Nodes started: [[id=us-east-1/i-604f9702, providerId=i-604f9702,
> group=hbase, name=null, location=[id=us-east-1c, scope=ZONE,
> description=us-east-1c, parent=us-east-1, iso3166Codes=[US-VA],
> metadata={}], uri=null, imageId=us-east-1/ami-6936fb00, os=[name=null,
> family=ubuntu, version=10.04, arch=paravirtual, is64Bit=false,
>
> description=ubuntu-images-us/ubuntu-lucid-10.04-i386-server-20110930.manifest.xml],
> state=RUNNING, loginPort=22, privateAddresses=[10.98.11.75],
> publicAddresses=[107.21.148.157], hardware=[id=m1.small,
> providerId=m1.small, name=null, processors=[[cores=1.0, speed=1.0]],
> ram=1740, volumes=[[id=null, type=LOCAL, size=10.0, device=/dev/sda1,
> durable=false, isBootDevice=true], [id=null, type=LOCAL, size=150.0,
> device=/dev/sda2, durable=false, isBootDevice=false]],
> supportsImage=Not(is64Bit())], loginUser=ubuntu, userMetadata={}],
> [id=us-east-1/i-624f9700, providerId=i-624f9700, group=hbase,
> name=null, location=[id=us-east-1c, scope=ZONE,
> description=us-east-1c, parent=us-east-1, iso3166Codes=[US-VA],
> metadata={}], uri=null, imageId=us-east-1/ami-6936fb00, os=[name=null,
> family=ubuntu, version=10.04, arch=paravirtual, is64Bit=false,
>
> description=ubuntu-images-us/ubuntu-lucid-10.04-i386-server-20110930.manifest.xml],
> state=RUNNING, loginPort=22, privateAddresses=[10.114.89.57],
> publicAddresses=[107.21.73.26], hardware=[id=m1.small,
> providerId=m1.small, name=null, processors=[[cores=1.0, speed=1.0]],
> ram=1740, volumes=[[id=null, type=LOCAL, size=10.0, device=/dev/sda1,
> durable=false, isBootDevice=true], [id=null, type=LOCAL, size=150.0,
> device=/dev/sda2, durable=false, isBootDevice=false]],
> supportsImage=Not(is64Bit())], loginUser=ubuntu, userMetadata={}]]
> Authorizing firewall ingress to [Instance{roles=[zookeeper,
> hadoop-namenode, hadoop-jobtracker, hbase-master],
> publicIp=107.21.72.159, privateIp=10.192.50.239,
> id=us-east-1/i-a44e96c6, nodeMetadata=[id=us-east-1/i-a44e96c6,
> providerId=i-a44e96c6, group=hbase, name=null,
> location=[id=us-east-1b, scope=ZONE, description=us-east-1b,
> parent=us-east-1, iso3166Codes=[US-VA], metadata={}], uri=null,
> imageId=us-east-1/ami-6936fb00, os=[name=null, family=ubuntu,
> version=10.04, arch=paravirtual, is64Bit=false,
>
> description=ubuntu-images-us/ubuntu-lucid-10.04-i386-server-20110930.manifest.xml],
> state=RUNNING, loginPort=22, privateAddresses=[10.192.50.239],
> publicAddresses=[107.21.72.159], hardware=[id=m1.small,
> providerId=m1.small, name=null, processors=[[cores=1.0, speed=1.0]],
> ram=1740, volumes=[[id=null, type=LOCAL, size=10.0, device=/dev/sda1,
> durable=false, isBootDevice=true], [id=null, type=LOCAL, size=150.0,
> device=/dev/sda2, durable=false, isBootDevice=false]],
> supportsImage=Not(is64Bit())], loginUser=ubuntu, userMetadata={}]}] on
> ports [2181] for [72.205.25.214/32]
>
> Exception in thread "main" java.lang.IllegalStateException: The
> permission '72.205.25.214/32-1-2181-2181' has already been authorized
> on the specified group
>        at
> org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.refineException(ParseAWSErrorFromXmlContent.java:105)
>        at
> org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.handleError(ParseAWSErrorFromXmlContent.java:85)
>        at
> org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:69)
>        at
> org.jclouds.http.internal.BaseHttpCommandExecutorService$HttpResponseCallable.shouldContinue(BaseHttpCommandExecutorService.java:200)
>        at
> org.jclouds.http.internal.BaseHttpCommandExecutorService$HttpResponseCallable.call(BaseHttpCommandExecutorService.java:165)
>        at
> org.jclouds.http.internal.BaseHttpCommandExecutorService$HttpResponseCallable.call(BaseHttpCommandExecutorService.java:134)
>        at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>        at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>        at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>        at java.lang.Thread.run(Thread.java:679)
> Caused by: org.jclouds.http.HttpResponseException: command: POST
> https://ec2.us-east-1.amazonaws.com/ HTTP/1.1 failed with response:
> HTTP/1.1 400 Bad Request; content: [The permission
> '72.205.25.214/32-1-2181-2181' has already been authorized on the
> specified group]
>        at
> org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.handleError(ParseAWSErrorFromXmlContent.java:74)
>        ... 9 more
>
> And this point, the AWS panel shows three instances have been started.
> But the whirr command does not return back the linux prompt.
>

Mime
View raw message