Oh, thanks, I dont know there is an issue tracker. I will do so. Thanks a lot.
On Sun, May 29, 2011 at 5:38 AM, Andrei Savu <savu.and...@gmail.com> wrote: > I've seen the log file. I'm trying to say that you should open an > issue on the Issue Tracker: > https://issues.apache.org/jira/browse/WHIRR > > It's easier for us to track progress there rather than on the email list. > > You should attach: the properties file used, the ami and owner IDs and > the log file. > > Thanks, > > -- Andrei Savu / andreisavu.ro > > On Sun, May 29, 2011 at 3:29 PM, Allen <allen...@gmail.com> wrote: > > I thought i attached the whirr.log file in previous email. Here you go > > again. Thanks a lot. > > > > On Sun, May 29, 2011 at 5:26 AM, Andrei Savu <savu.and...@gmail.com> > wrote: > >> > >> Looks like a problem in Whirr or Jclouds. > >> > >> Could you open an issue and attach the log file? > >> > >> Thanks, > >> > >> -- Andrei Savu / andreisavu.ro > >> > >> On Sun, May 29, 2011 at 2:18 PM, Allen <allen...@gmail.com> wrote: > >> > Thanks, Andrei, > >> > > >> > I also tried whirr 0.5.0, it didn't work. Attached is the whirr.log > >> > file. > >> > > >> > -allen > >> > > >> > On Sun, May 29, 2011 at 4:04 AM, Andrei Savu <savu.and...@gmail.com> > >> > wrote: > >> >> > >> >> Hi Allen, > >> >> > >> >> First of all you should get the latest release, Whirr 0.4.0 from: > >> >> http://www.apache.org/dyn/closer.cgi/incubator/whirr/ > >> >> > >> >> There is a long list of improvements and architectural changes from > >> >> 0.1.0. Check the recipes folder for more info. > >> >> > >> >> > I wonder if anyone knows what is going on or how to fix it. > >> >> > >> >> Could you attach whirr.log? > >> >> > >> >> -- Andrei Savu / andreisavu.ro > >> >> > >> >> On Sun, May 29, 2011 at 1:50 PM, Allen <allen...@gmail.com> wrote: > >> >> > Hi, All > >> >> > > >> >> > I have installed whirr-0.1.0+23, Java 1.6, Maven 2, Ruby 1.9 in my > >> >> > ubuntu, > >> >> > so I set up a Hadoop.properties file in order to fire up a cluster > in > >> >> > amazon > >> >> > ec2 via > >> >> > > >> >> > bin/whirr launch-cluster --config hadoop.properties > >> >> > > >> >> > It worked well if my hadoop.properties as below: > >> >> > > >> >> > whirr.service-name=hadoop > >> >> > whirr.cluster-name=myhadoopcluster > >> >> > whirr.instance-templates=1 jt+nn,1 dn+tt > >> >> > whirr.provider=ec2 > >> >> > whirr.identity=< Amazon EC2 Access Key ID> > >> >> > whirr.credential=< Amazon EC2 Secret Access Key> > >> >> > whirr.private-key-file=${sys:user.home}/.ssh/id_rsa > >> >> > whirr.public-key-file=${sys:user.home}/.ssh/id_rsa.pub > >> >> > whirr.hardware-id= m1.large > >> >> > whirr.location-id=us-west-1 > >> >> > whirr.hadoop-install-runurl=cloudera/cdh/install > >> >> > whirr.hadoop-configure-runurl=cloudera/cdh/post-configure > >> >> > > >> >> > > >> >> > But once i added two more lines into hadoop.properties file, it > went > >> >> > wrong: > >> >> > whirr.image-id= us-west-1/ami-***** (my ami) > >> >> > jclouds.ec2.ami-owners=(my owner id> > >> >> > > >> >> > I wonder if anyone knows what is going on or how to fix it. Thanks > >> >> > > >> >> > -allen > >> >> > > >> >> > > >> >> > > >> >> > > >> > > >> > > > > > >
