4.2. Log Files
4.2.1. Manager Installation Log Files
| Log File | Description |
|---|---|
| /var/log/ovirt-engine/engine-cleanup_yyyy_mm_dd_hh_mm_ss.log |
Log from the |
| /var/log/ovirt-engine/engine-db-install-yyyy_mm_dd_hh_mm_ss.log |
Log from the |
| /var/log/ovirt-engine/ovirt-engine-dwh-setup-yyyy_mm_dd_hh_mm_ss.log |
Log from the |
| /var/log/ovirt-engine/setup/ovirt-engine-setup-yyyymmddhhmmss.log |
Log from the |
4.2.2. Red Hat Virtualization Manager Log Files
| Log File | Description |
|---|---|
| /var/log/ovirt-engine/engine.log | Reflects all Red Hat Virtualization Manager GUI crashes, Active Directory lookups, Database issues, and other events. |
| /var/log/ovirt-engine/host-deploy | Log files from hosts deployed from the Red Hat Virtualization Manager. |
| /var/lib/ovirt-engine/setup-history.txt | Tracks the installation and upgrade of packages associated with the Red Hat Virtualization Manager. |
| /var/log/httpd/ovirt-requests-log | Logs files from requests made to the Red Hat Virtualization Manager via HTTPS, including how long each request took.
A |
| /var/log/ovn-provider/ovirt-provider-ovn.log | Logs the activities of the OVN provider. For information about Open vSwitch logs, see the Open vSwitch documentation. |
4.2.3. SPICE Log Files
SPICE log files are useful when troubleshooting SPICE connection issues. To start SPICE debugging, change the log level to debugging. Then, identify the log location.
Both the clients used to access the guest machines and the guest machines themselves have SPICE log files. For client-side logs, if a SPICE client was launched using the native client, for which a console.vv file is downloaded, use the remote-viewer command to enable debugging and generate log output.
4.2.3.1. SPICE Logs for Hypervisor SPICE Servers
| Log Type | Log Location | To Change Log Level: |
|---|---|---|
| Host/Hypervisor SPICE Server | /var/log/libvirt/qemu/(guest_name).log |
Run |
4.2.3.2. SPICE Logs for Guest Machines
| Log Type | Log Location | To Change Log Level: |
|---|---|---|
| Windows Guest | C:\Windows\Temp\vdagent.log C:\Windows\Temp\vdservice.log | Not applicable |
| Red Hat Enterprise Linux Guest |
Use |
To run the
To run $ killall - u $USER spice-vdagent $ spice-vdagent -x -d [-d] [ |& tee spice-vdagent.log ] |
4.2.3.3. SPICE Logs for SPICE Clients Launched Using console.vv Files
For Linux client machines:
Enable SPICE debugging by running the
remote-viewercommand with the--spice-debugoption. When prompted, enter the connection URL, for example, spice://virtual_machine_IP:port.# remote-viewer --spice-debug
To run SPICE client with the debug parameter and to pass a .vv file to it, download the console.vv file and run the
remote-viewercommand with the--spice-debugoption and specify the full path to the console.vv file.# remote-viewer --spice-debug /path/to/console.vv
For Windows client machines:
-
In versions of
virt-viewer2.0-11.el7ev and later, virt-viewer.msi installsvirt-vieweranddebug-viewer.exe. Run the
remote-viewercommand with thespice-debugargument and direct the command at the path to the console:remote-viewer --spice-debug path\to\console.vv-
To view logs, connect to the virtual machine, and you will see a command prompt running GDB that prints standard output and standard error of
remote-viewer.
4.2.4. Host Log Files
| Log File | Description |
|---|---|
| /var/log/messages |
The log file used by |
| /var/log/vdsm/spm-lock.log | Log file detailing the host’s ability to obtain a lease on the Storage Pool Manager role. The log details when the host has acquired, released, renewed, or failed to renew the lease. |
| /var/log/vdsm/vdsm.log | Log file for VDSM, the Manager’s agent on the host(s). |
| /tmp/ovirt-host-deploy-Date.log |
A host deployment log that is copied to the Manager as |
| /var/log/vdsm/import/import-UUID-Date.log | Log file detailing virtual machine imports from a KVM host, a VMWare provider, or a RHEL 5 Xen host, including import failure information. UUID is the UUID of the virtual machine that was imported and Date is the date and time that the import began. |
| /var/log/vdsm/supervdsm.log | Logs VDSM tasks that were executed with superuser permissions. |
| /var/log/vdsm/upgrade.log | VDSM uses this log file during host upgrades to log configuration changes. |
| /var/log/vdsm/mom.log | Logs the activities of the VDSM’s memory overcommitment manager. |
4.2.5. Setting debug-level logging for Red Hat Virtualization services
Setting logging to debug-level may expose sensitive information such as passwords or internal VM data. Make sure that non-trusted or unauthorized users do not have access to debug logs.
You can set the logs of the following Red Hat Virtualization (RHV) services to debug-level by modifying the sysconfig file of each service.
| Service | File path |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
This modification affects logging done by the Python wrapper, not the main service process.
Setting logging to debug-level is useful for debugging issues related to start up - for example, if the main process fails to start due to a missing or incorrect Java runtime or library.
Prerequisites
-
Verify that the
sysconfigfile you want to modify exists. If necessary, create it.
Procedure
Add the following to the
sysconfigfile of the service:OVIRT_SERVICE_DEBUG=1
Restart the service:
# systemctl restart <service>
The sysconfig log file of the service is now set to debug-level.
Logging caused by this setting goes to the system log, so the logs it generates can be found in /var/log/messages, not in the service-specific log file, or by using the journalctl command.
4.2.6. Main configuration files for Red Hat Virtualization services
In addition to a sysconfig file, each of these Red Hat Virtualization (RHV) services has another configuration file that is used more often.
| Service | sysconfig file path | Main configuration file |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4.2.7. Setting Up a Host Logging Server
Hosts generate and update log files, recording their actions and problems. Collecting these log files centrally simplifies debugging.
This procedure should be used on your centralized log server. You could use a separate logging server, or use this procedure to enable host logging on the Red Hat Virtualization Manager.
Procedure
Check to see if the firewall allows traffic on the
UDP 514port, and is open tosyslogservice traffic:# firewall-cmd --query-service=syslog
If the output is
no, allow traffic on theUDP 514port with:# firewall-cmd --add-service=syslog --permanent # firewall-cmd --reload
Create a new
.conffile on the syslog server, for example,/etc/rsyslog.d/from_remote.conf, and add the following lines:template(name="DynFile" type="string" string="/var/log/%HOSTNAME%/%PROGRAMNAME%.log") RuleSet(name="RemoteMachine"){ action(type="omfile" dynaFile="DynFile") } Module(load="imudp") Input(type="imudp" port="514" ruleset="RemoteMachine")Restart the
rsyslogservice:# systemctl restart rsyslog.service
Log in to the hypervisor, and in the
/etc/rsyslog.confadd the following line:*.info;mail.none;authpriv.none;cron.none @<syslog-FQDN>:514
Restart the rsyslog service on the hypervisor.
# systemctl restart rsyslog.service
Your centralized log server is now configured to receive and store the messages and secure logs from your virtualization hosts.
4.2.8. Enabling SyslogHandler to pass RHV Manager logs to a remote syslog server
This implementation uses the JBoss EAP SyslogHandler log manager and enables passing log records from the engine.log and server.log to a syslog server.
RHV versions earlier than RHV 4.4.10 featured similar functionality provided by ovirt-engine-extension-logger-log4j. That package was removed in RHV 4.4.10 and replaced by a new implementation using the JBoss EAP SyslogHandler log manager. If you have been using ovirt-engine-extension-logger-log4j in earlier RHV versions, following an upgrade to RHV 4.4.10, perform following steps:
- Manually configure sending log records to a remote syslog server using the guidelines provided in this chapter.
-
Manually remove the
ovirt-engine-extension-logger-log4jconfiguration files (remove the/etc/ovirt-engine/extensions.d/Log4jLogger.propertiesconfiguration file).
Use this procedure on the central syslog server. You can use a separate logging server, or use this procedure to pass the engine.log and server.log files from the Manager to the syslog server. See also the configuration procedure Setting up a Host Logging Server.
Configuring the SyslogHandler implementation
Create the configuration file
90-syslog.confin the/etc/ovirt-engine/engine.conf.ddirectory and add the following content:SYSLOG_HANDLER_ENABLED=true SYSLOG_HANDLER_SERVER_HOSTNAME=localhost SYSLOG_HANDLER_FACILITY=USER_LEVEL
Install and configure
rsyslog.# dnf install rsyslog
Configure SELinux to allow
rsyslogtraffic.# semanage port -a -t syslogd_port_t -p udp 514
Create the configuration file
/etc/rsyslog.d/rhvm.confand add the following content:user.* /var/log/jboss.log module(load="imudp") # needs to be done just once input(type="imudp" port="514")
Restart the rsyslog service.
# systemctl restart rsyslog.service
If the firewall is enabled and active, run the following command to add the necessary rules for opening the
rsyslogports inFirewalld:# firewall-cmd --permanent --add-port=514/udp # firewall-cmd --reload
Restart Red Hat Virtualization Manager.
# systemctl restart ovirt-engine
The syslog server can now receive and store the engine.log files.
