I have never tried to use Whirr with a proxy and I don't think we are using system wide settings. Is this a https proxy or socks?
Here you can find some instructions about how to make jclouds work: http://www.jclouds.org/documentation/reference/jclouds-api You need to edit ./bin/whirr to set the required jvm system properties. Are there any other log messages in whirr.log? -- Andrei On Thu, Nov 10, 2011 at 2:34 PM, Christian Schäfer <[email protected]>wrote: > Hi, > > I'm trying to setup an hbase cluster with default properties file from > recipes and get errors as follows. > > > cloudera@cloudera-vm:~/whirr-0.6.0-incubating$ bin/whirr launch-cluster > --config hbase-ec2.properties > Cannot retry after server error, command has exceeded retry limit 5: > [method=AvailabilityZoneAndRegionAsyncClient.describeRegions, request=POST > https://ec2.us-east-1.amazonaws.com/ HTTP/1.1] > Cannot retry after server error, command has exceeded retry limit 5: > [method=AvailabilityZoneAndRegionAsyncClient.describeRegions, request=POST > https://ec2.us-east-1.amazonaws.com/ HTTP/1.1] > Cannot retry after server error, command has exceeded retry limit 5: > [method=AvailabilityZoneAndRegionAsyncClient.describeRegions, request=POST > https://ec2.us-east-1.amazonaws.com/ HTTP/1.1] > Cannot retry after server error, command has exceeded retry limit 5: > [method=AvailabilityZoneAndRegionAsyncClient.describeRegions, request=POST > https://ec2.us-east-1.amazonaws.com/ HTTP/1.1] > Cannot retry after server error, command has exceeded retry limit 5: > [method=AvailabilityZoneAndRegionAsyncClient.describeRegions, request=POST > https://ec2.us-east-1.amazonaws.com/ HTTP/1.1] > Cannot retry after server error, command has exceeded retry limit 5: > [method=AvailabilityZoneAndRegionAsyncClient.describeRegions, request=POST > https://ec2.us-east-1.amazonaws.com/ HTTP/1.1] > Cannot retry after server error, command has exceeded retry limit 5: > [method=AvailabilityZoneAndRegionAsyncClient.describeRegions, request=POST > https://ec2.us-east-1.amazonaws.com/ HTTP/1.1] > > Any hint? > > Maybe proxy need to be set...although proxy is set system wide? >
