Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-8238

Queue Hang on FreePBX Reload

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Third Party Issue
    • Affects Version/s: 2.10
    • Fix Version/s: None
    • Component/s: Queues
    • Labels:
    • Environment:

      Asterisk 1.8.15-cert2
      CentOS 6.4
      FreePBX 2.9.0.15

    • ToDo:
    • Asterisk Version:
      1.8.15-cert2

      Description

      Sometimes when doing a FreePBX "Apply configuration changes" on the server when it is busy, the queues seem to "hang". By this I mean that the status of all devices in the queue remains static until Asterisk is restarted. Strangely there are only ever "In use", "paused" or "On Hold" statuses - never "Not in use". Once Asterisk is restarted everything returns to normal.

      While the queues are "hung" we see a lot of the following errors in the logs:

      [Nov 4 09:12:59] WARNING[45096] channel.c: Exceptionally long voice queue length queuing to Local/4066@ctidialed-4ca8;2

      I believe the above message is a symptom rather than the cause as we occasionally get this message throughout the day normally.

      I have done a lot of research on FreePBX/Asterisk forums over the last week to find a solution, but have not found anything that resolved this. I have temporarily renamed retrieve_conf so that FreePBX can't reload and hang the queues on this production server.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                duncanb duncanb
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.