[SOLVED] System time is +4hrs from hardware clock

Hello again.
Now I can't set up my system`s time properly. (Set system time from hardware clock)
Timezone is GMT+4 (Europe/Samara) and hardware clock (RTC) is set to proper time so does UTC.
But system`s time itself is 4 hours in the future from HW clock!
# hwclock --hctosys --utc
does nothing.
# timedatectl set-local-rtc 1
or
# timedatectl set-time "$mytime"
both do nothing and output following error:
Failed to issue method call: The name org.freedesktop.PolicyKit1 was not provided by any .service files
Also, removing /etc/adjtime does nothing!
How can I fix it?
Last edited by eruditorum (2012-11-25 10:52:14)

ewaller,
hwclock from util-linux 2.22.1
Using /dev interface to clock.
Last drift adjustment done at 1353744432 seconds after 1969
Last calibration done at 1353744432 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: 2012/11/25 05:40:17
Hw clock time : 2012/11/25 05:40:17 = 1353822017 seconds since 1969
Sun 25 Nov 2012 09:40:17 AM SAMT -0.907738 seconds
Last edited by eruditorum (2012-11-25 04:35:10)

Similar Messages

(SOLVED) system time refuses to change

My hwclock is correct. However, --systohc doesn't work. I also tried ntp and openntpd and they don't help any either.
Has anyone had a super-stubborn system clock?
I have tried UTC, localtime and the whole shebang. I can make the system clock change if I alter my location but I don't want to spoof my location just to fix my time. My location is set correctly but my system clock is about 14 hours in the future.
Last edited by Google (2011-08-12 01:17:14)

hwclock from util-linux 2.19.1
Using /dev interface to clock.
Last drift adjustment done at 1313128033 seconds after 1969
Last calibration done at 1313128033 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2011/08/12 15:07:28
Hw clock time : 2011/08/12 15:07:28 = 1313129248 seconds since 1969
Fri 12 Aug 2011 03:07:28 PM KST -0.063131 seconds

Hardware clock and system clock don't match

hello. i recently upgraded to kde 4.7, and i don't know if it's the culprit or not, but my system clock is now ahead of the hardware clock by the timezone offset.
my timezone is Asia/Manila, which is UTC+8. so if the correct time is 00:00, the system time is 08:00.
i dual boot with windows so the HARDWARECLOCK setting in /etc/rc.conf is set to localtime.
interestingly, the commands "hwclock --show" and "date" both show PHT as the timezone, but with the aforementioned time skew. to illustrate:
# hwclock --show
Fri 05 Aug 2011 10:45:02 AM PHT -0.500309 seconds
# date
Fri Aug 5 18:45:02 PHT 2011
running "hwclock --hctosys" fixes the problem while logged in, but restarting the computer reverts the problem. i could put a daemon that runs the command at startup, but i never needed to do that before and i'm not inclined to at the moment. i think this is just a misconfiguration somewhere.
thanks for any help you could give.

hello. it is
hwclock from util-linux 2.19.1
Using /dev interface to clock.
Last drift adjustment done at 1312511647 seconds after 1969
Last calibration done at 1304274137 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2011/08/05 12:08:46
Hw clock time : 2011/08/05 12:08:46 = 1312517326 seconds since 1969
Fri 05 Aug 2011 12:08:46 PM PHT -0.690104 seconds

[SOLVED] System clock / Timezone issues

Hey everyone,
The issue, as it appears to me, is that arch is assuming that my timezone is +00:00, or UTC. I don't really understand why (it should be +10:00) but here is the output to the frequently requested information for this issue
$ cat /etc/adjtime
0.000000 1349592374 0.000000
1349592374
UTC
$ date
Sun Oct 7 07:42:52 UTC 2012
$ date --utc
Sun Oct 7 07:43:18 UTC 2012
$ hwclock --debug
hwclock from util-linux 2.22
Using /dev interface to clock.
Last drift adjustment done at 1349592374 seconds after 1969
Last calibration done at 1349592374 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: 2012/10/07 07:43:54
Hw clock time : 2012/10/07 07:43:54 = 1349595834 seconds since 1969
Sun 07 Oct 2012 07:43:54 UTC -0.969672 seconds
$ ls -l /etc/localtime
lrwxrwxrwx 1 root root 37 Oct 7 06:39 /etc/localtime -> /usr/share/zoneinfo/Austalia/Brisbane
$ hwclock --show --utc
Sun 07 Oct 2012 07:44:53 UTC -0.687942 seconds
$ hwclock --show --localtime
Sun 07 Oct 2012 07:44:57 UTC -0.281630 seconds
I'm using sytemd, have no rc.conf file, my BIOS clock reported being in UTC. I've been trying to fix this issue for the past few hours (including searching the wiki entries for time, beginner's guide, systemd and many other user's issues related to the clocks/timezones.)
I hope it's just a case of I missed something crucial somehow. Any help is greatly aprpeciated
Last edited by hungryb (2012-10-07 08:40:58)

skunktrader wrote:You didn't need to reinstall tzdata. The reason for your error was a typo in the symlink
lrwxrwxrwx 1 root root 37 Oct 7 06:39 /etc/localtime -> /usr/share/zoneinfo/Austalia/Brisbane
Yeah, that's true, but I'd been remaking symlinks and changing the clock for a while before that iteration, I think it was only that version of the symlink that contained a spelling error.

[SOLVED] UTC Time Displaying Localtime

I am trying to get Conky to display the correct UTC time on my desktop, but the localtime is being displayed instead. In light of this issue, I concluded that the hardware clock must be set to use localtime, rather than UTC, and or that the system clock is not syncing correctly with the hardware clock on boot up.
So, I tried issuing the command
timedatectl set-local-rtc 0
to set the system time to use UTC as indicated in this ArchWiki page. However, even after rebooting, Conky still displays the localtime rather than the UTC time.
Issuing the command
timedatectl status
results in the output
Local time: Tue 2013-07-16 07:27:07 EDT
Universal time: Tue 2013-07-16 11:27:07 UTC
RTC time: Tue 2013-07-16 11:27:07
Timezone: America/New_York (EDT, -0400)
NTP enabled: n/a
NTP synchronized: no
RTC in local TZ: no
DST active: yes
Last DST change: DST began at
Sun 2013-03-10 01:59:59 EST
Sun 2013-03-10 03:00:00 EDT
Next DST change: DST ends (the clock jumps one hour backwards) at
Sun 2013-11-03 01:59:59 EDT
Sun 2013-11-03 01:00:00 EST
After having tried the above command without success, I then entered into the system BIOS on boot, and inspected the hardware clock time, which is correctly set to the UTC time.
So, after booting again into Arch Linux, I tried using the
hwclock
command to troubleshoot the problem.
Issuing the command
hwclock --debug
yields
hwclock from util-linux 2.23.1
Using /dev interface to clock.
Last drift adjustment done at 1373971186 seconds after 1969
Last calibration done at 1373971186 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: 2013/07/16 11:19:10
Hw clock time : 2013/07/16 11:19:10 = 1373973550 seconds since 1969
Tue 16 Jul 2013 07:19:10 AM EDT -0.985669 seconds
According to the output above, the
Hardware clock is on UTC time
, so I am not sure why the system clock is not syncing properly with the hardware clock on boot up.
Issuing the command
hwclock -r
yields
Tue 16 Jul 2013 07:37:51 AM EDT -0.797938 seconds
which displays localtime, instead of UTC.
In addition, I find it somewhat confusing that
hwclock --localtime
yields
Tue 16 Jul 2013 11:39:23 AM EDT -0.079090 seconds
which appears to be the UTC time, and issuing
hwclock --utc
yields
Tue 16 Jul 2013 07:40:17 AM EDT -0.485343 seconds
which appears to be the localtime.
I also tried using the command
hwclock --systohc
according to this question on serverfault.com, with no success.
The output of the
date
command is
Tue Jul 16 07:46:03 EDT 2013
, which appears to be the localtime, rather than the UTC time.
I noted that in the ouput of
timedatectl status
it says
NTP enabled: n/a
NTP synchronized: no
which I believe may be contributing to the problem, but I am somewhat unclear as to whether or not NTP is necessary for the system time to be correctly synced with the hardware clock and the UTC time.
Also, I am using the Conky Metro Clock Conky configuration for my .conkyrc file.
Any help would be greatly appreciated.
Thank you.
EDIT:
For clarification, I did not actually actual want to display the UTC time with Conky, but rather the localtime. I accidentally concluded that I wanted to display the UTC time because my hardware clock was synced to my localtime, rather than the actual UTC time. Therefore, this caused the UTC time to be synced with the localtime, and furthermore, the localtime to be 4 hours behind the correct localtime in my timezone (UTC-4hrs).
Last edited by kevin.gurney (2013-07-16 22:52:15)

kevin.gurney wrote:2ManyDogs, I don't actually want to display the UTC time. The reason why I originally wanted to display the UTC time was because it appeared to be the correct time because it was actually set to the localtime in my timezone. Therefore, the localtime that was being displayed on my system was actually 4 hours behind the correct time in my timezone relative to this UTC time since my timezone is UTC-4hrs. I apologize for the misunderstanding, although I do understand the difference between UTC and my localtime, it it simply a matter of the UTC time being incorrect on my system, and, therefore, the localtime, as well.
Ah. We could have helped you much more quickly if we understood what the real problem was. Oh well, at least you have it the way you want it now.
This is what confused me:
kevin.gurney wrote:I am trying to get Conky to display the correct UTC time on my desktop
With your last explanation, I understand what you were actually asking for.
Last edited by 2ManyDogs (2013-07-16 22:36:26)

Actual System Time

Hi Guys,
I was wondering if anyone could help me? I'm looking for a method to retrieve the actual system time. The time that I'm after is not the time that would be displayed on the user's clock, since this can be changed by the user, and is not a question relating to time zones, but the underlying time on which the actual time is calculated from.
The reason for this is I am hoping to have a time which cannot be changed by the owner of a device, so that when each device is first configured, it sends this time to the server so that it can by synchronized (by the server storing the difference between the device's system time & it's own against the device name in a database), and then offsetting the times in any data from this device by this amount. By doing this, even if the local time of the device were to be changed by the user after it's initial configuration, we would still get the time from the server (without the device needing to contact the server to get it's time). This would allow offline devices to be synchronized whilst protecting from user hacks.
Many thanks in advance,
JB

Hi folks,
thanks for all the feedback; it seems that you're right about users being able to change the time even at hardware level & about my proposed solution being impossible. For anyone coming to this post looking for a similar solution, here's what I've found out.
I had thought that the date & time were kept up to date by a hardware clock that constantly ran (even when the computer was turned off), that the system could use to work out universal time (by offsetting the hardware clock by an offset amount given when the time was last synchronised), and then the OS applied the time zone to this corrected time.
This is not far off what actually happens, except that in my theory, the hardware clock ran all the time, with the system time being offset from it, but running in parallel. What actually seems to happen is that when the computer boots up, the hardware time is read in as the system time (taken as either universal or local depending on the OS / config). The OS then applies the time zone offset as required (depending if an application asks for local or universal). However, when the system is shutdown, it updates the hardware clock with its own time (since the hardware clock is not very accurate, the OS time is considered more reliable since it is likely to have been synchronised with a more accurate clock). This means that should a user change the time, when the device is shutdown, the hardware clock is updated with the user's correction.
The only solution to my problem therefore seems to be to use universal time (avoiding daylight savings issues), have the system synchronise with the server when possible, and use security to block the users from altering the time.
Thanks again,
JB

System TIme out interval

Hi experts ,
any idea how to increase the system Time out interval from Set up
Thanks,
Tayi.

Tayi,
Are you speaking about the session timeout that a user experiences? If so, re-run configure.exe, and check the Change Session Timeout button, which will give you the option of adjusting it. You may also need to rebuild/redeploy the war/ear/sca/sda to incorporate the change.
Let us know if it works
-Howie Wexler
www.craftysystems.com

[SOLVED] Incorrect time displayed in my system

Hey Archers,
I have trouble correct time being displayed in my system.
My BIOS time is:
May 18 2012 08:39:21 PM IST
Date command displays
Sat May 19 02:09:59 IST 2012
Clearly the time displayed by date command is localtime+05:30 (Asia/Kolkata), when I expect it to be just localtime.
How do I correct this?
I dont dual boot and have just Arch installed on my machine.
And my /etc/rc.conf has this:
HARDWARECLOCK="UTC"
TIMEZONE="Asia/Kolkata"
Please correct if my understanding is wrong, but is this how it works?
When I say HARDWARECLOCK=UTC and TIMEZONE=''Asia/Kolkata",
It assumes, hardwareclock, time displayed by BIOS, is infact UTC, and, since the user is interested in timezone, +0530, it adds 0530 to hardware clock.
Thanks,
Nachiket.
Last edited by Nachiket (2012-05-19 07:22:47)

Hey Tectu,
The wiki article on Time was indeed splendid. It had all the information I needed. Thank you.
Trilby,
You were right, my hardware clock was on local time.
So this is what I did to set it correct.
1. Set the HARDWARECLOCK to "localtime" in /etc/rc.conf
HARDWARECLOCK="localtime"
TIMEZONE="Asia/Kolkata"
2. Reboot the system
3. Set the systemclock to UTC by doing a -0530 (minus 05 hours 30 minutes)
# date `date -d "-05 hours -30 mins" +%m%d%H%M%Y`
4. Copy the system clock value to hardware clock
# hwclock --systohc
5. Edit the /etc/rc.conf to set HARDWARECLOCK back to UTC
HARDWARECLOCK="UTC"
TIMEZONE="Asia/Kolkata"
6. Reboot the system.
And yes, now my system clock displays correct time
Just setting HARDWARECLOCK to "localtime" also worked. But since I the beginners guide recomments "UTC" I did all this.
Marking the thread as SOLVED.
Regards,
Nachiket.
Last edited by Nachiket (2012-05-19 07:23:33)

[SOLVED] System Clock Issues (Wrong UTC?)

**RESOLVED -- SEE END FOR FIX
Hello everyone.
First off I'd like to say that I am thrilled to be here. I've been an Ubuntu user for a few months now, but decided that it was time to take a trip down the rabbit hole and see all that Linux had to offer--and to that end I switched to Arch. And I must say that I have nothing but positive things to say of it. The documentation on the Arch Wiki was phenomenal in helping me get started on the process, and the installation of it has proved to be a very enjoyable learning experience.
With that said, I have run into a bit of a snag, and after perusing the documentation on the Wiki, as well as running a few Google searches and searches of this particular forum, am no closer to a solution that when I started, so here I am. The problem is with my clock.
Okay, so I live in the Eastern United States, and as a result have my local time set as Eastern, and I have my hardware clock running UTC. Here is the problem. . . For whatever reason, the time displayed on my clock is five hours behind. Perplexed, I decided to see if I had set up my time zone info incorrectly and ran the "timedatectl status" command, and the results were really strange. A copy paste of the output is here:
Local time: Thu, 2012-12-20 19:27:02 EST
Universal time: Fri, 2012-12-21 00:27:02 UTC
RTC time: Fri, 2012-12-21 00:27:02
Timezone: America/New_York
UTC offset: -0500
NTP enabled: no
NTP synchronized: no
RTC in local TZ: no
DST active: no
Last DST change: EDT → EST, DST became inactive
Sun, 2012-11-04 01:59:59 EDT
Sun, 2012-11-04 01:00:00 EST
Next DST change: EST → EDT, DST will become active
the clock will jump one hour forward
Sun, 2013-03-10 01:59:59 EST
Sun, 2013-03-10 03:00:00 EDT
As you can see, the time zone is set correctly to America/New_York (originally US/Eastern, but I changed it to try and resolve the problem--to no effect, obviously). However here is where it gets strange. As I type this, it is 00:27 local time. My computer has decided to use the local time for UTC, and then subtracts five hours (as I live in UTC -5) to get the local time that it displays.
I've tried rerunning the hwclock --systohc --utc command, to no avail.
If anyone has any input as to why my computer is confusing UTC and local time, and any way I could fix it, I would greatly appreciate it.
I could just change my timezone to UTC - 0, that would cause my system to display the right time (I think) but I'd rather actually fix the problem, instead of simply covering it up with a band aid, if it is possible.
Thank you,
Douglas
EDIT:
I probably should mention that the machines (I'm having this same problem on two different computers) are both running Arch Linux and Arch Linux alone, although one was originally a Windows 7 and the other a dual boot of Win 7 and Ubuntu.
RESOLUTION (Thanks lhoffman):
Install the network time protocol daemon. This will allow you to sync your system time over the internet.
sudo pacman -S ntp
Once installed, run the following command:
ntpdate pool.ntp.org
This will link your computer with the time servers of the NTP Pool Project. For me my clocks fixed themselves quickly after running the command. And that was it.
After running this command and setting the system clock, run:
hwclock -systohc (thanks Scimmia)
Otherwise the computer will mistake local time for UTC and subtract/add time based upon your timezone again upon reboot.
Last edited by douglasr (2012-12-21 21:23:11)

Scimmia wrote:Not exactly. The root of the problem is that your hardware clock is set to localtime. To change this, you need to update the system (software) clock, which ntpd already did for you. The timedatectl command would have just done that manually. Now that your system clock is correct, you need to write this to your hardware clock so that it is correct when you reboot. hwclock --systohc does that. If you don't run that command, the system will boot up thinking it's getting UTC from the hardware clock and will subtract 5 hours. Then, once ntpd runs, the time will skip ahead 5 hours. This will cause all kinds of issues.
I fixed this on my system too. Thanks for the explanation.

After recent upgrade to IOS 7 i an seeing systems rebooting very frequently. it just goes offline and comeback online after some time. IS this hardware issue or others also facing the same

After recent upgrade to IOS 7 i an seeing systems rebooting very frequently. it just goes offline and comeback online after some time. IS this hardware issue or others also facing the same

Hello there, Kishoresaraogi.
The following Knowledge Base article provides some great steps to troubleshoot your issue:
iPhone: Hardware troubleshooting
http://support.apple.com/kb/TS2802
Particularly:
Will not turn on, will not turn on unless connected to power, or unexpected power off
Verify that the Sleep/Wake button functions. If it does not function, inspect it for signs of damage. If the button is damaged or is not functioning when pressed, seek service.
Check if a Liquid Contact Indicator (LCI) is activated or there are signs of corrosion. Learn about LCIsand corrosion.
Connect the iPhone to the iPhone's USB power adapter and let it charge for at least ten minutes.
After at least 30 minutes, if:
The home screen appears: The iPhone should be working. Update to the latest version of iOS if necessary. Continue charging it until it is completely charged and you see this battery icon in the upper-right corner of the screen . Then unplug the phone from power. If it immediately turns off, seek service.
The low-battery image appears, even after the phone has charged for at least 20 minutes: See "iPhone displays the low-battery image and is unresponsive" symptom in this article.
Something other than the Home screen or Low Battery image appears, continue with this article for further troubleshooting steps.
If the iPhone did not turn on, reset it while connected to the iPhone USB power adapter.
If the display turns on, go to step 4.
If the display remains black, go to next step.
Connect the iPhone to a computer and open iTunes. If iTunes recognizes the iPhone and indicates that it is in recovery mode, attempt to restore the iPhone. If the iPhone doesn't appear in iTunes or if you have difficulties in restoring the iPhone, see this article for further assistance.
If restoring the iPhone resolved the issue, go to step 4. If restoring the iPhone did not solve the issue, seek service.
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro.

Time and date from an atomic clock

Hi,
I want to make an application in Labview 6i which gets the time and date
from an atomic clock (this is a must!). What is the easiest way to do this?
Regards,
Sergio

Sergio Cruz wrote:
>
> Hi,
>
> I want to make an application in Labview 6i which gets the time and date
> from an atomic clock (this is a must!). What is the easiest way to do this?
You cannot maintain atomic clock accuracy using software on a PC. Think
about it. You're running on a PC whose clock may gain milliseconds per
day if you're lucky, probably seconds / day.
Out of the box, Windows can do things (like downloading Windows updates)
which can delay operations for seconds.
It can take several milliseconds to update an indicator that shows the
time, if that is what you plan to do.
I can see some approaches:
* If you can accept moderate accuracy of about 1-10 ms run software such
as Dimension 4 from www.thinkman.com.
That can be set up to run ever
y 15 minutes, automatically synchronizing
your PC to Internet time servers.
You don't need to control it from LabVIEW; if you had to, you could run
the executable C:\Program Files\D4\D4.exe using System Exec.
* You haven't described what you are doing. If you want more accurate
time keeping, then you might get a timekeeping board to plug into your
PC and control any other hardware you may be using.
Search the Web for "IRIG board".
Good luck, Mark

How to get system time from cRIO?

Hello,
I have an NI cRIO-9076 chassis with an NI-9467 GPS module and an NI-9234 module.
I've downloaded the FPGA Timekeeper application which synchronises the FPGA clock to the 1PPS GPS, this works well. What I want to do is create a trigger that at a pre-defined HH:MMS the system will start to acquire and log data from the Accelerometers connected to the NI-9234 module.
I have added the controls for the entry of the HH:MMS and calculated the time in seconds. I would like to compare the system clock once it is locked to the entered timestamp and then trigger.
As I only have a value that represents seconds in the day I need to calculate the offset from EPOCH to compare against the GPS time reference. I have read that the NI system clock runs from 01/01/1904 instead of the EPOCH 01/01/1970.
The question is how do I get the current system time so that I can compare it against the entered time? I only need seconds in the day = (HH * 3600) + (MM * 60) + (SS)
Thank you,
Kind Regards,
Simon

You should use the Get Date/Time in Seconds VI which will return a timestamp. You can then format this timestamp using the Format Date/Time String to give you exactly the time format that you need. Then you can extract the numbers you need and do your math.
www.movimed.com - Custom Imaging Solutions
Attachments:
Get Seconds in Day.vi ‏9 KB

Times in system.log different than server's clock

Hello,
The time that an event is recorded in system.log is different that the current time in the server's clock. For example, there is the entry:
Dec 7 02:22:42 XServe DirectoryService[52]: Failed Authentication ....
but the time on the server is Dec 7 12.22:42.
I use Mac OS X Server 10.4.3.
Thanks in advance for any suggestions on how to make the times appear correctly in system.log.

I've tried this:
I've put log4j.jar to the lib dir of the logicalhost and log4j.properties to another jar (my own) and put it to the lib dir too. I deleted the PropertyCOnfigurator.configure() line from the apps. Built it, manually deleted log4j.jar from the EARs. Then I deployed EARs, restarted the domain and ran the apps. They both logged to the same and correct file, but again the rolling didn't work. How is this possible? I thought that this way the IS should have one and only one instance of Log4j...

Subtract minutes from system time

Hi Experts,
I want to subtract 5 min from the system time.
Is there any function module.
Regards,
Chandu

Hi Chandu,
Use the below statment to subtract 5 minutes:
data: v_time type sy-uzeit.
v_time = sy-uzeit.
v_time = v_time - 300.
This might solve your problem.
Thanks,
Chidanand

System Time is Incorrect After Waking From Hibernation

If my MBA runs out of battery when its asleep, after coming back to life, the system time is wrong. The time is correct when it comes back from normal sleep.
Message was edited by: DrFooMod2 -- Corrected OS version

Hi
Same here. On PC boards the clock is usually buffered by a small battery.
Maybe there is no battery in the MBA. But the clock is synchronized over the internet by asking a time server. So you dont need to do it manually
HTH
Enno
DrFooMod2 wrote:
If my MBA runs out of battery when its asleep, after coming back to life, the system time is wrong. The time is correct when it comes back from normal sleep.
Message was edited by: DrFooMod2 -- Corrected OS version

[SOLVED] System time is +4hrs from hardware clock

Similar Messages

Maybe you are looking for