Skip to main content

Jama Connect User Guide

Connection errors (KOTS)

The KOTS installation process includes using the kubectl command line tool. If you see an error message that relates to kubectl, use the workaround tips for the issue.

Error message

Reason

Workaround

The connection to the server localhost:8080 was refused - did you specify the right host or port? error: error loading config file "/etc/kubernetes/admin.conf": open /etc/kubernetes/admin.conf: permission denied

kubectl might not be configured properly for the user and/or node where you tried to use it.

  • Wrong user — Switch to the user that installed KOTS or to root (sudo su -), then rerun the kubectl command.

  • Wrong node — Switch to the server where KOTS was installed initially or to a primary node, then rerun the kubectl command.

kubectl can be configured for other users and nodes but it requires some research. See Embedded Cluster: How to get kubectl working for other users.

Waited for 1.184446141s due to client-side throttling, not priority and fairness

When using kubectl with Ubuntu 18.04, you might see this warning message.

Log in to Jama Connect as the root user (sudo su -).

Application status is not accurate

This error usually occurs when the cluster is restarted or if a cluster was restored from a snapshot. The Application status in the KOTS Admin Console might differ from what you see in the UI when using kubectl.

Redeploy the latest license version from the Version history tab in the KOTS Admin Console.

In this section: