retrieve_Conf failed, config not appied

Beta Program Issues
21

Yeah, unfortunately that is a different kind of problem and I’ve fixed those issues. On the r11760 mod, how do I apply that diff to try that? Though I think it has more to do with the undefined variables than it does with the AUTH.

I have applied Core beta2.1 and that hasn’t helped.

By the way, excited to hear another training happening, go to see if I can get myself and one of my employees over there. Cleveland is tough for us west coasters, but we’ll see what we can do.

22

you can just grab the whole from svn and replace the current one.

Otherwise: patch original_file patch_file

where the patch file is the content of the diff.

23

Got that applied, so the message about AUTH is not showing up anymore, but the other issues about the undefined variable are still there and causing the problem. I’ve compared files to my other systems, and even tried copying one over and no difference.

24

I renamed chan_dahdi.conf and then generated a new file from the GUI. The message has gone.

T

25

you must have had a chan_dahdi.conf file already there. Either remove it or remove the module. FreePBX does not provide a chan_dahdi.conf file except through the optional Digium module.

26

I just did the latest upgrade on both my boxes. The one running asterisk 1.4 is fine but I am getting the following warning on the 1.8 box:

Error Symlink from modules failed
Ignore this
retrieve_conf failed to sym link:
   /etc/asterisk/chan_dahdi.conf from dahdiconfig/etc
This can result in FATAL failures to your PBX. If the target file exists and not identical, the symlink will not occur and you should rename the target file to allow the automatic sym link to occur and remove this error, unless this is an intentional customization.
Added 8 seconds ago
(retrieve_conf.SYMLINK)
27

