Start a Conversation

Unsolved

This post is more than 5 years old

S

1366

June 23rd, 2017 01:00

Avamar install pauses waiting for NTP

Hi,

I'm currently deploying an Avamar Gen4T.

EMC are upgrading the Avamar code to 7.3.1, during the install it attempts to connect to the NTP servers but times out.

Running asktime on the Utility node, it also times out.

Running the following command /usr/sbin/ntpdate -d xx.xx.xx.xx

It connects to the NTP server.

root@something:~/#: /usr/sbin/ntpdate -d xx.xx.xx.xx

23 Jun 09:35:43 ntpdate[2730]: ntpdate 4.2.8p8@1.3265-o Mon Jun  6 12:31:21 UTC 2016 (1)

Looking for host xx.xx.xx.xx and service ntp

xx.xx.xx.xx reversed to xx.xx.xxcom

host found : xx.xx.xx.com

transmit(xx.xx.xx.xx)

receive(xx.xx.xx.xx)

transmit(xx.xx.xx.xx)

receive(xx.xx.xx.xx)

transmit(xx.xx.xx.xx)

receive(xx.xx.xx.xx)

transmit(xx.xx.xx.xx)

receive(xx.xx.xx.xx)

server xx.xx.xx.xx, port 123

stratum 5, precision -21, leap 00, trust 000

refid [xx.xx.xx.xx], delay 0.02666, dispersion 0.00006

transmitted 4, in filter 4

reference time:    dcf74e8e.118372ae  Fri, Jun 23 2017  9:23:42.068

originate timestamp: dcf75166.39ab5e47  Fri, Jun 23 2017  9:35:50.225

transmit timestamp:  dcf75166.34214c49  Fri, Jun 23 2017  9:35:50.203

filter delay:  0.02716  0.02666  0.02667  0.02678

         0.00000  0.00000  0.00000  0.00000

filter offset: 0.021447 0.021127 0.021077 0.021019

         0.000000 0.000000 0.000000 0.000000

delay 0.02666, dispersion 0.00006

offset 0.021127

23 Jun 09:35:50 ntpdate[2730]: adjust time server xx.xx.xx.xx offset 0.021127 sec

If I update the NTP.conf file to have the following line

"restrict      -4        default         ignore"

rather than

"restrict       default         ignore"

It works, so is there a bug in the version of NTP code that is currently being run which is ntp-4.2.8p8-47.3

Avamar server version

SUSE Linux Enterprise Server 11 (x86_64)

VERSION = 11

PATCHLEVEL = 3

Regards

Stuart

Update:- I've found this technote which explains the problem I'm having https://emcservice.force.com/CustomersPartners/kA2j0000000RFHxCAO

5 Practitioner

 • 

274.2K Posts

July 17th, 2018 23:00

Another method that also works


Perform the below steps:


1.       Login to the affected node as root user

2.       Stop the ntp daemon

           rcntp stop


1.  Edit /etc/ntp.conf file using vi and perform the following changes:

      a.    change the following line

           restrict default         ignore


               to


           restrict -6 default         ignore


a.    add an extra line in "Local machine restrictions" section

             restrict -6 ::1


1.      Save the changes

2.      Restart the ntp daemon

           rcntp start


(if it's a multi-node, use the mapall lite script to copy the /etc/ntp.conf file to all storage nodes when ntp daemon is stopped)

No Events found!

Top