================== ovnkube.sh --- version: 3 ================
 ==================== command: nb-ovsdb
 =================== hostname: ovn-ovsdb-nb-0
 =================== daemonset version 3
error: subresource cannot be used when bulk resources are specified
Node  zone is global
=============== run nb_ovsdb ========== MASTER ONLY
info: Waiting for process_ready ovnnb_db to come up, waiting 1s ...
chown: cannot access '/etc/openvswitch': No such file or directory
chown: cannot access '/var/log/openvswitch': No such file or directory
/etc/ovn/ovnnb_db.db does not exist ... (warning).
Creating empty database /etc/ovn/ovnnb_db.db.
2026-05-28T09:22:59Z|00001|vlog|INFO|opened log file /var/log/ovn/ovsdb-server-nb.log
2026-05-28T09:22:59Z|00002|ovsdb_server|INFO|ovsdb-server (Open vSwitch) 3.3.7
process_ready ovnnb_db came up in 1 5 sec tries
=============== nb-ovsdb ========== RUNNING
setting northd probe interval to 5000 ms
the current value of northd probe interval is  ms
successfully set northd probe interval to 5000 ms
=============== nb-ovsdb ========== reconfigured for northd backoff
2026-05-28T09:23:00Z|00003|ovsdb_server|INFO|memory trimming after compaction enabled.
2026-05-28T09:22:59.175Z|00001|vlog|INFO|opened log file /var/log/ovn/ovsdb-server-nb.log
2026-05-28T09:22:59.179Z|00002|ovsdb_server|INFO|ovsdb-server (Open vSwitch) 3.3.7
2026-05-28T09:23:00.138Z|00003|ovsdb_server|INFO|memory trimming after compaction enabled.
2026-05-28T09:23:09Z|00004|memory|INFO|26888 kB peak resident set size after 10.0 seconds
2026-05-28T09:23:09Z|00005|memory|INFO|atoms:50 cells:43 json-caches:1 monitors:2 n-weak-refs:0 sessions:1
2026-05-28T09:23:09.185Z|00004|memory|INFO|26888 kB peak resident set size after 10.0 seconds
2026-05-28T09:23:09.185Z|00005|memory|INFO|atoms:50 cells:43 json-caches:1 monitors:2 n-weak-refs:0 sessions:1
2026-05-28T10:05:45Z|00006|jsonrpc|WARN|tcp:10.0.0.157:43850: receive error: Connection reset by peer
2026-05-28T10:05:45Z|00007|reconnect|WARN|tcp:10.0.0.157:43850: connection dropped (Connection reset by peer)
2026-05-28T10:05:45.017Z|00006|jsonrpc|WARN|tcp:10.0.0.157:43850: receive error: Connection reset by peer
2026-05-28T10:05:45.017Z|00007|reconnect|WARN|tcp:10.0.0.157:43850: connection dropped (Connection reset by peer)
2026-05-28T10:09:21Z|00008|jsonrpc|WARN|tcp:10.0.0.157:41406: receive error: Connection reset by peer
2026-05-28T10:09:21Z|00009|reconnect|WARN|tcp:10.0.0.157:41406: connection dropped (Connection reset by peer)
2026-05-28T10:09:21.045Z|00008|jsonrpc|WARN|tcp:10.0.0.157:41406: receive error: Connection reset by peer
2026-05-28T10:09:21.045Z|00009|reconnect|WARN|tcp:10.0.0.157:41406: connection dropped (Connection reset by peer)
2026-05-28T10:09:21.385Z|00010|jsonrpc|WARN|tcp:10.0.0.157:41410: receive error: Connection reset by peer
2026-05-28T10:09:21.385Z|00011|reconnect|WARN|tcp:10.0.0.157:41410: connection dropped (Connection reset by peer)
2026-05-28T10:09:21Z|00010|jsonrpc|WARN|tcp:10.0.0.157:41410: receive error: Connection reset by peer
2026-05-28T10:09:21Z|00011|reconnect|WARN|tcp:10.0.0.157:41410: connection dropped (Connection reset by peer)
2026-05-28T10:11:39.370Z|00012|jsonrpc|WARN|tcp:10.0.0.157:52260: receive error: Connection reset by peer
2026-05-28T10:11:39.370Z|00013|reconnect|WARN|tcp:10.0.0.157:52260: connection dropped (Connection reset by peer)
2026-05-28T10:11:39Z|00012|jsonrpc|WARN|tcp:10.0.0.157:52260: receive error: Connection reset by peer
2026-05-28T10:11:39Z|00013|reconnect|WARN|tcp:10.0.0.157:52260: connection dropped (Connection reset by peer)
2026-05-28T10:15:16Z|00014|jsonrpc|WARN|tcp:10.0.0.157:50516: receive error: Connection reset by peer
2026-05-28T10:15:16Z|00015|reconnect|WARN|tcp:10.0.0.157:50516: connection dropped (Connection reset by peer)
2026-05-28T10:15:16.470Z|00014|jsonrpc|WARN|tcp:10.0.0.157:50516: receive error: Connection reset by peer
2026-05-28T10:15:16.470Z|00015|reconnect|WARN|tcp:10.0.0.157:50516: connection dropped (Connection reset by peer)
2026-05-28T10:15:24Z|00016|jsonrpc|WARN|tcp:10.0.0.157:50488: receive error: Connection reset by peer
2026-05-28T10:15:24Z|00017|reconnect|WARN|tcp:10.0.0.157:50488: connection dropped (Connection reset by peer)
2026-05-28T10:15:24.275Z|00016|jsonrpc|WARN|tcp:10.0.0.157:50488: receive error: Connection reset by peer
2026-05-28T10:15:24.275Z|00017|reconnect|WARN|tcp:10.0.0.157:50488: connection dropped (Connection reset by peer)
2026-05-28T10:17:42.020Z|00018|jsonrpc|WARN|tcp:10.0.0.157:33160: receive error: Connection reset by peer
2026-05-28T10:17:42.021Z|00019|reconnect|WARN|tcp:10.0.0.157:33160: connection dropped (Connection reset by peer)
2026-05-28T10:17:42Z|00018|jsonrpc|WARN|tcp:10.0.0.157:33160: receive error: Connection reset by peer
2026-05-28T10:17:42Z|00019|reconnect|WARN|tcp:10.0.0.157:33160: connection dropped (Connection reset by peer)
2026-05-28T10:20:09Z|00020|jsonrpc|WARN|tcp:10.0.0.157:60806: receive error: Connection reset by peer
2026-05-28T10:20:09Z|00021|reconnect|WARN|tcp:10.0.0.157:60806: connection dropped (Connection reset by peer)
2026-05-28T10:20:09.070Z|00020|jsonrpc|WARN|tcp:10.0.0.157:60806: receive error: Connection reset by peer
2026-05-28T10:20:09.071Z|00021|reconnect|WARN|tcp:10.0.0.157:60806: connection dropped (Connection reset by peer)