Installation Errors

Prerequisite check failure

At the time of the package installation, check for the following prerequisites:

  • Hardware
    • Check if the current hardware configuration is according to the prerequisites.

  • Connectivity

    • Check the firewall policies, proxy settings, and network configuration settings. Refer to the firewall and network-related prerequisites.
  • OS Version
    • Check if the current system configuration is according to the prerequisites.
  • Docker installation
    • Check if the current configuration is according to the prerequisites.
      Note: Since RHEL8+ excludes Docker support, Docker prerequisites are not applicable when the AppViewX Cloud Connector is being installed on a RHEL 8+ node.

SHA256 checksum failure

Cross check the SHA256 checksum in the AppViewX Cloud Connector inventory with the SHA256 checksum in the installer package.

To view the SHA256 checksum in the installer package, execute the command given below:

sha256sum <absolute path of the installer package file>

Installation Errors

Table 1. Full list of installation error codes and their resolutions
Error Code Error Message Resolution
CC_CONF_001 Improper docker version (Docker version currently installed: <current version number>) Ensure that the installed version of the Docker is 20.10.5 or above.
CC_CONF_002 Incompatible system architecture Ensure the operating system on the node complies with the following prerequisites:
  • x86 64 bit
CC_CONF_003 Failed to establish connection to AppViewX cloud Check the firewall policies and proxy settings in the tenant premises.
CC_CONF_004 Docker is not installed.
  • Install Docker with non sudo access.
  • Required configuration: version 20.10.5 or higher
  • For instructions for installing the Docker Engine, click here.
  • For post-installation steps for Linux:, click here.
  • In the event of a VM reboot, the Docker needs to be restarted. To configure the Docker to restart on boot, follow the instructions given here.
CC_CONF_005 Insufficient memory (Free memory: <available memory>) Required RAM specification: 8GB
CC_CONF_006 Disk space available is low: <available disk space in MB> Minimum available disk space required: 16GB
CC_CONF_007 Docker not running or not accessible for non sudoers
  1. To check the Docker status, execute one of the following commands:
    • service docker status
    • systemctl status docker
  2. To start the Docker, execute one of the following commands:
    • service docker start
    • systemctl start docker
  3. Ensure that the Docker is accessible to non sudoers.
CC_CONF_008 Cluster already exists.
  1. Uninstall the AppViewX Cloud Connector.
  2. Reinstall the AppViewX Cloud Connector in the same/different node.
CC_CONF_009 firewalld is running
  • Execute the following script to open the port in firewalld that requires sudo access:

    ./deps/utils/open-ips-ports-firewalld.sh

OR

  • Execute the following commands:
    sudo firewall-cmd --permanent --add-port=22/tcp
sudo firewall-cmd --permanent --add-source=10.42.0.0/16 
sudo firewall-cmd --permanent --add-source=10.43.0.0/16 
sudo firewall-cmd --direct --permanent --add-rule ipv4 filter FORWARD 1  -m state --state NEW,RELATED,ESTABLISHED -j ACCEPT 
sudo firewall-cmd --permanent --add-forward-port=port=30020:proto=tcp:toport=30020:toaddr= 
sudo firewall-cmd --permanent --add-forward-port=port=30021:proto=tcp:toport=30021:toaddr= 
sudo firewall-cmd --permanent --add-forward-port=port=30022:proto=tcp:toport=30022:toaddr= 
sudo firewall-cmd --reload
CC_CONF_010 Not met cpu requirement:- No of available processors(vCPU): <number> The required number of processors (vCPU) is 4.
CC_CONF_011 Docker running with Incompatible storage Driver

Update the storage driver to overlay2.

For setup instructions, click here.

CC_CONF_012 A default route is not available in the tenant premises or the tenant is not connected to a network.
  • Add a default route with an IP address.
  • Ensure that the network connection is up.
CC_CONF_013 Cluster already exists Uninstall the AppViewX Cloud Connector.
CC_CONF_015 Low available disk space Minimum available (free) disk space required for /var/lib: 5 GB

