[ovs-discuss] ovsdb_idl - received unexpected reply message

Shivaram Mysore shivaram.mysore at gmail.com
Tue Aug 27 20:18:49 UTC 2019


Ignore this request for help.  There was some mistakes in my setup.

Thanks

On Mon, Aug 26, 2019 at 9:53 PM Shivaram Mysore <shivaram.mysore at gmail.com>
wrote:

> Hi,
>
> System info:
> # *ovs-vswitchd --version*
> ovs-vswitchd (Open vSwitch) 2.10.1
>
> # *lsmod | grep openvswitch*
> openvswitch           155648  3
> nsh                    16384  1 openvswitch
> nf_conncount           24576  1 openvswitch
> nf_nat                 49152  3 openvswitch,ipt_MASQUERADE,iptable_nat
> nf_conntrack          151552  6
> openvswitch,nf_conncount,ipt_MASQUERADE,nf_conntrack_netlink,xt_conntrack,nf_nat
> nf_defrag_ipv6         24576  2 openvswitch,nf_conntrack
> libcrc32c              16384  4 openvswitch,nf_nat,nf_conntrack,xfs
>
> On OVS startup, I am seeing this error and am unable to understand the
> reason or where I should look for more debugging:
>
> 2019-08-27T04:40:50Z|00027|ovsdb_idl|DBG|unix:/var/run/openvswitch/db.sock:
> SERVER_MONITOR_COND_REQUESTED -> DATA_MONITOR_COND_REQUESTED at
> lib/ovsdb-idl.
> c:1817
> 2019-08-27T04:40:50Z|00028|jsonrpc|DBG|unix:/var/run/openvswitch/db.sock:
> send request, method="set_db_change_aware", params=[true], id=5
> 2019-08-27T04:40:50Z|00029|poll_loop|DBG|wakeup due to [POLLIN] on fd 11
> (<->/var/run/openvswitch/db.sock) at lib/stream-fd.c:157
> 2019-08-27T04:40:50Z|00030|jsonrpc|DBG|unix:/var/run/openvswitch/db.sock:
> received reply, result={}, id=4
> 2019-08-27T04:40:50Z|00031|ovsdb_idl|DBG|unix:/var/run/openvswitch/db.sock:
> DATA_MONITOR_COND_REQUESTED -> MONITORING at lib/ovsdb-idl.c:694
> 2019-08-27T04:40:50Z|00032|jsonrpc|DBG|unix:/var/run/openvswitch/db.sock:
> received reply, result={}, id=5
> 2019-08-27T04:40:50Z|00033|ovsdb_idl|DBG|unix:/var/run/openvswitch/db.sock:
> received unexpected reply message: {"error":null,"id":5,"result":{}}
> 2019-08-27T04:40:50Z|00034|netlink_socket|DBG|nl_sock_send__ (Success):
> nl(len:17, type=26(family-defined), flags=305[REQUEST][ACK][DUMP], seq=1,
> pid=3163
> 940381
> ....
> ...
> 2019-08-27T04:40:50Z|00049|netlink_socket|DBG|nl_sock_recv__ (Success):
> nl(len:172, type=16(control), flags=0, seq=1, pid=13,genl(cmd=1,version=2)
> 2019-08-27T04:40:50Z|00050|netlink_socket|DBG|nl_sock_transact_multiple__
> (Success): nl(len:52, type=18(family-defined), flags=1[REQUEST], seq=1,
> pid=3283
> 033594
> 2019-08-27T04:40:50Z|00051|netlink_socket|DBG|nl_sock_recv__ (Success):
> nl(len:72, type=2(error), flags=0, seq=1, pid=3283033594 error(-19(No such
> device)
> , in-reply-to(nl(len:52, type=18(family-defined), flags=1[REQUEST], seq=1,
> pid=3283033594))
> 2019-08-27T04:40:50Z|00052|netlink_socket|DBG|received NAK error=0 (No
> such device)
> 2019-08-27T04:40:50Z|00053|netlink_socket|DBG|nl_sock_transact_multiple__
> (Success): nl(len:104, type=16(family-defined),
> flags=405[REQUEST][ACK][ATOMIC],
>  seq=2, pid=3283033594
> 2019-08-27T04:40:50Z|00054|netlink_socket|DBG|nl_sock_recv__ (Success):
> nl(len:124, type=2(error), flags=0, seq=2, pid=3283033594 error(-95(Not
> supported)
> , in-reply-to(nl(len:104, type=16(family-defined),
> flags=405[REQUEST][ACK][ATOMIC], seq=2, pid=3283033594))
> 2019-08-27T04:40:50Z|00055|netlink_socket|DBG|received NAK error=0 (Not
> supported)
> 2019-08-27T04:40:50Z|00056|netlink_socket|DBG|nl_sock_transact_multiple__
> (Success): nl(len:36, type=31(ovs_vport), flags=9[REQUEST][ECHO], seq=1,
> pid=13,
> genl(cmd=3,version=1)
> 2019-08-27T04:40:50Z|00057|netlink_socket|DBG|nl_sock_recv__ (Success):
> nl(len:56, type=2(error), flags=0, seq=1, pid=13 error(-19(No such device),
> in-rep
> ly-to(nl(len:36, type=31(ovs_vport), flags=9[REQUEST][ECHO], seq=1,
> pid=13))
> 2019-08-27T04:40:50Z|00058|netlink_socket|DBG|received NAK error=0 (No
> such device)
> ....
> ...
> 2019-08-27T04:40:50Z|00154|netlink_socket|DBG|nl_sock_recv__ (Success):
> nl(len:56, type=2(error), flags=0, seq=1d, pid=13 error(-19(No such
> device), in-re
> ply-to(nl(len:36, type=31(ovs_vport), flags=9[REQUEST][ECHO], seq=1d,
> pid=13))
> 2019-08-27T04:40:50Z|00155|netlink_socket|DBG|received NAK error=0 (No
> such device)
> 2019-08-27T04:40:50Z|00156|ovs_router|DBG|src addr not available for route
> ff00::
> 2019-08-27T04:40:50Z|00157|netlink_socket|DBG|nl_sock_recv__ (Success):
> nl(len:20, type=3(done), flags=2[MULTI], seq=1, pid=3163940381 done(0)
> ovs-vswitchd: /var/run/openvswitch/ovs-vswitchd.pid: already running as
> pid 13, aborting
> ovs-vswitchd: /var/run/openvswitch/ovs-vswitchd.pid: already running as
> pid 13, aborting
> ovs-vswitchd: /var/run/openvswitch/ovs-vswitchd.pid: already running as
> pid 13, aborting
>
> Thanks
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20190827/4a0e29dd/attachment-0001.html>


More information about the discuss mailing list