Elemental Support

The elemental-support is a utility program that collects all information about the machine where the Elemental stack is running.

When troubleshooting issues with any Elemental node, it is possible to generate a compressed file containing logs and config files.
Be aware that the tar.gz generated file may contain sensitive information, like access tokens to the management cluster and more.

Requirements

Optionally, the elemental-support utility needs kubectl to be available on the target machine, in order to collect node information. This can be very useful to debug Elemental upgrade issues with a node.
The kubectl config used will be looked up from the KUBECONFIG environment variable, or in its absence either the /etc/rancher/k3s/k3s.yaml or /etc/rancher/rke2/rke2.yaml files will be used instead.

Collecting information

Once ran, the elemental-support will create the compressed archive within the same directory.

Example run:

  1. m-993369ec-4b3f-4368-86c3-1449ebf57cf2# elemental-support 
  2. I0430 11:33:38.934777    8536 log.go:42] Support version 1.3.4, commit 192dc33d, commit date 20230831
  3. I0430 11:33:38.934865    8536 log.go:46] Getting elemental-support version
  4. I0430 11:33:38.934918    8536 log.go:42] Copying /etc/os-release
  5. I0430 11:33:38.935008    8536 log.go:42] Copying /etc/resolv.conf
  6. I0430 11:33:38.935066    8536 log.go:42] Copying /etc/hostname
  7. I0430 11:33:38.935131    8536 log.go:42] Copying /etc/rancher/agent/config.yaml
  8. I0430 11:33:38.935174    8536 log.go:42] Copying /etc/rancher/agent/config.yaml
  9. I0430 11:33:38.935214    8536 log.go:42] Copying dir /var/lib/elemental/agent/applied/
  10. I0430 11:33:38.935434    8536 log.go:42] Copying dir /var/lib/rancher/agent/applied/
  11. I0430 11:33:38.935572    8536 log.go:42] Copying dir /system/oem
  12. I0430 11:33:38.936584    8536 log.go:42] Copying dir /oem/
  13. I0430 11:33:38.937121    8536 log.go:42] Getting service log elemental-system-agent
  14. I0430 11:33:38.959813    8536 log.go:42] Getting service log rancher-system-agent
  15. I0430 11:33:38.979271    8536 log.go:42] Getting service log k3s
  16. I0430 11:33:39.018177    8536 log.go:42] Getting service log rke2
  17. I0430 11:33:39.036852    8536 log.go:42] Getting service log cos-setup-boot
  18. I0430 11:33:39.053409    8536 log.go:42] Getting service log cos-setup-fs
  19. I0430 11:33:39.068132    8536 log.go:42] Getting service log cos-setup-initramfs
  20. I0430 11:33:39.085935    8536 log.go:42] Getting service log cos-setup-network
  21. I0430 11:33:39.101440    8536 log.go:42] Getting service log cos-setup-reconcile
  22. I0430 11:33:39.119528    8536 log.go:42] Getting service log cos-setup-rootfs
  23. I0430 11:33:39.136151    8536 log.go:42] Getting service log cos-immutable-rootfs
  24. I0430 11:33:39.153850    8536 log.go:42] Getting service log elemental
  25. I0430 11:33:39.170564    8536 log.go:42] Getting service log NetworkManager
  26. I0430 11:33:39.190169    8536 log.go:42] Getting elemental-cli version
  27. I0430 11:33:39.205410    8536 log.go:42] Getting elemental-operator version
  28. I0430 11:33:39.205621    8536 log.go:42] Getting elemental-register version
  29. I0430 11:33:39.266263    8536 log.go:42] Found k3s kubeconfig at /etc/rancher/k3s/k3s.yaml
  30. I0430 11:33:39.266312    8536 log.go:42] Found k3s kubectl at /usr/local/bin/kubectl
  31. I0430 11:33:39.266320    8536 log.go:42] Getting k8s info for pods
  32. I0430 11:33:39.770730    8536 log.go:42] Getting k8s info for secrets
  33. I0430 11:33:39.962037    8536 log.go:42] Getting k8s info for nodes
  34. I0430 11:33:40.118680    8536 log.go:42] Getting k8s info for services
  35. I0430 11:33:40.280797    8536 log.go:42] Getting k8s info for deployments
  36. I0430 11:33:40.458869    8536 log.go:42] Getting k8s info for plans
  37. I0430 11:33:40.612138    8536 log.go:42] Getting k8s info for apps
  38. I0430 11:33:40.787309    8536 log.go:42] Getting k8s info for jobs
  39. I0430 11:33:40.932361    8536 log.go:42] Getting k8s logs for namespace cattle-system
  40. I0430 11:33:41.353556    8536 log.go:42] Getting k8s logs for namespace kube-system
  41. I0430 11:33:41.935885    8536 log.go:42] Getting k8s logs for namespace ingress-nginx
  42. W0430 11:33:41.999345    8536 log.go:62] No pods in namespace ingress-nginx
  43. I0430 11:33:41.999365    8536 log.go:42] Getting k8s logs for namespace calico-system
  44. W0430 11:33:42.061902    8536 log.go:62] No pods in namespace calico-system
  45. I0430 11:33:42.061927    8536 log.go:42] Getting k8s logs for namespace cattle-fleet-system
  46. I0430 11:33:42.204459    8536 log.go:42] Creating final file
  47. I0430 11:33:42.215815    8536 log.go:42] All done. File created at m-993369ec-4b3f-4368-86c3-1449ebf57cf2-2024-04-30T113342Z.tar.gz