- 工信部備案號 滇ICP備05000110號-1
- 滇公安備案 滇53010302000111
- 增值電信業(yè)務經(jīng)營許可證 B1.B2-20181647、滇B1.B2-20190004
- 云南互聯(lián)網(wǎng)協(xié)會理事單位
- 安全聯(lián)盟認證網(wǎng)站身份V標記
- 域名注冊服務機構(gòu)許可:滇D3-20230001
- 代理域名注冊服務機構(gòu):新網(wǎng)數(shù)碼
我們經(jīng)常遇到各種各樣的nginx錯誤日志,平時根據(jù)一些nginx錯誤日志就可以分析出原因了。不過不是很系統(tǒng),這里網(wǎng)上看到一篇資料還是比較系統(tǒng)的關于nginx的error.log的詳細說明,這里記錄下,方便以后查看了解。
錯誤信息 | 錯?說明 |
“upstream prematurely(過早的) closed connection” | 請求uri的時候出現(xiàn)的異常,是由于upstream還未返回應答給用戶時用戶斷掉連接造成的,對系統(tǒng)沒有影響,可以忽略 |
“recv() failed (104: Connection reset by peer)” | (1)服務器的并發(fā)連接數(shù)超過了其承載量,服務器會將其中一些連接Down掉; (2)客戶關掉了瀏覽器,而服務器還在給客戶端發(fā)送數(shù)據(jù); (3)瀏覽器端按了Stop |
“(111: Connection refused) while connecting to upstream” | 用戶在連接時,若遇到后端upstream掛掉或者不通,會收到該錯誤 |
“(111: Connection refused) while reading response header from upstream” | 用戶在連接成功后讀取數(shù)據(jù)時,若遇到后端upstream掛掉或者不通,會收到該錯誤 |
“(111: Connection refused) while sending request to upstream” | Nginx和upstream連接成功后發(fā)送數(shù)據(jù)時,若遇到后端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發(fā)送了RST,將連接重置 |
“upstream sent invalid header while reading response header from upstream” | upstream發(fā)送的響應頭無效 |
“upstream sent no valid HTTP/1.0 header while reading response header from upstream” | upstream發(fā)送的響應頭無效 |
“client intended to send too large body” | 用于設置允許接受的客戶端請求內(nèi)容的最大值,默認值是1M,client發(fā)送的body超過了設置值 |
“reopening logs” | 用戶發(fā)送kill -USR1命令 |
“gracefully shutting down”, | 用戶發(fā)送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)” |
以上表格來自網(wǎng)絡資料。這里只是記錄下,方便以后查看。
售前咨詢
售后咨詢
備案咨詢
二維碼
TOP