Troubleshooting

Whenever the AppViewX installation fails, you will get an error stating that some script execution failed.

• Prerequisites not met

  Please check for all the items below.

  • port not opened
  • insufficient disk/CPU
  • time not in sync
  • packages not found
  • hostname incorrect in configuration
• Error while installing the docker

  If a customer brings in a custom OS, the Linux packages that AppViewX includes with the installer may not be compatible with the OS. In such situations, you may need to install the appropriate package to continue. This can be observed from the log messages that indicate an error while installing a package.

• Error while installing the docker

  Occasionally, we have observed intermittent errors from the OS during the installation of Docker. If you encounter an error at this stage, please attempt to uninstall the application, reboot all nodes, and then proceed with the installation.

• Docker gets uninstalled from the CAGateway

  Root cause: Although we removed the "uninstall docker" commands from our scripts, we discovered that Docker relies on containerd, which is used as a runtime in the product. The scripts also include steps to remove containerd in the install, uninstall, and upgrade scripts, which cannot be avoided. This ultimately results in the removal of Docker as well. Additionally, the containerd version used in the product conflicts with the pre-existing containerd version of Docker on the server.

  Docker and the AppViewX application cannot co-exist in the same server as it is tightly coupled with containerd. The manually installed docker will be removed during every maintenance activity such as install, uninstall and infra upgrade.

• Context deadline exceeded in consul after the FP3 patching process
  For setups with high network latency or slow I/O, after the FP3 patch process, the consul may be stuck in 1/2 stage, causing the vault to go in a crash loop back. If you encounter this, check the consul logs using the command

  kubectl logs consul-consul-server-0 -n avx

  If the logs specify “context deadline exceeded,” then increase the timeout in consul by the following steps:

  1. Navigate to <installer location>/appviewx_kubernetes/yaml/appviewx_vaut/consul/chart/vaules.yaml
  2. Edit consulAPITimeout: 5s (old value) to consulAPITimeout: 10s (new value)
  3. Save the changes.

  Note: Increase this timeout only based on the latency.
• Error while initializing the kube master/worker

  In certain cases, when uninstallation does not clean up the data properly, we may observe errors while initializing kube master and worker. In such cases, perform an uninstall, reboot all the nodes and then go ahead with the install. Additionally, there are cases where the installation fails due to port connectivity issues. If a failure occurs in this stage, check if ports 6443, 10250, 2379 and 2380 are opened properly.

• Error while initializing the mongodb chart

  This specific error occurs after a timeout of 5 minutes to initialize the mongodb charts. This error occurs when the pods are not able to communicate between themselves. Use the following commands to verify that:

  kubectl describe statefulset -n avx mongo-shareddb

  For any connectivity issues, the output of this command will display the specific error stating connection timed out.
• Node is enabled with IPv6 but the application is not.
  Verify the output of the command:

  ifconfig | grep -i inet6

  If an IPv6 address is displayed, it is necessary to enable IPv6 in the appviewx.conf file. Failure to do so may result in communication issues.
• IP in IP tunneling is not enabled

  If the IP in IP traffic is disabled, which means that the IPv4 protocol is not permitted, we will encounter the same problem. The prerequisite check script does not identify this, so we need to verify it separately to confirm.

• Error while installing the AppViewX plugins

  If an error occurs during the installation of AppViewX plugins, it is likely due to an error in the configuration file. You may observe an error such as Upload failed: scp, in such cases re-trigger plugins_install.sh to install the plugins. Likewise, ensure to review the configuration file carefully and proceed with the execution of plugins_install.sh to install only the plugins.