Re: [ovirt-users] OVS error logs after upgrade to 4.2

On Wed, Dec 27, 2017 at 12:42 PM, Dan Kenigsberg <danken(a)redhat.com&gt; wrote: > On Wed, Dec 27, 2017 at 8:49 AM, Misak Khachatryan <kmisak(a)gmail.com&gt; wrote: >> Hi, >> >> It's not on log file, it's from automatic email sent by cron daemon. >> This one from logrotate. > > Would you file a bug about this daily logrotate spam? > Sure, will do. >> >> I'd like to migrate my network to OVS, but as i can't find any guide >> for that, it's a bit scary. > > Why would you like to do that? OVN is useful for big deployments, that > have many isolated networks. It is not universally recommended, as it > uses more CPU. > No particular reason, thought that will be future in oVIRT networking, also i work in relatively big ISP with many PoP and DCs in many cities. And I'm interested to try it some time. >> >> Best regards, >> Misak Khachatryan >> >> >> On Tue, Dec 26, 2017 at 3:29 PM, Dan Kenigsberg <danken(a)redhat.com&gt; wrote: >>> On Tue, Dec 26, 2017 at 8:35 AM, Misak Khachatryan <kmisak(a)gmail.com&gt; wrote: >>>> Hi, >>>> >>>> After upgrade to 4.2 I started getting this error from engine: >>>> >>>> /etc/cron.daily/logrotate: >>>> >>>> 2017-12-25T23:12:02Z|00001|unixctl|WARN|failed to connect to >>>> /var/run/openvswitch/ovnnb_db.19883.ctl >>>> ovs-appctl: cannot connect to >>>> "/var/run/openvswitch/ovnnb_db.19883.ctl" (No such file or directory) >>>> 2017-12-25T23:12:02Z|00001|unixctl|WARN|failed to connect to >>>> /var/run/openvswitch/ovnsb_db.19891.ctl >>>> ovs-appctl: cannot connect to >>>> "/var/run/openvswitch/ovnsb_db.19891.ctl" (No such file or directory) >>>> >>>> >>>> Seems harmless as i don't use OVS, but how to fix it? >>> >>> By default, ovirt-4.2 installs and configure OVN (which uses OVS). You >>> can turn it off on Engine host by running >>> systemctl stop ovirt-provider-ovn ovn-northd openvswitch > > did you try that? > No, but is correct way to disable it completely? >>> >>> but I'd appreciate your help to understand in which log file do you >>> see these warnings? > >>> Have you already disabled openvswitch? > > have you ^^ ? No, what is a correct way to do it?