Troubleshooting And Log Files

Troubleshooting Compute Service Problems

If your Private Cloud Director Service Health dashboard indicates that the Compute Service is unhealthy, it may be because a large percentage of your hosts with the Hypervisor role assigned are either offline or the Compute service is unresponsive on those hosts. Refer to the Log Filesto debug the issue further.

Important Directories

/var – All logs go under /var/log/pf9. The only exception is the pcdctl log files which go under /var/log

/opt – All the packages for services installed by Private Cloud Director go under /opt/pf9

/var/opt/pf9 - Subdirectories for the Platform9 host agent and networking service go under here with temp files or state files.

Log Files

Essential log files for debugging:

1. Log files for all services - Each host stores all its log files for the various components running on it at /var/log/pf9. Here you will find logs for compute, image library, storage, networking, and other services, depending on the roles assigned to that host. See the documentation for each service for more information about its log files.

2. Compute service log - The log file for the compute service is located /var/log/pf9/ostackhost.log on all hosts with the hypervisor role assigned. Useful for debugging issues with virtual machine creation or updates.

3. Host agent log - The log file for the Platform9 host agent that is installed on each host is located at /var/log/pf9/hostagent.log. This is helpful for debugging issues with host agent install or connectivity with the management plane.

4. Communication agent log - Located at /var/log/pf9/comms/comms.log. Log file for the Platform9 communications agent, which is responsible for ensuring the health and uptime of the host agent. Helpful for debugging issues regarding connectivity.

5. Libvirt logs - Located at /var/log/libvirt/qemu/<vm-id> where <vm-id>should be the UUID of the VM, and at /var/log/libvirt/libvirtd.log. Libvirt logs help with debugging any resource allocation or other issues with virtual machine instances.

Troubleshooting Steps

1. Verify that the host has outbound network connectivity to the internet and the management plane controller:

   • $ curl -s https://<FQDN>

   • $ ping www.google.com

   • $ telnetwww.google.com443

2. If your environment has a proxy server, make sure that you have configured the Platform9 host agent installed on the host to route traffic via the proxy:

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

3. Verify that the hostname on the host matches the hostname shown in the GUI.

4. The UUID given in the host_id file should match the host UUID shown on the GUI. $ sudo cat /etc/pf9/host_id.conf

5. If NTP is enabled, make sure the NTP servers are configured correctly across all the nodes within the configuration file /etc/systemd/timesyncd.conf.d/conf.d

6. Check that the Platform9 packages are installed on the host and the version which is shown on the GUI. $ sudo apt list | grep -i pf9*

7. Confirm that the host agent is running on your host:

   • $ sudo service pf9-hostagent status

   • $ sudo service pf9-ostackhost status

   • $ sudo service pf9-comms status

   • $ sudo service pf9-sidekick status

8. Check the below service logs for any “errors/timeouts/warnings”, during the time of issue. verify if any recent network changes might have impacted the 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. If these steps prove insufficient to resolve the issue, kindly reach out to the Platform9 Support team for additional assistance.

Most Common causes

• Connectivity to the 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 that you are trying to add meets the ​pre-requisites.

HOST ISSUES - Previous