Hi, i tried to deployed the api proxy in dev environment. Deployed the revision but getting traffic can not flow and call timed out error. What will be the reason of getting this error?
Solved! Go to Solution.
Usually you can see that error if the deployment fails on specific router/message processor UUIDs.
You can get deployment details for a specific revision number of an API proxy, which includes router and message processor UUIDs. you can troubleshoot deployment status on a router or message processor by noting the router or message processor ID and checking your server logs. You may need to restart the router or message processor that has a deployment issue.
The API Proxy Deployment fails with "Call timed out error" typically either because there is communication failure between Management Server and Message Processor due to network connectivity issues or because the bundle size is large and it may take longer time for MP to download so we see a time out.
If you are on Private Cloud, please refer to the section "Troubleshooting Deployment Errors" in Apigee Edge Troubleshooting Guide for steps to diagnose this issue.
If you are on Public Cloud, you can get the deployment status of the API and check which component has the error
curl -v https://api.enterprise.apigee.com/organizations/<orgname>/environments/<envname>/apis/<apiname>/depl... -u <user>:<password>
And then contact Apigee Support to investigate this issue further.
Usually you can see that error if the deployment fails on specific router/message processor UUIDs.
You can get deployment details for a specific revision number of an API proxy, which includes router and message processor UUIDs. you can troubleshoot deployment status on a router or message processor by noting the router or message processor ID and checking your server logs. You may need to restart the router or message processor that has a deployment issue.
Is it possible to verify the status of the deployment?
The API Proxy Deployment fails with "Call timed out error" typically either because there is communication failure between Management Server and Message Processor due to network connectivity issues or because the bundle size is large and it may take longer time for MP to download so we see a time out.
If you are on Private Cloud, please refer to the section "Troubleshooting Deployment Errors" in Apigee Edge Troubleshooting Guide for steps to diagnose this issue.
If you are on Public Cloud, you can get the deployment status of the API and check which component has the error
curl -v https://api.enterprise.apigee.com/organizations/<orgname>/environments/<envname>/apis/<apiname>/depl... -u <user>:<password>
And then contact Apigee Support to investigate this issue further.
You can use API http://docs.apigee.com/management/apis/get/organizations/ %7Borg_name%7D/apis/%7Bapi_name%7D/revisions/%7Brevision_number %7D/deployments
to get the deployment status of your API proxy.You may need to restart the router or message processor that has a deployment issue.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 | |
1 |