Skip to content

Anyware Connector Support Bundle on RHEL/Rocky Linux

Beta Feature

Please be aware that the Anyware Connector on RHEL/Rocky Linux is only currently available in a beta version. As such, this feature may change as it is developed, and it will not be supported by Teradici Global Support Services. Features in the beta version are considered not yet ready for full production and you use them at your own risk.

If you encounter an issue with the Anyware Connector on RHEL/Rocky Linux, it is possible to generate a support bundle that can be sent to the HP support team to investigate and resolve.

To generate the support bundle, run the following command:

sudo /usr/local/bin/cas-connector diagnose --support-bundle
If this command is successful, a tar.gz file will be located under the /tmp/ directory with a name formatted as follows:

/tmp/cas-connector-support-bundle-(date)-(time).tar.gz

Support Bundle Information and Logs

The support bundle collects the various information from the system and then zip the files into a .tar.gz file in the /tmp directory.

Once you unzip the file the structure is as follows:

  • files/etc folder contains files with OS level information:
    • issue file contains a copy of all contents from the /etc/issue file.
    • os-release file contains all operating system identification data that was found in the /usr/lib/os-release file.
    • **systemd/system/k3s.service**folder contains the information about k3s.service configuration.
  • files/var/log/cas-connector folder collects all of the CAS Connector log files, for example generate, configure, diagnose, install logs.

The out folder collects outputs from running various commands to expose the details of relevant system information and Anyware Connector backend services, as outlined below:

  • os folder contains the following files:
    • dmesg.out file contains the output of command dmesg.
    • ls_-l@var@crash.out file contains the output of the command ls -l /var/crash.
    • pgrep_-l_k3s.out file contains the output of the command pgrep -l k3s.
    • ps_wwauxfx.out file contains the output of the command ps wwauxfZ.
    • ss-aux.out file contains the output of the command ss -ax.
    • who.out file contains the output of the command who.
    • dnf_list_--installed_--disablerepo=*.out file contains the packages that are currently installed on the system and their versions.
  • The firewall folder contains the outputs of the command firewall-cmd --list-services.
  • The network folder displays the following network files:
    • netstat_-Wnap.out file contains the output of the command netstat -Wnap.
    • ip_add.out file contains the output of the command ip add.
    • selinux folder contains the following files:
      • semodule_-l.out file contains the output of the command semodule -l.
      • sestatus.out file contains the output of the command sestatus.
  • The deployments folder contains the following files:
    • kubectl_get_deployment.out file is the output of the command kubectl get deployments that lists the status of all deployments for CAS Manager services.
    • The description of the deployment for each of the deployments through the output of the command kubectl describe.
    • The deployments information is retrieved from the following namespaces: kube-system, kube-public, kube-node-lease, connector, logging, and ingress-nginx.
  • The pods folder contains the following files:
    • kubectl_get_pods.out file is the output of the command get pods that lists the status of all pods for CAS Manager services.
    • The description of a pod for each of the pods through the output of the command kubectl describe pod
    • The pod information is retrieved from the following namespaces: kube-system, kube-public, kube-node-lease, connector, logging, and ingress-nginx.
  • logs folder contains the following files:
    • The log files for each pod.
    • The logs files are retrieved from the following namespaces: kube-system, kube-public, kube-node-lease, connector, logging, and ingress-nginx.
  • The services folder contains the following files:
    • kubectl_get_services.out file is the output of the command get services that lists the status of all services for CAS Manager services.
    • The description of a service for each of the services through the output of the command kubectl describe services
    • The services information is retrieved from the following namespaces: kube-system, kube-public, kube-node-lease, connector, logging, and ingress-nginx.
  • secrets folder displays the output of the command kubectl get secrets and displays the following files:
    • kubectl_get_secrets.out file is the output of the command get secrets that lists the status of all services for CAS Manager services.
    • The description of a secrets through the output of the command kubectl describe secrets.
    • The secrets information is retrieved from the following namespaces: kube-system, kube-public, kube-node-lease, connector, logging, and ingress-nginx.