Ntpdate - no server suitable for synchronizationfound - NTP

This is a discussion on Ntpdate - no server suitable for synchronizationfound - NTP ; If I run ntpdate from client against new server I get error "no server suitable for synchronization found" If I run ntpdate against another older server it has no problems and instantly changes the time and shows the drift. Old ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: Ntpdate - no server suitable for synchronizationfound

  1. Ntpdate - no server suitable for synchronizationfound

    If I run ntpdate from client against new server I get error

    "no server suitable for synchronization found"

    If I run ntpdate against another older server it has no problems and
    instantly changes the time and shows the drift.

    Old server is running RH 7.3 with ntpd 4.1.1@1.786
    New Server Centos 4.3 with ntpd 4.2.0a@1.1190-r

    I have disbaled iptables and selinux but with no joy - can anyone
    suggest what I can try next.

    Nmap for udp:123 says its there and waiting

    ntpd debug reports

    receive: at 1030 192.168.40.202<-192.168.40.34 mode 3 code 2
    receive: at 1031 192.168.40.202<-192.168.40.34 mode 3 code 2
    receive: at 1032 192.168.40.202<-192.168.40.34 mode 3 code 2
    refclock_transmit: at 1033 127.127.1.0
    refclock_receive: at 1033 127.127.1.0
    refclock_sample: n 1 offset 0.000000 disp 0.010000 jitter 0.000001
    clock_filter: n 8 off 0.000000 del 0.000000 dsp 0.000944 jit 0.000001,
    age 66
    receive: at 1033 192.168.40.202<-192.168.40.34 mode 3 code 2
    transmit: at 1034 192.168.40.202->192.81.123.67 mode 3
    receive: at 1034 192.168.40.202<-192.81.123.67 mode 4 code 1
    clock_filter: n 8 off -0.008419 del 0.055972 dsp 0.001666 jit 0.016144,
    age 66
    clock_update: at 1034 assoc 2
    local_clock: assocID 23668 offset -0.008419000 freq -46.188 state 4
    local_clock: time 968 clock 0.012612 offset -0.008419 freq -46.188 state
    4
    local_clock: mu 259 jitr 0.038 freq -48.276 stab 309.462 poll 7 count 0

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


  2. Re: Ntpdate - no server suitable for synchronizationfound

    ian.harper@vaisala.com wrote:

    > If I run ntpdate from client against new server I get error
    >
    > "no server suitable for synchronization found"
    >
    > If I run ntpdate against another older server it has no problems and
    > instantly changes the time and shows the drift.


    Try "ntpdate -d" and compare the output - might help.

    --
    Ronan Flood
    working for but not speaking for
    Network Services, University of London Computer Centre
    (which means: don't bother ULCC if I've said something you don't like)

  3. Re: Ntpdate - no server suitable for synchronization found

    >>> In article , ian.harper@vaisala.com writes:

    ian> If I run ntpdate from client against new server I get error "no server
    ian> suitable for synchronization found"

    This means that either you are not communicating with the new server or the
    new server has not yet sync'd.

    ian> If I run ntpdate against another older server it has no problems and
    ian> instantly changes the time and shows the drift.

    This means you are communicating with the old server and ntpd on that
    machine is sync'd.

    Have you seen http://ntp.isc.org/Support, sections 5 and 9?

    H

  4. Re: Ntpdate - no server suitable for synchronization found


    Harlan Stenn wrote:
    > >>> In article , ian.harper@vaisala.com writes:

    >
    > ian> If I run ntpdate from client against new server I get error "no server
    > ian> suitable for synchronization found"
    >
    > This means that either you are not communicating with the new server or the
    > new server has not yet sync'd.
    >
    > ian> If I run ntpdate against another older server it has no problems and
    > ian> instantly changes the time and shows the drift.
    >
    > This means you are communicating with the old server and ntpd on that
    > machine is sync'd.
    >
    > Have you seen http://ntp.isc.org/Support, sections 5 and 9?
    >
    > H


    I don't think so ,I think this is a bug,I have recompiled the
    ntpdate,if I comment lines from 1791 to 1805,I can use "ntpdate -b
    server" to correctthe time. otherwise,I must use "ntpdate -d server" or
    "ntpdate -u server" to correct the time.


  5. Re: Ntpdate - no server suitable for synchronization found

    It would help to see the results of 'ntpq -p server' before you run 'ntpdate
    server'.

    Also, ntpdate is being deprecated.

    Please see http://ntp.isc.org/Dev/DeprecatingNtpdate for alternatives.

    H

  6. Re: Ntpdate - no server suitable for synchronization found

    xvenw@163.com wrote:

    > I don't think so ,I think this is a bug,I have recompiled the
    > ntpdate,if I comment lines from 1791 to 1805,I can use "ntpdate -b
    > server" to correct the time. otherwise,I must use "ntpdate -d server"
    > or "ntpdate -u server" to correct the time.


    That sounds deeply wrong; for one, "ntpdate -d" does not set the time.

    Are you running ntpdate on a client system which is also running ntpd?
    If so, ntpd will have allocated UDP port 123, which looks like why you
    need to tell ntpdate not to try to use that port. But there should have
    been an obvious error message from ntpdate about it.

    --
    Ronan Flood
    working for but not speaking for
    Network Services, University of London Computer Centre
    (which means: don't bother ULCC if I've said something you don't like)

+ Reply to Thread