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

Dashboard Cron errors when asterisk isn't running

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 13
    • Fix Version/s: 14
    • Component/s: System Dashboard
    • Labels:
      None
    • ToDo:

      Description

      The following cron email is sent from dashboard when asterisk is not running

       

      
      Exception: Asterisk is not connected in file /usr/src/freepbx/framework/amp_conf/htdocs/admin/libraries/php-asmanager.php on line 236
      Stack trace:
        1. Exception->() /usr/src/freepbx/framework/amp_conf/htdocs/admin/libraries/php-asmanager.php:236
        2. AGI_AsteriskManager->send_request() /usr/src/freepbx/dashboard/classes/AsteriskInfo.class.php:27
        3. AsteriskInfo2->get_channel_totals() /usr/src/freepbx/dashboard/classes/SysInfo.class.php:94
        4. SysInfo->getAstInfo() /usr/src/freepbx/dashboard/classes/SysInfo.class.php:55
        5. SysInfo->getSysInfo() /usr/src/freepbx/dashboard/Dashboard.class.php:211
        6. Dashboard->genSysInfo() /usr/src/freepbx/dashboard/Dashboard.class.php:245
        7. Dashboard->getSysInfo() /usr/src/freepbx/dashboard/Dashboard.class.php:193
        8. Dashboard->runTrigger() /usr/src/freepbx/dashboard/scheduler.php:35
      
      

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jphilip Philip Joseph
                  Reporter:
                  jfinstrom James Finstrom
                • 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.