IP Address Seem to be be changed

Couchbase Server Kubernetes
1

Wonder why I am getting below ?
As from the previous threads I can confirm there is NO XDCR running , Cluster is not undersized and there is no activity going on but still keep getting this ? We are running on 8 node K8s cluster on-prem and not in cloud . Is this false positive then how can we remove this annoying message . If this is true issue where can we find the details what the problem is ?

[4:23:00 AM] - IP address seems to have changed. Unable to listen on ‘ns_1@tccbldc-cluster-0004.tccbldc-cluster.bi-cb.svc’. (POSIX error code: ‘nxdomain’)
[4:23:00 AM] - IP address seems to have changed. Unable to listen on ‘ns_1@tccbldc-cluster-0009.tccbldc-cluster.bi-cb.svc’. (POSIX error code: ‘nxdomain’)
[4:23:00 AM] - IP address seems to have changed. Unable to listen on ‘ns_1@tccbldc-cluster-0001.tccbldc-cluster.bi-cb.svc’. (POSIX error code: ‘nxdomain’)
[4:23:00 AM] - IP address seems to have changed. Unable to listen on ‘ns_1@tccbldc-cluster-0012.tccbldc-cluster.bi-cb.svc’. (POSIX error code: ‘nxdomain’)
[4:23:00 AM] - IP address seems to have changed. Unable to listen on ‘ns_1@tccbldc-cluster-0008.tccbldc-cluster.bi-cb.svc’. (POSIX error code: ‘nxdomain’)
[4:23:00 AM] - IP address seems to have changed. Unable to listen on ‘ns_1@tccbldc-cluster-0010.tccbldc-cluster.bi-cb.svc’. (POSIX error code: ‘nxdomain’)
[4:23:01 AM] - IP address seems to have changed. Unable to listen on ‘ns_1@tccbldc-cluster-0011.tccbldc-cluster.bi-cb.svc’. (POSIX error code: ‘nxdomain’)

2

Do you have any other indications the cluster manager is not able to update?

What more can you tell us about you Kubernetes setup. What version are you on? Does the UI show anything out of order or do you see anything unusual from apps?

3

hi there ,
I dont have any indication on that . If you can help me find out that info I can certainly do that .
I don’t see anything unusual on Admin UI except annoying popup intermittently and we don’t any app build on this db yet … we are on CB 6.0 and K8s setup is 4 data+query node , 3 index + query nodes , 1 - analytics ,event ,search node on a 48x6 = 288 logical Core K8s env where in data and query node 25 overall CPU assigned and index + query node total 45 CPU assigned .

kubectl version
Client Version: version.Info{Major:“1”, Minor:“12”, GitVersion:“v1.12.7+1.1.2.el7”, GitCommit:“02dd7eef0970a31fb7bd6e3392a3d0e411870c59”, GitTreeState:“archive”, BuildDate:“2019-04-05T17:53:36Z”, GoVersion:“go1.10.8”, Compiler:“gc”, Platform:“linux/amd64”}
Server Version: version.Info{Major:“1”, Minor:“13”, GitVersion:“v1.13.10”, GitCommit:“37d169313237cb4ceb2cc4bef300f2ae3053c1a2”, GitTreeState:“clean”, BuildDate:“2019-08-19T10:44:49Z”, GoVersion:“go1.11.13”, Compiler:“gc”, Platform:“linux/amd64”}

4

Any solutions bro? I had the same issues

5

The underlying problem is that the Kubernetes DNS server isn’t responding, and Couchbase mistakenly thinking the IP address has changed. I’d direct your efforts to looking at any logs/monitoring associated with kubedns.