Hello,

While trying to start this cluster (pertaining portion of the properties file):

whirr.instance-templates=1 zk+nn+jt+hbase-master,2 zk+dn+tt+hbase-regionserver
whirr.provider=ec2

I received this message (which appears to hang the whirr
launch-cluster process):

Exception in thread "main" java.lang.IllegalStateException: The
permission '50.16.131.205/32-1-2181-2181' has already been authorized
on the specified group
        at 
org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.refineException(ParseAWSErrorFromXmlContent.java:106)
        at 
org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.handleError(ParseAWSErrorFromXmlContent.java:86)
        at 
org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:70)
        at 
org.jclouds.http.internal.BaseHttpCommandExecutorService$HttpResponseCallable.shouldContinue(BaseHttpCommandExecutorService.java:201)
        at 
org.jclouds.http.internal.BaseHttpCommandExecutorService$HttpResponseCallable.call(BaseHttpCommandExecutorService.java:166)
        at 
org.jclouds.http.internal.BaseHttpCommandExecutorService$HttpResponseCallable.call(BaseHttpCommandExecutorService.java:135)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
        at java.lang.Thread.run(Thread.java:619)
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
'50.16.131.205/32-1-2181-2181' has already been authorized on the
specified group]
        at 
org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.handleError(ParseAWSErrorFromXmlContent.java:75)
        ... 9 more

I would be happy to provide more information if this is not a known issue.

It seems that this exception should be caught and ignored.  Or,
redundant requests should not be made in the first place.

Regards,
Loren
-- 
Loren J. Rittle, Principal Staff Engineer, Motorola Mobility (IL93)
ljrittle@{motorola.com, acm.org, gcc.gnu.org, freebsd.org, gmail.com}

Reply via email to