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

Reload failed because retrieve_conf encountered an error: 255

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 13
    • Fix Version/s: 13
    • Component/s: Asterisk Logfiles
    • Labels:
      None
    • ToDo:
    • Asterisk Version:
      14.0.2

      Description

      FreePBX 13.0.188.9

      On a fresh install, I deleted the DADHI trunk and successfully applied the change.

      Then I went to Asterisk Logfile Settings, set Log Queues=No, deleted the console and full log definitions, and then clicked Submit. Upon clicking Apply Config, I got the following errors:

      Reload failed because retrieve_conf encountered an error: 255
      click here for more info

      1 error(s) occurred, you should view the notification log on the dashboard or main screen to check for more details.

      Reload failed because retrieve_conf encountered an error: 255
      exit: 255
      Unable to continue. implode(): Invalid arguments passed in /var/www/html/admin/modules/logfiles/functions.inc.php on line 215
      #0 [internal function]: Whoops\Run->handleError(2, 'implode(): Inva...', '/var/www/html/a...', 215, Array)
      #1 /var/www/html/admin/modules/logfiles/functions.inc.php(215): implode(',', NULL)
      #2 /var/www/html/admin/libraries/BMO/DialplanHooks.class.php(95): logfiles_get_config('asterisk')
      #3 /var/lib/asterisk/bin/retrieve_conf(866): FreePBX\DialplanHooks->processHooks('asterisk', Array)
      #4

      {main}

      Critical Errors found

      Please check for errors in the notification section

      retrieve_conf failed, config not applied

      Reload failed because retrieve_conf encountered an error: 255

      No amount of retries or reboots will allow Apply Config to succeed (the same errors are repeated).

      /etc/asterisk/asterisk.conf and /etc/freepbx.conf and amportal.conf exist.

      Disabling the Asterisk Logfiles modules eliminates the error, but as soon as the module is re-enabled, the problem returns.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jfinstrom James Finstrom
                Reporter:
                reraikes RonR
              • 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.