blocks|key|3920066|text|禁用错误日志的语法是ok的，但docs状态是在读取配置之前使用默认日志文件。(这似乎是合理的，因为否则它如何告诉您配置中有错误)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3920067|尝试使用运行nginx的用户的正确权限手动创建此文件。或者尝试以root用户身份启动服务器。|3920068|entityMap|0|LINK|mutability|MUTABLE|url|http://wiki.nginx.org/CoreModule#error_log^0|F|4|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

The syntax for disabling the error log is ok, but the <a href="http://wiki.nginx.org/CoreModule#error_log">docs</a> state that a default logfile is used before the config is read. (which seems reasonable because how would it otherwise tell you you have an error in your config)

Try creating this file by hand with the correct permissions for the user that runs nginx. Or try starting the server as root.

blocks|key|5647876|text|我在启动nginx时使用-p参数解决了这个问题，例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5647877|/home/ubuntu/nginx/sbin/nginx+-c+/home/ubuntu/nginx/conf/nginx.conf+-p+/home/ubuntu/nginx|code-block|syntax|javascript|5647878|这将在配置中指定的任何日志路径前面加上前缀目录。|5647879|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I solved this issue using the -p parameter when starting nginx e.g:

<pre><code>/home/ubuntu/nginx/sbin/nginx -c /home/ubuntu/nginx/conf/nginx.conf -p /home/ubuntu/nginx
</code></pre>

This will prepend any log paths specified in the config with the prefix directory.

blocks|key|3437469|text|我刚刚通过使用这个配置参数解决了这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3437470|./configure+--prefix="$HOME/nginx"+--error-log-path=/dev/stderr|code-block|syntax|javascript|3437471|因为我从未将这个nginx用作守护进程，并且总是在shell中运行它，所以它将错误记录到stderr中是有意义的。|3437472|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I just solved this by using this configure parameter:

<pre><code>./configure --prefix="$HOME/nginx" --error-log-path=/dev/stderr
</code></pre>

Since I never use this nginx as a daemon and always run it in a shell, it makes sense for it to log errors to stderr.

blocks|key|3920141|text|您不能通过指定-p前缀来解决问题；因为这只适用于配置文件中的指令；正如RickyA已经注意到的，问题是nginx甚至在打开配置之前就想要打开一个编译的错误日志。由于显而易见的原因，更改编译的错误日志的权限并不理想。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3920142|解决方法是在命令行上将错误日志指定为配置：|3920143|$+nginx+-p+.+-g+'error_log+error.log;'|code-block|syntax|javascript|3920144|或|3920145|$+nginx+-p+.+-g+'error_log+stderr;'|3920146|您仍然会收到警告，但至少它允许我在Ubuntu上以非root用户身份启动nginx。|3920147|entityMap^0|7|2|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|11|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|T|$]]

You can't solve the problem by specifying a <code>-p</code> prefix; because that would only apply to the directives in the configuration file; and as RickyA already noted the problem is that there is a compiled-in error log that nginx wants to open even before it opens the configuration. Changing permissions of the compiled-in error log is not ideal, for obvious reasons.

A workaround is to specify the error log as a configuration on the command line:

<pre><code>$ nginx -p . -g 'error_log error.log;'
</code></pre>

or

<pre><code>$ nginx -p . -g 'error_log stderr;'
</code></pre>

You'll still get an [alert] but at least it allowed me to start nginx as non-root on Ubuntu.

