Ingress-nginx: bind() to 127.0.0.1:10256 failed (98: Address already in use)

Created on 28 Sep 2019 · 2Comments · Source: kubernetes/ingress-nginx

NGINX Ingress controller version: 0.26.0

Kubernetes version : 1.16.0

What happened: when I start I get errors:

2019/09/28 18:53:22 [emerg] 24#24: bind() to 127.0.0.1:10256 failed (98: Address already in use)
2019/09/28 18:53:22 [emerg] 24#24: bind() to 127.0.0.1:10257 failed (98: Address already in use)
2019/09/28 18:53:22 [emerg] 24#24: bind() to 127.0.0.1:10256 failed (98: Address already in use)
2019/09/28 18:53:22 [emerg] 24#24: bind() to 127.0.0.1:10257 failed (98: Address already in use)
W0928 18:53:23.090440       6 controller.go:177] Dynamic reconfiguration failed: unexpected error code: 404
E0928 18:53:23.091029       6 controller.go:181] Unexpected failure reconfiguring NGINX:
unexpected error code: 404
W0928 18:53:23.091391       6 queue.go:130] requeuing initial-sync, err unexpected error code: 404

What you expected to happen:

How to reproduce it: Daemonset with hostNetwork

Anything else we need to know:

# ss -pnatl | grep 10256
LISTEN   0         128                        *:10256                  *:*       users:(("kube-proxy",pid=9561,fd=14))
# ss -pnatl | grep 10257
LISTEN   0         128                127.0.0.1:10257            0.0.0.0:*       users:(("kube-controller",pid=9687,fd=5))

Source

stamm

Most helpful comment

@aledbf I affirm that it's working with this image. Thanks for quick response!
I0928 20:09:49.887610 6 nginx.go:307] Starting NGINX process I0928 20:09:49.888103 6 leaderelection.go:241] attempting to acquire leader lease ingress/ingress-controller-leader-nginx... I0928 20:09:49.889373 6 controller.go:134] Configuration changes detected, backend reload required. I0928 20:09:49.913939 6 status.go:86] new leader elected: nginx-nginx-ingress-controller-8pr8w I0928 20:09:50.188610 6 controller.go:150] Backend successfully reloaded. I0928 20:09:50.188800 6 controller.go:159] Initial sync, sleeping for 1 second. I0928 20:10:25.460337 6 leaderelection.go:251] successfully acquired lease ingress/ingress-controller-leader-nginx I0928 20:10:25.464018 6 status.go:86] new leader elected: nginx-nginx-ingress-controller-s668k

stamm on 28 Sep 2019

👍3

All 2 comments

@stamm apologies for this issue. I've opened #4617 to fix this problem and also allow custom ports.
Please use quay.io/kubernetes-ingress-controller/nginx-ingress-controller-amd64:dev to confirm this is fixed. If this works, I will release 0.26.1 with this fix, so other users do not suffer this regression.