EC2 via AMI - Can't get more than one EC2 instance to spawn
|
09-02-2016, 06:02 AM
(This post was last modified: 09-03-2016 12:27 AM by joseph.)
Post: #1
|
|||
|
|||
EC2 via AMI - Can't get more than one EC2 instance to spawn
Edit: False alarm! I was looking for other logs and found /var/www/webpagetest/www/ec2/log/. It looks like it was starting a new instance but it just didn't show up in the AWS EC2 Dashboard or instance list.
Code: 20:15:09 - Launching m3.medium ami ami-678afe07 in us-west-1 for us-west-1,us-west-1_IE11 with user data: wpt_server=54.162.99.86 wpt_loc=us-west-1,us-west-1_IE11 wpt_key=X First of all, thank you for making Webpagetest available via EC2 AMI! Everything seems to be working as expected for the default us-east-1 location. It spins up a new us-east-1 EC2 instance when I start a new test for US East (N. Virginia). However, when I run a test for us-west-1 or us-west-2 it does not spin up a new EC2 instance. Furthermore, I was able to run tests simultaneously on us-east-1, us-west-1, and us-west-2, so I don't think it is running them my EC2 instance (or it would be queued, no?). Is it using the webpagetest.org test agents for us-west-1 and us-west-2? I have not modified ec2_locations.ini and am using the default EC2 instance values in settings.ini: Code: ec2_locations=1 I tried using the instance values below from settings.ini.sample but this seemed to break my available locations (the dropdowns were empty). Code: ; Start an EC2 instance for every X tests in the queue (up to the location max) |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)