Stratum 0 - no server suitable for synchronizationfound - NTP

This is a discussion on Stratum 0 - no server suitable for synchronizationfound - NTP ; Hello People, I'll explain my problem: --------------------------------------------------------------------------------------------------------------------------- SERVER --------------------------------------------------------------------------------------------------------------------------- bash-2.05# ntpdate -q localhost server 127.0.0.1, stratum 1, offset 0.000005, delay 0.02580 15 Sep 13:58:19 ntpdate[2020]: no server suitable for synchronization found bash-2.05# ntpq ntpq> pe remote refid st t when ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: Stratum 0 - no server suitable for synchronizationfound

  1. Stratum 0 - no server suitable for synchronizationfound

    Hello People,

    I'll explain my problem:
    ---------------------------------------------------------------------------------------------------------------------------
    SERVER
    ---------------------------------------------------------------------------------------------------------------------------
    bash-2.05# ntpdate -q localhost
    server 127.0.0.1, stratum 1, offset 0.000005, delay 0.02580
    15 Sep 13:58:19 ntpdate[2020]: no server suitable for synchronization found

    bash-2.05# ntpq
    ntpq> pe
    remote refid st t when poll reach delay offset disp
    ================================================== ============================
    WWVB_SPEC(2) .WWVB. 0 l 20d 64 0 0.00 0.000 0..00
    host19 .STEP. 16 u - 1024 0
    0.00 0.000 0.00
    ntpq> as
    ind assID status conf reach auth condition last_event cnt
    ================================================== =========
    1 27436 8053 yes no lost reach 5
    2 27437 8000 yes no

    ---------------------------------------------------------------------------------------------------------------------------
    CLIENT
    ---------------------------------------------------------------------------------------------------------------------------
    br-nsps11# ntpdate -q localhost
    server ::1, stratum 2, offset 0.000008, delay 0.02577
    15 Sep 14:01:08 ntpdate[6486]: no server suitable for synchronization found

    br-nsps11# ntpq
    ntpq> pe
    remote refid st t when poll reach delay offset jitter
    ================================================== ============================
    10.24.8.12 .DROP. 16 u 204 64 0 0.000 0.000 4000..00
    host18 .WWVB. 1 u 965 1024 0 0.000 0.000 4000.00
    host19 .INIT. 16 u 974 1024 0 0.000 0.000 4000.00
    ntpq> as
    ind assID status conf reach auth condition last_event cnt
    ================================================== =========
    1 48556 a0f4 yes yes none reject reachable 15
    2 48557 a023 yes yes none reject lost reach 2
    3 48558 a043 yes yes none reject lost reach 4

    Iīd like do know what is happening with this server.

    Anyone know why i didnīt get to syncronize with my client's?

    Why i receive the message "no server suitable for synchronization found"?

    What is it mean "reject" ?

    I really appreciate some help.

    regards,

    Marcos Luiz Onisto
    _______________________________________________
    questions mailing list
    questions@lists.ntp.isc.org
    https://lists.ntp.isc.org/mailman/listinfo/questions


  2. Re: Stratum 0 - no server suitable for synchronization found

    Marcos Onisto wrote:

    > Hello People,
    >
    > I'll explain my problem:
    > ---------------------------------------------------------------------------------------------------------------------------
    >
    > SERVER
    > ---------------------------------------------------------------------------------------------------------------------------
    >
    > bash-2.05# ntpdate -q localhost
    > server 127.0.0.1, stratum 1, offset 0.000005, delay 0.02580
    > 15 Sep 13:58:19 ntpdate[2020]: no server suitable for synchronization found
    >
    > bash-2.05# ntpq
    > ntpq> pe
    > remote refid st t when poll reach delay offset
    > disp
    > ================================================== ============================
    >
    > WWVB_SPEC(2) .WWVB. 0 l 20d 64 0 0.00 0.000
    > 0.00
    > host19 .STEP. 16 u - 1024 0
    > 0.00 0.000 0.00


    That says that ntpd has been unable to contact WWVB_SPEC for twenty
    days!! If it's a reference clock, it's not working. If it's not a
    reference clock, it's still not working!! Host19 is also unreachable.

    > ntpq> as
    > ind assID status conf reach auth condition last_event cnt
    > ================================================== =========
    > 1 27436 8053 yes no lost reach 5
    > 2 27437 8000 yes no
    >
    > ---------------------------------------------------------------------------------------------------------------------------
    >
    > CLIENT
    > ---------------------------------------------------------------------------------------------------------------------------
    >
    > br-nsps11# ntpdate -q localhost
    > server ::1, stratum 2, offset 0.000008, delay 0.02577
    > 15 Sep 14:01:08 ntpdate[6486]: no server suitable for synchronization found
    >
    > br-nsps11# ntpq
    > ntpq> pe
    > remote refid st t when poll reach delay offset
    > jitter
    > ================================================== ============================
    >
    > 10.24.8.12 .DROP. 16 u 204 64 0 0.000 0.000
    > 4000.00
    > host18 .WWVB. 1 u 965 1024 0 0.000 0.000
    > 4000.00
    > host19 .INIT. 16 u 974 1024 0 0.000 0.000
    > 4000.00



    This client has been unable to reach any server for 204 minutes. The
    last two servers have been unreachable for 965 and 974 minutes
    respectively!!! I won't attempt to guess why.


  3. Re: Stratum 0 - no server suitable for synchronization found

    In article ,
    Richard B. Gilbert wrote:
    > Marcos Onisto wrote:
    >
    > > 10.24.8.12 .DROP. 16 u 204 64 0 0.000 0.000 4000.00
    > > host18 .WWVB. 1 u 965 1024 0 0.000 0.000 4000.00
    > > host19 .INIT. 16 u 974 1024 0 0.000 0.000 4000.00


    > This client has been unable to reach any server for 204 minutes. The
    > last two servers have been unreachable for 965 and 974 minutes
    > respectively!!! I won't attempt to guess why.


    It doesn't say that at all. The 204, 965 and 974 are in seconds, and the
    latter two are perfectly reasonable. What is not reasonable is that none
    of these sources have been successfully polled on the last 8 attempts.

    I'm not sure what .DROP. means; I wonder if trying to say do not use
    this server. I think a check on the rules of engagement is called for,
    even though this is on a private IP address range.

    host18 has been successfully polled at some time, at least to get its
    stratum and reference ID. host19 has never been contacted. The root
    dispersion for host18 will be well above the maximum allowed.

    I presume host18 is the server machine which hasn't been updated for
    20 days.

  4. Re: Stratum 0 - no server suitable for synchronization found

    >>> In article , david@djwhome.demon.co.uk (David Woolley) writes:

    David> I'm not sure what .DROP. means; I wonder if trying to say do not use
    David> this server. I think a check on the rules of engagement is called
    David> for, even though this is on a private IP address range.

    It's a KISS code - DROP means "lost peer in symmetric mode".

    Similarly:

    INIT: the association has not yet synchronized for the first time
    STEP: a time step has occured, but the assoc has not yet re-sync'd

    H

  5. Re: Stratum 0 - no server suitable for synchronization found

    The KISS codes are documented in the html/debug.html file.

    H

+ Reply to Thread