Amazon AMI not found - Githubissues

praneethpatlola commented 12 years ago

looks like the recommended amazon instance as per instructions is not available. Can you please provide a public instance which we can use

oliverlloyd commented 12 years ago

Try this:

AMI_ID="ami-e1e8d395" INSTANCE_TYPE="c1.medium" (Or t1.micro, m1.medium, m1.large, m1.small etc.) USER="ubuntu"

It's an ubuntu ami, much cheaper than SUSE LINUX. You'll need to download the latest version of the script for this to work.

I'll update the properties file soon.

Oliver

On 4 Jun 2012, at 21:56, Praneeth Patlola wrote:

looks like the recommended amazon instance as per instructions is not available. Can you please provide a public instance which we can use

Reply to this email directly or view it on GitHub: https://github.com/oliverlloyd/jmeter-ec2/issues/1

oliverlloyd commented 12 years ago

You'll also need to update the install.sh script at LINE 24 as below. Ubuntu does not handle rpm files.

if [ $INSTALL_JAVA -eq 1 ] ; then
    # install java

#ubuntu
sudo DEBIAN_FRONTEND=noninteractive apt-get -qqy install default-jre
wait

#    bits=`getconf LONG_BIT`
#    if [ $bits -eq 32 ] ; then
#        wget -q -O $REMOTE_HOME/jre-6u30-linux-i586-rpm.bin https://s3.amazonaws.com/jmeter-ec2/jre-6u30-linux-        i586-rpm.bin
#        chmod 755 $REMOTE_HOME/jre-6u30-linux-i586-rpm.bin
#        $REMOTE_HOME/jre-6u30-linux-i586-rpm.bin
#    else # 64 bit
#        wget -q -O $REMOTE_HOME/jre-6u30-linux-x64-rpm.bin https://s3.amazonaws.com/jmeter-ec2/jre-6u30-linux-i586-rpm.bin
#        chmod 755 $REMOTE_HOME/jre-6u30-linux-x64-rpm.bin
#        $REMOTE_HOME/jre-6u30-linux-x64-rpm.bin
#    fi
fi

praneethpatlola commented 12 years ago

i used ami-7722f71e (ubuntu) c1.medium and it worked till the point of copying install.sh into machine but then keeps greping for the log file to ensure the scp is complete. Let me play around with the script little bit and will keep you posted

oliverlloyd commented 12 years ago

OK, it should work now - I've just updated the properties and install.sh files. Tests OK for me, the output should look something like:

-------------------------------------------------------------------------------------
   jmeter-ec2 Automation Script - Running ohw.jmx over 2 AWS Instance(s)
-------------------------------------------------------------------------------------

requesting 2 instance(s)...success

waiting for instance status checks to pass (this can take several minutes)................all hosts ready

assigning tags...TAG    instance    i-b517a5fd  ProjectName ohw
TAG instance    i-b717a5ff  ProjectName ohw

copying install.sh to 2 server(s)....complete

running install.sh on 2 server(s)...
Extracting templates from packages: 100%
Extracting templates from packages: 100%
.................complete

editing thread counts - ohw.jmx has 4 threadgroup(s) - [Disabled & Enabled]...done

copying test files to 2 server(s)...jmx files..done....data dir..done....jmeter.properties..done....jmeter execution file...all files uploaded

starting jmeter on:

If you see this 'Extracting templates from packages: 100%' it means the new java install is working.

praneethpatlola commented 12 years ago

Below is the log. it looks like there might be some permission issue while scping over the install.sh file as it says lost connection.

~/jmeter-ec2$ ./jmeter-ec2.sh airwalatest 1

   jmeter-ec2 Automation Script - Running airwalatest.jmx over 1 AWS Instance(s)

requesting 1 instance(s)...success

waiting for instance status checks to pass (this can take several minutes).............all hosts ready

assigning tags... TAG instance i-8466a0fd ProjectName airwalatest

copying install.sh to 1 server(s)...lost connection

praneethpatlola commented 12 years ago

It worked . It worked. Thanks a bunch!

oliverlloyd / jmeter-ec2

Amazon AMI not found #1