App Visibility proxy installation or upgrade connectivity and cluster issues

Before the App Visibility proxy installation process begins, the installation utility conducts several connectivity checks to verify that the storage engine nodes can communicate and form a redundancy cluster. The following diagram describes the communication between components for the connectivity checks.

The diagram shows two previously installed App Visibility proxy servers, and one server marked New from which the installation utility runs. The App Visibility portal holds the configuration information for each of the proxy servers.

The following table describes the communication checks that are labeled in the diagram, and how to troubleshoot issues before the installation process begins, or after the installation process is complete.

App Visibility proxy connectivity checks

ConnectionCommunication check descriptionTroubleshooting suggestions
1

From the installation utility on the New App Visibility proxy, the App Visibility portal receives a request for the list of currently connected proxies.

The portal returns a list of online App Visibility proxy servers.

 

If the new proxy receives the list, the connectivity check continues.

Before installation

Verify the following configuration:

  • New App Visibility proxy can access the App Visibility portal IP address or host name, and port number (default 8100)
  • App Visibility portal can access the New App Visibility proxy IP address or host name (Listening Address), and port number (default 8300)

After installation

Verify the following configuration:

  • On the App Visibility portal, open the portal.properties file and confirm that the callback.address is accessible from the New App Visibility proxy server.
  • On the New App Visibility proxy server, open the apm-proxy.properties file and confirm that the callback.address is accessible from the App Visibility portal server.
2

The New App Visibility proxy checks communication to the previously installed App Visibility proxy storage engines.

The check confirms both the IP address and host name.

If the new proxy can communicate with the previously installed proxy servers, the connectivity check continues.

Before installation

Verify the following configuration:

  • New App Visibility proxy can access the IP address and host name of each previously installed App Visibility proxy servers and storage transport port numbers (default 8303)
  • Previously installed App Visibility proxy servers can access the New App Visibility proxy IP address or host name (Listening Address), and storage transport port number (default 8303)

    If your App Visibility proxy server has more than one IP address, ensure that you use the IP address that is accessible from previously installed App Visibility proxy servers and from the App Visibility portal.

After installation

Verify the following configuration:

  • On the previously installed App Visibility proxy servers, open the apm-proxy.properties files and confirm that the callback.address is accessible from the New App Visibility proxy server.

    If you changed a previously installed proxy's callback address, you must update the transport.host in the proxy_installationDirectory/elasticsearch/config/elasticsearch.yml file.
    Restart the App Visibility proxy service and the Elasticsearch service.
  • On the New App Visibility proxy server, open the apm-proxy.properties file and confirm that the callback.address is accessible from the previously installed App Visibility proxy servers.

    If you changed the new proxy's callback address, you must update the transport.publich_host in the proxy_installationDirectory/elasticsearch/config/elasticsearch.yml file.
    Restart the App Visibility proxy service and the Elasticsearch service.
3

The New App Visibility proxy sends its IP address, host name, and designated storage engine port number to the App Visibility portal.

If the portal receives the configuration information, the connectivity check continues.

Same check as for connection #1.
4

The App Visibility portal sends the configuration information for the New App Visibility proxy to the previously installed proxy servers.

If the previously installed proxy servers receive the configuration information, the connectivity check continues.

Before installation

Verify that the App Visibility portal can access the previously installed App Visibility proxy servers IP address or host name (Listening Address), and storage HTTP port number (default 8302).

After installation

  • On the previously installed App Visibility proxy servers, open the apm-proxy.properties files and confirm that the callback.address is accessible from the App Visibility portal.

    If you changed a previously installed proxy's callback address, on the previously installed proxy you must update the transport.host in the proxy_installationDirectory/elasticsearch/config/elasticsearch.yml file.
    Restart the App Visibility proxy service and the Elasticsearch service.
5

The previously installed App Visibility proxy servers confirm communication with the New App Visibility proxy.

If the communication is confirmed, the connectivity check is complete and the installation process begins.

Before installation

Verify that the previously installed App Visibility proxy servers can access the New App Visibility proxy IP address or host name (Listening Address), and storage transport port number (default 8303).

After installation

  • On the New App Visibility proxy server, open the apm-proxy.properties file and confirm that the callback.address is accessible from the previously installed App Visibility proxy servers.

    If you changed the new proxy's callback address, you must update the transport.publich_host in the proxy_installationDirectory/elasticsearch/config/elasticsearch.yml file.
    Restart the App Visibility proxy service and the Elasticsearch service.




Was this page helpful? Yes No Submitting... Thank you

Comments