Red Hat Bugzilla – Bug 1562591
Conf file is missing/incomplete for collectd libvirt plugin
Last modified: 2018-06-27 09:09:31 EDT
Description of problem: libvirt plugin fails to load because data is missing in the plugin conf file [2018-04-01 08:02:52] virt plugin: Unable to connect: virConnectOpen failed. [2018-04-01 08:02:52] Initialization of plugin `virt' failed with status -1. Plugin will be unloaded. [2018-04-01 08:02:52] plugin_unregister_read: No such read function: virt libvirt.conf plugin looks like this: -------- ()[root@controller-0 collectd.d]# cat libvirt.conf LoadPlugin libvirt --------- We should either to provide complete libvirt.conf file or to remove it at tall and let user to create it. Now,we do provide conf file but it misses required data which is wrong.
Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Re opening this bug. qa_ack was set to minus by mistake.
In general, the config would be overwritten by puppet-collectd, thus one can provide the connection string via config.yaml. I'll propose a patch upstream in a few mins.
merged upstream
Our oVirt metrics conf file is like this: LoadPlugin virt <Plugin virt> ExtraStats "disk disk_err pcpu vcpupin cpu_util domain_state" HostnameFormat hostname PluginInstanceFormat name </Plugin> We get the same error... Is there something missing?
This bug is about a missing config file for the virt plugin. Ok, the config only contains LoadPlugin virt, and nothing more. This causes the plugin to be unloaded. Shirly, I believe you need to specify the connection URL, which seems to be missing in your snippet. If you receive another error message, please open a new bug rather than posting to another one. Opening a new bug will help us to guarantee that both issues are fixed. Thank you.
conf file updated. LoadPlugin libvirt <Plugin "virt"> Connection "qemu:///system" HostnameFormat "hostname uuid" ExtraStats "disk disk_err domain_state pcpu perf vcpupin cpu_util" </Plugin>
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:2084