110: Connection timed out

[ghost]

Hello.
I got it from error.log.

upstream timed out (110: Connection timed out) while reading response header from upstream, client: xx.xx.xx.xx, server: kong, request: "GET /console/dashboard/real-time/connections-pool HTTP/1.1", upstream: "http://10.0.0.8:8944/console/dashboard/real-time/connections-pool", host: "xxx.xxx.xxx"

It happens randomly.

Please tell me what does it mean?

[Tieske]

what does your api configuration look like?

[ghost]

These are from a dashboard written by myself.
And I use the ssl plugin.

[ghost]

When I send a request to kong 0.10.0, sometimes, viewing access.log, kong did not resend this request immediately until one minute later. this problem sometimes occurs and trouble me .
After this happen ,next call will be normal .
Does it because of the https connection?

I am a Chinese with poor English. 😄

[Tieske]

Might be a dns issue.

See #2290
In that case there were 5 dns servers configured, and the last 2 were included but shouldn't have been. One of those returned errors.

Please ensure you have only valid working nameservers listed in your resolv.conf

[Tieske]

@hongkang have you been able to resolve this?

[harryparmar]

@hongkang @Tieske Try changing default 60k ms upstream_*_timeouts to bigger value on your endpoint.

upstream_read_timeout: 260000
upstream_send_timeout: 260000
upstream_connect_timeout: 260000

[p0pr0ck5]

Closing as a stale issue. Feel free to reopen if there are unanswered questions regarding this.