Asterisk
  1. Asterisk
  2. ASTERISK-17036

[patch] Output of queue_log stopped after several hours

    Details

    • Type: Bug Bug
    • Status: Closed
    • Severity: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Target Release Version/s: 1.8.7.2
    • Component/s: Applications/app_queue
    • Labels:
      None

      Description

      Tested in two systems with Asterisk 1.8.2. After several hours the logger output to queue_log is stopped and there are no more writes of statistics in this file.

      After a reload of the logger module the queue_log output starts working well again but with the loss of the events processed while logger was not wrinting queue_log.

      This affect report statistics of queues, and is very important in call center environments. No effect has been noted with CDR, as CDR works OK. No call lost in CDR, only in Queue_log.

                • ADDITIONAL INFORMATION ******

      In logger.conf:

      queue_log = yes
      queue_log_to_file = yes
      queue_log_name = queue_log

      An example:

      1295004727|1295004638.165|operadora|SIP/501|COMPLETECALLER|9|52|1
      1295435167|NONE|NONE|NONE|CONFIGRELOAD|
      1295435679|1295435652.224|comercial|NONE|ENTERQUEUE||660481917|1

      As can see, after an output of Jabuary 11th, the statistics stopped. After a reload works again.

      No selinux, no errors in messages or full logs. Simply stopped.

      1. backtrace-threads.txt
        27 kB
      2. core-show-locks.txt
        0.4 kB
      3. jira_asterisk_17036_v1.8.patch
        7 kB
        Richard Mudgett
      4. queue_logger.patch
        0.6 kB
        Juan Carlos Valero

        Issue Links

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

          Hide
          Richard Mudgett added a comment - - edited
          Show
          Richard Mudgett added a comment - - edited jira_asterisk_17036_v1.8.patch is the first patch version posted on https://reviewboard.asterisk.org/r/1333
          Hide
          Richard Mudgett added a comment -
          Show
          Richard Mudgett added a comment - jira_asterisk_17036_v1.8.patch committed.
          Hide
          Indreias Ioan added a comment - - edited

          Issue looks to be fixed but not on 1.8.6.0 (installed from Asterisk RPM repo) even that this version was released on 30/Aug/2011 (issue marked as resolve on 10/Aug/2011)
          Strange enough is that the ChangeLog for the last version (1.8.7.0) do not mention that this issue (#18642) was fixed.
          Could somebody confirm the real status of this issue?

          Show
          Indreias Ioan added a comment - - edited Issue looks to be fixed but not on 1.8.6.0 (installed from Asterisk RPM repo) even that this version was released on 30/Aug/2011 (issue marked as resolve on 10/Aug/2011) Strange enough is that the ChangeLog for the last version (1.8.7.0) do not mention that this issue (#18642) was fixed. Could somebody confirm the real status of this issue?
          Hide
          Richard Mudgett added a comment -

          Look above. There is a tab called "Subversion Commits". Clicking on that tab you will see the commit message. The ChangeLog will have that commit message if it is in that version. The Mantis issue 18642 reference is no longer used to reference this issue since the Mantis to JIRA transition. The JIRA reference for this issue is ASTERISK-17036.

          The reason a particular commit is not in a particular revision has to do with when the -rc1 version of an Asterisk version was tagged. If the -rc1 tag was done before an issue fix commit then it will not likely be put in that release version.

          Show
          Richard Mudgett added a comment - Look above. There is a tab called "Subversion Commits". Clicking on that tab you will see the commit message. The ChangeLog will have that commit message if it is in that version. The Mantis issue 18642 reference is no longer used to reference this issue since the Mantis to JIRA transition. The JIRA reference for this issue is ASTERISK-17036 . The reason a particular commit is not in a particular revision has to do with when the -rc1 version of an Asterisk version was tagged. If the -rc1 tag was done before an issue fix commit then it will not likely be put in that release version.
          Hide
          Indreias Ioan added a comment -

          Thanks Richard for sorting this out - it was my confusion between JIRA and Mantis issue IDs.

          Show
          Indreias Ioan added a comment - Thanks Richard for sorting this out - it was my confusion between JIRA and Mantis issue IDs.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development