Deployment errors

You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info

Any error that occurs during deployment of an API Proxy is called a Deployment error. Deployment of API proxies might fail due to various reasons such as network connectivity issues between Edge servers, issues with the Cassandra datastore, ZooKeeper exceptions, and errors in the API proxy bundle.

Playbooks

This section provides information and guidance on some specific procedures that can be followed for troubleshooting and resolving deployment errors.

Error message	Playbook
`Error: Call timed out; either server is down or server is not reachable`	Timeout Error
`Unexpected error Error while fetching children for path`	Error Fetching Children for Path
`Error while accessing datastore;Please retry later`	Error Accessing Datastore
`Configuration failed, associated contexts = []`	Configuration Failed
`Unexpected error occurred while processing the updates,associated contexts = []`	Error Processing Updates

Diagnostic information

If you need assistance from Apigee Edge Support on the deployment error, then gather the following diagnostic information and share it in the support case:

Diagnostic information	Where can I gather this information?	How do I gather this information?
Deployments API Output	Management Server	curl -s 0:8080/v1/organizations/`ORGNAME`/environments/`ENVNAME`/apis/`APINAME`/deployments > /tmp/ms_deployments_output_$(hostname)_$(date +%Y.%m.%d_%H.%M.%S).json Note: Gather this information on the Management Server after replacing `ORGNAME`, `ENVNAME` and `APINAME` with the actual values.
Management Server logs	Management Server	tar cvzf /tmp/ms_systemlogs_$(hostname)_$(date +%Y.%m.%d_%H.%M.%S).tar.gz /opt/apigee/var/log/edge-management-server/logs/system* tar cvzf /tmp/ms_transactionlogs_$(hostname)_$(date +%Y.%m.%d_%H.%M.%S).tar.gz /opt/apigee/var/log/edge-management-server/logs/transactions* Bundle all the data on Management Server with the following command: tar -cvzf /tmp/ms_data_`CASE#`_$(hostname).tar.gz* /tmp/ms_* Note: Replace `CASE#` with the specific case number for which you are providing these documents. Attach this file also to the case.
Classification Tree output	Message Processor	curl -s 0:8082/v1/classification/tree > /tmp/rmp_classification_tree_$(hostname)_$(date +%Y.%m.%d_%H.%M.%S).json Note: Gather this information on the Message Processor.
Message Processor logs	Message Processor	tar cvzf /tmp/rmp_systemlogs_$(hostname)_$(date +%Y.%m.%d_%H.%M.%S).tar.gz /opt/apigee/var/log/edge-message-processor/logs/system* tar cvzf /tmp/rmp_transactionlogs_$(hostname)_$(date +%Y.%m.%d_%H.%M.%S).tar.gz /opt/apigee/var/log/edge-message-processor/logs/transactions* tar cvzf /tmp/rmp_system_monitor_config_mp_logs_$(hostname)_$(date +%Y.%m.%d_%H.%M.%S).tar.gz /opt/apigee/var/log/edge-message-processor/edge-message-processor* /opt/apigee/var/log/edge-message-processor/config* /opt/apigee/var/log/edge-message-processor/system-monitor*
Connectivity with Cassandra	Message Processor	telnet `CASSANDRA_IP` 9042 \| tee /tmp/rmp_cassandra_`NODE#`_connectivity_$(hostname)_$(date +%Y.%m.%d_%H.%M.%S).txt telnet `CASSANDRA_IP` 9160 \| tee /tmp/rmp_cassandra_`NODE#`_connectivity_$(hostname)_$(date +%Y.%m.%d_%H.%M.%S).txt If you don’t have `telnet`, then you can use the `netcat` command as follows: nc -vz `CASSANDRA_IP` 9042 \| tee /tmp/rmp_cassandra_`NODE#`_connectivity_$(hostname)_$(date +%Y.%m.%d_%H.%M.%S).txt nc -vz `CASSANDRA_IP` 9160 \| tee /tmp/rmp_cassandra_`NODE#`_connectivity_$(hostname)_$(date +%Y.%m.%d_%H.%M.%S).txt Note: Replace `NODE#` with 1, 2 and so on. You need to repeat the above steps for each of the Cassandra nodes in each of the data centers.
Connectivity with ZooKeeper	Message Processor	telnet `ZOOKEEPER_IP` 2181 \| tee /tmp/rmp_zookeeeper_`NODE#`_connectivity_$(hostname)_$(date +%Y.%m.%d_%H.%M.%S).txt If you don’t have `telnet`, then you can use the `netcat` command as follows: nc -vz `ZOOKEEPER_IP` 2181 \| tee /tmp/rmp_zookeeper_`NODE#`_connectivity_$(hostname)_$(date +%Y.%m.%d_%H.%M.%S).txt Note: Replace `NODE#` with 1, 2 and so on. You need to repeat the above steps for each of the ZooKeeper nodes in each of the data centers.
Compress all the diagnostic data	Message Processor	tar -cvzf /tmp/rmp_data_`CASE#`_$(hostname).tar.gz* /tmp/rmp_* Note: Replace `CASE#` with the specific case number for which you are providing these documents.
Cassandra logs	Cassandra	tar cvzf /tmp/cassandra_logs_$(hostname)_$(date +%Y.%m.%d_%H.%M.%S).tar.gz /opt/apigee/var/log/apigee-cassandra/system* /opt/apigee/var/log/apigee-cassandra/config* tail -2000 /opt/apigee/var/log/apigee-cassandra/apigee-cassandra.log > /tmp/cassandra_apigee-cassandra_log_$(hostname)_$(date +%Y.%m.%d_%H.%M.%S).log Note: Attach these files to the support case.
ZooKeeper logs and associated files	ZooKeeper	tar cvzf /tmp/zookeeper_logs_$(hostname)_$(date +%Y.%m.%d_%H.%M.%S).tar.gz /opt/apigee/var/log/apigee-zookeeper/.log /opt/apigee/apigee-zookeeper/conf/zoo.cfg /opt/apigee/data/apigee-zookeeper/data/myid Note:* Attach this file to the support case.