I have a Dell SC1430 running XUbuntu 16.04 acting as a Mythtv backend server. It's been running fine for many years but now after upgrading from 12.04, via 14.04 to 16.04 (using do-release-upgrade) the system time is off by 2 hours and it can't be set to the correct time.
When I, or any mechanism such as ntpd
or timesyncd
, tries to set the time, it immediately changes back. I get this in syslog when trying ntpd
:
Sep 17 12:32:33 eddie ntpd[21484]: proto: precision = 0.131 usec (-23)
Sep 17 12:32:33 eddie ntpd[21484]: restrict 0.0.0.0: KOD does nothing without LIMITED.
Sep 17 12:32:33 eddie ntpd[21484]: restrict ::: KOD does nothing without LIMITED.
Sep 17 12:32:33 eddie ntpd[21484]: Listen and drop on 0 v6wildcard [::]:123
Sep 17 12:32:33 eddie ntpd[21484]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Sep 17 12:32:33 eddie ntpd[21484]: Listen normally on 2 lo 127.0.0.1:123
Sep 17 12:32:33 eddie ntpd[21484]: Listen normally on 3 eth0 192.168.1.11:123
Sep 17 12:32:33 eddie ntpd[21484]: Listen normally on 4 lo [::1]:123
Sep 17 12:32:33 eddie ntpd[21484]: Listen normally on 5 eth0 [fe80::219:b9ff:fe22:9d01%2]:123
Sep 17 12:32:33 eddie ntpd[21484]: Listening on routing socket on fd #22 for interface updates
Sep 17 10:32:52 eddie systemd[28438]: Time has been changed
Sep 17 10:32:52 eddie ntpd[21484]: ntpd: time set -7188.398130 s
Sep 17 10:32:52 eddie systemd[2506]: Time has been changed
Sep 17 10:32:52 eddie systemd[1]: Time has been changed
Sep 17 12:32:41 eddie systemd[28438]: Time has been changed
Sep 17 12:32:41 eddie systemd[2506]: Time has been changed
Sep 17 12:32:41 eddie systemd[1]: Time has been changed
As you can see, the time actually changes for a moment, then something is changing it back.
Timedatectl status gives me:
root@eddie:~# timedatectl status
Local time: Sun 2017-09-17 14:24:12 CEST
Universal time: Sun 2017-09-17 12:24:12 UTC
RTC time: Sun 2017-09-17 12:24:12
Time zone: Europe/Stockholm (CEST, +0200)
Network time on: no
NTP synchronized: no
RTC in local TZ: no
UTC should be 10:24:12 and Local time should be 12:24:12 in this example.
My best guess is that some other program/process is (trying) to keep the time correct but gets confused with timezone or whatnot after the upgrade.
As I suggested above I have tried using NTP instead of the timedatectl
approach, but the behavior is exactly the same.
This is not a dual-boot situation that I've read others having issues with.
Any help would be greatly appreciated!
Sep 17 10:32:52 eddie systemd[28438]: Time has been changed
so check what systemd time service is doing ;) Probably:hwclock --systoh
Set the time to something and then do THAT command yourself. See if that changes your clock to the wrong timetimedatectl set-time "12:00"
and thenhwclock --systohc
but nothing changes permanently. I get the same type of entries in syslog - time changes back immediately. How can I check what systemd time service is doing?timedatectl
to assure that your time zone is set correctly, then use theset-local-rtc
option to set the clock to local/rtc.