Hide Forgot
from https://bugzilla.redhat.com/show_bug.cgi?id=1317513 : * Verify that the log file locations in '17.4. Red Hat Enterprise > Virtualization Host Log Files' are correct. No such log files when tested > against vdsm-4.17.14-0.el7ev.noarch. Summary: The following table is, as of 18 Oct 2016, incorrect: 19.4. Red Hat Virtualization Host Log Files Table 19.5. Log File Description /var/log/vdsm/libvirt.log Log file for libvirt. /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 virtualization host(s). /tmp/ovirt-host-deploy-@DATE@.log Host deployment log, copied to engine as /var/log/ovirt-engine/host-deploy/ovirt-@DATE@-@HOST@-@CORRELATION_ID@.log after the host has been successfully deployed. This table should be removed from the Admin Guide, and it should be replaced with a table that has the correct log locations in it.
Can you provide the correct log locations?
- /var/log/vdsm/libvirt.log Log file for libvirt. Not correct - we use default libvirt configuration which direct the log to syslog - /var/log/vdsm/spm-lock.log - /var/log/vdsm/vdsm.log Those are the same. But there is also /var/log/vdsm/supervdsm.log\Mom.log\connectivity.log\upgrade.log that we might need to document as well. - /tmp/ovirt-host-deploy-@DATE@.log Host deployment log, copied to engine as /var/log/ovirt-engine/host-deploy/ovirt-@DATE@-@HOST@-@CORRELATION_ID@.log after the host has been successfully deployed. Also correct.
Moving back to NEW to be reassigned as resources allow.
Hi Dan Can you please verify and where necessary update the log files detailed in this section. https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/administration_guide/#Setting_up_a_Host_Logging_Server Thanks!
Moving version over to 4.2, and untargeting pending answer to comment 4.
Miguel, can you verify the doc's content?
Regarding host logging - e.g. [1]: As Yaniv already mentioned in [2], the following logs are missing from the docs: - supervdsm.log -> /var/log/vdsm/supervdsm.log - mom.log -> /var/log/vdsm/mom.log - upgrade.log -> /var/log/upgrade.log Furthermore, the ovn-controller logs (host logs) are also relevant. Those are located at: - /var/log/openvswitch/ovn-controller.log Regarding manager logging - e.g. [3]: The ovirt-provider-ovn logs should also be referenced. Those are located at: - /var/log/ovn-provider/ovirt-provider-ovn.log Also, the ovn-north logs could also be of interest: - /var/log/openvswitch/ovn-northd.log [1] - https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/administration_guide/#Host_Log_Files [2] - https://bugzilla.redhat.com/show_bug.cgi?id=1386096#c2 [3] - https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/administration_guide/#Manager_Log_Files
(In reply to Miguel Duarte Barroso from comment #7) > Regarding host logging - e.g. [1]: > > As Yaniv already mentioned in [2], the following logs are missing > from the docs: > - supervdsm.log -> /var/log/vdsm/supervdsm.log > - mom.log -> /var/log/vdsm/mom.log > - upgrade.log -> /var/log/upgrade.log > > Furthermore, the ovn-controller logs (host logs) are also relevant. > Those are located at: > - /var/log/openvswitch/ovn-controller.log > > Regarding manager logging - e.g. [3]: > > The ovirt-provider-ovn logs should also be referenced. Those are located at: > - /var/log/ovn-provider/ovirt-provider-ovn.log > > Also, the ovn-north logs could also be of interest: > - /var/log/openvswitch/ovn-northd.log > > > [1] - > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ > html-single/administration_guide/#Host_Log_Files > [2] - https://bugzilla.redhat.com/show_bug.cgi?id=1386096#c2 > [3] - > https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/ > html-single/administration_guide/#Manager_Log_Files Thanks Miguel, currently the docs don't mention anything about syslog, except for setting up a central logging server. Where are the host's syslog files located?
I've made a mistake in comment #7: The correct path for 'upgrade.log' is in /var/log/vdsm/upgrade.log Regarding Emma's question on comment #8: The default location for the hosts's syslog is /var/log/messages, but I think the recommended way of interacting with syslog is through the journal - journalctl
(In reply to Miguel Duarte Barroso from comment #9) > I've made a mistake in comment #7: > The correct path for 'upgrade.log' is in /var/log/vdsm/upgrade.log > > Regarding Emma's question on comment #8: > The default location for the hosts's syslog is /var/log/messages, but I > think the recommended way of interacting with syslog is through the journal > - journalctl Thanks Miguel. Should journalctl always be run as root user?
Miguel. Could you provide a short description for: - supervdsm.log - mom.log - upgrade.log
comment#10 : - Every user gets access to its 'portion' of the journal. To get access to the system-wide journal, the user will need to feature in *any* of the following groups: - adm - systemd-journal - wheel comment#11 : - supervdsm: log file for supervdsm (e.g. executes vdsm tasks that require superuser permissions) - mom: log file for vdsm's memory overcommitment manager. - upgrade: log file for one time scripted executions before startup of the vdsm services @Dan, I can't be 100% of my description of the upgrade log file; can you confirm / improve the description ?
In some cases, when vdsm is upgraded it can find that the state of the host is not up-to-date to its existing assumption. the state of the host (mostly content of /var/lib/vdsm) is upgraded, and the upgrade log is used.
(In reply to Dan Kenigsberg from comment #13) > In some cases, when vdsm is upgraded it can find that the state of the host > is not up-to-date to its existing assumption. the state of the host (mostly > content of /var/lib/vdsm) is upgraded, and the upgrade log is used. Is this what you mean? During host upgrades, if the contents of _/var/lib/vdsm_ are out-of-date, the pre-upgrade state will be logged in 'upgrade.log'.
Hey Miguel. Could you please add a couple of sentences about what each of these files contain? /var/log/ovn-provider/ovirt-provider-ovn.log /var/log/openvswitch/ovn-northd.log
(In reply to Emma Heftman from comment #15) > Hey Miguel. Could you please add a couple of sentences about what each of > these files contain? > /var/log/ovn-provider/ovirt-provider-ovn.log > > /var/log/openvswitch/ovn-northd.log I went ahead and wrote some discriptions. Can you pls review the changes to the manager's logs topic - 2 new log files at the end: http://file.tlv.redhat.com/~eheftman/bz1386096/html-single/#Manager_Log_Files and the hosts topic: http://file.tlv.redhat.com/~eheftman/bz1386096/html-single/#Host_Log_Files
Looks good to me, but I can't help but wonder if the reader won't get confused by the ovn-northd (in manager) and ovn-controller logs - not sure if they were mentioned anywhere throughout the docs. @marcin: what's your opinion on this? should the ovn-northd / ovn-controller logs appear in the RHV documentation?
No I would redirect to ovs/ovn docs. > /var/log/ovn-provider/ovirt-provider-ovn.log This is the ovirt-provider-ovn log. This should be included in our docs > /var/log/openvswitch/ovn-northd.log This and others in "/var/log/openvswitch" are NOT ours, they belong to openvswtich. We use it, but I don't think we should describe it, just like we don't describe other dependencies. Maybe instead of describing them we could add something like: "Information related to ovn/ovn can be found in their relevant logs. Please refer to the openvswitch documentation (www.openvswitch.org) for more information"
The updated information is available in the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/administration_guide/index#Host_Log_Files