Installation Issues

Management Pack fails to install

Management Packs can fail to install for a number of reasons, although it is not common. The best way to diagnose what is happening is to look in the logs on the main VMware Aria Operations cluster node (not a Cloud Proxy). There are two methods to access these logs:

• Using ssh: ssh into the cluster and navigate to $ALIVE_BASE/user/log. Installation issues are logged to the analytics log, which has the form analytics-<GUID>.log. Generally, a good place to start is to search that log file for the adapter kind key (found in the manifest.txt file in the project directory, as the entry in the adapter_kinds array).
• Using the VMware Aria Operations UI: Navigate to Administration → Support Logs. Expand the first VMware Aria Operations Cluster Node, and expand ANALYTICS. Select the analytics log, which has the form analytics-<GUID>.log. By default, the viewer only displays 1000 lines of the file. You may need to increase this. To search, use your browser's search function.

---

Adding an Account: 'Collector is not compatible with adapter type.'

Example of a 'Collector is not compatible with adapter type' error message

This message occurs if the Collector/Group field in the 'Add Account' page is set to a collector that is not a Cloud Proxy. Integration SDK management packs can only run on a Cloud Proxy. See below for instructions on installing a Cloud Proxy in VMware Aria Operations.

---

Adding an Account: 'Unknown adapter type'

Example of an 'Unknown Adapter Type' error message for an adapter with type/key 'Testserver'.

This message can occur for several reasons: - The Collector/Group the MP is running on is a Cloud Proxy. See below for instructions on installing a Cloud Proxy in VMware Aria Operations. - Check that the Cloud Proxy version supports containerized adapters. Containerized adapter support was added in VMware Aria Operations version 8.10.0.

---

Adding an Account: "Wait for response of task 'Test connection' is timed out for collector ''"

If the test connection times out, logs can be found in collector.log. In particular, if you see a message similar to this:

Status 404: {"message":"manifest for <image> not found: manifest unknown: 
    The named manifest is not known to the registry."}

It means that the Docker Repository is not public. See Setting up a Container Registry and if necessary, a workaround (for development only) for using a public repository.

Access the collector log using the Aria Operations Cloud Proxy the adapter is running on. There are two methods to access these logs:

• Using ssh: ssh into the cloud proxy the adapter is running on and navigate to $ALIVE_BASE/user/log. Test Connection issues are logged to the collector log collector.log. Generally, a good place to start is to search that log file for recent ERROR level logs.
• Using the VMware Aria Operations UI: Navigate to Administration → Support Logs. Expand the first Cloud Proxy item that the adapter is running on, expand COLLECTOR, and select the collector.log file. By default, the viewer only displays 1000 lines of the file. You may need to increase this. To search, use your browser's search function.

---

How can I install a Cloud Proxy in my VMware Aria Operations environment?

For instructions for setting up a Cloud Proxy, see this document.