Nginx调试日志记录级别

Question

我遵循了these指令并在nginx中启用了错误日志。在

我在尝试测试日志时，在for循环的末尾删除了一个:，从而产生了一个语法错误。在

当试图加载网站时，它抛出了一个500内部服务器错误。在

看了日志后，我对所看到的感到很迷茫。我当前的级别设置为debug。在

如何配置这些设置，以便它告诉我问题是语法错误？在

下面是错误日志尾部的示例：

5098 2016/08/06 01:53:05 [debug] 23526#23526: *44 write new buf t:1 f:0 0000559FAC0F0508, pos 0000559FAC0F0508, size: 161 file: 0, size: 0
5099 2016/08/06 01:53:05 [debug] 23526#23526: *44 http write filter: l:0 f:0 s:161
5100 2016/08/06 01:53:05 [debug] 23526#23526: *44 http output filter "/tag/getting-started/?"
5101 2016/08/06 01:53:05 [debug] 23526#23526: *44 http copy filter: "/tag/getting-started/?"
5102 2016/08/06 01:53:05 [debug] 23526#23526: *44 image filter
5103 2016/08/06 01:53:05 [debug] 23526#23526: *44 xslt filter body
5104 2016/08/06 01:53:05 [debug] 23526#23526: *44 http postpone filter "/tag/getting-started/?" 0000559FAC0F06E8
5105 2016/08/06 01:53:05 [debug] 23526#23526: *44 write old buf t:1 f:0 0000559FAC0F0508, pos 0000559FAC0F0508, size: 161 file: 0, size: 0
5106 2016/08/06 01:53:05 [debug] 23526#23526: *44 write new buf t:0 f:0 0000000000000000, pos 0000559FAB989AC0, size: 120 file: 0, size: 0
5107 2016/08/06 01:53:05 [debug] 23526#23526: *44 write new buf t:0 f:0 0000000000000000, pos 0000559FAB98ADA0, size: 62 file: 0, size: 0
5108 2016/08/06 01:53:05 [debug] 23526#23526: *44 http write filter: l:1 f:0 s:343
5109 2016/08/06 01:53:05 [debug] 23526#23526: *44 http write filter limit 0
5110 2016/08/06 01:53:05 [debug] 23526#23526: *44 writev: 343 of 343
5111 2016/08/06 01:53:05 [debug] 23526#23526: *44 http write filter 0000000000000000
5112 2016/08/06 01:53:05 [debug] 23526#23526: *44 http copy filter: 0 "/tag/getting-started/?"
5113 2016/08/06 01:53:05 [debug] 23526#23526: *44 http finalize request: 0, "/tag/getting-started/?" a:1, c:1
5114 2016/08/06 01:53:05 [debug] 23526#23526: *44 event timer add: 12: 5000:1470462790191
5115 2016/08/06 01:53:05 [debug] 23526#23526: *44 http lingering close handler
5116 2016/08/06 01:53:05 [debug] 23526#23526: *44 recv: fd:12 -1 of 4096
5117 2016/08/06 01:53:05 [debug] 23526#23526: *44 recv() not ready (11: Resource temporarily unavailable)
5118 2016/08/06 01:53:05 [debug] 23526#23526: *44 lingering read: -2
5119 2016/08/06 01:53:05 [debug] 23526#23526: *44 event timer: 12, old: 1470462790191, new: 1470462790191
5120 2016/08/06 01:53:05 [debug] 23526#23526: *44 http empty handler
5121 2016/08/06 01:53:05 [debug] 23526#23526: *44 http empty handler
5122 2016/08/06 01:53:05 [debug] 23526#23526: *44 http lingering close handler
5123 2016/08/06 01:53:05 [debug] 23526#23526: *44 recv: fd:12 -1 of 4096
5124 2016/08/06 01:53:05 [info] 23526#23526: *44 recv() failed (104: Connection reset by peer) while sending to client, client: 180.76.15.12, server: chriskoh.io, request: "GET /tag/getting-started/ HTTP/1.1", upstream: "http://127     .0.0.1:2368/tag/getting-started/", host: "sites.bugsplat.info"
5125 2016/08/06 01:53:05 [debug] 23526#23526: *44 lingering read: -1
5126 2016/08/06 01:53:05 [debug] 23526#23526: *44 http request count:1 blk:0
5127 2016/08/06 01:53:05 [debug] 23526#23526: *44 http close request
5128 2016/08/06 01:53:05 [debug] 23526#23526: *44 http log handler
5129 2016/08/06 01:53:05 [debug] 23526#23526: *44 free: 0000559FAC0F8BA0, unused: 0
5130 2016/08/06 01:53:05 [debug] 23526#23526: *44 free: 0000559FAC0EFB70, unused: 881
5131 2016/08/06 01:53:05 [debug] 23526#23526: *44 close http connection: 12
5132 2016/08/06 01:53:05 [debug] 23526#23526: *44 event timer del: 12: 1470462790191
5133 2016/08/06 01:53:05 [debug] 23526#23526: *44 reusable connection: 0
5134 2016/08/06 01:53:05 [debug] 23526#23526: *44 free: 0000559FAC0EE400
5135 2016/08/06 01:53:05 [debug] 23526#23526: *44 free: 0000559FAC0EE1F0, unused: 128

Answer 1

1）禁用nginx调试模式，它会吃掉你的硬盘。Nginx调试模式日志的目的是调试Nginx本身，而不是您的应用程序错误。在

2）不要在错误的地方查找错误，nginx错误日志与您的应用程序（flask）/中间件（在您的例子中是uwsgi）日志无关

3）DO faq about uwsgi logs