Hi all,
We've found two different coredumps in production machines running 1.10.3
handing ssl and http v2 traffic.
Here is the backtrace of version compiles with -O0 -g -ggdb
warning: exec file is newer than core file.
[New LWP 28665]
[Thread debugging using libthread_db enabled]
Using host li
On Monday 13 March 2017 15:06:17 George . wrote:
> Hi all,
>
> We've found two different coredumps in production machines running 1.10.3
> handing ssl and http v2 traffic.
>
> Here is the backtrace of version compiles with -O0 -g -ggdb
>
[..]
Do you use any 3rd-party modules or patches? Could
Hello!
On Mon, Mar 13, 2017 at 03:06:17PM +0200, George . wrote:
> Hi all,
>
> We've found two different coredumps in production machines running 1.10.3
> handing ssl and http v2 traffic.
>
> Here is the backtrace of version compiles with -O0 -g -ggdb
>
>
>
> warning: exec file is newer than
Hi Valentin, Sorry, I've sent the mail incidentally before I complete it ;)
ssl_proxy_cores # ./nginx -V
nginx version: nginx/1.10.3
built by gcc 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
built with OpenSSL 1.0.2g 1 Mar 2016 (running with OpenSSL 1.0.2g-fips 1
Mar 2016)
TLS SNI support ena
Eww, that looks like a backport exploded.
Do me a favor and file a bug in Ubuntu for this with `ubuntu-bug nginx` so the
retraced can trace the core dump.
Thomas
*Sent from my iPhone. Please excuse any typos, as they are likely to happen by
accident.*
> On Mar 13, 2017, at 09:24, George .
Hi Maxim
Unfortunately I guess it will be hard to reproduce it quickly because it
happened on production machine with heavy traffic.
About the gdb warring - it't not a problem: causes because I've copied
binary to folder were we've collected the core itself:
-rwxr-xr-x 1 cdnuser cdnuser 475341
it our build from nginx repository
it a vanilla source
On Mon, Mar 13, 2017 at 3:30 PM, Thomas Ward wrote:
> Eww, that looks like a backport exploded.
>
> Do me a favor and file a bug in Ubuntu for this with `ubuntu-bug nginx` so
> the retraced can trace the core dump.
>
>
> Thomas
>
>
>
> *Sent
details: http://hg.nginx.org/njs/rev/243c9c96511a
branches:
changeset: 313:243c9c96511a
user: Igor Sysoev
date: Mon Mar 13 16:32:40 2017 +0300
description:
Miscellaneous non-functional changes in nxt_mem_cache_pool.
diffstat:
nxt/nxt_mem_cache_pool.c | 125 +++
details: http://hg.nginx.org/njs/rev/6bda82d5bd54
branches:
changeset: 312:6bda82d5bd54
user: Igor Sysoev
date: Sun Mar 12 22:40:13 2017 +0300
description:
Using nxt_rbtree_destroy_next() iterator for nxt_mem_cache_pool
destruction without rbtree rebalancing.
diffstat:
nxt/nxt_mem
On Monday 13 March 2017 15:24:46 George . wrote:
> Hi Valentin, Sorry, I've sent the mail incidentally before I complete it ;)
>
>
> ssl_proxy_cores # ./nginx -V
> nginx version: nginx/1.10.3
> built by gcc 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
> built with OpenSSL 1.0.2g 1 Mar 2016 (ru
Yes, for me it looks like memory corruption and really hard to guess with
only bt.
We will run with in-memory debug, but we have to wait till next core. I'll
update you when we have more info.
On Mon, Mar 13, 2017 at 3:55 PM, Valentin V. Bartenev
wrote:
> On Monday 13 March 2017 15:24:46 George
We have couple of these per week, I was blaming our third party modules, but
seems like vanilla is also affected.
> On Mar 13, 2017, at 7:22 AM, George . wrote:
>
> Yes, for me it looks like memory corruption and really hard to guess with
> only bt.
> We will run with in-memory debug, but we
12 matches
Mail list logo
