Kong error logs create functionality break?

Questions
1

Hi,

*[info] 11983#0: 198148506 recv() failed (104: Connection reset by peer) while sending to client, client: 127.0.0.1, server: kong

*2018/09/17 14:36:39 [error] 11984#0: 198070560 [lua] reports.lua:49: log(): [reports] could not send data: connection refused, context: ngx.timer

Above information was logged in kong error log. it will affect the API executions? Could you please guide me?
and how to fix this issues?

2

Yes it will affect API Transactions:

A good stack overflow response covers it best:

It’s fatal. The remote server has sent you a RST packet, which indicates an immediate dropping of the connection, rather than the usual handshake. This bypasses the normal half-closed state transition. I like this description:

“Connection reset by peer” is the TCP/IP equivalent of slamming the phone back on the hook. It’s more polite than merely not replying, leaving one hanging. But it’s not the FIN-ACK expected of the truly polite TCP/IP converseur.

3

how to fix this issues?

4

After upgraded Kong 0.14.1 getting following issues. kindly help me how to fix this?

upstream timed out (110: Connection timed out) while reading response header from upstream, client: 127.0.0.1, server: kong

5

Hi @thiraj89,

Please see this post as a good starting point to debug Kong ↔ upstream connection issues:

An upstream timeout as you noted in your latest post, means that Kong (Nginx here) waited to receive the response headers from your upstream and reached its timeout value (which you can configure on the Service Object, and is 60s by default). This is most likely an issue with your upstream itself, and not Kong.

6

Thanks @thibaultcha . i will check the listed possibility…