Announcement

Collapse
No announcement yet.

Zee S2 Mysterious Time Change

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Zee S2 Mysterious Time Change

    Sometime today, my Zee S2 decided to change it's internal time to an hour earlier (like it was falling back for CST). Nothing has been changed on it, and the time zone settings are correct. I have it set for the nearest city in the program.

    Sunrise and Sunset time show as correct in the bar, but the time is exactly one hour slow (hence all times events are running an hour behind.

    Unit has been rebooted but this did not correct the issue.

    Any ideas?

    #2
    If you can log in (ssh or console), you can check if the Network Time Protocol daemon is running:

    Code:
    $ ps -C ntpd
      PID TTY          TIME CMD
      663 ?        00:00:08 ntpd
    Config file is at /etc/ntd.conf. Standard Raspbian Jessie build starts like this:
    Code:
    # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help
    
    driftfile /var/lib/ntp/ntp.drift
    
    
    # Enable this if you want statistics to be logged.
    #statsdir /var/log/ntpstats/
    
    statistics loopstats peerstats clockstats
    filegen loopstats file loopstats type day enable
    filegen peerstats file peerstats type day enable
    filegen clockstats file clockstats type day enable
    
    
    # You do need to talk to an NTP server or two (or three).
    #server ntp.your-provider.example
    
    # pool.ntp.org maps to about 1000 low-stratum NTP servers.  Your server will
    # pick a different set every time it starts up.  Please consider joining the
    # pool: <http://www.pool.ntp.org/join.html>
    server 0.debian.pool.ntp.org iburst
    server 1.debian.pool.ntp.org iburst
    server 2.debian.pool.ntp.org iburst
    server 3.debian.pool.ntp.org iburst

    Comment


      #3
      Solved

      No idea what caused it - but the following command from the command line fixed it:

      sudo sntp -s pool.ntp.org

      followed by:

      sudo reboot

      Time is now correct.

      Comment


        #4
        Interesting. From this line in the config file: "Your server will pick a different set every time it starts up." I'd guess that yours was unlucky enough to get a server that provided the wrong time. The sntp command grabbed a different server of course and corrected it. No doubt would have corrected eventually, but you forced the issue.

        Comment

        Working...
        X