search cancel

Engines not starting, not termination after aborting test

book

Article ID: 201891

calendar_today

Updated On:

Products

BlazeMeter

Issue/Introduction

Tried running a test and none of the engines in the Canada (Central, AWS) region started—all were stuck in “Booting”.  It was necessary to abort the test.

From the System Log found on the log tab of the aborted test's report, errors similar to the following can be found for multiple engines configured in the test:

[ERROR] [r-v4-<sessionID>] system: Error executing &quot;RunInstances&quot; on &quot;https://ec2.ca-central-1.amazonaws.com&quot;; AWS HTTP error: Server error response [url] https://ec2.ca-central-1.amazonaws.com [status code] 500 [reason phrase] Internal Server Error InsufficientInstanceCapacity (server): We currently do not have sufficient m4.xlarge capacity in the Availability Zone you requested (ca-central-1a). Our system will be working on provisioning additional capacity. You can currently get m4.xlarge capacity by not specifying an Availability Zone in your request or choosing ca-central-1b. - &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;Response&gt;&lt;Errors&gt;&lt;Error&gt;&lt;Code&gt;InsufficientInstanceCapacity&lt;/Code&gt;&lt;Message&gt;We currently do not have sufficient m4.xlarge capacity in the Availability Zone you requested (ca-central-1a). Our system will be working on provisioning additional capacity. You can currently get m4.xlarge capacity by not specifying an Availability Zone in your request or choosing ca-central-1b.&lt;/Message&gt;&lt;/Error&gt;&lt;/Errors&gt;&lt;RequestID&gt;dcaedaec-0c89-4388-891e-8eeb7801d919&lt;/RequestID&gt;&lt;/Response&gt;

Cause

The Canada (Central, AWS) configured location uses Availability Zones.  BlazeMeter tried to get the requested number of machines from this zone, but there was not enough machines, so it failed. This is not an issue BlazeMeter can fix.  AWS just did not have enough availability for machines in the configured region at the time that the test was executed.

Environment

Release : SAAS

Component : BLAZEMETER PERFORMANCE TESTING

Resolution

Two possible solutions:

1.  Configure the test to use a different location.

2.  Try running the test again with the same location at a different time, although this problem can occur again if there are still not enough machines available in the configured location.