Troubleshoot Telemetry Pipeline installations on Linux servers
As part of the installation process, Chronosphere Telemetry Pipeline performs health checks on your behalf. If you encounter any issues when trying to install Telemetry Pipeline, Chronosphere recommends taking the following troubleshooting steps.
-
Check for any warnings or errors in the output of the health checks that Telemetry Pipeline ran on your behalf.
-
Confirm that you've met the networking and OS requirements for Telemetry Pipeline.
-
Confirm that you've met the K3s requirements necessary for Core Operator and Core Instances.
-
Run the following command to disable FIPS mode, and then reboot:
fips-mode-setup --disable
-
Run the following command to disable your firewall:
systemctl disable firewalld --now
-
Verify that SELinux is either disabled or in permissive (not enforcing) mode.
-
For Red Hat Enterprise Linux only, verify that your cryptographic policy is set to either
default
orlegacy
. -
For Red Hat Enterprise Linux only, run the following command to disable
nm-cloud-setup
, then reboot the node:systemctl disable nm-cloud-setup.service nm-cloud-setup.timer reboot
-
Examine the following K3s network ranges to ensure they aren't conflicting with your network settings:
- Pods are allocated in the CIDR range
10.42.0.0/16
. Use theINSTALL_CALYPTIA_CLUSTER_CIDR
environment variable to override. - Services are allocated in the CIDR range
10.43.0.0/16
. Use theINSTALL_CALYPTIA_SERVICE_CIDR
environment variable to override. - Cluster DNS is set to
10.43.0.10
. Use theINSTALL_CALYPTIA_CLUSTER_DNS
environment variable to override. - The cluster domain suffix is set to
cluster.local
. Use theINSTALL_CALYPTIA_CLUSTER_DOMAIN
environment variable to override. - Node ports are allocated in the range
30000
to32767
. Use theINSTALL_CALYPTIA_SERVICE_NODE_PORT_RANGE
environment variable to override during installation.
- Pods are allocated in the CIDR range
-
Examine your local
/etc/resolv.conf
configuration to ensure it isn't using a DNS server or specifying any override that might conflict with K3s.