SymLink fault in FreePBX 2.8 with Elastix 2.0

Discussion in 'General' started by gbrook, Sep 19, 2010.

  1. gbrook

    Joined:
    Aug 29, 2007
    Messages:
    74
    Likes Received:
    0
    Error Symlink from modules failed
    retrieve_conf failed to sym link:
    /etc/asterisk/sip_notify.conf from core/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 16 hours, 54 minutes ago
    (retrieve_conf.SYMLINK)

    Any suggestions how to fix this and is it as bad as it suggests?

    Cheers
    Garry
     
  2. chucky

    Joined:
    Jun 29, 2010
    Messages:
    4
    Likes Received:
    0
    I have the same problem following a module upgrade in FreePBX and am also interested as to whether there is a simple fix without breaking things further.
     
  3. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    as it says:-


    " . . .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. . . ."

    if you intentionally changed it then don't:-

    mv /etc/asterisk/sip_notify.conf /etc/asterisk/sip_notify.conf.backup


    It is largely a minor bug in FreePBX, Elastix does not endorse FreePBX 2.8 and some newer library files in FreePBX 2.8 are in conflict with the current Elastix FreePBX libraries and will screw you up rotten if you use both the broken "embedded" FreePBX and your self installed updated FreePBX 2.8, I guess that counts as a major Catch-22. :)
     

Share This Page