NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

steveoelliott's avatar
May 30, 2017

NTP Issue - Time Jump

Hi all,

 

Today for the second time since I've owned my OS 6 unit (now on 6.7.1 FW) the NTP process has incorrectly set my device time to a date in the past before correcting itself sometime later.

 

May 30 09:23:34 DESPAIR connmand[5534]: ntp: adjust (jump): -454753305.317564 sec

Jan 01 00:01:49 DESPAIR systemd[1]: Time has been changed

Jan 01 00:18:53 DESPAIR connmand[5534]: ntp: adjust (jump): +454753299.218670 sec
May 30 09:40:33 DESPAIR systemd[1]: Time has been changed

 

Any idea why this is happening? The servers I used were 0.pool.ntp.org and 1.pool.ntp.org. I've now changed to time.nist.gov but I doubt this is a global issue with the NTP servers in pool.ntp.org otherwise it would be all over the internet.

 

Thanks...

12 Replies

Replies have been turned off for this discussion
  • Retired_Member's avatar
    Retired_Member

    You might want to use

    time-e.netgear.com

    as the first and 

    time-a.netgear.com

    as the second server to synchronize with.

     

    Using that on my rn104 for years not having any issues.

     

  • StephenB's avatar
    StephenB
    Guru - Experienced User

    steveoelliott wrote:

     

    May 30 09:23:34 DESPAIR connmand[5534]: ntp: adjust (jump): -454753305.317564 sec

    Jan 01 00:01:49 DESPAIR systemd[1]: Time has been changed

    Jan 01 00:18:53 DESPAIR connmand[5534]: ntp: adjust (jump): +454753299.218670 sec
    May 30 09:40:33 DESPAIR systemd[1]: Time has been changed

     

    I also use 0.pool.ntp.org, and the biggest NTP slew I see for 30 May is about 5 ms.  I am wondering if something went south with the RTT estimate built into the protocol?

     

     

    • steveoelliott's avatar
      steveoelliott
      Luminary

      Thanks all...

       

      I will say that the internet connection this device leverages is very slow circa 2Mbps but that should not be an issue for NTP and it's calculation. I will see how we get on with a new NTP server.

      • steveoelliott's avatar
        steveoelliott
        Luminary

        I understand that NTPD can be setup to reject huge time offsets and consider these erroneous / ignore them. I believe in future releases Netgear should configure it in this way to prevent this issue from occurring. It can cause all manor of issues.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More