17 messages in ru.sysoev.nginxRe: upcoming 0.7.53 large patch
FromSent OnAttachments
Igor SysoevApr 23, 2009 12:11 pm 
Jérôme LoyetApr 23, 2009 2:27 pm 
Jérôme LoyetApr 23, 2009 3:24 pm 
Igor SysoevApr 23, 2009 11:20 pm 
Jérôme LoyetApr 23, 2009 11:35 pm 
Igor SysoevApr 24, 2009 12:39 am 
Jérôme LoyetApr 24, 2009 12:48 am 
Igor SysoevApr 24, 2009 1:58 am.Other
Jérôme LoyetApr 24, 2009 2:10 am 
Jérôme LoyetApr 24, 2009 5:43 am 
Igor SysoevApr 24, 2009 7:59 am 
Jérôme LoyetApr 24, 2009 8:58 am 
Igor SysoevApr 24, 2009 9:00 am 
Igor SysoevApr 24, 2009 9:18 am 
Jérôme LoyetApr 24, 2009 9:43 am 
Igor SysoevApr 24, 2009 10:06 am 
Jérôme LoyetApr 24, 2009 1:03 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: upcoming 0.7.53 large patchActions...
From:Jérôme Loyet (jer@loyet.net)
Date:Apr 24, 2009 5:43:20 am
List:ru.sysoev.nginx

2009/4/24 Igor Sysoev <is@rambler-co.ru>:

On Fri, Apr 24, 2009 at 12:25:09AM +0200, J?r?me Loyet wrote:

Hi igor,

in order to compile the patch version, I had to modify the patch because it tried to patch auto/configure. The configure is in the root directory, not in auto. Or I misunderstood something ?

Then I didn't understand how the -p option works. I made the following test: ./configure /usr/local/nginx/sbin/nginx -p /root/test/nginx

but all file are relative to the default prefix (/usr/local/nginx) except the root directive which is relative to /root/test/nginx in my case.

I don't know what I did but this behaviour is not the one I described earlier.

The test is the following! .#/configure #make && make install # /usr/local/nginx/sbin/nginx -V nginx version: nginx/0.7.52 configure arguments:

# (cd /tmp && /usr/local/nginx/sbin/nginx) [emerg]: could not open error log file: open() "logs/error.log" failed (2: )

# (cd /path/where/logs/directory/exists && /usr/local/nginx/sbin/nginx) [emerg]: open() "conf/conf/nginx.conf" failed (2: )

# (cd /tmp && strace -e open /usr/local/nginx/sbin/nginx -p /root/test/nginx/) [emerg]: could not open error log file: open() "logs/error.log" failed (2: )

It seems there is a bug with the default error_log and/or the prefix.

A new version, that fixes startup error log prefix:

http://sysoev.ru/tmp/patch.0.7.52.1.prefix

here the test I made: #tar -xzvf nginx-0.7.52.tar.gz # cd nginx-0.7.52 # patch -p0 < ../patch.0.7.52.1.prefix # patch -p0 < ../patch.gnu_strerror_r #./configure #make && make install # (cd /tmp && /usr/local/nginx/sbin/nginx) [emerg]: could not open error log file: open() "/logs/error.log" failed (2: No such file or directory)

it should be /usr/local/nginx/logs/error.log

# (cd /tmp && /usr/local/nginx/sbin/nginx -p /root/test/nginx) 2009/04/24 14:38:57 [notice] 27082#0: using the "epoll" event method 2009/04/24 14:38:57 [notice] 27082#0: nginx/0.7.52 2009/04/24 14:38:57 [notice] 27082#0: OS: Linux 2.6.25.4dedibox-r9-smp-x32 2009/04/24 14:38:57 [notice] 27082#0: getrlimit(RLIMIT_NOFILE): 1024:1024 2009/04/24 14:38:57 [notice] 27083#0: start worker processes 2009/04/24 14:38:57 [notice] 27083#0: start worker process 27084 root@wild:~/nginx-0.7.52# 2009/04/24 14:39:04 [error] 27084#0: *1 open() "/root/test/nginx/docs/sdfsdfsdfs" failed (2: No such file or directory), client: 160.92.7.69, server: localhost, request: "GET /sdfsdfsdfs HTTP/1.0", host: "wild.xxxxxxxx.com"

The file /root/test/nginx/logs/error.log is created but stays empty. And for information it's owned by user root.

Hope this help