You are not logged in.

#1 2016-07-22 15:29:18

cfmg
Member
Registered: 2016-07-18
Posts: 11

[SOLVED] Incorrect time set, hwclock --debug, timedatectl status shown

Hello,

I have a new installation of Arch Linux as the only operating system (not dual booting). The BIOS clock is set to UTC. I am having the following issues with how the time is set: 

Despite having the Time Zone set, the local time is the same as UTC. Here's the output for 

timedatectl status
Local time: Fri 2016-07-22 14:43:44 America
  Universal time: Fri 2016-07-22 14:43:44 UTC
        RTC time: Fri 2016-07-22 14:43:44
       Time zone: America/New_York (America, +0000)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

   

The output for

hwclock --debug

is

hwclock from util-linux 2.28                                                             
Using the /dev interface to the clock.                                                   
Last drift adjustment done at 1468787865 seconds after 1969                              
Last calibration done at 1468787865 seconds after 1969                                   
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2016/07/22 14:52:15
Hw clock time : 2016/07/22 14:52:15 = 1469199135 seconds since 1969
Time since last adjustment is 411270 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2016-07-22 14:52:14.905566+0:00

The output for

time

is

real    0m0.000s
user    0m0.000s
sys     0m0.000s

The output for

date

is

Fri Jul 22 15:00:21 UTC 2016

I have tried

sudo ntpd -qg

, but that did not correct the local time.
What I have referred to so far:
https://bbs.archlinux.org/viewtopic.php?id=167407
https://wiki.archlinux.org/index.php/time
https://bbs.archlinux.org/viewtopic.php?id=205696
https://wiki.archlinux.org/index.php/Be … guide#Time

(The time and the caelndar daemons on systray are currently blank.)

I have very little experience with programming, and no prior experience with linux, and am finding my way around Arch using the wiki and the forum posts. So, far the wiki has been amazingly helpful in setting up everything, but I am stumped with the the incorrect time showing after a reboot. I would greatly appreciate any help and suggestions.

Thank you.

Last edited by cfmg (2016-07-23 14:01:19)

Offline

#2 2016-07-22 16:15:18

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,739

Re: [SOLVED] Incorrect time set, hwclock --debug, timedatectl status shown

Odd.   What are the output of ls -l /etc/localtime


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2016-07-22 16:27:06

cfmg
Member
Registered: 2016-07-18
Posts: 11

Re: [SOLVED] Incorrect time set, hwclock --debug, timedatectl status shown

The output for

ls -l /etc/localtime

is

lrwxrwxrwx 1 root root 36 Jul 17 20:36 /etc/localtime -> /usr/share/zoneinfo/America/New_York

Offline

#4 2016-07-22 16:32:33

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,739

Re: [SOLVED] Incorrect time set, hwclock --debug, timedatectl status shown

I just don't get this

Time zone: America/New_York (America, +0000)

This installation is on bare metal? (Not a virtual machine?)
This is purebred Arch?  Not something installed by some random "installer"?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#5 2016-07-22 16:38:46

cfmg
Member
Registered: 2016-07-18
Posts: 11

Re: [SOLVED] Incorrect time set, hwclock --debug, timedatectl status shown

Correct. This is a pure Arch installation is on the actual machine.

I am confused about the

Time zone: America/New_York (America, +0000)

too.

Offline

#6 2016-07-22 16:51:13

dockland
Member
From: Sweden
Registered: 2015-06-06
Posts: 861

Re: [SOLVED] Incorrect time set, hwclock --debug, timedatectl status shown

cfmg wrote:

Correct. This is a pure Arch installation is on the actual machine.

I am confused about the

Time zone: America/New_York (America, +0000)

too.

This might be a long shot, but can it be the BIOS-battery that is about to give up?


I possess a device, in my pocket, that is capable of accessing the entirety of information known to man.
I use it to look at funny pictures of cats and to argue with strangers.

Offline

#7 2016-07-23 01:23:51

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,463

Re: [SOLVED] Incorrect time set, hwclock --debug, timedatectl status shown

does `echo $TZ` return anything?

Offline

#8 2016-07-23 01:30:10

cfmg
Member
Registered: 2016-07-18
Posts: 11

