whirr.log:
2011-11-10 05:34:01,935 DEBUG [jclouds.compute] (pool-3-thread-2) >>
authorizing securityGroup region(us-east-1) name(jclouds#cassandra#us-east-1)
port(22)
2011-11-10 05:34:02,244 DEBUG [jclouds.compute] (pool-3-thread-2) << authorized
securityGroup(jclouds#cassandra#us-east-1)
2011-11-10 05:34:02,244 DEBUG [jclouds.compute] (pool-3-thread-2) >>
authorizing securityGroup region(us-east-1) name(jclouds#cassandra#us-east-1)
permission to itself
2011-11-10 05:34:02,851 DEBUG [jclouds.compute] (pool-3-thread-2) << authorized
securityGroup(jclouds#cassandra#us-east-1)
2011-11-10 05:34:02,851 DEBUG [jclouds.compute] (pool-3-thread-2) >> running 3
instance region(us-east-1) zone(null) ami(ami-ad36fbc4)
params({InstanceType=[m1.large], SecurityGroup.1=[jclouds#cassandra#us-east-1],
KeyName=[jclouds#cassandra#us-east-1#55]})
2011-11-10 05:34:03,550 DEBUG [jclouds.compute] (pool-3-thread-2) << started
instances([region=us-east-1, name=i-5f31b23c],[region=us-east-1,
name=i-5d31b23e],[region=us-east-1, name=i-2331b240])
2011-11-10 05:34:04,363 DEBUG [jclouds.compute] (pool-3-thread-2) << present
instances([region=us-east-1, name=i-5f31b23c],[region=us-east-1,
name=i-5d31b23e],[region=us-east-1, name=i-2331b240])
2011-11-10 05:34:17,610 DEBUG [jclouds.compute] (user thread 6) >> blocking on
socket [address=50.19.171.2, port=22] for 600000 seconds
2011-11-10 05:34:21,224 DEBUG [jclouds.compute] (user thread 2) >> blocking on
socket [address=107.20.113.138, port=22] for 600000 seconds
2011-11-10 05:34:21,310 DEBUG [jclouds.compute] (user thread 5) >> blocking on
socket [address=50.19.131.59, port=22] for 600000 seconds
I just created cassandra cluster ..because of "blocking on socket" I expect
that SSH doesnt get through proxy....(SSH needs to be opened from the admin
here for certain IPs..)
________________________________
Von: Andrei Savu <[email protected]>
An: [email protected]; Christian Schäfer <[email protected]>
Gesendet: 14:27 Donnerstag, 10.November 2011
Betreff: Re: Cluster Launch fails with whirr-0.6.0-incubating
If you are only seeing this it means the cluster is not yet running.
I not sure if SSH is going through your proxy as expected. What do you see in
whirr.log?
-- Andrei Savu
On Thu, Nov 10, 2011 at 3:22 PM, Christian Schäfer <[email protected]> wrote:
Is it normal that after cluster launch shell keeps busy with?:
>
> Bootstrapping cluster
>Configuring template
>Configuring template
>Starting 1 node(s) with roles [zookeeper, hadoop-namenode, hadoop-jobtracker,
>hbase-master]
>Starting 2 node(s) with roles [hadoop-datanode, hadoop-tasktracker,
>hbase-regionserver]
>
>
>
>
>________________________________
>Von: Christian Schäfer <[email protected]>
>An: "[email protected]" <[email protected]>
>Gesendet: 14:08 Donnerstag, 10.November 2011
>
>Betreff: Re: Cluster Launch fails with whirr-0.6.0-incubating
>
>
>
>Ah.. thanks Andrei ..the jcloud proxy attribute brought the cure :)
>
>
>
>
>________________________________
> Von: Andrei Savu <[email protected]>
>An: [email protected]
>Gesendet: 13:51 Donnerstag, 10.November 2011
>Betreff: Re: Cluster Launch fails with whirr-0.6.0-incubating
>
>
>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?
>>
>
>
>
>
>
