================== 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-06-11T02:30:27Z|00001|vlog|INFO|opened log file /var/log/ovn/ovsdb-server-nb.log 2026-06-11T02:30:27Z|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-06-11T02:30:28Z|00003|ovsdb_server|INFO|memory trimming after compaction enabled. 2026-06-11T02:30:27.109Z|00001|vlog|INFO|opened log file /var/log/ovn/ovsdb-server-nb.log 2026-06-11T02:30:27.113Z|00002|ovsdb_server|INFO|ovsdb-server (Open vSwitch) 3.3.7 2026-06-11T02:30:28.079Z|00003|ovsdb_server|INFO|memory trimming after compaction enabled. 2026-06-11T02:30:37Z|00004|memory|INFO|26732 kB peak resident set size after 10.0 seconds 2026-06-11T02:30:37Z|00005|memory|INFO|atoms:50 cells:43 json-caches:1 monitors:2 n-weak-refs:0 sessions:1 2026-06-11T02:30:37.115Z|00004|memory|INFO|26732 kB peak resident set size after 10.0 seconds 2026-06-11T02:30:37.115Z|00005|memory|INFO|atoms:50 cells:43 json-caches:1 monitors:2 n-weak-refs:0 sessions:1 2026-06-11T02:35:17Z|00006|jsonrpc|WARN|tcp:10.0.0.119:58188: receive error: Connection reset by peer 2026-06-11T02:35:17Z|00007|reconnect|WARN|tcp:10.0.0.119:58188: connection dropped (Connection reset by peer) 2026-06-11T02:35:17.828Z|00006|jsonrpc|WARN|tcp:10.0.0.119:58188: receive error: Connection reset by peer 2026-06-11T02:35:17.828Z|00007|reconnect|WARN|tcp:10.0.0.119:58188: connection dropped (Connection reset by peer) 2026-06-11T03:10:11Z|00008|jsonrpc|WARN|tcp:10.0.0.139:52088: receive error: Connection reset by peer 2026-06-11T03:10:11Z|00009|reconnect|WARN|tcp:10.0.0.139:52088: connection dropped (Connection reset by peer) 2026-06-11T03:10:11.225Z|00008|jsonrpc|WARN|tcp:10.0.0.139:52088: receive error: Connection reset by peer 2026-06-11T03:10:11.226Z|00009|reconnect|WARN|tcp:10.0.0.139:52088: connection dropped (Connection reset by peer) 2026-06-11T03:20:38Z|00010|jsonrpc|WARN|tcp:10.0.0.240:51766: receive error: Connection reset by peer 2026-06-11T03:20:38Z|00011|reconnect|WARN|tcp:10.0.0.240:51766: connection dropped (Connection reset by peer) 2026-06-11T03:20:38.570Z|00010|jsonrpc|WARN|tcp:10.0.0.240:51766: receive error: Connection reset by peer 2026-06-11T03:20:38.570Z|00011|reconnect|WARN|tcp:10.0.0.240:51766: connection dropped (Connection reset by peer)