blocks|key|3437523|text|对于this+post+on+the+nginx.org+mailing+list+(摘录如下)，%25%25ERROR_LOG_PATH%25%25被设置为编译选项，并在启动时立即检查，从而导致“无法打开”警报。指定前缀(使用-p)可能有助于抑制警报，但前提是在编译时将%25%25ERROR_LOG_PATH%25%25指定为相对路径。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|3437524|可以使用以下命令检查它在当前可执行文件中的指定方式|3437525|nginx+-V+2>&1+%7C+grep+-oE+'error-log-path=\S*'|3437526|这就是为什么@Michael提出的解决方案对一些人有效，但对另一些人无效。|3437527|3437528|参见changelog：|blockquote|3437529|3437530|与nginx+0.7.53的更改|3437531|..。|3437532|*)更改:现在在启动时创建了一个由--error-+log+-path设置的日志。|3437533|*)功能:现在可以将启动错误和警告输出到error_log和stderr。|3437534|3437535|现在编译成nginx的值总是用来在开始时记录错误(如果error_log不能打开它，就会发出警告)。一旦配置文件被读取，将使用配置文件中的error_log。|3437536|如果你已经编译了带有相对于前缀的error_log路径的nginx+-应该可以通过-p开关覆盖启动error_log。|3437537|马克西姆·杜宁|3437538|entityMap|0|LINK|mutability|MUTABLE|url|http://mailman.nginx.org/pipermail/nginx/2009-June/013326.html^0|1D|I|2Y|2|3K|I|45|2|2|13|0|0|0|0|19|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]|$9|1L|A|1M|B|D]]|E|@$9|1N|A|1O|1|1P]]|F|$]]|$1|G|3|H|5|6|7|1Q|8|@]|E|@]|F|$]]|$1|I|3|J|5|6|7|1R|8|@$9|1S|A|1T|B|C]]|E|@]|F|$]]|$1|K|3|L|5|6|7|1U|8|@]|E|@]|F|$]]|$1|M|3|-4|5|6|7|1V|8|@]|E|@]|F|$]]|$1|N|3|O|5|P|7|1W|8|@]|E|@]|F|$]]|$1|Q|3|-4|5|6|7|1X|8|@]|E|@]|F|$]]|$1|R|3|S|5|6|7|1Y|8|@]|E|@]|F|$]]|$1|T|3|U|5|6|7|1Z|8|@]|E|@]|F|$]]|$1|V|3|W|5|6|7|20|8|@]|E|@]|F|$]]|$1|X|3|Y|5|6|7|21|8|@]|E|@]|F|$]]|$1|Z|3|U|5|6|7|22|8|@]|E|@]|F|$]]|$1|10|3|11|5|6|7|23|8|@]|E|@]|F|$]]|$1|12|3|13|5|6|7|24|8|@]|E|@]|F|$]]|$1|14|3|15|5|6|7|25|8|@]|E|@]|F|$]]|$1|16|3|-4|5|6|7|26|8|@]|E|@]|F|$]]]|17|$18|$5|19|1A|1B|F|$1C|1D]]]]

Per <a href="http://mailman.nginx.org/pipermail/nginx/2009-June/013326.html" rel="nofollow noreferrer" title="0.7.60: Could not open error log">this post on the nginx.org mailing list</a> (extract quoted below), the <code>%%ERROR_LOG_PATH%%</code> is set as a compile option, and checked immediately on startup, causing the "Could not open" alert. Specifying the prefix (with <code>-p</code>) may help suppress the alert, but only if the <code>%%ERROR_LOG_PATH%%</code> was specified as a relative path at compile time.

You can check how it is specified in your current executable with

<code>nginx -V 2&gt;&amp;1 | grep -oE 'error-log-path=\S*'</code>

That is why the solution proposed by @Michael works for some, but not for others.

<blockquote>
 See changelog:
 
 Changes with nginx 0.7.53
 
 ...
 
 *) Change: now a log set by --error-log-path is created from the very 
 start-up.
 
 *) Feature: now the start up errors and warnings are outputted to an 
 error_log and stderr.
 
 ...
 
 Now compiled in error_log value always used to log errors at start 
 time (and emits warning if nginx can't open it). Once config file 
 have been read - error_log from config will be used instead.
 
 If you have compiled nginx with error_log path relative to prefix 
 - it should be possible to override startup error_log via -p 
 switch.
 
 Maxim Dounin
</blockquote>

blocks|key|5648079|text|不需要使用命令行参数。只需确保将error_log指令添加到nginx.conf的最顶部，或者至少在出现任何错误消息之前。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5648080|NH2在2016年1月发表的评论表明，这种选择至少已经存在几年了。我可以确认它是有效的，而且它的麻烦更少。与其他选择相比，对nginx.conf的自定义不太可能导致对打包的nginx安装的更新出现问题。|5648081|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

There's no need to use a command line parameter. Simply ensure you add the error_log directive to the very top of nginx.conf or at least before any error messages may occur.

nh2's comment from Jan 2016 suggests that this option would have been available for at least a couple years now. I can confirm it works and it's less hassle. Customisation to nginx.conf is less likely to cause issues with updates to a packaged nginx installation than the alternatives.

I compiled the nginx on Ubuntu myself.
I start my nginx with -c nginx.conf parameter.
In my nginx.conf file, I try to turn off error log with but failed.

<pre><code>error_log /dev/null crit;
</code></pre>

Still got the error message:
nginx: [alert] could not open error log file: open() "/usr/nginx/logs/error.log" failed (2: No such file or directory)

How could I turn off this log or change its location?

How to turn off or specify the nginx error log location?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我自己在Ubuntu上编译了nginx。我用-c nginx.conf参数开始我的nginx。在我的nginx.conf文件中，我尝试使用关闭错误日志，但失败了。error_log /dev/null crit;仍然得到错误信息: nginx: alert无法打开错误日志文件: open() "/usr/nginx/logs/error.log“失败(2:没有这样的文件或目录)如何关闭此日志或更改

问如何关闭或指定nginx错误日志位置？
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何关闭或指定nginx错误日志位置？EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何关闭或指定nginx错误日志位置？
EN