Re: Warning:Time goes back!

From: Marco Calistri (ifbne.ajdf@cc22.ne.jp)
Date: Fri Jan 18 2002 - 01:47:30 EET

  • Next message: Wilbert Knol: "Re: AX25 UTILS and PTC-II"

    On 07-Jan-2002 Riley Williams wrote:
    > Hi Marco.
    >
    >> Hello,I'm having this error and I don't remember which is the
    >> solution. I remember to have red about same problem in the past, but
    >> I've not found that document.
    >
    >> #error message:
    >> PING sys3.ik5bcu.ampr.org (192.168.2.3) from 192.168.2.1 :
    >> 56(84) bytes of data.
    >> Warning: time of day goes back, taking countermeasures.
    >
    >> Have you a suggestion?
    >
    > In this case, this indicates that the time of day on the system you're
    > using and on sys3.ik5bcu.ampr.org are not synchronised. The simple fix
    > is to implement an NTP server somewhere on your network (preferably on
    > the box that dials up to the Internet) that synchronises to one of the
    > many atomic timeservers on the Internet whenever you're dialled up, and
    > have all your other systems synchronise their clocks to it using NTP in
    > turn. If your dial-up server is a RH Linux box and the xntp3 RPM is
    > installed, then 99% of the work is done and you just need to find a
    > reasonably local timeserver to use and point xntp3 at it.
    >
    > If you're feeling adventurous, then you could set up as a timeserver for
    > your local ham radio community as well...
    >
    > Best wishes from Riley.

    Riley,sorry for delay of my answer,but I've got several problems with
    my computer and telephone line.

    I installed ntp and attempted to syncronize my hardware clock with
    ntpdate [server] through INTERNET,but this did not cured the problem.
    Same warnings appear also if I do a ping "localhost" and probably Craig Small,
    VK2XLZ is right about a possible bug into RH-7.2 iptools.
    Only by pinging my JNOS on a second pc does not shows the warnings:

    [marco@linux etc]$ ping 44.134.210.32
    PING 44.134.210.32 (44.134.210.32) from 192.168.2.1 : 56(84) bytes of data.
    64 bytes from 44.134.210.32: icmp_seq=0 ttl=253 time=12.854 msec
    64 bytes from 44.134.210.32: icmp_seq=1 ttl=253 time=9.902 msec
    64 bytes from 44.134.210.32: icmp_seq=2 ttl=253 time=9.931 msec
    64 bytes from 44.134.210.32: icmp_seq=3 ttl=253 time=9.576 msec
    64 bytes from 44.134.210.32: icmp_seq=4 ttl=253 time=9.930 msec
    64 bytes from 44.134.210.32: icmp_seq=5 ttl=253 time=9.908 msec
    64 bytes from 44.134.210.32: icmp_seq=6 ttl=253 time=9.928 msec
    64 bytes from 44.134.210.32: icmp_seq=7 ttl=253 time=9.913 msec
    64 bytes from 44.134.210.32: icmp_seq=8 ttl=253 time=9.898 msec
    64 bytes from 44.134.210.32: icmp_seq=9 ttl=253 time=9.916 msec

    While a ping 127.0.0.1 (localhost) generates:

    [marco@linux etc]$ ping 127.0.0.1
    PING 127.0.0.1 (127.0.0.1) from 127.0.0.1 : 56(84) bytes of data.
    Warning: time of day goes back, taking countermeasures.
    64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=590 usec
    64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=292 usec
    64 bytes from 127.0.0.1: icmp_seq=2 ttl=255 time=260 usec
    64 bytes from 127.0.0.1: icmp_seq=3 ttl=255 time=263 usec
    64 bytes from 127.0.0.1: icmp_seq=4 ttl=255 time=271 usec
    64 bytes from 127.0.0.1: icmp_seq=5 ttl=255 time=274 usec

    TKS,Marco.

    -
    To unsubscribe from this list: send the line "unsubscribe linux-hams" in
    the body of a message to wsq.ewtm@tl.ru
    More majordomo info at http://vger.kernel.org/majordomo-info.html

    This archive was generated by hypermail 2b30 : Fri Jan 18 2002 - 01:45:01 EET