1

Output from %timedatectl status is "Time zone: America/Denver (EDT, -0400)"

Something is corrupt since Denver is in fact MDT, -0600.

Is there a file I can remove and replace?

Edit: As Jaromanda has pointed out, the file to replace is "Navajo", which is pointed at by Denver. Deleted Navajo, copied over Edmonton and renamed it to Navajo. Now all is well when I select Denver as my timezone and reboot.

I'll attempt to mark this question as answered if this is possible. Or someone reading this with more experience, kindly feel free to do so.

  • Tried %sudo ntpd -q -g with no apparent effect. – Alan Malkiel Jul 13 '18 at 3:37
  • Using sudo raspi-config to change to Los_Angeles, I see the correct PDT, -0700. Seems only my time zone of Denver is corrupt. – Alan Malkiel Jul 13 '18 at 3:41
  • what is the output of ls -l /usr/share/zoneinfo/America/Denver – Jaromanda X Jul 13 '18 at 4:15
  • also, output of zdump Navajo America/Denver US/Mountain (all 3 times output here should be the same) – Jaromanda X Jul 13 '18 at 4:21
  • ls -l /usr/.../Denver returns lrwxrwxrwx root root ... as expected. Also, for what it is worth, if I select Edmonton, Canada as my location I get the correct -0600 offset and my Pi clock shows the correct MDT. I am thinking to replace the /usr/.../Denver with one from another working Pi. – Alan Malkiel Jul 13 '18 at 14:56
0

Replaced the suspected corrupt Navajo timezone file with a working one - Edmonton. Renamed it to Navajo, selected Denver in the Pi configuration dialog, rebooted and all is well.

| improve this answer | |
  • Edmonton and Navajo are NOT the same - Edmonton has 3 fewer transition times - though, this will only cause issues if dealing with times before 1975 - which may not be an issue for you – Jaromanda X Jul 14 '18 at 2:12
  • I've uploaded my Navajo zone file ... so you can get it using wget https://pastebin.com/raw/VYXZJdDu -O - | xxd -p -r > Navajo – Jaromanda X Jul 14 '18 at 2:37
  • I have retrieved your Navajo file - thank you. For the record, my Pi is dedicated to a clock radio and historical times are of no concern; only the present and the future. It was likely that my attempt to program the current timezone from within the clock code was responsible for the corruption - but I have no way of proving that. Again, thanks for your input and file. – Alan Malkiel Jul 15 '18 at 16:49

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.