Cockpit: sync system time
-
What are you doing or how are you "syncing system time"?
-
The set time should be set to
Automatically using NTPThere’s a greyed out option to automatically use a specific NTP server.
-
@black3dynamite said in Cockpit: sync system time:
The set time should be set to
Automatically using NTPThere’s a greyed out option to automatically use a specific NTP server.
I'm on the Automatic setting but the Red checkmark still says "Time not synced".
-
@FATeknollogee said in Cockpit: sync system time:
@black3dynamite said in Cockpit: sync system time:
The set time should be set to
Automatically using NTPThere’s a greyed out option to automatically use a specific NTP server.
I'm on the Automatic setting but the Red checkmark still says "Time not synced".
Is chronyd.service running?
https://1.2.3.4:9090/system/services#/chronyd.service -
@black3dynamite chronyd is active
-
timedatectl list-timezones
timedatectl set-timezone Asia/Tokyo -
@Emad-R Those settings are already set by default.
-
Are you syncing NTP from an external server? Possibly firewall not letting 123 out? Also, could be a similar issue for internal.
-
Am I the only one with the red exclamation?
-
@FATeknollogee said in Cockpit: sync system time:
Am I the only one with the red exclamation?
I've not seen it.
-
Went back, took another look, red mark is gone!!
Go figure! -
@FATeknollogee said in Cockpit: sync system time:
Went back, took another look, red mark is gone!!
Go figure!It just needed...... time.
-
NTP can take a considerable amount of time (hours) to whip the system clock into submission if it had drifted far off UTC.
You can start the ntpd with an option to force it to change time directly. It used to be that you'd run ntpdate first and then start ntpd but ntpdate has been depreciated.
ntpq -pwill show a little more details about the status of ntp sync. First thing to run when troubleshooting ntp.
