[ovs-discuss] ovsdb_idl - received unexpected reply message

Shivaram Mysore shivaram.mysore at gmail.com
Tue Aug 27 23:45:21 UTC 2019


Thanks Ben for more insight.

Regards

On Tue, Aug 27, 2019 at 4:20 PM Ben Pfaff <blp at ovn.org> wrote:

> On Mon, Aug 26, 2019 at 09:53:17PM -0700, Shivaram Mysore 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":{}}
>
> This particular message is DBG level because it isn't significant.
> There's a comment in the code that has a little more information:
>
>     /* Unknown message.  Log at a low level because this can happen if
>      * ovsdb_idl_txn_destroy() is called to destroy a transaction
>      * before we receive the reply.
>      *
>      * (We could sort those out from other kinds of unknown messages by
>      * using distinctive IDs for transactions, if it seems valuable to
>      * do so, and then it would be possible to use different log
>      * levels. XXX?) */
>     char *s = jsonrpc_msg_to_string(msg);
>     VLOG_DBG("%s: received unexpected %s message: %s",
>              jsonrpc_session_get_name(idl->session),
>              jsonrpc_msg_type_to_string(msg->type), s);
>     free(s);
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20190827/68b84d13/attachment.html>


More information about the discuss mailing list