Reload failed because retrieve_conf encountered an error: 255

General Help
1

Problem after upgrade from 2.5 to version 2.6

Reload failed because retrieve_conf encountered an error: 255
Added 9 minutes ago
(freepbx.RCONFFAIL)

More information:

Checking for PEAR DB…OK
Checking for PEAR Console::Getopt…OK
Checking for /etc/amportal.conf …OK
Bootstrapping /etc/amportal.conf …OK
Parsing /etc/amportal.conf …OK
Parsing /etc/asterisk/asterisk.conf …OK
Connecting to database…OK
Connecting to Asterisk manager interface…OK
PHP Fatal error: Call to undefined function dbug() in /var/www/html/admin/modules/setcid/functions.inc.php on line 130

2

I am running FreePBX 2.8 and I was updating modules to the latest version when I got the error 255 response. The “FreePBX framework” module was the issue and I had to drop back from 2.8.0.2 to 2.7.0.0, per the directions on the module manager.

I check for an update and module version 2.8.0.3 was already up and it works, so someone already found the issue and fixed it.

I thought you would want to know.

exit: 255

Checking for PEAR DB…OK
Checking for PEAR Console::Getopt…OK
Checking for /etc/amportal.conf …OK
Bootstrapping /etc/amportal.conf …OK
Parsing /etc/amportal.conf …OK
Parsing /etc/asterisk/asterisk.conf …OK
Connecting to database…OK
Connecting to Asterisk manager interface…OK
PHP Warning: Invalid argument supplied for foreach() in /var/www/html/admin/modules/dahdiconfig/functions.inc.php on line 779

Added to globals: … // lots of stuff here, but we don’t need it for this post

PHP Fatal error: Call to undefined method extensions::addSectionComment() in /var/www/html/admin/modules/core/functions.inc.php on line 1728

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

3

Module SetCID is not supported (if I remember correctly). Disable the module and try again.

Edit later: Nope, that is a leftover in the code that should not be there.
That is the root of the error you get.

I will try to get that fixed asap.

4

Upgraded to 2.7 out of curiosity… problem went away.

5

Yes, that would also worked as dbug is in the framework from 2.7 and later.