In case of restrictions in meeting this requirement, it is recommended to change the data root directory from /var/lib to another dedicated directory. For instructions on changing the data root directory, click here.
CC_CONF_016 Low available disk space Minimum available (free) disk space required for /run: 3 GB
Note: Currently, in the event that this requirement is not met, a workaround is not available.
CC_CONF_017 systemctl command not found Ensure that your operating system has systemctl and systemd installed.
CC_CONF_021 Local IP is configured as Nameserver
  1. On the command line terminal, execute the following command: cat /etc/resolv.conf

    Contents of the resolv.conf file are displayed, which include the nameserver IP addresses.

  2. Check the nameserver IP address(es) in the resolv.conf file.
    Scenario 1: If the nameserver IP address is other than 127.0.0.*:
    1. From the resolv.conf file, copy one (or more) IP address(es).
    2. On the command line terminal of the node where the cloud connector is installed, navigate to the location: (Cloud_Connector_Installed_Folder)/deps/tools.
    3. To edit the config map of the coredns pod, execute the following command: ./k3s kubectl edit cm coredns -n kube-system
    4. Replace the forward IP address in the coredns pod config map with the IP address(es) copied from the resolv.conf file.
    5. Restart the coredns pod: ./k3s kubectl delete pod <COREDNS_POD_NAME> -n kube-system.
    Scenario 2: Nameserver IP address in the resolv.conf file is 127.0.0.*:
    1. Execute the following command: /run/systemd/resolve/resolv.conf.
    2. Now, check the nameserver IP address(es).
      Scenario 2.1: If the nameserver IP address is other than 127.0.0.*:
      1. Copy the IP address(es).
      2. On the command line terminal of the node where the cloud connector is installed, navigate to the location: (Cloud_Connector_Installed_Folder)/deps/tools.
      3. To edit the config map of the coredns pod, execute the following command: ./k3s kubectl edit cm coredns -n kube-system
      4. Replace the forward IP address in the coredns pod config map with the IP address(es) copied from the resolv.conf file.
      5. Restart the coredns pod: ./k3s kubectl delete pod <COREDNS_POD_NAME> -n kube-system.

      Scenario 2.2: If the /run/systemd/resolve directory is not created:

      1. On the command line terminal of the node where the cloud connector is installed, navigate to the location: (Cloud_Connector_Installed_Folder)/deps/tools.
      2. To edit the config map of the coredns pod, execute the following command: ./k3s kubectl edit cm coredns -n kube-system
      3. Replace the forward IP address in the coredns pod config map with the location: /etc/resolv.conf.
      4. Restart the coredns pod: ./k3s kubectl delete pod <COREDNS_POD_NAME> -n kube-system.
CC_INSTALL_001 Moving images and k3s binary failed
  • Ensure that the user has write permission to the /var/lib and the /usr/local/bin directories.
  • Ensure that the sha256sum of the downloaded installer package matches with that of the corresponding cloud connector in the AppViewX Cloud Connector inventory.

    In case of a mismatch, redownload the package.

CC_INSTALL_002 Triggering k3s install failed
  • Ensure that the sha256sum of the downloaded installer package matches with that of the corresponding cloud connector in the AppViewX Cloud Connector inventory.

    In case of a mismatch, redownload the package

CC_INSTALL_003 Setting Kube config failed Uninstall and reinstall the AppViewX Cloud Connector.
CC_INSTALL_004 Importing CC base image failed
  • Uninstall and reinstall the AppViewX Cloud Connector.
  • Ensure that the sha256sum of the downloaded installer package matches with that of the corresponding cloud connector in the AppViewX Cloud Connector inventory.

    In case of a mismatch, redownload the package

CC_PLATFORM_001 Failed to untar the upgrade dependencies

For SRE:

  1. Retry the upgrade operation once.

  2. If the upgrade operation fails, reinstall the Cloud Connector.

CC_PLATFORM_002 Upgrade operation failed

For SRE: Check user logs for cause of operation failure (insufficient disk and/or memory).

  • If the cause of failure is insufficient disk and/or memory space, direct the tenant to free disk and/or memory.

  • If not, reinstall the Cloud Connector.
Troubleshooting: If your error remains unresolved even after executing the above troubleshooting steps, email the AppViewX Technical Support team at [email protected] or call them at +1 (212) 390 1644.