nginx 常見錯誤釋義

錯誤信息	錯誤說明
"upstream prematurely（過早的） closed connection"	請求uri的時候出現的異常，是由於upstream還未返回應答給用戶時用戶斷掉連接造成的，對系統沒有影響，可以忽略
"recv() failed (104: Connection reset by peer)"	（1）服務器的並發連接數超過了其承載量，服務器會將其中一些連接Down掉；  （2）客戶關掉了瀏覽器，而服務器還在給客戶端發送數據；  （3）瀏覽器端按了Stop
"(111: Connection refused) while connecting to upstream"	用戶在連接時，若遇到后端upstream掛掉或者不通，會收到該錯誤
"(111: Connection refused) while reading response header from upstream"	用戶在連接成功后讀取數據時，若遇到后端upstream掛掉或者不通，會收到該錯誤
"(111: Connection refused) while sending request to upstream"	Nginx和upstream連接成功后發送數據時，若遇到后端upstream掛掉或者不通，會收到該錯誤
"(110: Connection timed out) while connecting to upstream"	nginx連接后面的upstream時超時
"(110: Connection timed out) while reading upstream"	nginx讀取來自upstream的響應時超時
"(110: Connection timed out) while reading response header from upstream"	nginx讀取來自upstream的響應頭時超時
"(110: Connection timed out) while reading upstream"	nginx讀取來自upstream的響應時超時
"(104: Connection reset by peer) while connecting to upstream"	upstream發送了RST，將連接重置
"upstream sent invalid header while reading response header from upstream"	upstream發送的響應頭無效
"upstream sent no valid HTTP/1.0 header while reading response header from upstream"	upstream發送的響應頭無效
"client intended to send too large body"	用於設置允許接受的客戶端請求內容的最大值，默認值是1M，client發送的body超過了設置值
"reopening logs"	用戶發送kill  -USR1命令
"gracefully shutting down",	用戶發送kill  -WINCH命令
"no servers are inside upstream"	upstream下未配置server
"no live upstreams while connecting to upstream"	upstream下的server全都掛了
"SSL_do_handshake() failed"	SSL握手失敗
"SSL_write() failed (SSL:) while sending to client"
"(13: Permission denied) while reading upstream"
"(98: Address already in use) while connecting to upstream"
"(99: Cannot assign requested address) while connecting to upstream"
"ngx_slab_alloc() failed: no memory in SSL session shared cache"	ssl_session_cache大小不夠等原因造成
"could not add new SSL session to the session cache while SSL handshaking"	ssl_session_cache大小不夠等原因造成
"send() failed (111: Connection refused)"