Running ovirt 3.6.7 centos 7 ovirt hosted agent and broker logs in a HE setup are being output to both /var/log/messages as well as their own agent and broker log in ovirt-hosted-engine-ha messages Sep 15 12:29:25 ccovirt2 ovirt-ha-broker: INFO:ovirt_hosted_engine_ha.broker.listener.ConnectionHandler:Connection closed Sep 15 12:29:25 ccovirt2 ovirt-ha-broker: INFO:ovirt_hosted_engine_ha.broker.listener.ConnectionHandler:Connection established Sep 15 12:29:25 ccovirt2 ovirt-ha-broker: INFO:ovirt_hosted_engine_ha.broker.listener.ConnectionHandler:Connection closed Sep 15 12:29:26 ccovirt2 ovirt-ha-agent: INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:Initializing VDSM Sep 15 12:29:26 ccovirt2 ovirt-ha-agent: INFO:ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine:Connecting the storage rpm -qa|grep ovirt ovirt-host-deploy-1.4.1-1.el7.centos.noarch ovirt-setup-lib-1.0.1-1.el7.centos.noarch ovirt-hosted-engine-setup-1.3.7.2-1.el7.centos.noarch ovirt-hosted-engine-ha-1.3.5.7-1.el7.centos.noarch ovirt-engine-sdk-python-3.6.7.0-1.el7.centos.noarch ovirt-release36-3.6.7-1.noarch libgovirt-0.3.3-1.el7_2.4.x86_64 ovirt-vmconsole-1.0.2-1.el7.centos.noarch ovirt-vmconsole-host-1.0.2-1.el7.centos.noarch expected result is that those logs should only output to their respective log files
Oved, do we have a common logging project? Are we going to use syslog/journal or something else? We want to avoid storing duplicate data and we would like to allow the user to configure logging centrally for the whole machine (for log forwarding purposes for example).
I think it is a bit premature to discuss that, and wait for its outcome. Yaniv - your thoughts?
I would consider that a long overdue. We can easily enable standard systemd based logging for hosted engine right now (the same for mom btw), we just want to use the same way everybody else uses. And since we had to fix logging anyway, we wanted to know about any ongoing projects..
(In reply to Martin Sivák from comment #3) > I would consider that a long overdue. We can easily enable standard systemd > based logging for hosted engine right now (the same for mom btw), we just > want to use the same way everybody else uses. > > And since we had to fix logging anyway, we wanted to know about any ongoing > projects.. Use your own logs for the time being.
works for me on these components on engine: rhev-release-4.0.5-7-001.noarch rhevm-spice-client-x64-msi-4.0-3.el7ev.noarch rhevm-branding-rhev-4.0.0-5.el7ev.noarch rhev-release-4.0.6-3-001.noarch rhevm-doc-4.0.6-1.el7ev.noarch rhevm-dependencies-4.0.0-1.el7ev.noarch rhevm-spice-client-x86-msi-4.0-3.el7ev.noarch rhevm-guest-agent-common-1.0.12-3.el7ev.noarch rhevm-setup-plugins-4.0.0.3-1.el7ev.noarch rhev-guest-tools-iso-4.0-6.el7ev.noarch rhev-hypervisor7-7.2-20160209.2.bz1288237.el6ev.noarch rhevm-.0.6.1-0.1.el7ev.noarch Linux version 3.10.0-514.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Wed Oct 19 11:24:13 EDT 2016 Linux 3.10.0-514.el7.x86_64 #1 SMP Wed Oct 19 11:24:13 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.3 (Maipo) On hosts: ovirt-hosted-engine-ha-2.0.5-1.el7ev.noarch ovirt-setup-lib-1.0.2-1.el7ev.noarch ovirt-vmconsole-host-1.0.4-1.el7ev.noarch rhev-release-4.0.5-7-001.noarch ovirt-hosted-engine-setup-2.0.4-2.el7ev.noarch sanlock-3.4.0-1.el7.x86_64 ovirt-imageio-common-0.3.0-0.el7ev.noarch ovirt-host-deploy-1.5.3-1.el7ev.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7ev.noarch ovirt-imageio-daemon-0.4.0-0.el7ev.noarch ovirt-vmconsole-1.0.4-1.el7ev.noarch mom-0.5.8-1.el7ev.noarch libvirt-client-2.0.0-10.el7.x86_64 rhev-release-4.0.6-3-001.noarch vdsm-4.18.17-1.el7ev.x86_64 qemu-kvm-rhev-2.6.0-27.el7.x86_64 Linux version 3.10.0-514.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Wed Oct 19 11:24:13 EDT 2016 Linux 3.10.0-514.el7.x86_64 #1 SMP Wed Oct 19 11:24:13 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.3 (Maipo) Checked on both hosts, agent and broker logs not being duplicated on my environment.
*** Bug 1414658 has been marked as a duplicate of this bug. ***