Troubleshooting Backup and Restore Failures
In case the back up or restore process fails, check whether all components are running. To do so, use API Portal Cloud Controller (ACC).
To troubleshoot backup and restore failures
1. Check whether all components are running using ACC.
a. To start ACC under a Windows operating system click Start > All Programs > webMethods API Portal > Administration > Start webMethods API Portal Cloud Controller.
To start ACC under a Linux operating system, run the acc.sh file.
b. Type help or help <command> to get information about the usage of the commands.
c. Type list to monitor the status of all components (runnables). This example shows ACC of a API Portal Connect Server installation for a medium number of users.
All Components with their states are listed.
ACC+ Node localhost - 7 installed runnables.
ID State Version Type
zoo_s STARTED 10.0.14.0 com.aris.runnables.zookeeper-run-prod
postgres_s STARTED 10.0.14.0 com.aris.runnables.PostgreSQL-run-prod
cloudsearch_s STARTED 10.0.14.0 com.aris.cip.y-cloudsearch-run-prod
elastic_s STARTED 10.0.14.0 com.aris.runnables.elasticsearch-run-prod
kibana_s STARTED 10.0.14.0 com.aris.runnables.kibana-run-prod
apiportalbundle_s STARTED 10.0.14.0 com.aris.bundles.apiportalbundle-run-prod
loadbalancer_s STARTED 10.0.14.0 com.aris.runnables.httpd.httpd-run-prod
The status of all components represented by their instance IDs are listed. Possible states are:
UNKNOWN: The component state is not yet known. This state is shown directly after the agent was started.
STOPPED: The component is currently not running.
STARTING: The component is starting, but this process is not complete yet.
STARTED: The component is running.
STOPPING: The component is stopping, but this process is not complete yet.
DOWN: This component has and crashed. The agent attempts to automatically restart the component momentarily.
FAILED: Component has crashed. The agent has given up trying to restart the component.