RTC and System clock not in sync

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite
1












How to set the system clock sync with RTC (Hardware Clock / BIOS). I am writing a script that uses a system clock in order to start the system with alarm.
For this the sole requirement is to have a proper RTC clock. On my test system (SLES 10 SP4), I use NTP Server to manage the system clock. But the RTC clock is always ahead.
So for example : currently the system clock shows 14:00 26.05.2016 and the RTC shows 16:00 Hrs. I read the man pages of hwclock and it shows that following command
would sync the RTC clock to system clock. Which it did.



hwclock --systohc --localtime.



But after a reboot/shutdown, when the system comes up again , the RTC is again messed up. So there is something more which controls the RTC when the system is rebooted.
Could someone point me in the right direction. Thanx in advance.










share|improve this question





















  • What time zone is the system set to? Try using --utc rather than --localtime. Lastly, what does hwclock show after you run it with --systohc?
    – mkomarinski
    May 26 '16 at 13:10










  • A Unix system's system clock should be set to UTC.
    – Kusalananda
    Apr 7 at 7:51














up vote
1
down vote

favorite
1












How to set the system clock sync with RTC (Hardware Clock / BIOS). I am writing a script that uses a system clock in order to start the system with alarm.
For this the sole requirement is to have a proper RTC clock. On my test system (SLES 10 SP4), I use NTP Server to manage the system clock. But the RTC clock is always ahead.
So for example : currently the system clock shows 14:00 26.05.2016 and the RTC shows 16:00 Hrs. I read the man pages of hwclock and it shows that following command
would sync the RTC clock to system clock. Which it did.



hwclock --systohc --localtime.



But after a reboot/shutdown, when the system comes up again , the RTC is again messed up. So there is something more which controls the RTC when the system is rebooted.
Could someone point me in the right direction. Thanx in advance.










share|improve this question





















  • What time zone is the system set to? Try using --utc rather than --localtime. Lastly, what does hwclock show after you run it with --systohc?
    – mkomarinski
    May 26 '16 at 13:10










  • A Unix system's system clock should be set to UTC.
    – Kusalananda
    Apr 7 at 7:51












up vote
1
down vote

favorite
1









up vote
1
down vote

favorite
1






1





How to set the system clock sync with RTC (Hardware Clock / BIOS). I am writing a script that uses a system clock in order to start the system with alarm.
For this the sole requirement is to have a proper RTC clock. On my test system (SLES 10 SP4), I use NTP Server to manage the system clock. But the RTC clock is always ahead.
So for example : currently the system clock shows 14:00 26.05.2016 and the RTC shows 16:00 Hrs. I read the man pages of hwclock and it shows that following command
would sync the RTC clock to system clock. Which it did.



hwclock --systohc --localtime.



But after a reboot/shutdown, when the system comes up again , the RTC is again messed up. So there is something more which controls the RTC when the system is rebooted.
Could someone point me in the right direction. Thanx in advance.










share|improve this question













How to set the system clock sync with RTC (Hardware Clock / BIOS). I am writing a script that uses a system clock in order to start the system with alarm.
For this the sole requirement is to have a proper RTC clock. On my test system (SLES 10 SP4), I use NTP Server to manage the system clock. But the RTC clock is always ahead.
So for example : currently the system clock shows 14:00 26.05.2016 and the RTC shows 16:00 Hrs. I read the man pages of hwclock and it shows that following command
would sync the RTC clock to system clock. Which it did.



hwclock --systohc --localtime.



But after a reboot/shutdown, when the system comes up again , the RTC is again messed up. So there is something more which controls the RTC when the system is rebooted.
Could someone point me in the right direction. Thanx in advance.







linux suse






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked May 26 '16 at 13:01









Sachin H

1614




1614











  • What time zone is the system set to? Try using --utc rather than --localtime. Lastly, what does hwclock show after you run it with --systohc?
    – mkomarinski
    May 26 '16 at 13:10










  • A Unix system's system clock should be set to UTC.
    – Kusalananda
    Apr 7 at 7:51
















  • What time zone is the system set to? Try using --utc rather than --localtime. Lastly, what does hwclock show after you run it with --systohc?
    – mkomarinski
    May 26 '16 at 13:10










  • A Unix system's system clock should be set to UTC.
    – Kusalananda
    Apr 7 at 7:51















