During the install script, the AMM looks for the programmed NTP server. If it does not find a NTP server programmed, or the NTP that is used, has to much drift or is not able to sync off of it, the install script will fail. The rest of the programming will not complete until the NTP server issue is resolved. Get another NTP server and reprogram.
From the Install logs in /tmp
cat AMM_Install_2017-01-01_12:00.log
Checking for xfsprogs component ......................... [ OK ]
Checking for linux "dialog" component ................... [ OK ]
Checking for ntp installation / configuration ...........
Initial ntp check failed, attempting ntpd -gq to force sync
(may take up to 2 minutes)
Shutting down ntpd ...................................... [ OK ]
ntpd: no servers found
Starting ntpd ........................................... [ OK ]
Rechecking for ntp installation / configuration ......... [FAILED]
Avaya Multimedia Messaging depends on system clock accuracy.
....start of ntpstat output:
unsynchronised
time server re-starting
polling server every 8 s
unsynchronised
time server re-starting
polling server every 8 s
....end of ntpstat output
Please configure ntp for an accurate system clock
Once configured, ntp synchronization time can be shortened by:
Adding "iburst" after each time server FQDN/address in /etc/ntp.conf
sudo service ntpd stop
sudo ntpd -gq
sudo service ntpd start
Checking for SeLinux to be disabled ..................... [ OK ]
Checking disk space on ...
Found 38474524 KB. Require 209715200 KB
Disk Space Check ........................................ [WARNING]
Checking for openssl libraries ......................... [ OK ]
Checking for zlib libraries ............................ [ OK ]
Installation Check Complete ............................. [FAILED]
