Details

    • Type: Bug Bug
    • Status: Closed
    • Severity: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 13.17.0
    • Target Release Version/s: None
    • Component/s: pjproject/pjsip
    • Security Level: None
    • Labels:
      None
    • Environment:
      Ubuntu 16.04
    • Frequency of Occurrence:
      Frequent

      Description

      Since upgrading from 13.15.rc1 to 13.17.0 we're seeing times where Asterisk will stop responding to packets for up to a minute.

      Not being sure if this is a deadlock situation or not I've compiled some information during when this is happening with ast_coredumper.

        Issue Links

          Activity

          Hide
          Asterisk Team added a comment -

          Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

          A good first step is for you to review the Asterisk Issue Guidelines if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

          Then, if you are submitting a patch, please review the Patch Contribution Process.

          Show
          Asterisk Team added a comment - Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the Asterisk Issue Guidelines if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the Patch Contribution Process .
          Hide
          Rusty Newton added a comment -

          Dan you can collect a debug log during the time of the issue as well?

          https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

          Show
          Rusty Newton added a comment - Dan you can collect a debug log during the time of the issue as well? https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information
          Hide
          DanQ added a comment -

          Sure, this issue only manifests itself at certain times during the week when things get a little busier so it'll take a few days to get this info.

          Show
          DanQ added a comment - Sure, this issue only manifests itself at certain times during the week when things get a little busier so it'll take a few days to get this info.
          Hide
          DanQ added a comment - - edited

          Debug log attached, monitoring picked up an issue at 09:32:27, logs include a minute either side.

          It seems another user is having similar issues; ASTERISK-27247 but my logs don't reference any queue size warnings.

          Show
          DanQ added a comment - - edited Debug log attached, monitoring picked up an issue at 09:32:27, logs include a minute either side. It seems another user is having similar issues; ASTERISK-27247 but my logs don't reference any queue size warnings.
          Hide
          Charlie Smurthwaite added a comment -

          I have reason to believe this issue was caused by DNS lookups not receiving a response. This will be confirmed in the coming days.

          Show
          Charlie Smurthwaite added a comment - I have reason to believe this issue was caused by DNS lookups not receiving a response. This will be confirmed in the coming days.
          Hide
          Charlie Smurthwaite added a comment -

          This issue has not recurred since implementing changes to prevent slow DNS lookups. This issue could be closed, however I'd be interested to know why these lookups are occurring in the first place and whether some configuration exists (or could be added) to prevent them as they seems entirely unnecessary and seem to represent a rather unpleasant accidental or deliberate DoS vector.

          Show
          Charlie Smurthwaite added a comment - This issue has not recurred since implementing changes to prevent slow DNS lookups. This issue could be closed, however I'd be interested to know why these lookups are occurring in the first place and whether some configuration exists (or could be added) to prevent them as they seems entirely unnecessary and seem to represent a rather unpleasant accidental or deliberate DoS vector.
          Hide
          Rusty Newton added a comment -

          Hmm. Well, getting a debug log could help narrow it down. The one provided doesn't contain debug messages, so we'll have to get a new one.

          You can follow the instructions here: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

          Make sure the log gets warning,error,notice,verbose,debug log levels and turn the verbosity of "verbose" and "debug" log levels up to 5 or above each. Verify the log contains "DEBUG" messages before attaching the log.

          Show
          Rusty Newton added a comment - Hmm. Well, getting a debug log could help narrow it down. The one provided doesn't contain debug messages, so we'll have to get a new one. You can follow the instructions here: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information Make sure the log gets warning,error,notice,verbose,debug log levels and turn the verbosity of "verbose" and "debug" log levels up to 5 or above each. Verify the log contains "DEBUG" messages before attaching the log.
          Hide
          Asterisk Team added a comment -

          Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

          [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

          Show
          Asterisk Team added a comment - Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1] . [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:

                Development