Troubleshooting cheatsheet

Check	Action

Check	Action
Always try precheck first	`curl -sfL https://assets.master.k3s.getvisibility.com/k3s/k3s.sh \| PRODUCT_NAME=enterprise ONLY_PRECHECK=true bash -` Make sure a valid label is used: `synergy, focus, dspm, enterprise, ultimate`
What Linux version	`cat /etc/os-release`
Storage details Make sure no noexec flag on /var Always disable swap!	`df -h df -h /var df /var/lib/rancher -h`
Check memory Check CPUs
Ubuntu, disable: RHEL/CentOS/Suse, disable: Restart k3s
Check name resolution Make sure no more than 2 nameservers used - coredns has issues with it verify ssl bypass	verify entries with nslookup or dig, example:
Proxy settings Check if proxy added in `$PROXY_IP` is your IP for proxy, so replace in the commands to the right. Remember to add `.svc` and `.cluster.local`	Should contain: If doesn’t, add and:
Check if proxy added in Rancher
Dashboard proxy - this is for connectors. Some connectors require SSL bypass on proxy.
Uninstall k3s
Get cluster name
Check product
Grab logs
Get logs from failing pod (here: connector)
Check if user has proper rights if SMB fails In second terminal window If smbclient not available
Watch deployments

GV-KnowledgeBase