Too many anonymous requests in proxy server

I am using kong 2.0.3 with the Postgres database by using kong chart 1.5.0 and deployed by Helm.
There are too many anonymous requests in kong proxy but I don’t know why it is.
Does anyone got it, or know why about it. Please help me to fix it. Many thanks.

2020/04/25 08:53:00 [debug] 24#0: *6556558 [lua] init.lua:280: [cluster_events] polling events from: 1587800932.421
2020/04/25 08:53:01 [info] 24#0: *6552209 client closed connection while waiting for request, client: 10.120.150.128, server: 0.0.0.0:8000
2020/04/25 08:53:01 [info] 24#0: *6556628 client closed connection while waiting for request, client: 10.120.255.128, server: 0.0.0.0:8000
2020/04/25 08:53:01 [info] 24#0: *6552211 client timed out (110: Connection timed out) while waiting for request, client: 10.100.80.128, server: 0.0.0.0:8000
2020/04/25 08:53:01 [info] 24#0: *6556629 client closed connection while waiting for request, client: 10.109.41.192, server: 0.0.0.0:8000
2020/04/25 08:53:01 [info] 24#0: *6556630 client closed connection while waiting for request, client: 10.123.183.128, server: 0.0.0.0:8000
2020/04/25 08:53:01 [info] 24#0: *6556631 client closed connection while waiting for request, client: 10.109.159.64, server: 0.0.0.0:8000
2020/04/25 08:53:01 [info] 24#0: *6556632 client closed connection while waiting for request, client: 10.120.11.128, server: 0.0.0.0:8000
2020/04/25 08:53:01 [info] 24#0: *6556633 client closed connection while waiting for request, client: 10.100.113.192, server: 0.0.0.0:8000
2020/04/25 08:53:01 [info] 24#0: *6556634 client closed connection while waiting for request, client: 10.124.78.192, server: 0.0.0.0:8000
2020/04/25 08:53:01 [info] 24#0: *6556635 client closed connection while waiting for request, client: 10.111.209.128, server: 0.0.0.0:8000
2020/04/25 08:53:01 [info] 24#0: *6556636 client closed connection while waiting for request, client: 10.117.48.0, server: 0.0.0.0:8000
2020/04/25 08:53:02 [info] 24#0: *6552289 client closed connection while waiting for request, client: 10.126.27.0, server: 0.0.0.0:8000
2020/04/25 08:53:02 [info] 24#0: *6552291 client closed connection while waiting for request, client: 10.124.78.192, server: 0.0.0.0:8000
2020/04/25 08:53:02 [info] 24#0: *6552292 client closed connection while waiting for request, client: 10.124.78.192, server: 0.0.0.0:8000
2020/04/25 08:53:03 [info] 24#0: *6552366 client closed connection while waiting for request, client: 10.120.255.128, server: 0.0.0.0:8000
2020/04/25 08:53:03 [info] 24#0: *6552367 client closed connection while waiting for request, client: 10.120.255.128, server: 0.0.0.0:8000
2020/04/25 08:53:03 [info] 24#0: *6556774 client closed connection while waiting for request, client: 10.99.2.192, server: 0.0.0.0:8000
2020/04/25 08:53:03 [info] 24#0: *6552442 client closed connection while waiting for request, client: 10.127.212.128, server: 0.0.0.0:8000
2020/04/25 08:53:03 [info] 24#0: *6552444 client closed connection while waiting for request, client: 10.105.206.64, server: 0.0.0.0:8000
2020/04/25 08:53:03 [info] 24#0: *6552443 client closed connection while waiting for request, client: 10.127.212.128, server: 0.0.0.0:8000
2020/04/25 08:53:03 [info] 24#0: *6552445 client closed connection while waiting for request, client: 10.105.206.64, server: 0.0.0.0:8000
2020/04/25 08:53:03 [info] 24#0: *6552447 client closed connection while waiting for request, client: 10.108.43.0, server: 0.0.0.0:8000
2020/04/25 08:53:03 [info] 24#0: *6552448 client closed connection while waiting for request, client: 10.108.43.0, server: 0.0.0.0:8000
2020/04/25 08:53:03 [info] 24#0: *6513263 client 10.105.206.64 closed keepalive connection
2020/04/25 08:53:03 [info] 24#0: *6552451 client closed connection while waiting for request, client: 10.112.248.192, server: 0.0.0.0:8000
2020/04/25 08:53:03 [info] 24#0: *6552452 client closed connection while waiting for request, client: 10.112.248.192, server: 0.0.0.0:8000
2020/04/25 08:53:03 [info] 24#0: *6517817 client 10.112.248.192 closed keepalive connection
2020/04/25 08:53:03 [info] 24#0: *6552453 client closed connection while waiting for request, client: 10.119.252.192, server: 0.0.0.0:8000
2020/04/25 08:53:03 [info] 24#0: *6552454 client closed connection while waiting for request, client: 10.119.252.192, server: 0.0.0.0:8000
2020/04/25 08:53:03 [info] 24#0: *6550555 client 10.119.252.192 closed keepalive connection
2020/04/25 08:53:03 [info] 24#0: *6552455 client closed connection while waiting for request, client: 10.119.101.64, server: 0.0.0.0:8000
2020/04/25 08:53:03 [info] 24#0: *6552456 client closed connection while waiting for request, client: 10.119.101.64, server: 0.0.0.0:8000
2020/04/25 08:53:03 [info] 24#0: *6550626 client 10.119.101.64 closed keepalive connection
2020/04/25 08:53:04 [info] 24#0: *6556787 client closed connection while waiting for request, client: 10.0.33.21, server: 0.0.0.0:8000
2020/04/25 08:53:04 [info] 24#0: *6556788 client closed connection while waiting for request, client: 10.112.248.192, server: 0.0.0.0:8000
2020/04/25 08:53:04 [info] 24#0: *6556789 client closed connection while waiting for request, client: 10.126.47.64, server: 0.0.0.0:8000
2020/04/25 08:53:04 [info] 24#0: *6556790 client closed connection while waiting for request, client: 10.119.101.64, server: 0.0.0.0:8000
2020/04/25 08:53:04 [info] 24#0: *6556791 client closed connection while waiting for request, client: 10.105.206.64, server: 0.0.0.0:8000
2020/04/25 08:53:04 [info] 24#0: *6556792 client closed connection while waiting for request, client: 10.119.252.192, server: 0.0.0.0:8000
2020/04/25 08:53:04 [info] 24#0: *6556793 client closed connection while waiting for request, client: 10.127.212.128, server: 0.0.0.0:8000
2020/04/25 08:53:04 [info] 24#0: *6552449 client closed connection while waiting for request, client: 10.109.181.192, server: 0.0.0.0:8000
2020/04/25 08:53:04 [info] 24#0: *6552450 client closed connection while waiting for request, client: 10.109.181.192, server: 0.0.0.0:8000
2020/04/25 08:53:04 [info] 24#0: *6552463 client closed connection while waiting for request, client: 10.99.2.192, server: 0.0.0.0:8000
2020/04/25 08:53:04 [info] 24#0: *6552464 client closed connection while waiting for request, client: 10.99.2.192, server: 0.0.0.0:8000
2020/04/25 08:53:04 [info] 24#0: *6552440 client closed connection while waiting for request, client: 10.117.48.0, server: 0.0.0.0:8000
2020/04/25 08:53:04 [info] 24#0: *6552439 client timed out (110: Connection timed out) while waiting for request, client: 10.109.41.192, server: 0.0.0.0:8000
2020/04/25 08:53:05 [info] 24#0: *6556863 client closed connection while waiting for request, client: 10.108.43.0, server: 0.0.0.0:8000
2020/04/25 08:53:05 [info] 24#0: *6556864 client closed connection while waiting for request, client: 10.102.150.64, server: 0.0.0.0:8000
2020/04/25 08:53:05 [debug] 24#0: *6556930 [lua] init.lua:280: [cluster_events] polling events from: 1587800932.421

This shouldn’t be anything to do with Kubernetes specifically. client closed connection while waiting for request is a generic error logged when a client aborts its request, i.e. it opens a connection but never sends a complete HTTP request.

This could be due to any of a number of causes, but it’s generally impossible to tell from the proxy end: all the proxy sees is the connection; any information about why the connection was closed after would only be available on the client. You’ll want to review the client logs and diagnostics for any indication of what’s going on.


© 2019 Kong Inc.    Terms  •  Privacy  •  FAQ