What time zone is the system set to? Try using --utc rather than --localtime. Lastly, what does hwclock show after you run it with --systohc?
– mkomarinski
May 26 '16 at 13:10




What time zone is the system set to? Try using --utc rather than --localtime. Lastly, what does hwclock show after you run it with --systohc?
– mkomarinski
May 26 '16 at 13:10












A Unix system's system clock should be set to UTC.
– Kusalananda
Apr 7 at 7:51




A Unix system's system clock should be set to UTC.
– Kusalananda
Apr 7 at 7:51










3 Answers
3






active

oldest

votes

















up vote
0
down vote













You can use the hwclock command to set the hardware clock.

From the man hwclock page :



 --set Set the Hardware Clock to the time given by the --date option.


You can apply the current system time to the hw clock with :



hwclock -w


or even manually with :



hwclock --set --date "$(date)"


After you added details to your question, my answer is not enough though, so here are more details below.

You can check timezone with the timedatectl status command.

List timezones with timedatectl list-timezones.

You can set your timezone to UTC for example with timedatectl set-timezone UTC.

You will find more details about timezone settings here.






share|improve this answer






















  • I tried above command but it did not set the time. pluto:~ # curr_da=$(date "+%d %m %Y %H:%M") pluto:~ # echo $curr_da 26 05 2016 16:45 pluto:~ # hwclock --set --date "$curr_da" date: invalid date `26 05 2016 16:45' The date command issued by hwclock returned unexpected results. The command was: date --date="26 05 2016 16:45" +seconds-into-epoch=%s The response was: No usable set-to time. Cannot set clock. pluto:~ #
    – Sachin H
    May 26 '16 at 13:32











  • thanx but timedatectl command not found.
    – Sachin H
    May 26 '16 at 13:39










  • ok hwclock -w or my corrected example should work. can you install timedatectl ?
    – mazs
    May 26 '16 at 13:45










  • Since my Installation Timezone is CEST . It makes sense that system clock always goes +2Hrs ahead than RTC (which i manually set to current time). So e.g. here the current time is = 11:00 which I set in BIOS as well. And then booted the system and it shows now : 13:00 But then how do I set both these clocks show same time? I dont think I should change the timezone completely as it is correctly set to Europe.
    – Sachin H
    May 27 '16 at 9:03

















up vote
0
down vote













It depends how you system is set up. Normally Unix expects the RTC to be in GMT/UTC, and the system knows its offset/timezone... But this is incompatible with old Windows systems that expect the RTC to be in local time and this causes problems in multi-boot systems. So there is a setting in /etc/default/rcS to tell if your system uses a RTC in GMT or local time (you likely want the latter, which is not the default):



# assume that the BIOS clock is set to UTC time (recommended)
UTC=yes





share|improve this answer




















  • # hwclock --debug hwclock from util-linux-2.12r Using /dev/rtc interface to clock. Last drift adjustment done at 1464276196 seconds after 1969 Last calibration done at 1464276196 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: 2016/05/26 17:49:55 Hw clock time : 2016/05/26 17:49:55 = 1464277795 seconds since 1969 Thu May 26 17:49:55 2016 -0.000185 seconds
    – Sachin H
    May 26 '16 at 14:37

















up vote
0
down vote













Is this a virtual machine? Or a physical system on blade hardware?



Some manufacturers' blade hardware has an option to sync the hardware clocks of each blade to the clock of the management processor of the blade enclosure. At least on (some models of) Fujitsu's blade hardware, this sync option was enabled by default. To turn it off, you had to access the BIOS settings of the blade.



Virtual machines usually sync their virtual hardware clock according to the clock of the physical host system at VM initialization time, since a virtual machine cannot have a real physical hardware clock. If your hosting provider has primarily Windows systems, the syncing may have been configured to use local time rather than UTC.






