ntpdate relata falha após obter com sucesso o deslocamento

0

ntpdate -d às vezes imprime no server suitable de erro, embora tenha se conectado com êxito ao servidor e imprimido o deslocamento. Por quê?

Nos meus scripts, preciso distinguir erros de rede e este. Como forçá-lo a sair com status zero?

bom:

# ntpdate -d 10.3.2.67
12 Nov 13:23:21 ntpdate[6565]: ntpdate [email protected] Mon Jul 15 09:22:50 UTC 2013 (1)
Looking for host 10.3.2.67 and service ntp
host found : ec-prod-app-1
transmit(10.3.2.67)
receive(10.3.2.67)
transmit(10.3.2.67)
receive(10.3.2.67)
transmit(10.3.2.67)
receive(10.3.2.67)
transmit(10.3.2.67)
receive(10.3.2.67)
server 10.3.2.67, port 123
stratum 4, precision -21, leap 00, trust 000
refid [10.3.2.67], delay 0.02574, dispersion 0.00000
transmitted 4, in filter 4
reference time:    d9eee40d.738ce7c1  Thu, Nov 12 2015 13:10:21.451
originate timestamp: d9eee719.a97c80cf  Thu, Nov 12 2015 13:23:21.662
transmit timestamp:  d9eee719.a9245fa8  Thu, Nov 12 2015 13:23:21.660
filter delay:  0.02579  0.02586  0.02574  0.02574
         0.00000  0.00000  0.00000  0.00000
filter offset: 0.001251 0.001187 0.001244 0.001243
         0.000000 0.000000 0.000000 0.000000
delay 0.02574, dispersion 0.00000
offset 0.001244

12 Nov 13:23:21 ntpdate[6565]: adjust time server 10.3.2.67 offset 0.001244 sec

ruim:

# ntpdate -d 10.3.2.68
12 Nov 13:23:24 ntpdate[6566]: ntpdate [email protected] Mon Jul 15 09:22:50 UTC 2013 (1)
Looking for host 10.3.2.68 and service ntp
host found : ec-prod-app-2
transmit(10.3.2.68)
receive(10.3.2.68)
transmit(10.3.2.68)
receive(10.3.2.68)
transmit(10.3.2.68)
receive(10.3.2.68)
transmit(10.3.2.68)
receive(10.3.2.68)
10.3.2.68: Server dropped: strata too high
server 10.3.2.68, port 123
stratum 16, precision -20, leap 11, trust 000
refid [10.3.2.68], delay 0.02574, dispersion 0.00000
transmitted 4, in filter 4
reference time:    00000000.00000000  Mon, Jan  1 1900  3:00:00.000
originate timestamp: d9eee71b.a14c710c  Thu, Nov 12 2015 13:23:23.630
transmit timestamp:  d9eee71c.5e083201  Thu, Nov 12 2015 13:23:24.367
filter delay:  0.02577  0.02574  0.02574  0.02577
         0.00000  0.00000  0.00000  0.00000
filter offset: -0.73732 -0.73732 -0.73733 -0.73734
         0.000000 0.000000 0.000000 0.000000
delay 0.02574, dispersion 0.00000
offset -0.737324

12 Nov 13:23:24 ntpdate[6566]: no server suitable for synchronization found
    
por basin 12.11.2015 / 11:33

1 resposta

0

Você percebeu o seguinte:

10.3.2.68: Server dropped: strata too high

E o:

stratum 16, precision -20, leap 11, trust 000

Linhas na sua saída?

O cliente ntp acha que a fonte de tempo não é sensata o suficiente (ou seja, não está sincronizando com um servidor de estrato inferior) o suficiente

    
por 12.11.2015 / 11:44

Tags