Get help with Connected Azure Gateway

This section provides troubleshooting, known limitations and restrictions that you may encounter while you are working with the connected managed environment for Azure Gateway within Amplify Central. It also provides tips you may find useful when working with this environment.

7 minute read

Troubleshooting

Question Answer
Why can’t Discovery Agent connect to Azure Gateway? Make sure that the Azure configuration (Subscription, tenantID and service principal) are correct.
Why can’t Traceability Agent connect to Azure event hub? Make sure that the Azure configuration (Subscription, tenantID and service principal) are correct.
Why can’t my agents connect to Amplify Central? Go to Amplify Central UI > Access > Service Accounts and make sure that the Service Account is correctly named and valid. Make sure that the organizationID and team are correct.
I have the following error: Amplify Central - FAIL (error creating request header. bad response from AxwayId: 400 Bad Request) Make sure that the Service Account set up is properly spelled (refer to central.clientId property). Verify that the public/private key pair is the one corresponding to the Service Account.
Why don’t I see traffic in Amplify Central? Make sure that the Condor URL is accessible from the machine where Traceability Agent is installed.
Why isn’t my agent status displayed in the environment details page? It is possible that your agents and their corresponding resources are not linked together. Follow this procedure to ensure the correct usage of agent resources.

Limitations

  • Azure versioning not taken into account while discovering APIs
  • Discovery Agent is not able to send credentials to subscribers

Error Codes and Mitigations

