Chapter 4. Troubleshooting a Self-Hosted Engine Deployment

Procedure 4.1. Troubleshooting the Manager Virtual Machine

1. Check the status of the Manager virtual machine by running hosted-engine --vm-status.

   Note

   Any changes made to the Manager virtual machine will take about 20 seconds before they are reflected in the status command output.

   If the Manager virtual machine is up and running as normal, you will see the following output:

   --== Host 1 status ==--
   
   Status up-to-date              : True
   Hostname                       : hypervisor.example.com
   Host ID                        : 1
   Engine status                  : {"health": "good", "vm": "up", "detail": "up"}
   Score                          : 3400
   stopped                        : False
   Local maintenance              : False
   crc32                          : 99e57eba
   Host timestamp                 : 248542

   Copy to Clipboard Toggle word wrap
2. If the health is bad or the vm is down, enable the global maintenance mode so that the hosts are no longer managed by the HA services.
   • In the Administration Portal, right-click the engine virtual machine, and select Enable Global HA Maintenance.
   • You can also set the maintenance mode from the command line:

     # hosted-engine --set-maintenance --mode=global

     Copy to Clipboard Toggle word wrap
3. If the Manager virtual machine is down, start the Manager virtual machine. If the virtual machine is up, skip this step.

   # hosted-engine ---vm-start

   Copy to Clipboard Toggle word wrap
4. Set the console password:

   # hosted-engine --add-console-password

   Copy to Clipboard Toggle word wrap
5. Connect to the console. When prompted, enter the password set in the previous step. For more console options, see https://access.redhat.com/solutions/2221461.

   # hosted-engine --console

   Copy to Clipboard Toggle word wrap
6. Determine why the Manager virtual machine is down or in a bad health state. Check /var/log/messages and /var/log/ovirt-engine/engine.log. After fixing the issue, reboot the Manager virtual machine.
7. Log in to the Manager virtual machine as root and verfiy that the ovirt-engine service is up and running:

   # service ovirt-engine status

   Copy to Clipboard Toggle word wrap
8. After ensuring the Manager virtual machine is up and running, close the console session and disable the maintenance mode to enable the HA services again:

   # hosted-engine --set-maintenance --mode=none

   Copy to Clipboard Toggle word wrap