Runtime Environments > Elastic runtime environments > Troubleshooting
  

Troubleshooting

Use the following sections to troubleshoot errors in elastic runtime environments.
Note: To get support for elastic runtime environments, you might need to give your organization ID to Informatica Global Customer Support. You can find your organization ID through the Organization menu in the upper right corner.
The following image shows the Organization menu:
The Organization menu displays the organization name and ID. The Copy option appears when you hover the cursor to the right of the Org ID field.
To copy the organization ID, click the Copy option that appears when you hover the cursor to the right of the Org ID field.
You can also find your organization ID on the Organization page in Administrator.

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 config.txt.
<<COUNT>> variable(s) are not defined in config.txt
Ensure that all variables are defined in config.text.
<<COUNT>> variable(s) are not defined in config.txt when High Availability (HA) mode is on
Ensure that all variables related to High Availability (HA) mode are defined in config.text.
Failed to get <<VPC_NAME>>
Ensure that VPC_NAME is valid. Check that the AWS roles and privileges assigned to master node permissions 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>>
Failed to get root volume name for AMI ID <<AMI_ID>>
Failed to check if instance <<NAME>> exists
Ensure that the AWS Describe Instances permission is present in master node instance profile.
Failed to authenticate, please check config.txt
Ensure that the username and password in config.txt are correct.
Failed to get Subnet of instance <<INSTANCE_ID>>
Ensure that the AWS Describe Instances permission is present in the master node instance profile.
VPC_NAME should be defined when script is not running on master node
Ensure that VPC_NAME and value of IS_RUNNING_ON_MASTER are in config.txt.
MASTER_INSTANCE_TYPE is not defined
Ensure that the Master Instance Type is defined in the Environment Configuration tab.
Instance type <<TYPE>> is invalid in region <<NAME>>
Ensure that the Region and Instance Type defined in the Environment Configuration tab.
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 HA mode is not enabled, only one subnet can be specified. Check the subnet names in the Environment Configuration tab.
Exactly 3 subnets should be provided in HA mode, given <<values>>
When HA mode is enabled, three subnets must be specified. Check the subnet names on the Environment Configuration tab.
Subnet <<NAME>> does not exist
Ensure that the subnet names on the Environment Configuration tab are correct.
Given Subnets map to only <<COUNT>> Availability Zone(s)
Ensure that the subnet names in the Environment Configuration tab are not the same as the Master Node's subnet.

Troubleshooting proxy-related errors

The following table lists proxy-related error messages for elastic runtime environments:
Message
Corrective action
Proxy connection failed
Ensure that you can reach www.informatica.com using the proxy connection details specified.
Proxy port [<<PORT>>] is invalid
Check the proxy port number. The port values must be numeric and be between 1 and 65535 (inclusive).
<<file>> does not exist
Ensure that <<FILE>> is one of agent_token.dat, agent_nwid.dat, agent_key.dat, infaagent.ini, agentcore.cfg, proxy.ini.
Proxy configuration is not valid.
Check and correct the specific errors shown before this message.
Failed to generate agent token
The ProxyUtil binary failed to generate proxy.ini. Contact Informatica Global Customer Support for assistance.
Proxy password not specified
The proxy password was not entered by the user.
Don't run the installer in background mode when proxy mode is enabled, because the installer needs to read the password from the keyboard.
Failed to setup proxy config
Check and correct the specific errors shown before this message.
Failed to set proxy for containerd
Failed to create proxy ini secret
Failed to setup containerd: proxy password not specified.

Troubleshooting AWS-related errors

The following table lists AWS Secret Manager-related errors for elastic runtime environments:
Message
Corrective action
Failed to create secret <<NAME>> in AWS secrets manager
Ensure that the AWS Create secret privilege is assigned to the master node instance profile.
Failed to update secret <<NAME>> in AWS secrets manager
Ensure that the AWS Update secret privilege is assigned to the master node instance profile.
Failed to read value of secret <<NAME>>
Ensure that the AWS Read secret privilege is assigned to the master node instance profile.
The following table lists AWS Security Group-related errors for elastic runtime environments:
Message
Corrective action
Failed to create security group $SECURITY_GROUP_NAME ingress rule for port <<PORT_NUMBER>
Ensure that AWS Create Security Group Rule privilege is assigned to master node instance profile.
Failed to get Security Group <<NAME>>
Ensure that AWS Read Security Group Rule privilege is assigned to master node instance profile.
Failed to create security group <NAME>>
Ensure that AWS Create Security Group privilege is assigned to master node instance profile.
Failed to create sec group rule for ssh
Check and correct the specific errors shown before this message.
Failed to create sec group rule for DNS
Failed to create sec group rule for BGP
Failed to create sec group rule for Kube API Service
Failed to create sec group rule for NFS/EFS
Failed to create sec group rule for etcd
Failed to create sec group rule for VXLAN
Failed to create sec group rule for Kubelet API
Failed to create sec group rule for Kube Proxy
Failed to create sec group rule for Kube-scheduler
Failed to create sec group rule for Kube-controller-manager
Failed to create sec group rule for Node Port