Not quite sure what might be going on. There were some changes to fix some localization things that touched the gui_auth.php file but I don’t see how they could be at all related (though I did make a mod r11760 to address the warning which I also don’t quite see why you would be calling gui_auth.php from retrieve_conf.

28

I have put in a trouble ticket under the “PAID” support plan.

Hopefully this will get corrected.

Thanks,

Tim

29

It appears the manager settings in manager.conf are:

[AMPMGRUSER]
secret = AMPMGRPASS

and in amportal.conf are:
AMPMGRUSER=admin
AMPMGRPASS=pzK75gZYBxPa

The settings you have in manager.conf definitely look off, it looks like the variable names got put in for the actuall names. Also, as of 2.9, this should now be controlled from the advanced settings module rather than individually in the files. Obviously these are not matching and are causing you a problem.

30

What lines are the “manager credentials” ?

This is what they are:

; AMI - Asterisk Manager interface
;
; FreePBX needs this to be enabled. Note that if you enable it on a different IP, you need
; to assure that this can’t be reached from un-authorized hosts with the ACL settings (permit/deny).
; Also, remember to configure non-default port or IP-addresses in amportal.conf.
;
; The AMI connection is used both by the portal and the operator’s panel in FreePBX.
;
; FreePBX assumes an AMI connection to localhost:5038 by default.
;
[general]
enabled = yes
port = 5038
bindaddr = 0.0.0.0
displayconnects=no ;only effects 1.6+

[AMPMGRUSER]
secret = AMPMGRPASS
deny=0.0.0.0/0.0.0.0
permit=127.0.0.1/255.255.255.0
read = system,call,log,verbose,command,agent,user,config,command,dtmf,reporting,cdr,dialplan,originate
write = system,call,log,verbose,command,agent,user,config,command,dtmf,reporting,cdr,dialplan,originate

#include manager_additional.conf
#include manager_custom.conf

And then:

This file is part of FreePBX.

FreePBX is free software: you can redistribute it and/or modify

it under the terms of the GNU General Public License as published by

the Free Software Foundation, either version 2 of the License, or

(at your option) any later version.

FreePBX is distributed in the hope that it will be useful,

but WITHOUT ANY WARRANTY; without even the implied warranty of

MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the

GNU General Public License for more details.

You should have received a copy of the GNU General Public License

along with FreePBX. If not, see http://www.gnu.org/licenses/.

This file contains settings for components of FreePBX

This file will be used to define the initial configuration installed

by the install_amp installation program, which can also obtain some

of this interactively.

Ths file should be writeable by the httpd user (usually asterisk for

FreePBX installations). Once running, FreePBX will maintain these settings

in a database and this file will be overwritten. It will also generate

a based freepbx.conf configuration file, usually in /etc, that will

be used to bootstrap FreePBX and any associated programs. The content

of that file will include the core database credentials and path

information needed to bootstrap FreePBX.

Once installed and running properly out of the database, this file

will be overwritten to include all the configuration settings specified

in the Advanced Settings page of FreePBX and made available here for

potential outside applications that may require access to some of these

parameters. This will be maintained for a transitionary period to give

the eco system time to conform to the new mode of setting configurations.

The freepbx.conf file can also be specified in an evnironment variable:

FREEPBX_CONF

A full path should be specified. This configuration file is formatted as

a very short snippet of PHP, here is an example of what it should look

like:

#-----------------------------------------------------------------

<?php

$amp_conf[‘AMPDBUSER’] = ‘my_db_user’;

$amp_conf[‘AMPDBPASS’] = ‘my_db_password’;

$amp_conf[‘AMPDBHOST’] = ‘localhost’;

$amp_conf[‘AMPDBNAME’] = ‘asterisk’;

$amp_conf[‘AMPDBENGINE’] = ‘mysql’;

$amp_conf[‘datasource’] = ‘’; //for sqlite3

require_once(’/var/www/html/admin/bootstrap.php’);

#-----------------------------------------------------------------

Where the paths and credentials match up with your system. This file

will be created by install_amp for you if not present, or will be

create by the amportal script that is used to start and stop Asterisk

and FOP for FreePBX.

Run /usr/src/AMP/apply_conf.sh after making changes to Asterisk

manager credentials or MySQL CDR credentials to apply the changes to

the corresponding manager.conf and cdr_mysql.conf files.

FreePBX Database configuration

AMPDBHOST: Hostname where the FreePBX database resides

AMPDBENGINE: Engine hosting the FreePBX database (e.g. mysql)

AMPDBNAME: Name of the FreePBX database (e.g. asterisk)

AMPDBUSER: Username used to connect to the FreePBX database

AMPDBPASS: Password for AMPDBUSER (above)

AMPENGINE: Telephony backend engine (e.g. asterisk)

AMPMGRUSER: Username to access the Asterisk Manager Interface

AMPMGRPASS: Password for AMPMGRUSER

AMPDBHOST=localhost
AMPDBENGINE=mysql
AMPENGINE=asterisk
AMPMGRUSER=admin
AMPMGRPASS=pzK75gZYBxPa

AMPBIN: Location of the FreePBX command line scripts

AMPSBIN: Location of (root) command line scripts

AMPBIN=/var/lib/asterisk/bin
AMPSBIN=/usr/local/sbin

AMPWEBROOT: Path to Apache’s webroot (leave off trailing slash)

AMPCGIBIN: Path to Apache’s cgi-bin dir (leave off trailing slash)

AMPWEBADDRESS: The IP address or host name used to access the AMP web admin

AMPWEBROOT=/var/www/html
AMPCGIBIN=/var/www/cgi-bin

AMPWEBADDRESS=x.x.x.x|hostname

FOPWEBROOT=/var/www/html/panel
FOPPASSWORD=passw0rd

This is the default admin name used to allow an administrator to login to ARI bypassing all security.

Change this to whatever you want, don’t forget to change the ARI_ADMIN_PASSWORD as well

ARI_ADMIN_USERNAME=admin

This is the default admin password to allow an administrator to login to ARI bypassing all security.

Change this to a secure password.

ARI_ADMIN_PASSWORD=ari_password

AUTHTYPE=database|none

DEFAULT VALUE: database

Authentication type to use for web admininstration. If type set to ‘database’, the primary

AMP admin credentials will be the AMPDBUSER/AMPDBPASS above.

AUTHTYPE=database

AMPEXTENSIONS=extensions|deviceanduser

Sets the extension behavior in FreePBX. If set to ‘extensions’, Devices and Users are

administered together as a unified Extension, and appear on a single page.

If set to ‘deviceanduser’, Devices and Users will be administered seperately. Devices (e.g.

each individual line on a SIP phone) and Users (e.g. ‘101’) will be configured

independent of each other, allowing association of one User to many Devices, or allowing

Users to login and logout of Devices.

AMPEXTENSIONS=extensions

AMPDBNAME=asterisk
AMPDBUSER=freepbxuser
AMPDBPASS=ZheYYYUtdpov
ASTETCDIR=/etc/asterisk
ASTMODDIR=/usr/lib/asterisk/modules
ASTVARLIBDIR=/var/lib/asterisk
ASTAGIDIR=/var/lib/asterisk/agi-bin
ASTSPOOLDIR=/var/spool/asterisk
ASTRUNDIR=/var/run/asterisk
ASTLOGDIR=/var/log/asterisk

Thanks,

Tim