[ale] NTP/Chrony time zone persistence

DJ-Pfulio DJPfulio at jdpfu.com
Wed Sep 14 10:18:45 EDT 2016


If I'm reading this correctly, the HW clock is working perfectly, as
expected. It just appears to be a display issue - is TZ set correctly?


On 09/14/2016 10:00 AM, Edward O. Holcroft wrote:
> hwclock Wed 14 Sep 2016 06:47:15 AM PDT  -0.896088 seconds
> date Wed Sep 14 06:47:23 PDT 2016
> 
> Then if I reboot, note how server drops back 3 hrs:
> hwclock Wed 14 Sep 2016 06:49:07 AM PDT  -0.364745 seconds
> date Wed Dec 14 03:50:17 PST 2016
> 
> Then if I run ntpdate 192.168.50.246 (the IP of the AD DC), I am back to
> the correct time:
> hwclock Wed 14 Sep 2016 06:51:06 AM PDT  -0.302285 seconds
> ​date ​Wed Sep 14 06:51:14 PDT 2016
> 
> ​In ntp.conf and in chrony.conf I have:
> 
> ​server 192.168.50.246
> 
> ​But it lacks persistence. Chronyd service shows as loaded and active,
> but it's not updating against the DC.
> 
> ​ed​
> 
> 
> 
> 
> 
> _________________________________________ 
> 
> *Edward O. Holcroft*
> IT Operations Manager
> 
> *Madsen, Kneppers & Associates, Inc.*
> Construction Consultants & Engineers 
> 11695 Johns Creek Parkway, Suite 250
> Johns Creek, GA 30097
> 
> *O*  770.446.9606  |  *F*  770.446.9612  |  *C*  770.630.0949  | 
> eholcroft at mkainc.com <mailto:eholcroft at mkainc.com>
> 
> www.mkainc.com <http://www.mkainc.com> 
> 
> On Tue, Sep 13, 2016 at 10:34 PM, Scott M. Jones <eff at dragoncon.org
> <mailto:eff at dragoncon.org>> wrote:
> 
>     What is the output of:
> 
>     hwclock;date
> 
>     If this is a virtual, I presume the hwclock time is coming from the
>     host OS?
> 
>     On Sep 13, 2016, at 9:30 PM, Edward O. Holcroft
>     <eholcroft at mkainc.com <mailto:eholcroft at mkainc.com>> wrote:
> 
>>     I have used this command to set the timezone (in this case
>>     Pacific), but it does not persist across reboots. Even with
>>     ntpd/chrony in place pointing to an NTP server in the same TZ.
>>
>>     If I run ntpdate it fixes the issue immediately and my AD
>>     authentication works ... until next reboot and it's back on UTC.
>>
>>     I only have this issue on the VM. Same setup on 20 other physical
>>     server works as advertised.
>>
>>     ed
>>
>>
>>     _________________________________________ 
>>
>>     *Edward O. Holcroft*
>>     IT Operations Manager
>>
>>     *Madsen, Kneppers & Associates, Inc.*
>>     Construction Consultants & Engineers 
>>     11695 Johns Creek Parkway, Suite 250
>>     Johns Creek, GA 30097
>>
>>     *O*  770.446.9606 <tel:770.446.9606>  |  *F*  770.446.9612
>>     <tel:770.446.9612>  |  *C*  770.630.0949 <tel:770.630.0949>  | 
>>     eholcroft at mkainc.com <mailto:eholcroft at mkainc.com>
>>
>>     www.mkainc.com <http://www.mkainc.com> 
>>
>>     On Tue, Sep 13, 2016 at 7:57 PM, Scott M. Jones <eff at dragoncon.org
>>     <mailto:eff at dragoncon.org>> wrote:
>>
>>         Are you using timedatectl?  Welcome to the systemd way of
>>         doing things...
>>
>>         timedatectl list-timezones
>>         timedatectl set-timezone [TIMEZONE]
>>
>>         https://www.freedesktop.org/software/systemd/man/timedatectl.html
>>         <https://www.freedesktop.org/software/systemd/man/timedatectl.html>
>>
>>         On 9/13/16 3:31 PM, Edward O. Holcroft wrote:
>>         > Hi all,
>>         >
>>         > I have a Samba server in an AD environment, so time sync
>>         with the DC is
>>         > important for autentication. I have this working fine on
>>         many physical
>>         > servers, but recently added a virtual CentOS 7 box on ESXi6,
>>         and cannot
>>         > get it to stick.
>>         >
>>         > First I used NTP, which works immediately when run, but has no
>>         > persistence through reboots. Then I read that CentOS7 uses
>>         chrony, so I
>>         > changed, but still, after reboot, the client machine is
>>         reset to UTC,
>>         > which it gets from the ESXi host, as it should.
>>         >
>>         > I tried setting the ESXi host to point to the local DC for
>>         time, but
>>         > that made no difference to the time zone.
>>         >
>>         > Any ideas on how to force time zone persistence? Other than
>>         a cron job?
>>         >
>>         > ed
>>
>>         _______________________________________________
>>         Ale mailing list
>>         Ale at ale.org <mailto:Ale at ale.org>
>>         http://mail.ale.org/mailman/listinfo/ale
>>         <http://mail.ale.org/mailman/listinfo/ale>
>>         See JOBS, ANNOUNCE and SCHOOLS lists at
>>         http://mail.ale.org/mailman/listinfo
>>         <http://mail.ale.org/mailman/listinfo>
>>
>>
>>
>>     MADSEN, KNEPPERS & ASSOCIATES USA, MKA Canada Inc.
>>     WARNING/CONFIDENTIALITY NOTICE: This message may be confidential
>>     and/or privileged. If you are not the intended recipient, please
>>     notify the sender immediately then delete it - you should not copy
>>     or use it for any purpose or disclose its content to any other
>>     person. Internet communications are not secure. You should scan
>>     this message and any attachments for viruses. Any unauthorized use
>>     or interception of this e-mail is illegal.
>>     _______________________________________________
>>     Ale mailing list
>>     Ale at ale.org <mailto:Ale at ale.org>
>>     http://mail.ale.org/mailman/listinfo/ale
>>     <http://mail.ale.org/mailman/listinfo/ale>
>>     See JOBS, ANNOUNCE and SCHOOLS lists at
>>     http://mail.ale.org/mailman/listinfo
>>     <http://mail.ale.org/mailman/listinfo>
> 
>     _______________________________________________
>     Ale mailing list
>     Ale at ale.org <mailto:Ale at ale.org>
>     http://mail.ale.org/mailman/listinfo/ale
>     <http://mail.ale.org/mailman/listinfo/ale>
>     See JOBS, ANNOUNCE and SCHOOLS lists at
>     http://mail.ale.org/mailman/listinfo
>     <http://mail.ale.org/mailman/listinfo>
> 
> 
> 
> MADSEN, KNEPPERS & ASSOCIATES USA, MKA Canada Inc.
> WARNING/CONFIDENTIALITY NOTICE: This message may be confidential and/or
> privileged. If you are not the intended recipient, please notify the
> sender immediately then delete it - you should not copy or use it for
> any purpose or disclose its content to any other person. Internet
> communications are not secure. You should scan this message and any
> attachments for viruses. Any unauthorized use or interception of this
> e-mail is illegal.
> 
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
> 


-- 
Got Linux? Used on smartphones, tablets, desktop computers, media
centers, and servers by kids, Moms, Dads, grandparents and IT
professionals.


More information about the Ale mailing list