Config files not updating
Submitted by EagleLink on Sun, 07/15/2007 - 6:10pm.
HELP, I'm having a bit of a problem. I've been trying to modify trunks and not having any luck with the changes working. Then I realized, by editing the extensions files, that the info is not being saved in the files in /etc/asterisk. By this I mean, when I edit the files, it still shows the old info. Very odd! But when I edit the files manually and do "amportal restart" everything is good. However it is also not reading the info from these files, as when I edit them manually then go into freepbx and reload the trunks page, it does not show the new info, just the old info. Is there a way to verify that freepbx is reading/writing the correct files? If I chance settings in freepbx, then reload the pages, the changes are saved in there, just not in the actual files in /etc/asterisk.
Thanks for any help,
Jeff
Don't manually edit anything
Sun, 07/15/2007 - 8:28pm
Don't manually edit anything with a _additional.conf tagged on the file.
It will be overwritten by the FreePBX GUI.
Any changes that you make in any .conf file, won't reflect in the FreePBX gui either. System doesn't read those config files. FreePBX stores everything in a mySQL database, and all entries (for argument sake) must be done through the GUI. Once these entries are done, the FreePBX system generates those files and triggers Asterisk to load them into its configuration.
If you have a specific thing that needs to be entered into a standard asterisk .conf file, you should be able to place it in via the FreePBX gui. If you are unsure, post the information and we can tell you how to enter it (just change/hide any vital IP and/or password information first)
you're not understanding me
Sun, 07/15/2007 - 8:39pm
Maybe you're not understanding what I'm saying, freepbx is not writing my changed to the .conf files. Therefore, I HAVE TO MANUALLY EDIT THEM! I did not post a message asking what files I can, or cannot modify, I posted a message asking how I can solve this problem. I am familiar with the different config files. _trixbox files are overwritten with upgrades, _additional files are overwritten, or are supposed to be, by freepbx when you change the config via the GUI, and _custom files are there for you to edit and make your own modifications.
I would appreciate it if anyone call tell me how to make sure freepbx is writing to the correct configuration files.
Jeff
You don't need to go off on
Sun, 07/15/2007 - 11:06pm
You don't need to go off on someone trying to help.
It NOT clear in your original post to me what you were trying to do, you are kind of all over the place. AND for the record, you only asked ONE question: "Is there a way to verify that freepbx is reading/writing the correct files? "
-FreePBX does not read those files ever. You can verify that they are being written by time of day stamp.
Now, to help trouble shoot your problem. What have you changed prior to this.
Have you changed passwords? Have you changed any permissions? Have you updated anything? Yum / Or module?
Have you tried a restart of the system?
I thought it was very clear
Mon, 07/16/2007 - 6:03am
Ok, first of all I thought it was very clear. And as you said, I only asked one question, but did not get an answer to it even now. Your answer is the time of day stamp, that does not answer my question. Time of day stamp will let me know when it was last written, not if freepbx is writing to the correct files. What I'm looking for is a more advanced user to give me an answer of possibly where I might look in some configuration files or something to find out if freepbx is writing to the correct files in the correct directories. And if this is all internal in freepbx, which I suspect it is not and that there is some kind of config file, then there is a bug with freepbx itself. And as far as I know, freepbx is not an actual program, but just web pages or more likely to be called scripts. So somehow somewhere there must be a way to verify the path and files it is writing to. And for anybody that for some reason does not understand my first message, here is a more simple diagram.
Open freepbx GUI => Change Trunk Settings => Click Red Bar => Nothing is changed in sip_additional.conf
And yes, I even tried "amportal restart" and rebooting the server.
This is what works
Edit sip_additional.conf manually => change settings => save files => amportal restart
So far the only thing anyone has mentioned that I may not have understood was that freepbx does not read these files, so I'm assuming somehow it stores this information somewhere else. Can anyone tell me where this information is stored before writing to conf files? Perhaps it is a bug that is not writing these files when I click the red bar.
Thanks for any help.
Jeff
http://freepbx.org/forums/vie
Mon, 07/16/2007 - 3:08pm
http://freepbx.org/forums/viewtopic.php?p=1160&highlight=write+co...
You might have better luck at freePbx forums.....
uninstall blacklist
Tue, 07/17/2007 - 5:16pm
Well, I have the same probelm with trixbox 2.0 after updating all the modules. I eventually end up reinstalling trixbox2.2 and again updating the modules result the same thing.
None of the configuration files was updating, except voicemail.conf. When I tried using #retrieve_conf, i get the following output.
[root@asterisk1 asterisk]# /var/lib/asterisk/bin/retrieve_conf
Content-type: text/html
X-Powered-By: PHP/4.3.11
Checking for PEAR DB..OK
Checking for PEAR Console::Getopt..OK
Checking for /etc/amportal.conf..OK
Reading /etc/amportal.conf..OK
Reading /etc/asterisk/asterisk.conf..OK
Connecting to database..OK
Connecting to Asterisk manager interface..OK
Fatal error: Cannot instantiate non-existent class: ext_waitexten in /var/www/html/admin/modules/blacklist/functions.inc.php on line 66
It seems to me there is a problem with the new update of blacklist modules. So, I have to UNSTALL the blacklist modules and it works !!! Well, it seems to be bug for me. Anyway, hoping to be resolved soon.
Blacklist Module
Tue, 07/17/2007 - 5:33pm
I tried uninstalling the blacklist module, but when I run /var/lib/asterisk/bin/retrieve_conf it still shows the problem with the blacklist module. This can be very aggrivating to someone who relies on the phone system to be working properly all the time. I just installed 2.2 deom ISO and same thing after updating all the modules. How can I actually remove the blacklist module? Do I have to delete the file? I do not use the blacklist module right now, but added it for future use.
Well, i guess, there is
Tue, 07/17/2007 - 8:08pm
Well, i guess, there is option to remove or uninstall the blacklist module. I tried disabling the blacklist module but it did not work, so I uninstalled the module.
By the way, have you changed your username and password at manager.conf, /etc/amportal.conf and crd_mysql.conf (??). ? If you have set the password don't put special character. I read somewhere in other post that special character on password barred freePBX from writing to the configuration file.
PS: I forget the configuration filename now crd_mysql.conf or something like that, as I am not in office, anyway, you can figure it out.
Reported to freepbx and fixed
Thu, 07/19/2007 - 7:49pm
After finding on my own the 3 lines that had the problem, I reported it to freepbx bug tracker. http://www.freepbx.org/trac/ticket/2107 There is already an update to the blacklist module available fixing this problem.
Thanks to anybody that tried to help.
Blacklist Fix(?)
Wed, 07/25/2007 - 5:14pm
Me too - update to Blacklist 1.1.3.1 did NOT fix the problem
Wed, 07/25/2007 - 10:15pm
I also just recently updated all my modules and the problem exists. Removing Blacklist in its entirety fixed the problem. To be honest, the blacklist feature has never functioned very well. Many times I have added numbers to the "blacklist" but either they disappear or just are ignored. Its probably better not being active.
Update to Blacklist definitely causes the problem
Mon, 07/30/2007 - 8:11pm
I just got done updating a new server and was having all kinds of problems getting the updates to take. I checked and the servers that were exhibiting this problem were all on 1.1.3.1. I uninstalled it from all of my servers, and they are all updating correctly again.
I had an older version of the module installed on a couple other servers and it didn't cause these problems. Removing it from the server altogether hasn't caused any problems and not having allows me to not waste another couple of hours trying to figure out what the problem was. This has cost me about $450 in lost time; to the author of the update, I'd like to say "How about some testing next time?"
Thanks mikesotov
Wed, 08/15/2007 - 5:41pm
this and more
Fri, 10/19/2007 - 10:05pm
I had this problem along with several others. The solution here did not work, but here is what did.
Upgraded FreePBX (even though I intentionally left the Beta turned off that is what I ended up with, a beta.
Upgraded at least two MySQL components
A database geek removed some offending data from my database where a SIP extension was entered as a name. (although this had been deleted from the GUI it remained in the database)
Upgraded free PBX modules as indicated within freepbx.
This was a major headache and it has now been working fine for the first time in 2 months!
Member Since:
2006-11-26