share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f285674%2frtc-and-system-clock-not-in-sync%23new-answer', 'question_page');

    );

    Post as a guest






























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    You can use the hwclock command to set the hardware clock.

    From the man hwclock page :



     --set Set the Hardware Clock to the time given by the --date option.


    You can apply the current system time to the hw clock with :



    hwclock -w


    or even manually with :



    hwclock --set --date "$(date)"


    After you added details to your question, my answer is not enough though, so here are more details below.

    You can check timezone with the timedatectl status command.

    List timezones with timedatectl list-timezones.

    You can set your timezone to UTC for example with timedatectl set-timezone UTC.

    You will find more details about timezone settings here.






    share|improve this answer






















    • I tried above command but it did not set the time. pluto:~ # curr_da=$(date "+%d %m %Y %H:%M") pluto:~ # echo $curr_da 26 05 2016 16:45 pluto:~ # hwclock --set --date "$curr_da" date: invalid date `26 05 2016 16:45' The date command issued by hwclock returned unexpected results. The command was: date --date="26 05 2016 16:45" +seconds-into-epoch=%s The response was: No usable set-to time. Cannot set clock. pluto:~ #
      – Sachin H
      May 26 '16 at 13:32











    • thanx but timedatectl command not found.
      – Sachin H
      May 26 '16 at 13:39










    • ok hwclock -w or my corrected example should work. can you install timedatectl ?
      – mazs
      May 26 '16 at 13:45










    • Since my Installation Timezone is CEST . It makes sense that system clock always goes +2Hrs ahead than RTC (which i manually set to current time). So e.g. here the current time is = 11:00 which I set in BIOS as well. And then booted the system and it shows now : 13:00 But then how do I set both these clocks show same time? I dont think I should change the timezone completely as it is correctly set to Europe.
      – Sachin H
      May 27 '16 at 9:03














    up vote
    0
    down vote













    You can use the hwclock command to set the hardware clock.

    From the man hwclock page :



     --set Set the Hardware Clock to the time given by the --date option.


    You can apply the current system time to the hw clock with :



    hwclock -w


    or even manually with :



    hwclock --set --date "$(date)"


    After you added details to your question, my answer is not enough though, so here are more details below.

    You can check timezone with the timedatectl status command.

    List timezones with timedatectl list-timezones.

    You can set your timezone to UTC for example with timedatectl set-timezone UTC.

    You will find more details about timezone settings here.






    share|improve this answer






















    • I tried above command but it did not set the time. pluto:~ # curr_da=$(date "+%d %m %Y %H:%M") pluto:~ # echo $curr_da 26 05 2016 16:45 pluto:~ # hwclock --set --date "$curr_da" date: invalid date `26 05 2016 16:45' The date command issued by hwclock returned unexpected results. The command was: date --date="26 05 2016 16:45" +seconds-into-epoch=%s The response was: No usable set-to time. Cannot set clock. pluto:~ #
      – Sachin H
      May 26 '16 at 13:32











    • thanx but timedatectl command not found.
      – Sachin H
      May 26 '16 at 13:39










    • ok hwclock -w or my corrected example should work. can you install timedatectl ?
      – mazs
      May 26 '16 at 13:45










    • Since my Installation Timezone is CEST . It makes sense that system clock always goes +2Hrs ahead than RTC (which i manually set to current time). So e.g. here the current time is = 11:00 which I set in BIOS as well. And then booted the system and it shows now : 13:00 But then how do I set both these clocks show same time? I dont think I should change the timezone completely as it is correctly set to Europe.
      – Sachin H
      May 27 '16 at 9:03












    up vote
    0
    down vote










    up vote
    0
    down vote









    You can use the hwclock command to set the hardware clock.

    From the man hwclock page :



     --set Set the Hardware Clock to the time given by the --date option.


    You can apply the current system time to the hw clock with :



    hwclock -w


    or even manually with :



    hwclock --set --date "$(date)"


    After you added details to your question, my answer is not enough though, so here are more details below.

    You can check timezone with the timedatectl status command.

    List timezones with timedatectl list-timezones.

    You can set your timezone to UTC for example with timedatectl set-timezone UTC.

    You will find more details about timezone settings here.






    share|improve this answer














    You can use the hwclock command to set the hardware clock.

    From the man hwclock page :



     --set Set the Hardware Clock to the time given by the --date option.


    You can apply the current system time to the hw clock with :



    hwclock -w


    or even manually with :



    hwclock --set --date "$(date)"


    After you added details to your question, my answer is not enough though, so here are more details below.

    You can check timezone with the timedatectl status command.

    List timezones with timedatectl list-timezones.

    You can set your timezone to UTC for example with timedatectl set-timezone UTC.

    You will find more details about timezone settings here.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited May 26 '16 at 13:44

























    answered May 26 '16 at 13:08









    mazs

    2,5251522




    2,5251522











    • I tried above command but it did not set the time. pluto:~ # curr_da=$(date "+%d %m %Y %H:%M") pluto:~ # echo $curr_da 26 05 2016 16:45 pluto:~ # hwclock --set --date "$curr_da" date: invalid date `26 05 2016 16:45' The date command issued by hwclock returned unexpected results. The command was: date --date="26 05 2016 16:45" +seconds-into-epoch=%s The response was: No usable set-to time. Cannot set clock. pluto:~ #
      – Sachin H
      May 26 '16 at 13:32











    • thanx but timedatectl command not found.
      – Sachin H
      May 26 '16 at 13:39










    • ok hwclock -w or my corrected example should work. can you install timedatectl ?
      – mazs
      May 26 '16 at 13:45










    • Since my Installation Timezone is CEST . It makes sense that system clock always goes +2Hrs ahead than RTC (which i manually set to current time). So e.g. here the current time is = 11:00 which I set in BIOS as well. And then booted the system and it shows now : 13:00 But then how do I set both these clocks show same time? I dont think I should change the timezone completely as it is correctly set to Europe.
      – Sachin H
      May 27 '16 at 9:03
















    • I tried above command but it did not set the time. pluto:~ # curr_da=$(date "+%d %m %Y %H:%M") pluto:~ # echo $curr_da 26 05 2016 16:45 pluto:~ # hwclock --set --date "$curr_da" date: invalid date `26 05 2016 16:45' The date command issued by hwclock returned unexpected results. The command was: date --date="26 05 2016 16:45" +seconds-into-epoch=%s The response was: No usable set-to time. Cannot set clock. pluto:~ #
      – Sachin H
      May 26 '16 at 13:32











    • thanx but timedatectl command not found.
      – Sachin H
      May 26 '16 at 13:39










    • ok hwclock -w or my corrected example should work. can you install timedatectl ?
      – mazs
      May 26 '16 at 13:45










    • Since my Installation Timezone is CEST . It makes sense that system clock always goes +2Hrs ahead than RTC (which i manually set to current time). So e.g. here the current time is = 11:00 which I set in BIOS as well. And then booted the system and it shows now : 13:00 But then how do I set both these clocks show same time? I dont think I should change the timezone completely as it is correctly set to Europe.
      – Sachin H
      May 27 '16 at 9:03















    I tried above command but it did not set the time. pluto:~ # curr_da=$(date "+%d %m %Y %H:%M") pluto:~ # echo $curr_da 26 05 2016 16:45 pluto:~ # hwclock --set --date "$curr_da" date: invalid date `26 05 2016 16:45' The date command issued by hwclock returned unexpected results. The command was: date --date="26 05 2016 16:45" +seconds-into-epoch=%s The response was: No usable set-to time. Cannot set clock. pluto:~ #
    – Sachin H
    May 26 '16 at 13:32





    I tried above command but it did not set the time. pluto:~ # curr_da=$(date "+%d %m %Y %H:%M") pluto:~ # echo $curr_da 26 05 2016 16:45 pluto:~ # hwclock --set --date "$curr_da" date: invalid date `26 05 2016 16:45' The date command issued by hwclock returned unexpected results. The command was: date --date="26 05 2016 16:45" +seconds-into-epoch=%s The response was: No usable set-to time. Cannot set clock. pluto:~ #
    – Sachin H
    May 26 '16 at 13:32













    thanx but timedatectl command not found.
    – Sachin H
    May 26 '16 at 13:39




    thanx but timedatectl command not found.
    – Sachin H
    May 26 '16 at 13:39












    ok hwclock -w or my corrected example should work. can you install timedatectl ?
    – mazs
    May 26 '16 at 13:45




    ok hwclock -w or my corrected example should work. can you install timedatectl ?
    – mazs
    May 26 '16 at 13:45












    Since my Installation Timezone is CEST . It makes sense that system clock always goes +2Hrs ahead than RTC (which i manually set to current time). So e.g. here the current time is = 11:00 which I set in BIOS as well. And then booted the system and it shows now : 13:00 But then how do I set both these clocks show same time? I dont think I should change the timezone completely as it is correctly set to Europe.
    – Sachin H
    May 27 '16 at 9:03




    Since my Installation Timezone is CEST . It makes sense that system clock always goes +2Hrs ahead than RTC (which i manually set to current time). So e.g. here the current time is = 11:00 which I set in BIOS as well. And then booted the system and it shows now : 13:00 But then how do I set both these clocks show same time? I dont think I should change the timezone completely as it is correctly set to Europe.
    – Sachin H
    May 27 '16 at 9:03












    up vote
    0
    down vote













    It depends how you system is set up. Normally Unix expects the RTC to be in GMT/UTC, and the system knows its offset/timezone... But this is incompatible with old Windows systems that expect the RTC to be in local time and this causes problems in multi-boot systems. So there is a setting in /etc/default/rcS to tell if your system uses a RTC in GMT or local time (you likely want the latter, which is not the default):



    # assume that the BIOS clock is set to UTC time (recommended)
    UTC=yes





    share|improve this answer




















    • # hwclock --debug hwclock from util-linux-2.12r Using /dev/rtc interface to clock. Last drift adjustment done at 1464276196 seconds after 1969 Last calibration done at 1464276196 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: 2016/05/26 17:49:55 Hw clock time : 2016/05/26 17:49:55 = 1464277795 seconds since 1969 Thu May 26 17:49:55 2016 -0.000185 seconds
      – Sachin H
      May 26 '16 at 14:37














    up vote
    0
    down vote













    It depends how you system is set up. Normally Unix expects the RTC to be in GMT/UTC, and the system knows its offset/timezone... But this is incompatible with old Windows systems that expect the RTC to be in local time and this causes problems in multi-boot systems. So there is a setting in /etc/default/rcS to tell if your system uses a RTC in GMT or local time (you likely want the latter, which is not the default):



    # assume that the BIOS clock is set to UTC time (recommended)
    UTC=yes





    share|improve this answer




















    • # hwclock --debug hwclock from util-linux-2.12r Using /dev/rtc interface to clock. Last drift adjustment done at 1464276196 seconds after 1969 Last calibration done at 1464276196 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: 2016/05/26 17:49:55 Hw clock time : 2016/05/26 17:49:55 = 1464277795 seconds since 1969 Thu May 26 17:49:55 2016 -0.000185 seconds
      – Sachin H
      May 26 '16 at 14:37












    up vote
    0
    down vote










    up vote
    0
    down vote









    It depends how you system is set up. Normally Unix expects the RTC to be in GMT/UTC, and the system knows its offset/timezone... But this is incompatible with old Windows systems that expect the RTC to be in local time and this causes problems in multi-boot systems. So there is a setting in /etc/default/rcS to tell if your system uses a RTC in GMT or local time (you likely want the latter, which is not the default):



    # assume that the BIOS clock is set to UTC time (recommended)
    UTC=yes





    share|improve this answer












    It depends how you system is set up. Normally Unix expects the RTC to be in GMT/UTC, and the system knows its offset/timezone... But this is incompatible with old Windows systems that expect the RTC to be in local time and this causes problems in multi-boot systems. So there is a setting in /etc/default/rcS to tell if your system uses a RTC in GMT or local time (you likely want the latter, which is not the default):



    # assume that the BIOS clock is set to UTC time (recommended)
    UTC=yes






    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered May 26 '16 at 13:57









    xenoid

    1,7171620




    1,7171620











    • # hwclock --debug hwclock from util-linux-2.12r Using /dev/rtc interface to clock. Last drift adjustment done at 1464276196 seconds after 1969 Last calibration done at 1464276196 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: 2016/05/26 17:49:55 Hw clock time : 2016/05/26 17:49:55 = 1464277795 seconds since 1969 Thu May 26 17:49:55 2016 -0.000185 seconds
      – Sachin H
      May 26 '16 at 14:37
















    • # hwclock --debug hwclock from util-linux-2.12r Using /dev/rtc interface to clock. Last drift adjustment done at 1464276196 seconds after 1969 Last calibration done at 1464276196 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: 2016/05/26 17:49:55 Hw clock time : 2016/05/26 17:49:55 = 1464277795 seconds since 1969 Thu May 26 17:49:55 2016 -0.000185 seconds
      – Sachin H
      May 26 '16 at 14:37















    # hwclock --debug hwclock from util-linux-2.12r Using /dev/rtc interface to clock. Last drift adjustment done at 1464276196 seconds after 1969 Last calibration done at 1464276196 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: 2016/05/26 17:49:55 Hw clock time : 2016/05/26 17:49:55 = 1464277795 seconds since 1969 Thu May 26 17:49:55 2016 -0.000185 seconds
    – Sachin H
    May 26 '16 at 14:37




    # hwclock --debug hwclock from util-linux-2.12r Using /dev/rtc interface to clock. Last drift adjustment done at 1464276196 seconds after 1969 Last calibration done at 1464276196 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: 2016/05/26 17:49:55 Hw clock time : 2016/05/26 17:49:55 = 1464277795 seconds since 1969 Thu May 26 17:49:55 2016 -0.000185 seconds
    – Sachin H
    May 26 '16 at 14:37










    up vote
    0
    down vote













    Is this a virtual machine? Or a physical system on blade hardware?



    Some manufacturers' blade hardware has an option to sync the hardware clocks of each blade to the clock of the management processor of the blade enclosure. At least on (some models of) Fujitsu's blade hardware, this sync option was enabled by default. To turn it off, you had to access the BIOS settings of the blade.



    Virtual machines usually sync their virtual hardware clock according to the clock of the physical host system at VM initialization time, since a virtual machine cannot have a real physical hardware clock. If your hosting provider has primarily Windows systems, the syncing may have been configured to use local time rather than UTC.






    share|improve this answer
























      up vote
      0
      down vote













      Is this a virtual machine? Or a physical system on blade hardware?



      Some manufacturers' blade hardware has an option to sync the hardware clocks of each blade to the clock of the management processor of the blade enclosure. At least on (some models of) Fujitsu's blade hardware, this sync option was enabled by default. To turn it off, you had to access the BIOS settings of the blade.



      Virtual machines usually sync their virtual hardware clock according to the clock of the physical host system at VM initialization time, since a virtual machine cannot have a real physical hardware clock. If your hosting provider has primarily Windows systems, the syncing may have been configured to use local time rather than UTC.






      share|improve this answer






















        up vote
        0
        down vote










        up vote
        0
        down vote









        Is this a virtual machine? Or a physical system on blade hardware?



        Some manufacturers' blade hardware has an option to sync the hardware clocks of each blade to the clock of the management processor of the blade enclosure. At least on (some models of) Fujitsu's blade hardware, this sync option was enabled by default. To turn it off, you had to access the BIOS settings of the blade.



        Virtual machines usually sync their virtual hardware clock according to the clock of the physical host system at VM initialization time, since a virtual machine cannot have a real physical hardware clock. If your hosting provider has primarily Windows systems, the syncing may have been configured to use local time rather than UTC.






        share|improve this answer












        Is this a virtual machine? Or a physical system on blade hardware?



        Some manufacturers' blade hardware has an option to sync the hardware clocks of each blade to the clock of the management processor of the blade enclosure. At least on (some models of) Fujitsu's blade hardware, this sync option was enabled by default. To turn it off, you had to access the BIOS settings of the blade.



        Virtual machines usually sync their virtual hardware clock according to the clock of the physical host system at VM initialization time, since a virtual machine cannot have a real physical hardware clock. If your hosting provider has primarily Windows systems, the syncing may have been configured to use local time rather than UTC.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Apr 7 at 7:46









        telcoM

        11.9k11335




        11.9k11335



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f285674%2frtc-and-system-clock-not-in-sync%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay