Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with system time #158

Open
morrmaker opened this issue Jan 6, 2024 · 11 comments
Open

Issue with system time #158

morrmaker opened this issue Jan 6, 2024 · 11 comments

Comments

@morrmaker
Copy link

I have reimaged my board several times and it always sets the back to July 16, 2023. I'm able to manually set it to current date time with timedatectl however, after having printer turned of for awhile I now notice it is 4 hours behind. Is there a way to set NTP service to keep this in sync. Timedatectl shows "NTP servie: n/a"

@Chinstrap777
Copy link

change your timezone in "system.cfg" to "America/Seattle" or whatever your designator is. I used google to find mine.

@morrmaker
Copy link
Author

Yes. Forgot to mention I already set the timezone.

@freegithubuser
Copy link

freegithubuser commented Jan 30, 2024

I also have the same problem.
Have set the timezone in the system.cfg as well as at the command line and I still get the same error.
All OS updates are installed.

#!/bin/bash

biqu@anet:~$ timedatectl status
               Local time: Tue 2024-01-30 15:44:44 AEDT
           Universal time: Tue 2024-01-30 04:44:44 UTC
                 RTC time: Fri 1970-01-02 00:21:24
                Time zone: Australia/Melbourne (AEDT, +1100)
System clock synchronized: no
              NTP service: n/a
          RTC in local TZ: no

biqu@anet:~$ ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 used-to-be-ntp. .INIT.          16 u    - 1024    0    0.000   +0.000   0.000

@Sayon13
Copy link

Sayon13 commented Mar 13, 2024

Same problem here, I cannot update via Mainsail because the system date is so old. Even in Kiauh I get the "E: Release file for http://deb.debian.org/debian-security/dists/bullseye-security/InRelease is not valid yet (invalid for another 243d 8h 37min 8s). Updates for this repository will not be applied."

@Sayon13
Copy link

Sayon13 commented Mar 13, 2024

image_2024-03-13_143446657

@Sayon13
Copy link

Sayon13 commented Mar 13, 2024

image
moonraker.log

@freegithubuser
Copy link

freegithubuser commented Mar 13, 2024

The problem appears that NTP which is responsible for network time isn't running/working.
I have tried changing NTP servers and configuration but still had no luck. I'm sure someone has figured it out, but until then I have found that I need to SSH into it and set the date and time manually after each boot for it to stay current. Some short power off states (a few minutes) or while whilst rebooting seem to freeze for that short period,

sudo date "YYYY-MM-DD HH:MM:SS"
or alternatively if your local is set to use a different date standard, follow that standard.

@Sayon13
Copy link

Sayon13 commented Mar 13, 2024

The think that kills me inside is that it was working fine before I update it.. I gave up on it and just change it for a rpi 3b+

@Chinstrap777
Copy link

I also have the same problem. Have set the timezone in the system.cfg as well as at the command line and I still get the same error. All OS updates are installed.

#!/bin/bash

biqu@anet:~$ timedatectl status
               Local time: Tue 2024-01-30 15:44:44 AEDT
           Universal time: Tue 2024-01-30 04:44:44 UTC
                 RTC time: Fri 1970-01-02 00:21:24
                Time zone: Australia/Melbourne (AEDT, +1100)
System clock synchronized: no
              NTP service: n/a
          RTC in local TZ: no

biqu@anet:~$ ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 used-to-be-ntp. .INIT.          16 u    - 1024    0    0.000   +0.000   0.000

Looks like you have to:

sudo debian-config

To actually change the time zone and time

@PH1980
Copy link

PH1980 commented Mar 15, 2024

Hello there!

I solved the problem. Had the same issue.

got to

https://wiki.debian.org/DateTime

and look for installation of ntp. Do it. Nano into the mentioned file and add local servers from the local sources under "Managing NTP Pools" right under the ones that are mentioned in the file. Save the file and reboot.

Just did it and it works now for me. Did Update and Upgrade and now downloaded KIAUH and install Klipper.

@freegithubuser
Copy link

Hello there!

I solved the problem. Had the same issue.

got to

https://wiki.debian.org/DateTime

and look for installation of ntp. Do it. Nano into the mentioned file and add local servers from the local sources under "Managing NTP Pools" right under the ones that are mentioned in the file. Save the file and reboot.

Just did it and it works now for me. Did Update and Upgrade and now downloaded KIAUH and install Klipper.

Thanks PH1980, worked a treat!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants