time is not being updated by openntpd - BSD

This is a discussion on time is not being updated by openntpd - BSD ; Hi, I just re-installed a a new system with openntpd setup from the ports, however the time is not being sync with remote ntp servers. Here is my setup: # cat /etc/rc.conf | grep open openntpd_enable="YES" # cat /usr/local/etc/ntpd.conf servers ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: time is not being updated by openntpd

  1. time is not being updated by openntpd

    Hi,

    I just re-installed a a new system with openntpd setup from the ports,
    however the time is not being sync with remote ntp servers.
    Here is my setup:
    # cat /etc/rc.conf | grep open
    openntpd_enable="YES"

    # cat /usr/local/etc/ntpd.conf
    servers stdtime.gov.hk
    servers asia.pool.ntp.org

    # ps -auxww | grep ntpd
    root 481 0.0 0.4 1416 1068 ?? Is 8:31AM 0:00.05 ntpd:
    [priv] (ntpd)
    _ntp 483 0.0 0.4 1352 1064 ?? S 8:31AM 0:00.03 ntpd: ntp
    engine (ntpd)

    # /usr/local/sbin/ntpd -d
    ntp engine ready
    reply from 210.0.235.14: offset -28796.173372 delay 0.007191, next query 5s
    reply from 202.73.37.27: offset -28796.171399 delay 0.069429, next query 5s
    reply from 61.206.115.3: offset -28796.162554 delay 0.078967, next query 5s
    reply from 210.118.170.59: offset -28796.174259 delay 0.097104, next
    query 5s
    reply from 192.115.133.35: offset -28796.172547 delay 0.420441, next
    query 5s

    I wonder why the system time is not being synchonized and get updated?

    Thanks
    Sam

  2. Re: time is not being updated by openntpd

    sam wrote:

    > Hi,
    >
    > I just re-installed a a new system with openntpd setup from the ports,
    > however the time is not being sync with remote ntp servers.
    > Here is my setup:
    > # cat /etc/rc.conf | grep open
    > openntpd_enable="YES"
    >
    > # cat /usr/local/etc/ntpd.conf
    > servers stdtime.gov.hk
    > servers asia.pool.ntp.org
    >
    > # ps -auxww | grep ntpd
    > root 481 0.0 0.4 1416 1068 ?? Is 8:31AM 0:00.05 ntpd:
    > [priv] (ntpd)
    > _ntp 483 0.0 0.4 1352 1064 ?? S 8:31AM 0:00.03 ntpd: ntp
    > engine (ntpd)
    >
    > # /usr/local/sbin/ntpd -d
    > ntp engine ready
    > reply from 210.0.235.14: offset -28796.173372 delay 0.007191, next query
    > 5s reply from 202.73.37.27: offset -28796.171399 delay 0.069429, next
    > query 5s reply from 61.206.115.3: offset -28796.162554 delay 0.078967,
    > next query 5s reply from 210.118.170.59: offset -28796.174259 delay
    > 0.097104, next query 5s
    > reply from 192.115.133.35: offset -28796.172547 delay 0.420441, next
    > query 5s
    >
    > I wonder why the system time is not being synchonized and get updated?
    >
    >


    It's not in the doc, but ntpd does not do jump synchronisations. there are
    good reasons for this which you should be able to work out for yourself.

    There are also limits within which it will not attempt to synchronise, but I
    forget what they are.

    What I always do is sync using rdate at boot time, then lock using ntpd.

+ Reply to Thread