Asterisk
  1. Asterisk
  2. ASTERISK-17774

Using "loose" option for "joinempty" and/or "leavewhenempty" settings causes severe Asterisk issues

    Details

    • Type: Bug Bug
    • Status: Closed
    • Severity: Critical Critical
    • Resolution: Not A Bug
    • Affects Version/s: None
    • Target Release Version/s: None
    • Component/s: Applications/app_queue
    • Labels:
      None
    • Mantis ID:
      19205
    • Regression:
      No

      Description

      We started using this option today and have run into two separate issues when using it:

      1) We received countless registration-related errors immediately upon reloading our config such as the following:

      [2011-04-29 12:11:54] NOTICE[2255]: chan_sip.c:23511 handle_request_register: Registration from '<sip:2143@[REMOVED]>' failed for '192.168.202.79:5060' - No matching peer found
      [2011-04-29 12:11:55] NOTICE[2255]: chan_sip.c:23511 handle_request_register: Registration from '<sip:2216@[REMOVED]>' failed for '192.168.202.76:5060' - No matching peer found
      [2011-04-29 12:11:55] NOTICE[2255]: chan_sip.c:23511 handle_request_register: Registration from '<sip:2216@[REMOVED]>' failed for '192.168.202.76:5060' - No matching peer found

      It appears as though parts of our config, such as sip_additional.conf, wasn't loaded, causing registrations from remote devices to fail. Upon reverting back to using the "no" option for joinempty and leavewhenempty, these errors went away.

      2) A second time that we tried changing these settings, we experienced an Asterisk crash a little later. We aren't able to find much information in terms of errors, but we did see a huge spike on our SNMP graphs that monitor server load and we were dropped out of our "asterisk -r" sessions.

        Activity

        Hide
        David Woolley added a comment -

        The background for this is in http://forums.digium.com/viewtopic.php?f=1&t=78109&p=156849

        wrp is being constrained by a GUI (FreePBX) that seems only able to access the legacy modes of these options.

        As they haven't provided the required debugging information, I can't tell whether their problems are actually related to the use of these options, although the mix of symptoms suggests a memory corruptions problem. wrp: please see https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace for what you need to do to progress a crash report. If this is memory corruption related, you will also need https://wiki.asterisk.org/wiki/display/AST/Valgrind

        In terms of wrp's original problem, the following, historic, issue is relevant: ASTERISK-1238451

        Show
        David Woolley added a comment - The background for this is in http://forums.digium.com/viewtopic.php?f=1&t=78109&p=156849 wrp is being constrained by a GUI (FreePBX) that seems only able to access the legacy modes of these options. As they haven't provided the required debugging information, I can't tell whether their problems are actually related to the use of these options, although the mix of symptoms suggests a memory corruptions problem. wrp: please see https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace for what you need to do to progress a crash report. If this is memory corruption related, you will also need https://wiki.asterisk.org/wiki/display/AST/Valgrind In terms of wrp's original problem, the following, historic, issue is relevant: ASTERISK-1238451
        Hide
        WRP added a comment -

        We are using FreePBX. We added the "loose" option to the FreePBX interface manually, allowing FreePBX to write this option out to the Asterisk configuration files, which our version of Asterisk supports.

        We do have a core dump file from last Friday's incident, however, our compiler flags were not set to the proper values. I will see what we can do in the way of producing a core file with these flags set.

        Show
        WRP added a comment - We are using FreePBX. We added the "loose" option to the FreePBX interface manually, allowing FreePBX to write this option out to the Asterisk configuration files, which our version of Asterisk supports. We do have a core dump file from last Friday's incident, however, our compiler flags were not set to the proper values. I will see what we can do in the way of producing a core file with these flags set.
        Hide
        Leif Madsen added a comment -

        Set to feedback per requested data in davidw's post.

        Show
        Leif Madsen added a comment - Set to feedback per requested data in davidw's post.
        Hide
        WRP added a comment -

        Problem seems to have been unrelated to loose option. Please close ticket. Thanks for your help!

        Show
        WRP added a comment - Problem seems to have been unrelated to loose option. Please close ticket. Thanks for your help!

          People

          • Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development