Hello guys,
my rack controller has my NTP servers (checked the Use external NTP servers only too) set correctly, but still it has not the right time and it is hours slower than my region’s time.
May i kindly ask you guys, if you have a tipp for me?
Thanks a lot.
Best regards.
what if you configure the host of the region to use the same ntp servers?
The direct approach is to check your /etc/ntp.conf and dmesg to see what happened there.
Normally even if the time is not synced with NTP server, the time diff should not be several hours when the machine is down and the BIOS battery is still alive.
thank you guys, i have still the same problem, although i tried both.
Here are some outputs:
root@maas-test:~# timedatectl
Local time: Wed 2024-09-04 13:58:30 CEST
Universal time: Wed 2024-09-04 11:58:30 UTC
RTC time: Wed 2024-09-04 11:58:30
Time zone: Europe/Zurich (CEST, +0200)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
root@maas-test:~# dmesg | grep -i time
[ 0.082231] ACPI: PM-Timer IO Port: 0x1008
[ 0.082500] TSC deadline timer available
[ 0.231864] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.337322] PM: RTC time: 15:32:23, date: 2024-08-15
[ 1.869638] workingset: timestamp_bits=36 max_order=22 bucket_order=0
[ 3.666908] Loaded X.509 cert 'Build time autogenerated kernel key: 2f322af05166b99aa790ffff5e1f713c37ac6407'
[ 3.693682] Loaded X.509 cert 'Build time autogenerated kernel key: 2f322af05166b99aa790ffff5e1f713c37ac6407'
[ 7.650325] systemd[1]: Reached target System Time Set.
[ 8.117723] systemd-journald[547]: Received client request to flush runtime journal.
root@maas-test:~# dmesg | grep -i rtc
[ 0.337322] PM: RTC time: 15:32:23, date: 2024-08-15
[ 1.985543] rtc_cmos 00:01: registered as rtc0
[ 1.985697] rtc_cmos 00:01: setting system clock to 2024-08-15T15:32:24 UTC (1723735944)
[ 1.985908] rtc_cmos 00:01: alarms up to one month, y3k, 114 bytes nvram
root@maas-test:~# hwclock --verbose
hwclock from util-linux 2.37.2
System Time: 1725451149.086234
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1725450683 seconds after 1969
Last calibration done at 1725450683 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: 2024/09/04 11:59:10
Hw clock time : 2024/09/04 11:59:10 = 1725451150 seconds since 1969
Time since last adjustment is 467 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2024-09-04 13:59:08.994624+02:00
root@maas-test:~# maas status
bind9 RUNNING pid 2351880, uptime 0:20:40
dhcpd STOPPED Not started
dhcpd6 STOPPED Not started
http RUNNING pid 2352259, uptime 0:20:23
ntp RUNNING pid 2351989, uptime 0:20:36
proxy STOPPED Not started
rackd RUNNING pid 2351883, uptime 0:20:40
regiond RUNNING pid 2351884, uptime 0:20:40
syslog RUNNING pid 2351990, uptime 0:20:36
root@maas-test:~#
do you see anything strange in this output?
What i am not understanding is, the MAAS time is alike the hardware time.