NSX Manager logs show warning message "Couldn't connect to 'tcp://127.0.0.1:4096'"
search cancel

NSX Manager logs show warning message "Couldn't connect to 'tcp://127.0.0.1:4096'"

book

Article ID: 318304

calendar_today

Updated On:

Products

VMware NSX Networking

Issue/Introduction

Symptoms:
  • NSX-T version is 2.5.x
  • NSX Manager logs (syslog.log)¬†display message(s) similar to, repeatedly¬†every 5 seconds:
<182>1 2020-04-30T06:04:33.880Z tec4-nsxt-mgr01 NSX 1784 - [nsx@6876 comp="nsx-manager" subcomp="opsagent" s2comp="nsx-rpc" tid="1807" level="INFO"] ConnectionKeeper[2 tcp://127.0.0.1:4096] attempting connection from timer callback
<180>1 2020-04-30T06:04:33.880Z tec4-nsxt-mgr01 NSX 1784 - [nsx@6876 comp="nsx-manager" subcomp="opsagent" s2comp="nsx-net" tid="1807" level="WARN"] StreamConnection[6585001 Connecting to tcp://127.0.0.1:4096 sid:6585001] Couldn't connect to 'tcp://127.0.0.1:4096' (error: 111-Connection refused)
<180>1 2020-04-30T06:04:33.880Z tec4-nsxt-mgr01 NSX 1784 - [nsx@6876 comp="nsx-manager" subcomp="opsagent" s2comp="nsx-net" tid="1807" level="WARN"] StreamConnection[6585001 Error to tcp://127.0.0.1:4096 sid:-1] Error 111-Connection refused
<180>1 2020-04-30T06:04:33.880Z tec4-nsxt-mgr01 NSX 1784 - [nsx@6876 comp="nsx-manager" subcomp="opsagent" s2comp="nsx-rpc" tid="1807" level="WARN"] RpcConnection[6585001 Connecting to tcp://127.0.0.1:4096] Couldn't connect to tcp://127.0.0.1:4096 (error: 111-Connection refused)
<180>1 2020-04-30T06:04:33.880Z tec4-nsxt-mgr01 NSX 1784 - [nsx@6876 comp="nsx-manager" subcomp="opsagent" s2comp="nsx-rpc" tid="1807" level="WARN"] RpcTransport[2] Unable to connect to grep "127.0.0.1:4096 " system/netstat_-nape: 111-Connection refused
<182>1 2020-04-30T06:04:33.880Z tec4-nsxt-mgr01 NSX 1784 - [nsx@6876 comp="nsx-manager" subcomp="opsagent" s2comp="nsx-rpc" tid="1807" level="INFO"] ConnectionKeeper[2 tcp://127.0.0.1:4096] scheduling connection attempt in 5000 ms


Environment

VMware NSX-T Data Center
VMware NSX-T Data Center 2.x

Cause

Those errors are purely "cosmestic" can be safely ignored.

Resolution

This issue is resolved in NSX-T 3.0.

For the NSX-T version impacted (2.5.x), the warning are non impacting an can be safely ignored.