Following errors found in log files. Are these serious or can be ignored.
Install of Asterisk-perl complete!
<<>> Modifying services
error reading information on service avahi-daemon: No such file or directory
error reading information on service ppoe-server: No such file or directory
<<>> Installing and enabling Music on hold
cp: cannot stat `/var/pbx_load/mohfix.tar.gz': No such file or directory
Untarring mohfix.tar.gz file
tar (child): mohfix.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
You might need to modify /etc/asterisk/vm_email.inc manually
Adjusting File Permissions..
SETTING FILE PERMISSIONS
Permissions OK
Done
done with apply_conf.sh
creating missing #include files..sudo: sorry, you must have a tty to run sudo
Error code 1: trying to create empty file /etc/asterisk/meetme_additional.conf
sudo: sorry, you must have a tty to run sudo
Error code 1: trying to create empty file /etc/asterisk/musiconhold_custom.conf
sudo: sorry, you must have a tty to run sudo
Error code 1: trying to create empty file /etc/asterisk/musiconhold_additional.conf
sudo: sorry, you must have a tty to run sudo
Error code 1: trying to create empty file /etc/asterisk/queues_general_additional.conf
sudo: sorry, you must have a tty to run sudo
Error code 1: trying to create empty file /etc/asterisk/queues_custom_general.conf
sudo: sorry, you must have a tty to run sudo
Error code 1: trying to create empty file /etc/asterisk/queues_custom.conf
sudo: sorry, you must have a tty to run sudo
Error code 1: trying to create empty file /etc/asterisk/queues_additional.conf
sudo: sorry, you must have a tty to run sudo
Error code 1: trying to create empty file /etc/asterisk/queues_post_custom.conf
OK
Performing some more configuration requirements
<<D>> CONFIGURING DAHDI_CFG -vvvvv -s -f -d5
DAHDI Tools Version - 2.6.2
Notice: Configuration file is /etc/dahdi/system.conf
line 0: Unable to open master device '/dev/dahdi/ctl'
1 error(s) detected
I have still gone ahead and run the incrediblepbx11 script.
-
Symlink from modules failed
retrieve_conf failed to sym link:
/etc/asterisk/logger.conf from core/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.
Added 40 minutes ago
(retrieve_conf.SYMLINK)
This error after module admin update. Tried to reboot and still this error exist.
-
Could not reload FOP server
Could not reload the FOP operator panel server using killall -HUP op_server.pl. Configuration changes may not be reflected in the panel display. If the FOP module was just installed you may have to retart Asterisk with the "amportal restart" command for the FOP server to run.
Added 6 minutes ago
(freepbx.reload_fop)