TIPS iPBX13-13 Warning Messages after Restore

[geopeterwc]

On an installed and working iPBX13-13 system on a cloud VPS, I get the following notice: "Critical Errors found" and "Symlink from modules failed". Clicking on the warning message, I get the following:

retrieve_conf failed to sym link:
   /etc/asterisk/cel.conf from cdr/etc (Already exists, linked to something else)
   /etc/asterisk/cel_odbc.conf from cdr/etc (Already exists, linked to something else)
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.

The message first appeared after this VPS server was restored from another working iPBX13-13 system, using the built-in FreePBX backup/restore tools.

The iPBX13-13 seems to be operating normally at this time. If I reboot the server, the error goes away away for several hours.

What's up with this. Should I 'worry' about it?

/Pete./

 

[Eliad]

On an installed and working iPBX13-13 system on a cloud VPS, I get the following notice: "Critical Errors found" and "Symlink from modules failed". Clicking on the warning message, I get the following:

retrieve_conf failed to sym link:
   /etc/asterisk/cel.conf from cdr/etc (Already exists, linked to something else)
   /etc/asterisk/cel_odbc.conf from cdr/etc (Already exists, linked to something else)
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.

The message first appeared after this VPS server was restored from another working iPBX13-13 system, using the built-in FreePBX backup/restore tools.

The iPBX13-13 seems to be operating normally at this time. If I reboot the server, the error goes away away for several hours.

What's up with this. Should I 'worry' about it?

/Pete./

I got the same error too.
First make a backup just in case.
Then delete those files and reboot the system.
This worked for me.