Changes between Initial Version and Version 1 of Ticket #789


Ignore:
Timestamp:
09/17/15 12:48:18 (9 years ago)
Author:
Maxim Dounin
Comment:

First backtrace looks like a duplicate of ticket #235, see the first comment to the ticket for detailed description and a workaround. Other core files seems to be corrupted.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #789

    • Property Status new → closed
    • Property Resolution → duplicate

  • Ticket #789 – Description

    initial v1  
    11Worker process constantly exited on signal 11 with different reasons:
    22
     3{{{
    34[New process 104318]
    45[New Thread 803408400 (LWP 102979)]
    … …  
    2829#11 0x000000000040841b in main (argc=3, argv=0x7fffffffed18) at src/core/nginx.c:419
    2930(gdb)
     31}}}
    3032
    3133another dump:
     34{{{
    3235Core was generated by `nginx'.
    3336Program terminated with signal SIGSEGV, Segmentation fault.
    … …  
    4548Backtrace stopped: previous frame inner to this frame (corrupt stack?)
    4649(gdb)
     50}}}
    4751
    4852one more coredump:
     53{{{
    4954[New process 101212]
    5055Core was generated by `nginx'.
    … …  
    5762    at src/core/ngx_resolver.c:3070
    5863Backtrace stopped: Cannot access memory at address 0x30a
     64}}}
    5965
    6066I don't know what preceded it.
    6167NGINX statistics:
     68{{{
    6269Active connections: 46714
    6370server accepts handled requests
    6471 111678 111678 298032
     72}}}