RHV 4.3.4 Collectd failed to send metrics data. While running 'systemctl status collectd' Getting output: collectd[38874]: write_syslog plugin: wr_callback_init failed. collectd[38874]: write_syslog plugin: error with wr_send_message Once the file '/etc/collectd.d/libvirt.conf' removed, the error messages gone.
Can you please attach sos report from the host where you see the failure?
Shirly, does this reproduce on our systems?
Also, please provide output of: rpm -qa | grep collectd rpm -qfi /etc/collectd.d/libvirt.conf What repos did you use for installation? Thanks.
Re-targeting to 4.3.6 not being identified as blocker for 4.3.5.
Shirly, does this happen _always_ and is a real problem? If it does not happen always but is a real problem, I suggest to try to find the root cause and fix that one. If it happens always and is a real problem, I suggest to try to add our own file before or after libvirt.conf so as to override it, not change/remove it. In "always" I mean e.g. something like this: Perhaps our custom configuration for libvirt (e.g. to make it require a password) causes this plugin (which expects to work without a password) fail. If this is the case, I wonder how come we do not get more reports. Did you manage to reproduce? If so, can I have a look there? Thanks.
It always happens when the file exists.
Hi, what should be tested here? Thanks
That collectd does not fail.
sync2jira
Steps: 1) Have clean engine and host with RHEL 7.7 and RHV 4.3.6 and working metrics store 2) Configure metrics according to the documentation 3) Check that collectd did not fail and data are successfully gathered in Kibana Result: Collectd did not fail, successfully connected to the engine database and data are successfully gathered in Kibana Verified in: collectd-5.8.1-3.el7ost.x86_64 ovirt-engine-metrics-1.3.4-1.el7ev.noarch ovirt-engine-4.3.6.3-0.1.el7.noarch
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/RHBA-2019:3018