Ticket #2864 (closed Bugs: invalid)

Opened 5 months ago

Last modified 5 months ago

BUG: Upgrading brand new 2.3 to 2.4 ended up with a "retrieve_conf failed to symlink the /etc/asterisk/sip.conf file from modules" error

Reported by: stevedavies Assigned to: p_lindheimer
Priority: minor Milestone: 2.5
Component: Core Version: 2.4.0
Keywords: Cc:
Confirmation: Unreviewed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description (Last modified by p_lindheimer)

Hi, I'm evaluating Elastix 1.1, which comes with FreePBX 2.3. I'm trying to test the end-user experience. With no tinkering behind the scenes at all, I managed to end up with an "retrieve_conf failed to sym link the /etc/asterisk/sip.conf file from modules" error in the FreePBX status. My steps:

  1. New install of Elastix 1.1
  2. Created one SIP extension.
  3. In FreePBX "unembedded", "Tools", I first upgraded everything to 2.3 latest
  4. I then installed the 2.4 upgrade tool
  5. Executed that, then, following instructions, did FreePBX upgrade, then did all the other modules.

The result is the error "retrieve_conf failed to sym link the /etc/asterisk/sip.conf file from modules" showing in then FreePBX Notices. Looking in the /etc/asterisk directory I see a sip.conf file. I understand this should have been replaced by a symlink to /var/www/html/admin/modules/core/etc/ I think this should have happened automatically - an end user is now stuck because manual manipulation is required in the shell. I guess that all of extensions.conf, features.conf, sip.conf and iax.conf are supposed to be symlinks to /var/www/html/admin/modules/core/etc? In my case only features.conf ended up as a symlink with a features.conf.0. For the other files I have no ".0" file. Hope this bug report is helpful. Steve Davies

Change History

06/25/08 07:12:12 changed by stevedavies

Hi again,

Also, /var/lib/asterisk/bin/fax-process.pl

Steve

06/25/08 07:37:53 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to invalid.
  • description changed.
  • milestone changed from Cut Line to 3.0.

Steve,

thanks for the report. This is actually an Elastix bug that I had reported to them some time back. Those files should have been symlinked in 2.3 but are installed wrong in Elastix. The symlink mechanism will not do a simlink if it detects the real file in /etc/asterisk as a protection for users who want to override what is in the module. The reason that features.conf was done is because this was an actual transition from 2.3 to 2.4 and therefore FreePBX did did the symlink automatically. The same thing would have happened with the other files had the upgrade been from an ealier version of FreePBX.

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads