Nginx日常報錯處理總結

在nginx錯誤日誌中，有大量的下列資訊：

upstream timed out (110: connection timed out) while reading response header from upstream

[root@www vhosts]# tailf /usr/local/nginx/logs/qderp_error.log

2018/10/31
02:05:39 [error] 12831#0: *149343 upstream timed out (110: connection timed out) while reading response header from upstream, 
2018/10/31
02:05:39 [error] 12831#0: *149341 upstream timed out (110: connection timed out) while reading response header from upstream, 
2018/10/31
02:05:39 [error] 12831#0: *149342 upstream timed out (110: connection timed out) while reading response header from upstream, 
2018/10/31
02:05:39 [error] 12831#0: *149340 upstream timed out (110: connection timed out) while reading response header from upstream, 
2018/10/31
02:05:39 [error] 12831#0: *149338 upstream timed out (110: connection timed out) while reading response header from upstream,

這種情況主要在下面兩種情況下發生:

需要適當的調整proxy_read_timeout值。

location /

在這種情況下，適當的調整fastcgi_read_timeout選項值

location ~*.php$

Nginx日誌499報錯處理

499對應的是 client has closed connection 這很有可能是因為伺服器端處理的時間過長，客戶端自己斷開連線解決問題 proxy ignore client abort on 讓 服務端不要主動關閉客戶端的連線。預設 proxy ignore client abort 是關閉...

ZF報錯處理

fatal error uncaught exception zend controller response exception with message cannot send headers headers already sent inind xampp php pear z end con...

oracle報錯處理

這裡的序號 1.2.3.不是步驟，而是每個單獨問題。1.不登入鏈結資料庫 sqlplus nolog 2.oracle檢視並修改最大連線數 alter system set processes 1000 scope spfile alter system set session 1105 scope...