[PLUG] Future Time Stamp: Clocks FUBAR

[King Beowulf]

On Thursday, January 16, 2014, Rich Shepard <rshepard at appl-ecosys.com>
wrote:

> On Fri, 16 Jan 2015, Rich Shepard wrote:
>
> >   More information.
>
>    Sigh. Here's another issue.
>
>    The 'date' command gives the correct local time; e.g., Thu Jan 16
> 13:13:14
> PST 2014. But, hwclock (which was sync'd to system time a bit more than an
> hour ago) has now jumped back 4 hours:
>
> Thu 16 Jan 2014 09:13:20 PM PST  -0.018213 seconds
>
>    I just re-sync'd them using 'hwclock -w'. The network time protocol
> daemon
> is running:
>
>   5262 ?        SLs    0:00 /usr/sbin/ntpd -g -p /var/run/ntpd.pid
>
> and servers are uncommented in /etc/ntp.conf with the daemon restarted
> after
> that.
>
>    Not the way I wanted to spend today.
>
>    All ideas and or guidance on getting the clocks correct and fixing the
> offset problem in the sqlite tarball are welcome.
>
> Rich
>
>
This 1st thing I would check is the BIOS clock.  Sometimes the OS can't set
it correctly if it's too far off.  The BIOS click can get jiggered from
power outages of similar power glitches.

Then check your time zone
Then check/set date

Note that ntpd will refuse to set the time if the current time is too far
off.

Next check the ntp time server adresses. Not all are allowed for the
general public.

I'm at Denver airport so I'll check when I get in which time servers I'm
using.



-- 
You! What PLANET is this!
    -- McCoy, "The City on the Edge of Forever", stardate 3134.0