Unity Connection upgrade 8.6.2 -> 9.1.2

dbooth · ‎12-06-2013

I'm testing Unity Conection procedures to v9 having done a fair number of previous version upgrades in the past, and cannot get this upgrade to complete, despite trying all sorts of things to fix. There are one or two references to the error I'm seeing but no definitive answers. The attached file shows some CLI output followed by the upgrade progress. It shows that the host uptime was 11 minutes (i.e. immediately after a system reboot) and that there were no previous upgrade attempts pending. Any pointers as to what going wrong here would be much appreciated. Thanks.

davrojas · ‎12-06-2013

Hello dbooth,

Remember that NTP is very-super-too-much sensitive when it comes to voice technology and any other for that matter.

After checking the traces i believe the root cause is due problems with your NTP source, below is a snippet:

12/06/2013 12:35:07 ntp_one_shot.sh|ntpdate query response: server 192.168.1.1, stratum 2, offset 0.128997, delay 0.02640

6 Dec 12:35:07 ntpdate[11574]: adjust time server 192.168.1.1 offset 0.128997 sec (rc=0).|<:INFO>

12/06/2013 12:35:07 ntp_one_shot.sh|NTP server '192.168.1.1' has minimum stratum (2) and delay (0.02640).|<:INFO>

12/06/2013 12:35:07 ntp_one_shot.sh|ntpdate 192.168.1.1 response: 6 Dec 12:35:07 ntpdate[11584]: the NTP socket is in use, exiting|<:INFO>

12/06/2013 12:35:07 ntp_one_shot.sh|'nptdate' failed to 192.168.1.1 (ntpdate rc=1).|<:WARN>

12/06/2013 12:35:07 ntp_one_shot.sh|ntpdate 192.168.1.1 response: 6 Dec 12:35:07 ntpdate[11588]: the NTP socket is in use, exiting|<:INFO>

12/06/2013 12:35:07 ntp_one_shot.sh|'nptdate' failed to 192.168.1.1 (ntpdate rc=1).|<:WARN>

12/06/2013 12:35:07 ntp_one_shot.sh|ntpdate 192.168.1.1 response: 6 Dec 12:35:07 ntpdate[11592]: the NTP socket is in use, exiting|<:INFO>

12/06/2013 12:35:07 ntp_one_shot.sh|'nptdate' failed to 192.168.1.1 (ntpdate rc=1).|<:WARN>

12/06/2013 12:35:07 ntp_one_shot.sh|File:/usr/local/bin/base_scripts/ntpUtilities.sh:559, Function: notification(), NTP time synchronization failed for NTP server(s) (192.168.1.1). Verify the network connectivity, delay and jitter to the external NTP server(s) and that the NTP server(s) are operational. Use CLI 'utils ntp status' to verify NTP server status.|<:ERROR>

So at the end it uses up your hardware clock:

12/06/2013 12:35:07 ntp_one_shot.sh|NTP time snchronization successful.|<:INFO>

12/06/2013 12:35:08 ntp_one_shot.sh|Successfully set the HW clock to the system clock.|<:INFO>

Recommendation is to use a different NTP source or fix the one in place =)

Sincerely,

(= DAVID =)