Code # Description Mitigation
1001 initialization error checking for dependencies to respond, possibly network or settings See Administer Azure network traffic and Reference - Agent configuration
1002 timeout error checking for dependencies to respond, possibly network or settings See Administer Azure network traffic and Reference - Agent configuration
1003 Periodic health checker or status updater failed. Services are not ready See Administer Azure network traffic and Reference - Agent configuration
1100 general configuration error in CENTRAL See Reference - Agent configuration for the Central Config
1101 error attempting to query for ENVIRONMENT Check that the Environment Name in config matches the name on Amplify Central
1102 could not find specified team in Amplify Central, check CENTRAL_TEAM Check that the Team Name in config matches the name on Amplify Central
1110 connection to Amplify Central failed See Administer Azure network traffic
1120 request to Amplify Central failed See Administer Azure network traffic and that the Environment Name in config matches the name on Amplify Central
1130 request to get authentication token failed Check the Auth configuration (ClientId, Private and Public keys/index.html). See Reference - Agent configuration
1131 token retrieved but was invalid on request to Amplify Central Check the Auth configuration (ClientId, Private and Public keys/index.html). See Reference - Agent configuration
1140 couldn’t find a subscriber email address based on the ID in the subscription event The user requesting this subscription may not have an Email address set
1141 couldn’t contact Amplify Central for subscription, possible network error See Administer Azure network traffic
1142 couldn’t get subscription data from Amplify Central See Administer Azure network traffic and Reference - Agent configuration
1143 couldn’t create or update subscription schema data See Administer Azure network traffic
1144 unexpected response when managing subscription schema on Amplify Central See Administer Azure network traffic and Reference - Agent configuration
1145 unable to create webhook for the subscription definition See Administer Azure network traffic
1146 unable to create secret for the subscription definition See Administer Azure network traffic
1147 error parsing filter in configuration. Syntax error See Discover APIs
1148 error parsing filter in configuration. Unrecognized expression See Discover APIs
1149 error parsing filter in configuration See Discover APIs
1150 error parsing filter in configuration. Invalid call argument See Discover APIs
1151 error parsing filter in configuration. Invalid selector type See Discover APIs
1152 error parsing filter in configuration. Invalid selector expression See Discover APIs
1153 error parsing filter in configuration. Invalid operator See Discover APIs
1154 error parsing filter in configuration. Unrecognized condition See Discover APIs
1155 error getting subscription definition properties in Amplify Central See Administer Azure network traffic and Reference - Agent configuration
1156 error updating subscription definition properties in Amplify Central See Administer Azure network traffic and Reference - Agent configuration
1157 error getting catalog item API server info properties in Amplify Central See Administer Azure network traffic and Reference - Agent configuration
1158 subscription manager is not running likely because the agent can’t communicate with Amplify Central See Administer Azure network traffic and Reference - Agent configuration
1160 error getting endpoints for the API specification Verify that the OpenAPI Specification for the discovered API has available endpoints and operations on each endpoint
1161 error deleting API Service for catalog item in Amplify Central Verify that the catalog item exists in Amplify Central
1162 error deleting catalog item in Amplify Central Verify that the catalog item exists in Amplify Central
1300 error communicating with server for subscription notifications (SMTP or webhook/index.html), check SUBSCRIPTION config See Manage subscription workflow
1301 subscription notifications not configured, check SUBSCRIPTION config See Manage subscription workflow
1302 error creating data for sending subscription notification Check API Manager UI for configuration of API and its applications
1303 email template not updated because an invalid authType was supplied Check API Manager UI for configuration of API and its applications, specifically enabled authentication on the application
1304 no email template found for action See Manage subscription workflow for the SMTP template settings
1305 error sending email to SMTP server See Manage subscription workflow for the SMTP settings
1401 error parsing configuration values, check the config referenced in error See Manage subscription workflow
1402 error in overriding configuration using file with environment variables Make sure the env_vars file exists and is properly formatted
1403 invalid value for statusHealthCheckPeriod. Value must be between 1 and 5 minutes Make sure the env_vars file exists and is properly formatted
1404 invalid value for statusHealthCheckInterval. Value must be between 30 seconds and 5 minutes Make sure the env_vars file exists and is properly formatted
1405 a key file could not be read For binary deployment, validate that your user running the agent has access to the key file. For docker deployment on Linux, give the User ID in the container read access to the file. setfacl -m u:2500:r private_key.pem
1410 invalid configuration settings for the logging setup See Reference - Agent configuration for logging configuration options
1500 could not set proxy Check the TRACEABILITY_PROXYURL setting here Reference - Agent configuration
1501 failed to publish events See Administer Azure network traffic
1502 error closing connection with Condor Likely a timeout error, processing will retry automatically
1503 http transport is not connected Check the TRACEABILITY_HOST setting here Reference - Agent configuration
1504 failed to encode the json content Internal system error. Contact your system administrator
1505 invalid traceability config See Reference - Agent configuration for the Traceability Config
1510 global redactions have not been initialized See Trace redaction
1511 error while compiling regular expression See Trace redaction
1550 error hit while applying redaction See Trace redaction
1600 error registering the job The agent attempted to register a job, but could not do so successfully
1601 error executing a job A job defined in the agent failed, see the logs for more info
1602 error executing a retry job A job defined in the agent failed, see the logs for more info
1611 periodic healthcheck failed One of the agent healthchecks failed, check the agent logs for more info
1612 a healthcheck failed the maximum consecutive times One of the agent healthchecks failed, check the agent logs for more info
1900 unsupported system for service installation The service installation only supports Linux
1901 systemd is required for service installation The service installation requires an OS with systemd
1902 service management requires root privileges All service actions require root privileges
1903 service has already been installed The service has already been installed, you can use “remove” to clean it up and then install it again
1904 service is running and cannot be removed until stopped The service has to be stopped before removing it
1905 service is not yet installed The service has to be installed prior to taking any other action
1906 service is already running The service is already running, nothing to do
1907 service is already stopped The service is already stopped, nothing to do
4100 error creating a service in AMPLIFY Central for API on Azure APIM service See Administer Azure network traffic and Reference - Agent configuration
4101 error getting API specification for API on Azure APIM service See [Administer Azure network traffic](/docs/central/connect-azure-gateway/network-traffic-azure)

Last modified May 10, 2021: APIGOV-18438 (#1858) (76ada034)