Troubleshooting Inactive clients

A Taskomatic job periodically pings clients to ensure they are connected. Clients are considered inactive if they have not responded to a Taskomatic check in for 24 hours or more. To see a list of inactive clients in the Web UI, navigate to Systems  System List  Inactive.

Clients can become inactive for a number of reasons:

  • The client is not entitled to any Uyuni service.

  • The client is behind a firewall that does not allow HTTPS connections.

  • The client is behind a proxy that is misconfigured.

  • The client is communicating with a different Uyuni Server, or the connection has been misconfigured.

  • The client is not in a network that can communicate with the Uyuni Server.

  • A firewall is blocking traffic between the client and the Uyuni Server.

  • Taskomatic is misconfigured.

For more information about client connections to the server, see Client Contact Methods.

For more information about configuring ports, see Required Network Ports.

For more information about troubleshooting firewalls, see Troubleshooting Firewalls.