0.7.60: "could not open error log"
mdounin at mdounin.ru
Fri Jun 26 16:27:01 MSD 2009
On Fri, Jun 26, 2009 at 10:51:42AM +0200, Toni Mueller wrote:
> while going from 0.6.x to 0.7.6, I notice the following:
> $ nginx -t -c /my/private/path/conf/nginx.conf
> [alert]: could not open error log file: open() "/var/log/nginx/error.log" failed (13: Permission denied)
> the configuration file /my/private/path/conf/nginx.conf syntax is ok
> configuration file /my/private/path/conf/nginx.conf test is successful
> I always set the log file locations to somewhere else, not
> /var/log/nginx (the system default). When I run nginx w/o the "-t"
> switch, it emits the same error message on the console, but proceeds to
> actually use the log file(s) that I've specified in my configuration
Changes with nginx 0.7.53
*) Change: now a log set by --error-log-path is created from the very
*) 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
More information about the nginx