Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Runtime environments
  3. Hosted Agent
  4. Secure Agent groups
  5. Elastic runtime environments
  6. Serverless runtime environments
  7. Secure Agents
  8. Secure Agent installation

Runtime Environments

Runtime Environments

Troubleshooting general validation errors

Troubleshooting general validation errors

The following table lists general validation error messages for elastic runtime environments:
Message
Corrective action
Variable <<NAME>> is not defined
Ensure that the missing variable is defined with the appropriate value in the config.txt file.
<<COUNT>> variable(s) are not defined in config.txt
Ensure that all variables are defined in the config.txt file.
<<COUNT>> variable(s) are not defined in config.txt when High Availability (HA) mode is on
Ensure that all variables related to high availability are defined in the config.txt file.
Failed to get <<VPC_NAME>>
Ensure that VPC_NAME is valid. Check that the AWS roles and privileges for the cluster installer are assigned to the master node.
Failed to get idmc ami id
Check the AWS roles and privileges assigned to the master node.
Failed to get Subnet <<NAME>>
Check the AWS roles and privileges assigned to the master node.
Failed to get root volume name for AMI ID <<AMI_ID>>
Check the AWS roles and privileges assigned to the master node.
Failed to check if instance <<NAME>> exists
Ensure that the AWS Describe Instances permission is present in instance profile that's attached to the master node.
Failed to authenticate, please check config.txt
Ensure that the user name and password in the config.txt file are correct.
Failed to get Subnet of instance <<INSTANCE_ID>>
Ensure that the AWS Describe Instances permission is present in the instance profile that's attached to the master node.
VPC_NAME should be defined when script is not running on master node
Ensure that VPC_NAME and the value of IS_RUNNING_ON_MASTER are in the config.txt file.
MASTER_INSTANCE_TYPE is not defined
Ensure that the master instance type is defined on the
Environment Configuration
tab in Administrator.
Instance type <<TYPE>> is invalid in region <<NAME>>
Ensure that the region and instance type are defined on the
Environment Configuration
tab in Administrator.
Invalid value <<VALUE>> for HA_MODE, Should be true or false
When using the REST API, ensure that the
heEnabled
field contains a boolean value.
Only one subnet should be specified in non-HA mode, given <<values>>
When high availability isn't enabled, only one subnet can be specified. Check the subnet names on the
Environment Configuration
tab in Administrator.
Exactly 3 subnets should be provided in HA mode, given <<values>>
When high availability is enabled, three subnets must be specified. Check the subnet names on the
Environment Configuration
tab in Administrator.
Subnet <<NAME>> does not exist
Ensure that the subnet names on the
Environment Configuration
tab in Administrator are correct.
Given Subnets map to only <<COUNT>> Availability Zone(s)
Ensure that the subnet names
Environment Configuration
tab in Administrator aren't the same as the master node's subnet.

0 COMMENTS

We’d like to hear from you!