Re: [SOLVED] Incorrect time set, hwclock --debug, timedatectl status shown

echo $TZ

returns a blank line followed by the command prompt.

Last edited by cfmg (2016-07-23 01:30:57)

Offline

#9 2016-07-23 01:36:09

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,463

Re: [SOLVED] Incorrect time set, hwclock --debug, timedatectl status shown

ok, so that's not it. Are you running a desktop environment that may be interfering? If not, is it possible the tzdata file for that zone is corrupt on your system?

Offline

#10 2016-07-23 01:48:47

cfmg
Member
Registered: 2016-07-18
Posts: 11

Re: [SOLVED] Incorrect time set, hwclock --debug, timedatectl status shown

I am using the KDE plasma desktop environment. I don't know enough about the inner workings of the system to know whether the desktop environment amy be interfereing. Is there a way to check this? (Perhaps installing another desktop environment?)

Also, is there a way to check whether the tzdata file is corrupt?

Thanks.

Offline

#11 2016-07-23 02:32:45

cfmg
Member
Registered: 2016-07-18
Posts: 11

Re: [SOLVED] Incorrect time set, hwclock --debug, timedatectl status shown

I followed up on Scimmia's comments, and used a different desktop environment (Cinnamon). The time showed on the tray icon on the system tray, but was showing UTC instead of Eastern Standard Time. I changed the time zone to Eastern Standard Time on the GUI interface of the time daemon, and saw the correct time.

Next, I logged into the KDE desktop. Now, the tray icon showed the UTC time. Upon changing the time zone to New York, the time no longer showed on the tray icon (just a blank in it's place). Upon changing the time zone to Mountain Time, the tray icon showed the correct time (as per Mountain time). Next, upon changing the time zone to Detroit (also on Eastern Standard Time as New York), I see the correct time now being displayed on the trya icon. (It goes blank if I change the time zone to New York.)

The

time

output still shows

                                                                                         
real    0m0.000s                                                                         
user    0m0.000s                                                                         
sys     0m0.000s

The

timedate ctl status

output for all three time zones are below:

Local time: Fri 2016-07-22 20:12:04 MDT
  Universal time: Sat 2016-07-23 02:12:04 UTC
        RTC time: Sat 2016-07-23 02:12:05
       Time zone: America/Denver (MDT, -0600)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no
Local time: Fri 2016-07-22 22:12:57 EDT
  Universal time: Sat 2016-07-23 02:12:57 UTC
        RTC time: Sat 2016-07-23 02:12:58
       Time zone: America/Detroit (EDT, -0400)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no
Local time: Sat 2016-07-23 02:14:21 America
  Universal time: Sat 2016-07-23 02:14:21 UTC
        RTC time: Sat 2016-07-23 02:14:22
       Time zone: America/New_York (America, +0000)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

I want to understand for future reference: What's going wrong when I set the time zone to New York? Is there some file I can delete, and have the system regenerate a new file for New York?
(I am new to the forum. If this question is tangential to the original post (now, that I have the correct time showing), I can mark the post as [SOLVED] and ask this question in a separate post.)

Thank you.

Last edited by cfmg (2016-07-23 13:57:26)

Offline

#12 2016-07-23 03:07:03

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,463

Re: [SOLVED] Incorrect time set, hwclock --debug, timedatectl status shown

Try reinstalling the tzdata package.

Offline

#13 2016-07-23 13:57:01

cfmg
Member
Registered: 2016-07-18
Posts: 11

Re: [SOLVED] Incorrect time set, hwclock --debug, timedatectl status shown

Reinstalled tzdata. Changing the time zone to 'New York' after reinstalling give the following output for

timedatectl status
     Local time: Sat 2016-07-23 09:49:35 EDT
  Universal time: Sat 2016-07-23 13:49:35 UTC
        RTC time: Sat 2016-07-23 13:49:35
       Time zone: America/New_York (EDT, -0400)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

I think this solves the issue, and I hope there won't be any snags with daylight savings changes.

Thank you so much ewaller, dockalnd, and Scimmia for your help and suggestions.

(Marking the post as [SOLVED])

Offline

Board footer

Powered by FluxBB