How to silence logs?

How do I silence these logs? Our Kong is running on k8s. Why these logs are getting triggered?

2019/08/29 06:04:28 [info] 31#0: *6413 client closed connection while SSL handshaking, client: 192.168.10.1, server: 0.0.0.0:8010
2019/08/29 06:04:29 [info] 31#0: *6414 client closed connection while SSL handshaking, client: 192.168.20.1, server: 0.0.0.0:8011
2019/08/29 06:04:29 [info] 31#0: *6418 client closed connection while SSL handshaking, client: 192.168.22.1, server: 0.0.0.0:8011
2019/08/29 06:04:31 [info] 31#0: *6428 client closed connection while SSL handshaking, client: 192.168.18.1, server: 0.0.0.0:8010
2019/08/29 06:04:31 [info] 31#0: *6429 client closed connection while SSL handshaking, client: 192.168.4.1, server: 0.0.0.0:8011
2019/08/29 06:04:31 [info] 31#0: *6436 client closed connection while SSL handshaking, client: 192.168.2.1, server: 0.0.0.0:8011
2019/08/29 06:04:31 [info] 31#0: *6437 client closed connection while SSL handshaking, client: 192.168.2.1, server: 0.0.0.0:8010
2019/08/29 06:04:32 [info] 31#0: *6438 client closed connection while SSL handshaking, client: 192.168.22.1, server: 0.0.0.0:8011
2019/08/29 06:04:33 [info] 31#0: *6451 client closed connection while SSL handshaking, client: 192.168.16.1, server: 0.0.0.0:8011
2019/08/29 06:04:33 [info] 31#0: *6455 client closed connection while SSL handshaking, client: 192.168.10.1, server: 0.0.0.0:8011
2019/08/29 06:04:33 [info] 31#0: *6456 client closed connection while SSL handshaking, client: 192.168.10.1, server: 0.0.0.0:8011
2019/08/29 06:04:33 [info] 31#0: *6457 client closed connection while SSL handshaking, client: 192.168.20.1, server: 0.0.0.0:8010

1 Like

Hello,

Looks like your client closed the connection to Kong before TLS handshake was finished. The exact reason is hard to tell from Kong’s side and you should check the log on 192.168.10.1 to see the real reason.

Datong

I’ve seen the same thing happen from a load balancer health check doing a TCP check. I don’t recall if switching to the HTTPS health check helped or not. Considering it’s an INFO level, you could change the logging to WARN status, though you’ll know your logs to know if you can support or not.


© 2018 Kong Inc.    Terms  •  Privacy  •  FAQ