Product SiteDocumentation Site

Chapter 10. Troubleshooting

10.1. Troubleshooting the Secondary Storage VM
10.1.1. Running the diagnostic script
10.1.2. Checking the log file
10.2. Troubleshooting the Console-proxy VM
Many install problems relate to the secondary storage VM. The most commmon problems include:
  • SSVM cannot reach the DNS server
  • SSVM cannot reach the Management Server
  • SSVM cannot reach the outside world to download templates. It contacts download.cloud.com via HTTP.
  • The configured DNS server cannot resolve your internal hostnames.
    E.g., you entered private-nfs.lab.example.org for secondary storage NFS, but gave a DNS server that your customers use, and that server cannot resolve private-nfs.lab.example.org.
A quick step to look for errors in the management server log is this:
# grep -i -E 'exc|unable|fail|invalid|leak|invalid|warn' /var/log/cloud/management/management-server.log

10.1. Troubleshooting the Secondary Storage VM

You can troubleshoot the secondary storage VM either by running a diagnostic script or by checking the log file. The following sections detail each of these methods.
If you have corrected the problem but the template hasn’t started to download, restart the cloud service with “service cloud restart”. This will restart the default CentOS template download.

Important

To recover a failed SSVM after making changes that fix the root cause of the failure, you must stop the VM first and then start it. A restart merely reboots the VM without resending the configuration, which may have changed

10.1.1. Running the diagnostic script

You can log into the SSVM. To do this you have to find the Host running the SSVM, ssh into it, then ssh into the SSVM’s private IP from that host. Once you are logged in, use the following steps to run a diagnostic script.
  1. In the admin UI, go to Instances tab, System section.
  2. Note the name of the Host hosting the SSVM as shown in the Host column. Also note the private IP of the SSVM as shown in the Private IP column.
  3. ssh into the Host using your known user and password.
  4. ssh into the private IP of the SSVM with the following.
    # ssh -i /root/.ssh/id_rsa.cloud -p 3922 root@private-ip
  5. Once into the SSVM, run the following diagnostic script:
    # /usr/local/cloud/systemvm/ssvm-check.sh
This script will test various aspects of the SSVM and report warnings and errors.

10.1.2. Checking the log file

You can also check the log file /var/log/cloud/cloud.log for any error messages