Bug 1771489
| Summary: | libvirt log is not created on a RHEL8.1 host | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Avihai <aefrat> | ||||
| Component: | libvirt | Assignee: | Michal Privoznik <mprivozn> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Yanqiu Zhang <yanqzhan> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 8.1 | CC: | bugs, chhu, dyuan, lmen, mprivozn, rbalakri, rbarry, xuzhang | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-01-23 16:30:54 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Avihai
2019-11-12 13:23:06 UTC
Michal, is this a known problem? (In reply to Ryan Barry from comment #1) > Michal, is this a known problem? Smells like bug 1718707. I'm switching over to libvirt for investigation. Avihai, can you please share libvirtd debug log? (In reply to Michal Privoznik from comment #2) > (In reply to Ryan Barry from comment #1) > > Michal, is this a known problem? > > Smells like bug 1718707. I'm switching over to libvirt for investigation. > Avihai, can you please share libvirtd debug log? This is all I can see on my hosts under /var/log/libvirt , no libvirtd debug log is seen : [root@storage-ge4-vdsm1 ~]# cd /var/log/libvirt/ [root@storage-ge4-vdsm1 libvirt]# ls -ltr total 12 drwx------. 2 root root 12288 Nov 24 03:12 qemu sorry for the dumb Q, as I do not have libvirt.log due to this bug where can I find libvirtd debug log? Looking at the service itself I see log output is incomplete or unavailable: [root@storage-ge4-vdsm1 libvirt]# systemctl status libvirtd ● libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/libvirtd.service.d └─unlimited-core.conf Active: active (running) since Tue 2019-11-12 14:56:15 IST; 1 weeks 5 days ago Docs: man:libvirtd(8) https://libvirt.org Main PID: 21161 (libvirtd) Tasks: 18 (limit: 32768) Memory: 31.6M CGroup: /system.slice/libvirtd.service └─21161 /usr/sbin/libvirtd --listen Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. (In reply to Avihai from comment #3) > (In reply to Michal Privoznik from comment #2) > > (In reply to Ryan Barry from comment #1) > > > Michal, is this a known problem? > > > > Smells like bug 1718707. I'm switching over to libvirt for investigation. > > Avihai, can you please share libvirtd debug log? > > This is all I can see on my hosts under /var/log/libvirt , no libvirtd debug > log is seen : > > [root@storage-ge4-vdsm1 ~]# cd /var/log/libvirt/ > [root@storage-ge4-vdsm1 libvirt]# ls -ltr > total 12 > drwx------. 2 root root 12288 Nov 24 03:12 qemu > > > sorry for the dumb Q, as I do not have libvirt.log due to this bug where can > I find libvirtd debug log? You need to set it up: https://wiki.libvirt.org/page/DebugLogs > > Looking at the service itself I see log output is incomplete or unavailable: > [root@storage-ge4-vdsm1 libvirt]# systemctl status libvirtd > ● libvirtd.service - Virtualization daemon > Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor > preset: enabled) > Drop-In: /etc/systemd/system/libvirtd.service.d > └─unlimited-core.conf > Active: active (running) since Tue 2019-11-12 14:56:15 IST; 1 weeks 5 > days ago > Docs: man:libvirtd(8) > https://libvirt.org > Main PID: 21161 (libvirtd) > Tasks: 18 (limit: 32768) > Memory: 31.6M > CGroup: /system.slice/libvirtd.service > └─21161 /usr/sbin/libvirtd --listen > > Warning: Journal has been rotated since unit was started. Log output is > incomplete or unavailable. D'oh! By default libvirt will not collect any debug logs, and errors/warnings will go to journal. Well, I'll try to fix the referenced bug and see if it fixes this one too. So the referenced bug is fixed now. However, this looks like a misconfiguration bug to me. By default, debug logs are not collected hence there are no files under /var/log/libvirt/ and all errors/warnings are logged through journald. Avihai, can you confirm that when you enable debug logs (see comment 4) then the log file is actually created? (In reply to Michal Privoznik from comment #5) > So the referenced bug is fixed now. However, this looks like a > misconfiguration bug to me. By default, debug logs are not collected hence > there are no files under /var/log/libvirt/ and all errors/warnings are > logged through journald. Avihai, can you confirm that when you enable debug > logs (see comment 4) then the log file is actually created? Indeed the workaround to make libvirt log to appear in /var/log/libvirt/ was to enable debug logs. Feel free to close this bug as NOTABUG if it's misconfiguration . However I wonder why libvirt log is different from other logs that do appear without any needed additional configurations(at lease in info level or a short log to save only errors), maybe RFE is needed here? (In reply to Avihai from comment #6) > (In reply to Michal Privoznik from comment #5) > > So the referenced bug is fixed now. However, this looks like a > > misconfiguration bug to me. By default, debug logs are not collected hence > > there are no files under /var/log/libvirt/ and all errors/warnings are > > logged through journald. Avihai, can you confirm that when you enable debug > > logs (see comment 4) then the log file is actually created? > > Indeed the workaround to make libvirt log to appear in /var/log/libvirt/ was > to enable debug logs. > Feel free to close this bug as NOTABUG if it's misconfiguration . > > However I wonder why libvirt log is different from other logs that do appear > without any needed additional configurations(at lease in info level or a > short log to save only errors), maybe RFE is needed here? Errors will appear in journal and so will warnings. But by default, debug logs are discarded because libvirt produces a lot of them. |