All OnePasses started 2 minutes late last night

Discussion in 'TiVo Coffee House - TiVo Discussion' started by nycityuser, Jul 19, 2018.

  1. sfhub

    sfhub Well-Known Member

    2,883
    486
    Jan 6, 2007

    Advertisements

    I do not know if this is what is going on, but before the "bad" server would gain a second every 7 minutes or so (it might have been 3 minutes, I am going by memory), so within 14 hrs it would get up to two minutes.

    Again it is quite possible TiVo is still using their new configuration of servers in which case the tivo time servers would not be relevant. Someone can do the backdoor to view the logs after a net connect. The ntpdate command being used is in the logs.
     
  2. JoeKustra

    JoeKustra in the other Alabama TCF Club

    20,389
    3,812
    Dec 7, 2012
    Ashland, PA...
    I finally got around to checking the logs. Seems sjr1, sjr2 and sjr3 were accessed.

    However, the three IP addresses in that link were also accessed. I'm not experienced enough to understand what's going on. A total of 7 IP addresses were in the line that started with /bin/ntpupdate -b....
     
  3. sfhub

    sfhub Well-Known Member

    2,883
    486
    Jan 6, 2007
    So NTP uses an algorithm to reject and/or smooth out time differences.

    You can do nslookup on the IP addresses and sometimes they will have reverse lookup set up in a meaningful way.

    Assuming all those are unique IP addresses and some of those servers are traditional servers run by people who know how to run NTP servers, it isn't likely the net connect to mothership is the pathway where bad time is introduced as it would take many servers being out of whack for the algorithm to pick such a bad time.

    You can monitor all 7 IP addresses and see what the offsets are just to confirm.
     

Share This Page

spam firewall

Advertisements