Troubleshooting Offline Or Failed Hosts

When you see a hypervisor host in a Private Cloud Director environment that's offline, failed, or in an error state, here's how to debug the issue:

Most common causes

• Connectivity to the Private Cloud Director management plane controller is broken or unreachable.

• Dependent services are down.

• Packages are corrupted or not installed.

• NTP is not synchronized.

• Insufficient disk space available.

• Ensure that the host you are trying to add meets the pre-requisites.

Steps To Troubleshoot

1

Verify outbound network connectivity

Ensure the host can reach the internet and the Private Cloud Director management plane controller:

$ curl -s https://<FQDN>
$ ping www.google.com
$ telnet www.google.com 443

2

Proxy configuration (if applicable)

If your environment uses a proxy, configure the Platform9 host agent on the host to route traffic via the proxy:

$ sudo bash <path to host agent installer> --proxy=<proxy server>:<proxy port>

3

Verify hostname consistency

Make sure the hostname on the host matches the hostname shown in the GUI.

4

Verify host UUID

Confirm the UUID in the host_id file matches the host UUID shown in the GUI:

$ sudo cat /etc/pf9/host_id.conf

5

Verify NTP configuration

If NTP is enabled, ensure NTP servers are configured correctly across nodes, then verify whether the host's time is in sync. The time synchronization service differs by host operating system: systemd-timesyncd on Ubuntu, chronyd on Platform9 OS.

Ubuntu

$ sudo cat /etc/systemd/timesyncd.conf.d/*.conf
$ sudo timedatectl status

Platform9 OS

$ sudo cat /etc/chrony.conf
$ chronyc sources
$ sudo timedatectl status

6

Verify Platform9 packages

Check that Platform9 packages are installed and match the version shown in the Private Cloud Director GUI:

Ubuntu

$ sudo apt list | grep -i pf9*

Platform9 OS

$ sudo rpm -qa | grep -i pf9

7

Confirm host agent services are running

Check the status of the Platform9 services:

$ sudo systemctl status pf9-hostagent
$ sudo systemctl status pf9-ostackhost
$ sudo systemctl status pf9-comms
$ sudo systemctl status pf9-sidekick

8

Inspect service logs

Check logs for errors, timeouts, or warnings around the time of the issue and verify whether recent network changes could have impacted connectivity:

$ sudo cat /var/log/pf9/hostagent.log
$ sudo cat /var/log/pf9/ostackhost.log
$ sudo cat /var/log/pf9/comms/comms.log
$ sudo cat /var/log/pf9/sidekick/sidekick.log

9

Contact Platform9 Support

If these steps don't resolve the issue, reach out to the Platform9 Support team for additional assistance.