You'll also need to restart your application after correcting those problems.$: sudo cp /usr/share/zoneinfo/America/New_York localtime$: ls -l /etc/localtime-rw-r--r-- 1 root root 3519 Jan 13 /etc/localtime$: date Fri Jan 13 EST 2017$: sudo hwclock Fri AM EST -1.004057 seconds$: rpm -V tzdata ..... There have been numerous high severity security updates released since 2013 and you probably have none of them.
Error: Nothing to do$: sudo cp /usr/share/zoneinfo/America/New_York localtime$: date Fri Jan 13 EST 2017$: sudo hwclock Fri AM EST -0.783752 seconds instead and it will get updated to the latest tzdata-2016j-1.el6.noarch Once you update you will need to recopy the zone file as it's one of the corrupted ones showing up in your rpm -V output.
Computer clocks tend to “drift” so regularly synchronizing them with NTP servers helps keep them accurate. The hardware clock on your server will not reflect that.
The first step is to make sure you have the ntp program installed. So you want to set it as well so that the correct time is maintained after reboot: The above two lines can sometimes prevent ntpd from properly synchronizing your clock.
Use the following procedures to configure the Amazon Time Sync Service on your instance using the Amazon Linux instances are set to the UTC (Coordinated Universal Time) time zone by default, but you may wish to change the time on an instance to the local time or to another time zone in your network.