Symlink From Modules Failed

Performed a fresh install of .iso image this afternoon.

After the initial boot up and setting passwords, I found the following error in the FreePBX Notices Pane:

retrieve_conf failed to sym link:
/etc/asterisk/logger.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 5 minutes ago
(retrieve_conf.SYMLINK)

Suggestions? Further information needed?

Hi Depster,

i think some version info might be usefull here.
please supply the version of : Distro, Asterisk and FreepBX

Richard.

This is from the FreePBX Distro v1.8.1.2. FreePBX 2.9.0rc1.3 and Asterisk 1.8.3.2

Depster

Can you tell me what is in your /etc/asterisk/logger.conf file? I think this is related to some changes made in logger with the latest 2.9RC


[general]
dateformat=%F %T

[logfiles]
; Format is "filename" and then "levels" of debugging to be included:
;    debug
;    notice
;    warning
;    error
;    verbose
;
console => notice,warning,error
full => notice,warning,error,debug,verbose

Ooops that was my fault. Made some changes today for logger.conf and tested it on our dev system with no problems but on fresh FreePBX 2.9 install it does not run a migration to take the old logger.conf and move it to the custom files.

I went ahead and made the changes to the current 1.8.1.2 that everyone is playing with that should resolve the issue, for any one who downloads it moving forward. I bumped the version to 1.8.1.2-1

To fix you problem on your existing system do this.

SSH into the box.

cd /usr/tmp
wget http://upgrades.freepbxdistro.org/1.8.1.2/upgrade-1.8.1.2-1.sh
chmod +x upgrade-1.8.1.2-1.sh
./upgrade-1.8.1.2-1.sh
rm /usr/tmp/upgrade-1.8.1.2-1.sh

Let me know if that fixes it.

The update fixed the issue.

Thanks.

Ok that is good. Sorry about not catching that before we went live.

FreePBX 2.10.0. *upgraded from FreePBX 2.10 (RC)
Asterisk 1.8.11.0
AsteriskNOW 2.01 beta 1 32-bit *distro installed

FreePBX System Status:
<citeSymlink from modules failed
Ignore this
retrieve_conf failed to sym link:
/etc/asterisk/logger.conf from core/etc (Already exists, not a link)
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 12 hours, 32 minutes ago
(retrieve_conf.SYMLINK)

Tony Lewis (tonyclewis) did provide this solution, but for an older version:

cd /usr/tmp
wget http://upgrades.freepbxdistro.org/1.8.1.2/upgrade-1.8.1.2-1.sh
chmod +x upgrade-1.8.1.2-1.sh
./upgrade-1.8.1.2-1.sh
rm /usr/tmp/upgrade-1.8.1.2-1.sh

Could someone help me out?

I was really hoping that someone could help me out with the above issue!

FreePBX 2.10.0.4
Asterisk 1.8.11.0

Firstly logged via ssh and compared two files:
"/etc/asterisk/logger.conf"
"/var/www/html/admin/modules/core/etc/logger.conf"
In my case they were identical.
So I did as following:

rm -rf /etc/asterisk/logger.conf
ln -s /var/www/html/admin/modules/core/etc/logger.conf /etc/asterisk/logger.conf
amportal reload

Regards.

Thanks for taking your time and providing me with your working solution.

Regards Seiern

the latest beta distro (FreePBX-1.1005.210.62) has the same issue, corymar’s trick did help here too :slight_smile:

Regards

That did the trick for me too!

Distribution: (Redhat CentOS release 5.8 (Final))
FreePBX version: (2.10.1)

Thank you!