Maxim Dounin
April 03, 2012 12:34PM
Hello!

On Mon, Apr 02, 2012 at 09:08:47PM -0400, Floren Munteanu wrote:

> Hi Maxim,
>
> On 4/2/2012 1:06 PM, Maxim Dounin wrote:
> >It's safe and only adds minimal overhead on logging level checks
> >as long as debug log isn't enabled.
> >
> >Note though that writing debug logs consume extra resources, and
> >it may be noticeable under high load. The debug_connection
> >directive allows to enable debug logging only for selected ip
> >addresses to minimize impact.
>
> I've built a nginx-debug RPM but I'm tempted to try 1.1.18 now. :)
> I will use instead 1.0.14, just in case is a nasty bug hidden
> somewhere in Nginx. In this way, we fix both versions. These are the

I'm afraid we aren't going to fix 1.0.x anyway. The 1.1.x branch
will become stable in serveral weeks, and 1.0.x is expected to get
only security fixes.

> compile cflags I used:
> gcc -c -pipe -O -W -Wall -Wpointer-arith -Wno-unused-parameter
> -Wunused-function -Wunused-variable -Wunused-value -Werror -g -O3 -g
> -m64 -mtune=nocona -m128bit-long-double -mmmx -msse3 -mfpmath=sse
>
> I'm going to leave the error_log set on error and give it a 256k
> buffer so it should not affect the performance. Since we only deal

The error log doesn't support buffering.

> [crit], I don't think we need to debug anything lower than error.

I need complete request debug log to understand what's going on
during request processing (and what's going wrong).

> I'll add the following settings into http:
> debug_points abort;
> worker_rlimit_core 512M;
> working_directory /var/lib/nginx/;
>
> Let me know please if I should do anything extra.

For now, please capture debug log. Anything else (including gdb
dump of the request in question) isn't that important, but if you
are going to obtain one it might be good idea to recompile nginx
without -O3 as it might produce undesired side-effects in gdb
output. The -O used by default is good enough.

Maxim Dounin

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

Socket leaks., pread and [crit] SSL_Write() in 1.0.14

TECK March 25, 2012 11:55PM

Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14

TECK March 26, 2012 12:01AM

Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14

Maxim Dounin March 26, 2012 06:22AM

Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14

TECK March 26, 2012 08:04AM

Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14

TECK March 26, 2012 08:49AM

Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14

Samael March 26, 2012 10:41AM

Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14

TECK March 26, 2012 06:57PM

Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14

TECK March 26, 2012 10:28PM

Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14

TECK March 29, 2012 04:50AM

Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14

Maxim Dounin March 26, 2012 12:50PM

Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14

teckinno March 31, 2012 06:42PM

Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14

Maxim Dounin April 02, 2012 07:18AM

Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14

TECK April 02, 2012 12:22PM

Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14

Maxim Dounin April 02, 2012 01:08PM

Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14

TECK April 02, 2012 09:10PM

Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14

Maxim Dounin April 03, 2012 12:34PM

Re: Socket leaks., pread and [crit] SSL_Write() in 1.0.14

TECK April 05, 2012 11:18AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 163
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready