[Sa] ntp проблем отново

[Vladimir Germanov]

On 1 March 2012 13:09, Vladimir Germanov <v.germanov at gmail.com> wrote:
> On 1 March 2012 12:48, "Боби Б." <606u at dir.bg> wrote:
>> On 01.03.2012, at 12:37, Vasil Kolev <vasil at ludost.net> wrote:
>>> В 09:56 +0200 на 01.03.2012 (чт), Vladimir Germanov написа:
>>>
>>>> Благодаря за информацията. Ами аз рестартирах също няколко пъти. В
>>>> момента nagios-а пак пуска ALERT:
>>>> Това ми изписва от chek_ntp
>>>>
>>>> u7 at phyllis:~$ /usr/lib/nagios/plugins/check_ntp -H u7.ludost.net -v
>>>> sending request to peer 0
>>>> response from peer 0: offset -0.7734282017
>>>> sending request to peer 0
>>>> response from peer 0: offset -0.7734596729
>>>> sending request to peer 0
>>>> response from peer 0: offset -0.7734520435
>>>> sending request to peer 0
>>>> response from peer 0: offset -0.7734479904
>>>> discarding peer 0: flags=3
>>>> overall average offset: 0
>>>> NTP OK: Offset unknown|
>>>> _______________________________________________
>>>
>>> Пак същия случай като с leap 11:
>>>
>>> 78.128.6.187: Server dropped: Leap not in sync
>>> server 78.128.6.187, port 123
>>> stratum 3, precision -22, leap 11, trust 000
>>> refid [78.128.6.187], delay 0.02846, dispersion 0.00563
>>> transmitted 4, in filter 4
>>> reference time:    d2f9cf84.32cd47b0  Thu, Mar  1 2012 12:35:48.198
>>> originate timestamp: d2f9cf88.62bde7b9  Thu, Mar  1 2012 12:35:52.385
>>> transmit timestamp:  d2f9cf89.c08bf330  Thu, Mar  1 2012 12:35:53.752
>>> filter delay:  0.03592  0.03104  0.03030  0.02846
>>>         0.00000  0.00000  0.00000  0.00000
>>> filter offset: -1.35260 -1.35901 -1.36493 -1.36793
>>>         0.000000 0.000000 0.000000 0.000000
>>> delay 0.02846, dispersion 0.00563
>>> offset -1.367931
>>>
>>> Виж в предишните thread-ове, Георги имаше същия проблем, мисля, че беше
>>> проблем на самата виртуалка, не на софтуера вътре.
>>
>>    discarding peer 0: stratum=0
>> или
>>    discarding peer 0: flags=3
>> Според сорса, check_ntp не харесва отговорите. check_ntp приема и -vv.
>
> Аз просто не мога да си го обясня при положение, че снощи е работило
> без проблем и само след рестарт без да са редактирани никакви
> настройки по ntp... да се получава това просто нямам идея...

Ето в момента работи ОК. Сега го рестартирах

root at u7:~# ntpdc
ntpdc> sysinfo
system peer:          ip-6-178.powernet.bg
system peer mode:     client
leap indicator:       00
stratum:              4
precision:            -22
root distance:        0.04848 s
root dispersion:      1.09268 s
reference ID:         [78.128.6.178]
reference time:       d2f9e9dd.9b570492  Thu, Mar  1 2012 14:28:13.606
system flags:         auth monitor ntp kernel stats
jitter:               0.008499 s
stability:            0.000 ppm
broadcastdelay:       0.000000 s
authdelay:            0.000000 s
ntpdc> quit
root at u7:~# ntpq
ntpq> peers
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*ip-6-178.powern 194.12.255.250   3 u    5   64    3    0.087   83.406  46.444
 212.70.148.13   192.93.2.20      2 u    6   64    3    1.690   89.631  43.560
 193.104.79.174  192.43.244.18    2 u    5   64    3    1.027   84.735  44.926
 212.70.148.14   94.26.7.48       2 u    2   64    3    9.593   87.799  46.142
ntpq> as

ind assid status  conf reach auth condition  last_event cnt
===========================================================
  1  3998  963a   yes   yes  none  sys.peer    sys_peer  3
  2  3999  9024   yes   yes  none    reject   reachable  2
  3  4000  9024   yes   yes  none    reject   reachable  2
  4  4001  9024   yes   yes  none    reject   reachable  2