18.04 not showing correct time (not a dual boot issue)
up vote
2
down vote
favorite
I realize that this is a common issue, but I can't find the fix to my problem.
Live in "America/Chicago (CST, -0600)" but ubuntu is showing UTC time.
It is 4pm local time here:
$ timedatectl
Local time: Thu 2018-11-22 16:11:47 CST
Universal time: Thu 2018-11-22 22:11:47 UTC
RTC time: Thu 2018-11-22 22:11:47
Time zone: America/Chicago (CST, -0600)
System clock synchronized: yes
systemd-timesyncd.service active: yes
RTC in local TZ: no
So TimeDateCtl knows local time, but the Date command is showing me UTC
$ date
Thu Nov 22 22:15:54 Chicago 2018
I have made sure that the BIOS time is UTC, and my service is started up, just wrong.
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-11-22 22:07:07 Chicago; 9min ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 1360 (systemd-timesyn)
Status: "Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com)."
Tasks: 2 (limit: 4915)
CGroup: /system.slice/systemd-timesyncd.service
└─1360 /lib/systemd/systemd-timesyncd
What else do I try? I set it to local time and back, I've restarted every service I can find.
Edit, I don't see a problem here either:
sudo hwclock --debug
hwclock from util-linux 2.31.1
System Time: 1542925579.769423
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2018/11/22 22:26:20
Hw clock time : 2018/11/22 22:26:20 = 1542925580 seconds since 1969
Time since last adjustment is 1542925580 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2018-11-22 22:26:19.764979+0000
18.04 time
New contributor
add a comment |
up vote
2
down vote
favorite
I realize that this is a common issue, but I can't find the fix to my problem.
Live in "America/Chicago (CST, -0600)" but ubuntu is showing UTC time.
It is 4pm local time here:
$ timedatectl
Local time: Thu 2018-11-22 16:11:47 CST
Universal time: Thu 2018-11-22 22:11:47 UTC
RTC time: Thu 2018-11-22 22:11:47
Time zone: America/Chicago (CST, -0600)
System clock synchronized: yes
systemd-timesyncd.service active: yes
RTC in local TZ: no
So TimeDateCtl knows local time, but the Date command is showing me UTC
$ date
Thu Nov 22 22:15:54 Chicago 2018
I have made sure that the BIOS time is UTC, and my service is started up, just wrong.
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-11-22 22:07:07 Chicago; 9min ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 1360 (systemd-timesyn)
Status: "Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com)."
Tasks: 2 (limit: 4915)
CGroup: /system.slice/systemd-timesyncd.service
└─1360 /lib/systemd/systemd-timesyncd
What else do I try? I set it to local time and back, I've restarted every service I can find.
Edit, I don't see a problem here either:
sudo hwclock --debug
hwclock from util-linux 2.31.1
System Time: 1542925579.769423
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2018/11/22 22:26:20
Hw clock time : 2018/11/22 22:26:20 = 1542925580 seconds since 1969
Time since last adjustment is 1542925580 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2018-11-22 22:26:19.764979+0000
18.04 time
New contributor
Do you have theTZ
environment variable set? Check the output ofecho $TZ
. That variable would override the timezonedate
shows, but not whattimedatectl
reports.
– Byte Commander
6 hours ago
Deleted the last comment because it was irrelevant. Fixed, thank you. TZ variable.
– Chris948
5 hours ago
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I realize that this is a common issue, but I can't find the fix to my problem.
Live in "America/Chicago (CST, -0600)" but ubuntu is showing UTC time.
It is 4pm local time here:
$ timedatectl
Local time: Thu 2018-11-22 16:11:47 CST
Universal time: Thu 2018-11-22 22:11:47 UTC
RTC time: Thu 2018-11-22 22:11:47
Time zone: America/Chicago (CST, -0600)
System clock synchronized: yes
systemd-timesyncd.service active: yes
RTC in local TZ: no
So TimeDateCtl knows local time, but the Date command is showing me UTC
$ date
Thu Nov 22 22:15:54 Chicago 2018
I have made sure that the BIOS time is UTC, and my service is started up, just wrong.
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-11-22 22:07:07 Chicago; 9min ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 1360 (systemd-timesyn)
Status: "Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com)."
Tasks: 2 (limit: 4915)
CGroup: /system.slice/systemd-timesyncd.service
└─1360 /lib/systemd/systemd-timesyncd
What else do I try? I set it to local time and back, I've restarted every service I can find.
Edit, I don't see a problem here either:
sudo hwclock --debug
hwclock from util-linux 2.31.1
System Time: 1542925579.769423
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2018/11/22 22:26:20
Hw clock time : 2018/11/22 22:26:20 = 1542925580 seconds since 1969
Time since last adjustment is 1542925580 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2018-11-22 22:26:19.764979+0000
18.04 time
New contributor
I realize that this is a common issue, but I can't find the fix to my problem.
Live in "America/Chicago (CST, -0600)" but ubuntu is showing UTC time.
It is 4pm local time here:
$ timedatectl
Local time: Thu 2018-11-22 16:11:47 CST
Universal time: Thu 2018-11-22 22:11:47 UTC
RTC time: Thu 2018-11-22 22:11:47
Time zone: America/Chicago (CST, -0600)
System clock synchronized: yes
systemd-timesyncd.service active: yes
RTC in local TZ: no
So TimeDateCtl knows local time, but the Date command is showing me UTC
$ date
Thu Nov 22 22:15:54 Chicago 2018
I have made sure that the BIOS time is UTC, and my service is started up, just wrong.
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-11-22 22:07:07 Chicago; 9min ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 1360 (systemd-timesyn)
Status: "Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com)."
Tasks: 2 (limit: 4915)
CGroup: /system.slice/systemd-timesyncd.service
└─1360 /lib/systemd/systemd-timesyncd
What else do I try? I set it to local time and back, I've restarted every service I can find.
Edit, I don't see a problem here either:
sudo hwclock --debug
hwclock from util-linux 2.31.1
System Time: 1542925579.769423
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2018/11/22 22:26:20
Hw clock time : 2018/11/22 22:26:20 = 1542925580 seconds since 1969
Time since last adjustment is 1542925580 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2018-11-22 22:26:19.764979+0000
18.04 time
18.04 time
New contributor
New contributor
edited 6 hours ago
New contributor
asked 6 hours ago
Chris948
133
133
New contributor
New contributor
Do you have theTZ
environment variable set? Check the output ofecho $TZ
. That variable would override the timezonedate
shows, but not whattimedatectl
reports.
– Byte Commander
6 hours ago
Deleted the last comment because it was irrelevant. Fixed, thank you. TZ variable.
– Chris948
5 hours ago
add a comment |
Do you have theTZ
environment variable set? Check the output ofecho $TZ
. That variable would override the timezonedate
shows, but not whattimedatectl
reports.
– Byte Commander
6 hours ago
Deleted the last comment because it was irrelevant. Fixed, thank you. TZ variable.
– Chris948
5 hours ago
Do you have the
TZ
environment variable set? Check the output of echo $TZ
. That variable would override the timezone date
shows, but not what timedatectl
reports.– Byte Commander
6 hours ago
Do you have the
TZ
environment variable set? Check the output of echo $TZ
. That variable would override the timezone date
shows, but not what timedatectl
reports.– Byte Commander
6 hours ago
Deleted the last comment because it was irrelevant. Fixed, thank you. TZ variable.
– Chris948
5 hours ago
Deleted the last comment because it was irrelevant. Fixed, thank you. TZ variable.
– Chris948
5 hours ago
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
Your environment variable TZ
is the cause of the problem.
$ echo $TZ
Chicago/New_York
Chicago/New_York
is an invalid time zone, so date
will default to UTC instead, but for some reason still display the first part of the zone name as time zone, resulting in:
$ timedatectl
Local time: Thu 2018-11-22 16:11:47 CST
Universal time: Thu 2018-11-22 22:11:47 UTC
RTC time: Thu 2018-11-22 22:11:47
Time zone: America/Chicago (CST, -0600)
System clock synchronized: yes
systemd-timesyncd.service active: yes
RTC in local TZ: no
$ date
Thu Nov 22 22:15:54 Chicago 2018
Now to fix the issue, we just need to find out where that wrong value is set and delete the line. Search for something like one of the lines below in your shell/profile initialization scripts, like ~/.profile
, ~/.bashrc
or if it affects all users maybe even /etc/environment
, /etc/profile
, /etc/profile.d/*
or /etc/bash.bashrc
:
TZ='Chicago/New_York'
export TZ='Chicago/New_York'
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
Your environment variable TZ
is the cause of the problem.
$ echo $TZ
Chicago/New_York
Chicago/New_York
is an invalid time zone, so date
will default to UTC instead, but for some reason still display the first part of the zone name as time zone, resulting in:
$ timedatectl
Local time: Thu 2018-11-22 16:11:47 CST
Universal time: Thu 2018-11-22 22:11:47 UTC
RTC time: Thu 2018-11-22 22:11:47
Time zone: America/Chicago (CST, -0600)
System clock synchronized: yes
systemd-timesyncd.service active: yes
RTC in local TZ: no
$ date
Thu Nov 22 22:15:54 Chicago 2018
Now to fix the issue, we just need to find out where that wrong value is set and delete the line. Search for something like one of the lines below in your shell/profile initialization scripts, like ~/.profile
, ~/.bashrc
or if it affects all users maybe even /etc/environment
, /etc/profile
, /etc/profile.d/*
or /etc/bash.bashrc
:
TZ='Chicago/New_York'
export TZ='Chicago/New_York'
add a comment |
up vote
2
down vote
accepted
Your environment variable TZ
is the cause of the problem.
$ echo $TZ
Chicago/New_York
Chicago/New_York
is an invalid time zone, so date
will default to UTC instead, but for some reason still display the first part of the zone name as time zone, resulting in:
$ timedatectl
Local time: Thu 2018-11-22 16:11:47 CST
Universal time: Thu 2018-11-22 22:11:47 UTC
RTC time: Thu 2018-11-22 22:11:47
Time zone: America/Chicago (CST, -0600)
System clock synchronized: yes
systemd-timesyncd.service active: yes
RTC in local TZ: no
$ date
Thu Nov 22 22:15:54 Chicago 2018
Now to fix the issue, we just need to find out where that wrong value is set and delete the line. Search for something like one of the lines below in your shell/profile initialization scripts, like ~/.profile
, ~/.bashrc
or if it affects all users maybe even /etc/environment
, /etc/profile
, /etc/profile.d/*
or /etc/bash.bashrc
:
TZ='Chicago/New_York'
export TZ='Chicago/New_York'
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
Your environment variable TZ
is the cause of the problem.
$ echo $TZ
Chicago/New_York
Chicago/New_York
is an invalid time zone, so date
will default to UTC instead, but for some reason still display the first part of the zone name as time zone, resulting in:
$ timedatectl
Local time: Thu 2018-11-22 16:11:47 CST
Universal time: Thu 2018-11-22 22:11:47 UTC
RTC time: Thu 2018-11-22 22:11:47
Time zone: America/Chicago (CST, -0600)
System clock synchronized: yes
systemd-timesyncd.service active: yes
RTC in local TZ: no
$ date
Thu Nov 22 22:15:54 Chicago 2018
Now to fix the issue, we just need to find out where that wrong value is set and delete the line. Search for something like one of the lines below in your shell/profile initialization scripts, like ~/.profile
, ~/.bashrc
or if it affects all users maybe even /etc/environment
, /etc/profile
, /etc/profile.d/*
or /etc/bash.bashrc
:
TZ='Chicago/New_York'
export TZ='Chicago/New_York'
Your environment variable TZ
is the cause of the problem.
$ echo $TZ
Chicago/New_York
Chicago/New_York
is an invalid time zone, so date
will default to UTC instead, but for some reason still display the first part of the zone name as time zone, resulting in:
$ timedatectl
Local time: Thu 2018-11-22 16:11:47 CST
Universal time: Thu 2018-11-22 22:11:47 UTC
RTC time: Thu 2018-11-22 22:11:47
Time zone: America/Chicago (CST, -0600)
System clock synchronized: yes
systemd-timesyncd.service active: yes
RTC in local TZ: no
$ date
Thu Nov 22 22:15:54 Chicago 2018
Now to fix the issue, we just need to find out where that wrong value is set and delete the line. Search for something like one of the lines below in your shell/profile initialization scripts, like ~/.profile
, ~/.bashrc
or if it affects all users maybe even /etc/environment
, /etc/profile
, /etc/profile.d/*
or /etc/bash.bashrc
:
TZ='Chicago/New_York'
export TZ='Chicago/New_York'
answered 5 hours ago
Byte Commander
62k26167278
62k26167278
add a comment |
add a comment |
Chris948 is a new contributor. Be nice, and check out our Code of Conduct.
Chris948 is a new contributor. Be nice, and check out our Code of Conduct.
Chris948 is a new contributor. Be nice, and check out our Code of Conduct.
Chris948 is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1095230%2f18-04-not-showing-correct-time-not-a-dual-boot-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
Do you have the
TZ
environment variable set? Check the output ofecho $TZ
. That variable would override the timezonedate
shows, but not whattimedatectl
reports.– Byte Commander
6 hours ago
Deleted the last comment because it was irrelevant. Fixed, thank you. TZ variable.
– Chris948
5 hours ago