XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 16
    • Fix Version/s: None
    • Component/s: Asterisk Logfiles
    • Labels:
      None
    • Bug Tracker:
      Customer Issue
    • ToDo:
    • Asterisk Version:
      16.17.0
    • Distro Version:
      12.7.8-2104-1.sng7
    • Distro:
      FreePBX Distro

      Description

      Asterisk is not writing the queue_log file however if I do a reload on asterisk it last for about 24 hours as far as I can tell. A system restart works for about a week, I could be wrong with the numbers because its time consuming to monitor this. Prior to opening this ticket I did a screen shot of the var/log/asterisk folder and the queue_log file was empty, after I reload then it writes to the file as seen in the captures I attach. This started after a May 1st modules and system updates as follows; 

      backup 15.0.10.51 (current: 15.0.10.48)

      cel 15.0.15.12 (current: 15.0.15.11)

      certman 15.0.42 (current: 15.0.39)

      filestore 15.0.3.13 (current: 15.0.3.12)

      findmefollow 15.0.25 (current: 15.0.24)

      firewall 15.0.8.14 (current: 15.0.8.9)

      framework 15.0.17.34 (current: 15.0.17.32)

      paging 15.0.4.30 (current: 15.0.4.29)

      presencestate 15.0.11 (current: 15.0.10)

      sysadmin 15.0.21.46 (current: 15.0.21.28)

      timeconditions 15.0.15.10 (current: 15.0.15.9)

      voicemail 15.0.18.31 (current: 15.0.18.25)

      sangoma-pbx.noarch 2104-1.sng7 (current: 2012.1.sng7)

       

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  sylwat sylwat
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    NextupJiraPlusStatus

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