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 miscellaneous errors

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
Service error. Contact Informatica Global Customer Support.
Internal error: Usage: <NAME>> masterIP isRunningOnMaster fileName
Service error. Contact Informatica Global Customer Support.
Usage: $0 ELB_NAME instance_id_1 ... instance_id_n
Service error. Contact Informatica Global Customer Support.
Usage: $0 instance_id AMI_NAME
Service error. Contact Informatica Global Customer Support.
Usage $0 \"asg_info_1 ... asg_info_n\" node_idle_timeout [toleration]
Service error. Contact Informatica Global Customer Support.
Usage: $0 ELB_NAME
Service error. Contact Informatica Global Customer Support.
Usage: $0 proxyHost proxyPort proxyUser
Service error. Contact Informatica Global Customer Support.
Usage: $0 ec2_instance_type_1 ... ec2_instance_type_n
Service error. Contact Informatica Global Customer Support.
Usage: $0 PROXY_HOST PROXY_PORT PROXY_USER
Service error. Contact Informatica Global Customer Support.
Failed to copy file <<NAME>> to <<IP>>
Check and correct the errors that appeared before this message.
Giving up after <<COUNT>> retries
Check and correct the errors that appeared before this message.
Failed to get worker info
Check and correct the errors that appeared before this message.
Failed to deploy cluster components
Check and correct the errors that appeared before this message.
Failed to process tags
Check the tags in the advanced properties on the
Environment Configuration
tab in Administrator.
Failed to update cluster config dateDeployed field for RTE <<ID>>, Response Code: <<CODE>>
Check and correct the errors that appeared before this message.
Failed to update clusterConfig dateDeployed field.
Check and correct the errors that appeared before this message.
Failed to get cluster id for RTE <<ID>>, Response Code: <<CODE>>
Check and correct the errors that appeared before this message.
Failed to get cluster config for RTE <<ID>>, Response Code: <<CODE>>
Check and correct the errors that appeared before this message.
Failed to get cluster config
Check and correct the errors that appeared before this message.
Failed to get CspRegionInstanceInfo for Region: <<NAME>>, Response Code: <<NAME>>
Check and correct the errors that appeared before this message.
Failed to get token from repository <<NAME>>
Ensure that you haven't exceeded your quota of 20 repository tokens.
Failed to execute `kubectl get namespace | grep -q idmc-system` E0715 22:33:37.559917 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp [::1]:8080: connect: connection refused" The connection to the server localhost:8080 was refused - did you specify the right host or port?
An error occurred during installation. You can ignore this message.
Instance count mismatch after deleting an EC2 instance
After an EC2 instance is deleted from AWS, it might continue to have the status
Up and Running
in
Informatica Intelligent Cloud Services
, so there's a discrepancy in the reported instance count.

0 COMMENTS

We’d like to hear from you!