Troubleshooting errors for master and worker nodes

The following table lists error messages related to the creation of master nodes for elastic runtime environments:
Message
Corrective action
<<NAME>> node creation failed
Ensure that the AWS RunInstances permission is present in the master node instance profile.
Failed to create instance <<NAME>>
Nodes were not ready after <<COUNT>> retries
Check the Master Node status and startup log from the AWS Console.
Failed to get instance id for <<NAME>>
Ensure that the AWS DescribeInstances permission is present in the master node instance profile.
The following table lists error messages related to the elastic load blancer for master nodes in HA mode in elastic runtime environments:
Message
Corrective action
Failed to create load balancer <<NAME>>
Ensure that the AWS Create ELB permission is present in the master node instance profile.
Failed to deregister all instances from elb
Ensure that the AWS Deregister Instances permission is present in the master node instance profile.
Failed to get elb dns
Ensure that the AWS Describe ELB permission is present in the master node instance profile.
Failed to add master instance <<INSTANCE_ID>> to <ELB_NAME>>
Ensure that the AWS Register Instances permission is present in the master node instance profile.
Failed to add first master instance <<INSTANCE_ID>> <<IP>> to <ELB_NAME>>
Failed to register instance <<INSTANCE_ID>> to load balancer <<NAME>>
Failed to get instance health of load balancer <<NAME>>
Ensure that the AWS Describe ELB permission is present in the master node instance profile.
Failed to get load balancer <<NAME>> details
The following table lists error messages related to the launch template and autoscaling group for worker nodes in elastic runtime environments:
Message
Corrective action
Failed to create launch template <<NAME>>
Ensure that the AWS Create Launch Template permission is present in the master node instance profile.
Failed to create ASG <<NAME>>
Ensure that the AWS Create Auto Scaling Group permission is present in the master node instance profile.
Failed to create ASG after <<COUNT>> attempts

Troubleshooting ALMS deployment errors

The following table lists ALMS deployment-related error messages for elastic runtime environments:
Message
Corrective action
Failed to generate ALMS manifest
Check and correct the specific errors shown before this message.
Failed to get services for RTE <<ID>>, Response Code: <<CODE>>
Ensure that the services are enabled in the elastic runtime environment.
ALMS is not configured for this RTE <<ID>>
Ensure that the services are enabled in the elastic runtime environment and the images are available in the repository.
ALMS image version not found for this RTE <<ID>>
Check and correct the specific errors shown before this message.
Could not get version of ALMS to run
Failed to create manifest for cluster autoscaler

Troubleshooting EFS-related errors

The following table lists EFS-related error messages for elastic runtime environments:
Message
Corrective action
Failed to generate manifests for EFS
Ensure that the correct AWS EFS permissions are present in the master node instance profile.
Failed to create EFS mount targets
Invalid EFS Id $systemDiskId specified in the cluster config
Failed to create mount target for EFS <<ID>> in subnet <<ID>>, secutiry group = <<ID>>

Troubleshooting miscellaneous errors

The following table lists general error messages related to elastic runtime environments:
Message
Corrective action
Internal error: Usage: <<NAME>> masterIP isRunningOnMaster command
Internal script error. Contact Informatica Global Customer Support for assistance.
Internal error: Usage: <NAME>> masterIP isRunningOnMaster fileName
Usage: $0 ELB_NAME instance_id_1 ... instance_id_n
Usage: $0 instance_id AMI_NAME
Usage $0 \"asg_info_1 ... asg_info_n\" node_idle_timeout [toleration]
Usage: $0 ELB_NAME
Usage: $0 proxyHost proxyPort proxyUser
Usage: $0 ec2_instance_type_1 ... ec2_instance_type_n
Usage: $0 PROXY_HOST PROXY_PORT PROXY_USER
Failed to copy file <<NAME>> to <<IP>>
Check and correct the specific errors shown before this message.
Giving up after <<COUNT>> retries
Failed to get worker info
Failed to deploy cluster components
Failed to process tags
Check the tags defined under "Advanced" in the Environment Configuration tab.
Failed to update cluster config dateDeployed field for RTE <<ID>>, Response Code: <<CODE>>
Check and correct the specific errors shown before this message.
Failed to update clusterConfig dateDeployed field.
Failed to get cluster id for RTE <<ID>>, Response Code: <<CODE>>
Failed to get cluster config for RTE <<ID>>, Response Code: <<CODE>>
Failed to get cluster config
Failed to get CspRegionInstanceInfo for Region: <<NAME>>, Response Code: <<NAME>>
Failed to get token from repository <<NAME>>
Ensure that you haven't exceeded your quota of 20 repository tokens.