|
error message |
Error description |
|
“upstream prematurely（Premature “closed connection” |
The exception that occurs when requesting URI is due to the disconnection of the user before upstream returns the response to the user. It has no effect on the system and can be ignored |
|
“recv() failed (104: Connection reset by peer)” |
（1）The number of concurrent connections of the server exceeds its carrying capacity, and the server will drop some of its connections to Down. （2）The client turned off the browser while the server was sending the data to the client. （3）The browser side pressed Stop. |
|
“(111: Connection refused) while connecting to upstream” |
Users will receive this error if they encounter the backend upstream hanging or blocked when they connect. |
|
“(111: Connection refused) while reading response header from upstream” |
When a user reads data after a successful connection, he or she receives the error if the backend upstream hangs up or fails. |
|
“(111: Connection refused) while sending request to upstream” |
NginxWhen sending data after a successful connection with upstream, you receive the error if the backend upstream hangs up or fails |
|
“(110: Connection timed out) while connecting to upstream” |
nginxTimeout when connecting upstream on the back |
|
“(110: Connection timed out) while reading upstream” |
nginxTimeout when reading response from upstream
|
|
“(110: Connection timed out) while reading response header from upstream” |
nginxTimeout when reading response header from upstream |
|
“(110: Connection timed out) while reading upstream” |
nginxTimeout when reading response from upstream |
|
“(104: Connection reset by peer) while connecting to upstream” |
upstreamRST is sent to reset the connection. |
|
“upstream sent invalid header while reading response header from upstream” |
upstreamThe response header sent is invalid. |
|
“upstream sent no valid HTTP/1.0 header while reading response header from upstream” |
upstreamThe response header sent is invalid. |
|
“client intended to send too large body” |
Used to set the maximum allowable client request content, the default value is 1M, and the body sent by the client exceeds the set value |
|
“reopening logs” |
The user sends the kill -USR1 command. |
|
“gracefully shutting down”, |
The user sends the kill -WINCH command. |
|
“no servers are inside upstream” |
upstreamNo server configured below |
|
“no live upstreams while connecting to upstream” |
upstreamAll the server below is hung up. |
|
“SSL_do_handshake() failed” |
SSLHandshake failed |
|
“ngx_slab_alloc() failed: no memory in SSL session shared cache” |
ssl_session_cacheInsufficient size and other causes |
|
“could not add new SSL session to the session cache while SSL handshaking” |
ssl_session_cacheInsufficient size and other causes
|
|
upstream prematurely closed connection while reading response header from upstream |
