#354 Crash in 1.6.4-tls

1.6.x
closed-out-of-date
None
5
2015-04-06
2011-02-16
No

We recently implemented Opensips 1.6.4 to begin use the ability to search
across dialogs in order to allow for attended transfers with multiple
Asterisk servers in a load balanced setup. Today we had a crash. Attached is
the log entries and the full backtrace. I mention the dialog search feature
only because even I can tell that is a big part of the backtrace. :-) I
XXXX'ed out a few host names and those are available on request if
necessary.

Discussion

  • James Van Vleet

    James Van Vleet - 2011-02-16

    log entries and "bt full"

     
  • James Van Vleet

    James Van Vleet - 2011-03-17
     
  • James Van Vleet

    James Van Vleet - 2011-03-17

    Crash finally happened again this morning. Two cores were created and bt full has been attached for both in crash2.txt.

    Let me know if you need anything else.

    Thanks!

    -James

     
  • Anca Vamanu

    Anca Vamanu - 2011-03-23
    • assigned_to: nobody --> anca_vamanu
     
  • Anca Vamanu

    Anca Vamanu - 2011-03-23

    Hi James,

    If you still have the core file - can you please enter with gdb in the second one ( the one with the backtrace in crash2.txt} and run 'f 3' and then 'p *cseq'.

    Thanks, Anca

     
  • James Van Vleet

    James Van Vleet - 2011-03-23

    'f 3' and then 'p *cseq' on pid 24166

     
  • James Van Vleet

    James Van Vleet - 2011-03-23

    Attached file pid24166detail.txt has the detail you requested.

    -James

     
  • Anca Vamanu

    Anca Vamanu - 2011-03-29

    Hi James,

    Sorry for not replying to you sooner. From the gdb print it looks that the 'cseq' is ok, so then the only left explanation is that there is some sort of a memory corruption.. unfortunately this is quite hard to debug. What you can do is to compile with memory debugging support - in Makefile.defs search -DDBG_QM_MALLOC line, uncomment it, move it above -DF_MALLOC line and comment this line with -DF_MALLOC. Then recompile and reinstall all. Also set mem_dump=1 in your config.

    And when you have a crash, look in the log for the lines above 'core was generated' for the process that crashed and send them.

    Regards,
    Anca

     
  • Bogdan-Andrei Iancu

    • status: open --> closed-out-of-date
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks