Why did system forget date for a few hours after reboot?

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












3















I have cron command that runs a shutdown bash script at 12:10am every day.



10 0 * * * /bin/bash /var/www/scripts/special-reboot.sh


The script is very basic, all it does is shutdown nginx and moves data from MEMORY tables in MySQL to normal tables. Then it performs sudo /sbin/shutdown -r now 'Daily restart.'



It's been running well for about a month or two, however last night something very strange happened and I need to know why.



I have a python logging script which checks that important processes are running every 15 minutes. After the reboot last night, the log looked like this (note the dates and times).



[2019-02-12 23:45] 
...
[2019-02-13 00:00]
...
[2016-11-04 03:30]
...
[2016-11-04 03:45]
...
[2016-11-04 04:00]
...
[2016-11-04 04:15]
...
[2016-11-04 04:30]
...
[2016-11-04 04:45]
...
[2016-11-04 05:00]
...
[2016-11-04 05:15]
...
[2016-11-04 05:30]
...
[2019-02-13 02:30]
...
[2019-02-13 02:45]
...
[2019-02-13 03:00]


As you can see, it suddenly starts counting from a different date time for about two hours, and then it goes back to normal.



The scariest part is that it wasn't only the python script that was affected. Another C script that tracks electrical pulses is missing data from that period of time.



I don't know what could've caused this. I know, due to my logging script that all of the important programs were running absolutely fine during this time period. I believe this is most likely a problem with the system rather than my programs.










share|improve this question


























    3















    I have cron command that runs a shutdown bash script at 12:10am every day.



    10 0 * * * /bin/bash /var/www/scripts/special-reboot.sh


    The script is very basic, all it does is shutdown nginx and moves data from MEMORY tables in MySQL to normal tables. Then it performs sudo /sbin/shutdown -r now 'Daily restart.'



    It's been running well for about a month or two, however last night something very strange happened and I need to know why.



    I have a python logging script which checks that important processes are running every 15 minutes. After the reboot last night, the log looked like this (note the dates and times).



    [2019-02-12 23:45] 
    ...
    [2019-02-13 00:00]
    ...
    [2016-11-04 03:30]
    ...
    [2016-11-04 03:45]
    ...
    [2016-11-04 04:00]
    ...
    [2016-11-04 04:15]
    ...
    [2016-11-04 04:30]
    ...
    [2016-11-04 04:45]
    ...
    [2016-11-04 05:00]
    ...
    [2016-11-04 05:15]
    ...
    [2016-11-04 05:30]
    ...
    [2019-02-13 02:30]
    ...
    [2019-02-13 02:45]
    ...
    [2019-02-13 03:00]


    As you can see, it suddenly starts counting from a different date time for about two hours, and then it goes back to normal.



    The scariest part is that it wasn't only the python script that was affected. Another C script that tracks electrical pulses is missing data from that period of time.



    I don't know what could've caused this. I know, due to my logging script that all of the important programs were running absolutely fine during this time period. I believe this is most likely a problem with the system rather than my programs.










    share|improve this question
























      3












      3








      3


      0






      I have cron command that runs a shutdown bash script at 12:10am every day.



      10 0 * * * /bin/bash /var/www/scripts/special-reboot.sh


      The script is very basic, all it does is shutdown nginx and moves data from MEMORY tables in MySQL to normal tables. Then it performs sudo /sbin/shutdown -r now 'Daily restart.'



      It's been running well for about a month or two, however last night something very strange happened and I need to know why.



      I have a python logging script which checks that important processes are running every 15 minutes. After the reboot last night, the log looked like this (note the dates and times).



      [2019-02-12 23:45] 
      ...
      [2019-02-13 00:00]
      ...
      [2016-11-04 03:30]
      ...
      [2016-11-04 03:45]
      ...
      [2016-11-04 04:00]
      ...
      [2016-11-04 04:15]
      ...
      [2016-11-04 04:30]
      ...
      [2016-11-04 04:45]
      ...
      [2016-11-04 05:00]
      ...
      [2016-11-04 05:15]
      ...
      [2016-11-04 05:30]
      ...
      [2019-02-13 02:30]
      ...
      [2019-02-13 02:45]
      ...
      [2019-02-13 03:00]


      As you can see, it suddenly starts counting from a different date time for about two hours, and then it goes back to normal.



      The scariest part is that it wasn't only the python script that was affected. Another C script that tracks electrical pulses is missing data from that period of time.



      I don't know what could've caused this. I know, due to my logging script that all of the important programs were running absolutely fine during this time period. I believe this is most likely a problem with the system rather than my programs.










      share|improve this question














      I have cron command that runs a shutdown bash script at 12:10am every day.



      10 0 * * * /bin/bash /var/www/scripts/special-reboot.sh


      The script is very basic, all it does is shutdown nginx and moves data from MEMORY tables in MySQL to normal tables. Then it performs sudo /sbin/shutdown -r now 'Daily restart.'



      It's been running well for about a month or two, however last night something very strange happened and I need to know why.



      I have a python logging script which checks that important processes are running every 15 minutes. After the reboot last night, the log looked like this (note the dates and times).



      [2019-02-12 23:45] 
      ...
      [2019-02-13 00:00]
      ...
      [2016-11-04 03:30]
      ...
      [2016-11-04 03:45]
      ...
      [2016-11-04 04:00]
      ...
      [2016-11-04 04:15]
      ...
      [2016-11-04 04:30]
      ...
      [2016-11-04 04:45]
      ...
      [2016-11-04 05:00]
      ...
      [2016-11-04 05:15]
      ...
      [2016-11-04 05:30]
      ...
      [2019-02-13 02:30]
      ...
      [2019-02-13 02:45]
      ...
      [2019-02-13 03:00]


      As you can see, it suddenly starts counting from a different date time for about two hours, and then it goes back to normal.



      The scariest part is that it wasn't only the python script that was affected. Another C script that tracks electrical pulses is missing data from that period of time.



      I don't know what could've caused this. I know, due to my logging script that all of the important programs were running absolutely fine during this time period. I believe this is most likely a problem with the system rather than my programs.







      debian raspberry-pi raspbian






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 13 at 6:14









      ZeiZei

      184




      184




















          1 Answer
          1






          active

          oldest

          votes


















          4














          There is no real time clock (RTC) on the raspberry pi.




          The Raspberry Pi is designed to be an ultra-low cost computer, so a lot of things we are used to on a computer have been left out. For example, your laptop and computer have a little coin-battery-powered 'Real Time Clock'  (RTC) module, which keeps time even when the power is off, or the battery removed. To keep costs low and the size small, an RTC is not included with the Raspberry Pi. Instead, the Pi is intended to be connected to the Internet via Ethernet or WiFi, updating the time automatically from the global ntp (nework time protocol) servers




          You can buy one for the raspberry pi for about $6 USD. Otherwise NTP is your only option.






          share|improve this answer

























          • I see, that's very enlightening. So that means the RPI doesn't carry over the time each restart. Does that mean it can't update the time if it loses it's internet connection? If that's the case, it could be that the internet was down. (Ah yes I just saw your edit, this sounds like it could be the problem.)

            – Zei
            Feb 13 at 6:40










          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',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          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%2f500322%2fwhy-did-system-forget-date-for-a-few-hours-after-reboot%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          4














          There is no real time clock (RTC) on the raspberry pi.




          The Raspberry Pi is designed to be an ultra-low cost computer, so a lot of things we are used to on a computer have been left out. For example, your laptop and computer have a little coin-battery-powered 'Real Time Clock'  (RTC) module, which keeps time even when the power is off, or the battery removed. To keep costs low and the size small, an RTC is not included with the Raspberry Pi. Instead, the Pi is intended to be connected to the Internet via Ethernet or WiFi, updating the time automatically from the global ntp (nework time protocol) servers




          You can buy one for the raspberry pi for about $6 USD. Otherwise NTP is your only option.






          share|improve this answer

























          • I see, that's very enlightening. So that means the RPI doesn't carry over the time each restart. Does that mean it can't update the time if it loses it's internet connection? If that's the case, it could be that the internet was down. (Ah yes I just saw your edit, this sounds like it could be the problem.)

            – Zei
            Feb 13 at 6:40















          4














          There is no real time clock (RTC) on the raspberry pi.




          The Raspberry Pi is designed to be an ultra-low cost computer, so a lot of things we are used to on a computer have been left out. For example, your laptop and computer have a little coin-battery-powered 'Real Time Clock'  (RTC) module, which keeps time even when the power is off, or the battery removed. To keep costs low and the size small, an RTC is not included with the Raspberry Pi. Instead, the Pi is intended to be connected to the Internet via Ethernet or WiFi, updating the time automatically from the global ntp (nework time protocol) servers




          You can buy one for the raspberry pi for about $6 USD. Otherwise NTP is your only option.






          share|improve this answer

























          • I see, that's very enlightening. So that means the RPI doesn't carry over the time each restart. Does that mean it can't update the time if it loses it's internet connection? If that's the case, it could be that the internet was down. (Ah yes I just saw your edit, this sounds like it could be the problem.)

            – Zei
            Feb 13 at 6:40













          4












          4








          4







          There is no real time clock (RTC) on the raspberry pi.




          The Raspberry Pi is designed to be an ultra-low cost computer, so a lot of things we are used to on a computer have been left out. For example, your laptop and computer have a little coin-battery-powered 'Real Time Clock'  (RTC) module, which keeps time even when the power is off, or the battery removed. To keep costs low and the size small, an RTC is not included with the Raspberry Pi. Instead, the Pi is intended to be connected to the Internet via Ethernet or WiFi, updating the time automatically from the global ntp (nework time protocol) servers




          You can buy one for the raspberry pi for about $6 USD. Otherwise NTP is your only option.






          share|improve this answer















          There is no real time clock (RTC) on the raspberry pi.




          The Raspberry Pi is designed to be an ultra-low cost computer, so a lot of things we are used to on a computer have been left out. For example, your laptop and computer have a little coin-battery-powered 'Real Time Clock'  (RTC) module, which keeps time even when the power is off, or the battery removed. To keep costs low and the size small, an RTC is not included with the Raspberry Pi. Instead, the Pi is intended to be connected to the Internet via Ethernet or WiFi, updating the time automatically from the global ntp (nework time protocol) servers




          You can buy one for the raspberry pi for about $6 USD. Otherwise NTP is your only option.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Feb 13 at 6:44

























          answered Feb 13 at 6:32









          DarkHeartDarkHeart

          3,52632340




          3,52632340












          • I see, that's very enlightening. So that means the RPI doesn't carry over the time each restart. Does that mean it can't update the time if it loses it's internet connection? If that's the case, it could be that the internet was down. (Ah yes I just saw your edit, this sounds like it could be the problem.)

            – Zei
            Feb 13 at 6:40

















          • I see, that's very enlightening. So that means the RPI doesn't carry over the time each restart. Does that mean it can't update the time if it loses it's internet connection? If that's the case, it could be that the internet was down. (Ah yes I just saw your edit, this sounds like it could be the problem.)

            – Zei
            Feb 13 at 6:40
















          I see, that's very enlightening. So that means the RPI doesn't carry over the time each restart. Does that mean it can't update the time if it loses it's internet connection? If that's the case, it could be that the internet was down. (Ah yes I just saw your edit, this sounds like it could be the problem.)

          – Zei
          Feb 13 at 6:40





          I see, that's very enlightening. So that means the RPI doesn't carry over the time each restart. Does that mean it can't update the time if it loses it's internet connection? If that's the case, it could be that the internet was down. (Ah yes I just saw your edit, this sounds like it could be the problem.)

          – Zei
          Feb 13 at 6:40

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f500322%2fwhy-did-system-forget-date-for-a-few-hours-after-reboot%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown






          Popular posts from this blog

          Peggy Mitchell

          Palaiologos

          The Forum (Inglewood, California)