On Tue, Oct 30, 2012 at 1:58 PM, Kyle Haefner <kyle.haef...@colostate.edu> wrote: > A quick follow-up on the issue of adding a redundant server. > > I did a yum update today (10/30/2012) on the primary server, then > started NTP (just to note, ntpd was not set to auto start in > chkconfig). I did the same on the redundant server and then went > through sipxecs-setup on the redundant node and it completed without > error. So it seams that my problem stemmed from NTP not starting. Is > NTP supposed to start on the primary node after first reboot?
chicken and egg. Currently we configure ntp (including chkconfig) after we get past setup, but apparently we cannot always get past setup until times are in sync. So fix is to configure ntp in setup script AND continue to manage it in system as we are today. Aaron P's problem was not NTP because we checked that. I think setup script didn't set supervisor's auth files correctly. Aaron is off and running, but I'm looking how Aaron could have gotten into this situation. After that i plan to look at fixing ntp issues. _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
