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

[Misak Khachatryan]

Hi Marcin,

Here is the output:

[root at ovirt-engine ~]# ps -ef|grep 'ovnsb_db\|ovnnb_db'
root     19883 19882  0 Dec20 ?        00:01:22 ovsdb-server --detach
--monitor -vconsole:off
--log-file=/var/log/openvswitch/ovsdb-server-nb.log
--remote=punix:/run/openvswitch/ovnnb_db.sock
--pidfile=/run/openvswitch/ovnnb_db.pid
--remote=db:OVN_Northbound,NB_Global,co
nnections --unixctl=ovnnb_db.ctl
--private-key=db:OVN_Northbound,SSL,private_key
--certificate=db:OVN_Northbound,SSL,certificate
--ca-cert=db:OVN_Northbound,SSL,ca_cert
/var/lib/openvswitch/ovnnb_db.db
root     19891 19890  0 Dec20 ?        00:01:23 ovsdb-server --detach
--monitor -vconsole:off
--log-file=/var/log/openvswitch/ovsdb-server-sb.log
--remote=punix:/run/openvswitch/ovnsb_db.sock
--pidfile=/run/openvswitch/ovnsb_db.pid
--remote=db:OVN_Southbound,SB_Global,co
nnections --unixctl=ovnsb_db.ctl
--private-key=db:OVN_Southbound,SSL,private_key
--certificate=db:OVN_Southbound,SSL,certificate
--ca-cert=db:OVN_Southbound,SSL,ca_cert
/var/lib/openvswitch/ovnsb_db.db
root     19897 19896  0 Dec20 ?        00:00:00 ovn-northd
-vconsole:emer -vsyslog:err -vfile:info
--ovnnb-db=unix:/run/openvswitch/ovnnb_db.sock
--ovnsb-db=unix:/run/openvswitch/ovnsb_db.sock --no-chdir
--log-file=/var/log/openvswitch/ovn-northd.log --pidfile=/run/openv
switch/ovn-northd.pid --detach --monitor
root     30800 30786  0 11:29 pts/0    00:00:00 grep --color=auto
ovnsb_db\|ovnnb_db
[root at ovirt-engine ~]#

And here is the list of files in   /var/run/openvswitch/

[root at ovirt-engine ~]# ll   /var/run/openvswitch/
total 20
srwxr-x---. 1 root root 0 Dec 20 20:32 db.sock
srwxr-x---. 1 root root 0 Dec 20 20:32 ovnnb_db.ctl
-rw-r--r--. 1 root root 6 Dec 20 20:32 ovnnb_db.pid
srwxr-x---. 1 root root 0 Dec 20 20:32 ovnnb_db.sock
srwxr-x---. 1 root root 0 Dec 20 20:32 ovn-northd.19897.ctl
-rw-r--r--. 1 root root 6 Dec 20 20:32 ovn-northd.pid
srwxr-x---. 1 root root 0 Dec 20 20:32 ovnsb_db.ctl
-rw-r--r--. 1 root root 6 Dec 20 20:32 ovnsb_db.pid
srwxr-x---. 1 root root 0 Dec 20 20:32 ovnsb_db.sock
srwxr-x---. 1 root root 0 Dec 20 20:32 ovsdb-server.19806.ctl
-rw-r--r--. 1 root root 6 Dec 20 20:32 ovsdb-server.pid
srwxr-x---. 1 root root 0 Dec 20 20:32 ovs-vswitchd.19845.ctl
-rw-r--r--. 1 root root 6 Dec 20 20:32 ovs-vswitchd.pid



Best regards,
Misak Khachatryan


On Wed, Dec 27, 2017 at 8:11 PM, Marcin Mirecki <mmirecki at redhat.com> wrote:
> Hello Misak,
>
> This error hints that your ovn databases are not up (or at least can not be
> connected to).
> Could you please check if the following command gives any output:
>
>     ps -ef|grep 'ovnsb_db\|ovnnb_db'
>
> The databases can be started (if not active) using:
>    /usr/share/openvswitch/scripts/ovn-ctl start_ovsdb
>
> Could you please also check the content of:
>   /var/run/openvswitch/
>
> The filenames don't look normal (usually they do not contain any numbers as
> part of them), please give me some time to check this.
>
> Thanks,
> Marcin
>
>
>
>
>
> On Wed, Dec 27, 2017 at 3:44 PM, Mor Kalfon <mkalfon at redhat.com> wrote:
>>
>> Hello Misak,
>>
>> Could you please file a bug about those error messages that you receive
>> from OVS?
>> You can use the log collector tool
>> (https://www.ovirt.org/documentation/admin-guide/chap-Utilities/#the-log-collector-tool)
>> which gathers all the required logs for us to investigate this issue.
>>
>> Thanks for reporting this issue!
>>
>> On Wed, Dec 27, 2017 at 11:03 AM, Misak Khachatryan <kmisak at gmail.com>
>> wrote:
>>>
>>> On Wed, Dec 27, 2017 at 12:42 PM, Dan Kenigsberg <danken at redhat.com>
>>> wrote:
>>> > On Wed, Dec 27, 2017 at 8:49 AM, Misak Khachatryan <kmisak at gmail.com>
>>> > 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 at redhat.com>
>>> >> wrote:
>>> >>> On Tue, Dec 26, 2017 at 8:35 AM, Misak Khachatryan <kmisak at gmail.com>
>>> >>> 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?
>>
>>
>>
>>
>> --
>> Mor Kalfon
>> RHV Networking Team
>> Red Hat IL-Raanana
>> Tel: +972-54-6514148
>>
>