Changes with nginx 0.8.23 11 Nov
2009
*) Security: now SSL/TLS renegotiation is disabled.
Thanks to Maxim D..
*) Bugfix: listen unix domain socket did not inherit while online
upgrade.
*) Bugfix: the "unix:" parameter of the "set_real_ip_from" directive
did not without yet another directive with any IP address.
*) Bugfix: segmentation fault and infinite looping in resolver.
*) Bugfix: in resolver.
Thanks to Artem Bokhan.
Hi, im trying to buy the new version on my Ubuntu 8.04 and I’m getting
this error:
gcc -c -O -pipe -O -W -Wall -Wpointer-arith -Wno-unused-parameter
-Wunused-function -Wunused-variable -Wunused-value -Werror -g -I
src/core -I src/event -I src/event/modules -I src/os/unix -I objs
-o objs/src/os/unix/ngx_process_cycle.o
src/os/unix/ngx_process_cycle.c
src/os/unix/ngx_process_cycle.c:174:50: error: macro “ngx_log_debug0”
passed 5 arguments, but takes just 4
src/os/unix/ngx_process_cycle.c: In function ‘ngx_master_process_cycle’:
src/os/unix/ngx_process_cycle.c:173: error: ‘ngx_log_debug0’ undeclared
(first use in this function)
src/os/unix/ngx_process_cycle.c:173: error: (Each undeclared identifier
is reported only once
src/os/unix/ngx_process_cycle.c:173: error: for each function it appears
in.)
make[1]: *** [objs/src/os/unix/ngx_process_cycle.o] Error 1
make[1]: Leaving directory `/users/root/downloads/source/nginx-0.8.23’
make: *** [build] Error 2
The previous one, works super fine, this one doesn’t.
not a single error or warning here on Ubuntu 9.04 (or whatever Jaunty
is)
Hello!
On Wed, Nov 11, 2009 at 12:36:37PM +0100, Robert G. wrote:
src/os/unix/ngx_process_cycle.c: In function ‘ngx_master_process_cycle’:
The previous one, works super fine, this one doesn’t.
Yes, thank you.
As a quick workaround consider ./configure --with-debug or apply
the following patch (trivial, changes ngx_log_debug0 to
ngx_log_debug1):
— a/src/os/unix/ngx_process_cycle.c
+++ b/src/os/unix/ngx_process_cycle.c
@@ -170,7 +170,7 @@ ngx_master_process_cycle(ngx_cycle_t *cy
ngx_time_update(0, 0);
-
ngx_log_debug1(NGX_LOG_DEBUG_EVENT, cycle->log, 0,
"wake up, sigio %i", sigio);
if (ngx_reap) {
Maxim D.
*) Bugfix: segmentation fault and infinite looping in resolver.
*) Bugfix: in resolver.
Thanks to Artem Bokhan.
Do these relate to a problem whereby, when the system’s resolver
becomes unavailable, it may cause that nginx child to hang and spin at
100% cpu?
If so, fantastic
I’ve been having this problem for a while. Guess
it’s time to upgrade
2009/11/11 Igor S. [email protected]:
— a/src/os/unix/ngx_process_cycle.c
+++ b/src/os/unix/ngx_process_cycle.c
@@ -170,7 +170,7 @@ ngx_master_process_cycle(ngx_cycle_t *cy
ngx_time_update(0, 0);
-
ngx_log_debug1(NGX_LOG_DEBUG_EVENT, cycle->log, 0,
"wake up, sigio %i", sigio);
if (ngx_reap) {
Ok that worked fine. Thx!
On Wed, Nov 11, 2009 at 10:29:33AM -0800, Gabriel R. wrote:
*) Bugfix: segmentation fault and infinite looping in resolver.
*) Bugfix: in resolver.
Thanks to Artem Bokhan.
Do these relate to a problem whereby, when the system’s resolver
becomes unavailable, it may cause that nginx child to hang and spin at
100% cpu?
Yes.