Hi :) after a reboot there always is an offset of -3600 sec, when running ntpdate. # timedatectl status | grep local RTC in local TZ: yes Warning: The RTC is configured to maintain time in the local time zone. This RTC in UTC, by calling 'timedatectl set-local-rtc 0'. # timedatectl set-local-rtc 1 Failed to issue method call: Input/output error Sometimes I don't get an output when running "timedatectl set-local-rtc 1". # cat /etc/adjtime LOCAL # ls -l /etc/localtime lrwxrwxrwx 1 root root 33 Feb 17 22:35 /etc/localtime -> /usr/share/zoneinfo/Europe/Berlin For my old Arch Linux install there wasn't this issue. I suspect I make a mistake, I'm missing something now. I already asked at the German forums, but until now without success: https://bbs.archlinux.de/viewtopic.php?id=23477 FWIW I don't have a Windows installed, this machine is a *NIX multi-boot only. I'm aware about the drawbacks and advantages of both, the usage of UTC and local time and in 10 years I never experienced a drawback using local time. At the moment it's simply more comfortable for me, if I've got local time available for the BIOS. The reason for this should be unimportant for this thread. Regards, Ralf
On Mon, Feb 18, 2013 at 5:50 PM, Ralf Mardorf <ralf.mardorf@alice-dsl.net> wrote:
after a reboot there always is an offset of -3600 sec, when running ntpdate.
# timedatectl status | grep local RTC in local TZ: yes Warning: The RTC is configured to maintain time in the local time zone. This RTC in UTC, by calling 'timedatectl set-local-rtc 0'.
# timedatectl set-local-rtc 1 Failed to issue method call: Input/output error
That message is disconcerting (at least the error message should have been clearer). Could you have a look in "journalctl" (as root) to see if you can get more information about what went wrong?
Sometimes I don't get an output when running "timedatectl set-local-rtc 1".
That means it succeeded.
# cat /etc/adjtime LOCAL
# ls -l /etc/localtime lrwxrwxrwx 1 root root 33 Feb 17 22:35 /etc/localtime -> /usr/share/zoneinfo/Europe/Berlin
For my old Arch Linux install there wasn't this issue. I suspect I make a mistake, I'm missing something now.
I already asked at the German forums, but until now without success: https://bbs.archlinux.de/viewtopic.php?id=23477
FWIW I don't have a Windows installed, this machine is a *NIX multi-boot only. I'm aware about the drawbacks and advantages of both, the usage of UTC and local time and in 10 years I never experienced a drawback using local time. At the moment it's simply more comfortable for me, if I've got local time available for the BIOS. The reason for this should be unimportant for this thread.
If I remember correctly, one of the side effects of having your RTC in localtime is that nothing will write to the RTC automatically. If the RTC is in UTC and an ntp client is running (and your RTC is not too much off), the kernel will write the system time to RTC every 11 minutes. However, that is not the case when your RTC is in localtime. I suggest writing the time manually using 'hwclock' once you know you have the correct system time (due to ntp). -t PS I know you don't want to hear about the problems with localtime, but to anyone else stumbling upon this: not having your RTC in UTC is broken and will cause problems.
On Tue, 19 Feb 2013 01:40:10 +0100, Tom Gundersen <teg@jklm.no> wrote:
# timedatectl set-local-rtc 1 Failed to issue method call: Input/output error
That message is disconcerting (at least the error message should have been clearer). Could you have a look in "journalctl" (as root) to see if you can get more information about what went wrong?
Sometimes I don't get an output when running "timedatectl set-local-rtc 1".
Resp. one time.
That means it succeeded.
Hi Tom, I don't know how to use journalctl, to get some useful information. root@freebsd:/mnt/archlinux/home/rocketmouse # cat journalctl.txt # journalctl | grep RTC Feb 17 22:37:38 localhost kernel: RTC time: 21:37:32, date: 02/17/13 Feb 17 22:37:38 localhost kernel: rtc_cmos 00:04: RTC can wake from S4 Feb 18 00:01:52 localhost kernel: RTC time: 23:01:46, date: 02/17/13 Feb 18 00:01:52 localhost kernel: rtc_cmos 00:04: RTC can wake from S4 Feb 18 11:48:07 localhost kernel: RTC time: 10:48:01, date: 02/18/13 Feb 18 11:48:07 localhost kernel: rtc_cmos 00:04: RTC can wake from S4 Feb 18 12:44:33 localhost kernel: RTC time: 11:44:28, date: 02/18/13 Feb 18 12:44:33 localhost kernel: rtc_cmos 00:04: RTC can wake from S4 Feb 18 13:06:26 localhost kernel: RTC time: 12:06:20, date: 02/18/13 Feb 18 13:06:26 localhost kernel: rtc_cmos 00:04: RTC can wake from S4 Feb 18 13:58:44 localhost kernel: RTC time: 12:58:38, date: 02/18/13 Feb 18 13:58:44 localhost kernel: rtc_cmos 00:04: RTC can wake from S4 Feb 18 13:04:12 localhost systemd-timedated[291]: Failed to set RTC to local/UTC: Input/output error Feb 18 14:38:10 localhost kernel: RTC time: 13:38:04, date: 02/18/13 Feb 18 14:38:10 localhost kernel: rtc_cmos 00:04: RTC can wake from S4 Feb 18 14:44:22 localhost kernel: RTC time: 13:44:16, date: 02/18/13 Feb 18 14:44:22 localhost kernel: rtc_cmos 00:04: RTC can wake from S4 Feb 18 19:17:11 localhost kernel: RTC time: 18:17:05, date: 02/18/13 Feb 18 19:17:11 localhost kernel: rtc_cmos 00:04: RTC can wake from S4 Feb 19 03:10:34 localhost kernel: RTC time: 2:10:27, date: 02/19/13 Feb 19 03:10:34 localhost kernel: rtc_cmos 00:04: RTC can wake from S4 # journalctl | grep UTC Feb 17 22:37:38 localhost kernel: rtc_cmos 00:04: setting system clock to 2013-02-17 21:37:33 UTC (1361137053) Feb 18 00:01:52 localhost kernel: rtc_cmos 00:04: setting system clock to 2013-02-17 23:01:47 UTC (1361142107) Feb 18 11:48:07 localhost kernel: rtc_cmos 00:04: setting system clock to 2013-02-18 10:48:02 UTC (1361184482) Feb 18 12:44:33 localhost kernel: rtc_cmos 00:04: setting system clock to 2013-02-18 11:44:28 UTC (1361187868) Feb 18 13:06:26 localhost kernel: rtc_cmos 00:04: setting system clock to 2013-02-18 12:06:21 UTC (1361189181) Feb 18 13:58:44 localhost kernel: rtc_cmos 00:04: setting system clock to 2013-02-18 12:58:39 UTC (1361192319) Feb 18 13:04:12 localhost systemd-timedated[291]: Failed to set RTC to local/UTC: Input/output error Feb 18 14:38:10 localhost kernel: rtc_cmos 00:04: setting system clock to 2013-02-18 13:38:05 UTC (1361194685) Feb 18 14:44:22 localhost kernel: rtc_cmos 00:04: setting system clock to 2013-02-18 13:44:17 UTC (1361195057) Feb 18 19:17:11 localhost kernel: rtc_cmos 00:04: setting system clock to 2013-02-18 18:17:06 UTC (1361211426) Feb 19 03:10:34 localhost kernel: rtc_cmos 00:04: setting system clock to 2013-02-19 02:10:28 UTC (1361239828) # journalctl -- Logs begin at Sun 2013-02-17 22:37:38 CET, end at Tue 2013-02-19 02:25:27 CET. -- Feb 17 22:37:38 localhost systemd-journal[128]: Allowing runtime journal files to grow to 185.2M. [snip]
If I remember correctly, one of the side effects of having your RTC in localtime is that nothing will write to the RTC automatically.
Correct for my new Arch Linux install.
I know you don't want to hear about the problems with localtime, but to anyone else stumbling upon this: not having your RTC in UTC is broken and will cause problems.
It doesn't cause an issue in 10 years, but for sure using UTC usually is the better choice, if you don't want to have the local time for the BIOS, e.g. for timestamps when storing BIOS settings, that by the way are limited anyway. For personal historical reasons currently all my *NIX expect local time. Regards, Ralf
On Tue, Feb 19, 2013 at 3:00 AM, Ralf Mardorf <ralf.mardorf@alice-dsl.net> wrote:
On Tue, 19 Feb 2013 01:40:10 +0100, Tom Gundersen <teg@jklm.no> wrote:
# timedatectl set-local-rtc 1 Failed to issue method call: Input/output error
That message is disconcerting (at least the error message should have been clearer). Could you have a look in "journalctl" (as root) to see if you can get more information about what went wrong?
Sometimes I don't get an output when running "timedatectl set-local-rtc 1".
Resp. one time.
That means it succeeded.
Hi Tom,
I don't know how to use journalctl, to get some useful information.
[snip]
If I remember correctly, one of the side effects of having your RTC in localtime is that nothing will write to the RTC automatically.
Correct for my new Arch Linux install.
I know you don't want to hear about the problems with localtime, but to anyone else stumbling upon this: not having your RTC in UTC is broken and will cause problems.
It doesn't cause an issue in 10 years, but for sure using UTC usually is the better choice, if you don't want to have the local time for the BIOS, e.g. for timestamps when storing BIOS settings, that by the way are limited anyway. For personal historical reasons currently all my *NIX expect local time.
Regards, Ralf
If you really, REALLY want this: 1. make the last line of /etc/adjtime say “LOCAL”. 2. pacman -S ntp 3. Run the following script, then run it whenever you think your clock is incorrect (as root). #!/bin/bash ntpdate de.pool.ntp.org hwclock --set --date "$(date)" -- Kwpolska <http://kwpolska.tk> | GPG KEY: 5EAAEA16 stop html mail | always bottom-post http://asciiribbon.org | http://caliburn.nl/topposting.html
On Tue, 19 Feb 2013 17:02:54 +0100 Kwpolska <kwpolska@gmail.com> wrote:
On Tue, Feb 19, 2013 at 3:00 AM, Ralf Mardorf <ralf.mardorf@alice-dsl.net> wrote:
On Tue, 19 Feb 2013 01:40:10 +0100, Tom Gundersen <teg@jklm.no> wrote:
# timedatectl set-local-rtc 1 Failed to issue method call: Input/output error
That message is disconcerting (at least the error message should have been clearer). Could you have a look in "journalctl" (as root) to see if you can get more information about what went wrong?
Sometimes I don't get an output when running "timedatectl set-local-rtc 1".
Resp. one time.
That means it succeeded.
Hi Tom,
I don't know how to use journalctl, to get some useful information.
[snip]
If I remember correctly, one of the side effects of having your RTC in localtime is that nothing will write to the RTC automatically.
Correct for my new Arch Linux install.
I know you don't want to hear about the problems with localtime, but to anyone else stumbling upon this: not having your RTC in UTC is broken and will cause problems.
It doesn't cause an issue in 10 years, but for sure using UTC usually is the better choice, if you don't want to have the local time for the BIOS, e.g. for timestamps when storing BIOS settings, that by the way are limited anyway. For personal historical reasons currently all my *NIX expect local time.
Regards, Ralf
If you really, REALLY want this:
1. make the last line of /etc/adjtime say “LOCAL”. 2. pacman -S ntp 3. Run the following script, then run it whenever you think your clock is incorrect (as root).
#!/bin/bash ntpdate de.pool.ntp.org hwclock --set --date "$(date)"
-- Kwpolska <http://kwpolska.tk> | GPG KEY: 5EAAEA16 stop html mail | always bottom-post http://asciiribbon.org | http://caliburn.nl/topposting.html
Notice, however, that ntpdate is going for deprecation in favor of ntpd -q and ideally both should be replaced by the ntp daemon. See man 8 ntpdate for drawbacks of running this program. -- Leonid Isaev GnuPG key: 0x164B5A6D Fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
On Mon, 18 Feb 2013 17:50:06 +0100 "Ralf Mardorf" <ralf.mardorf@alice-dsl.net> wrote:
Hi :)
after a reboot there always is an offset of -3600 sec, when running ntpdate.
# timedatectl status | grep local RTC in local TZ: yes Warning: The RTC is configured to maintain time in the local time zone. This RTC in UTC, by calling 'timedatectl set-local-rtc 0'.
# timedatectl set-local-rtc 1 Failed to issue method call: Input/output error
Sometimes I don't get an output when running "timedatectl set-local-rtc 1".
# cat /etc/adjtime LOCAL
That's why timedatectl command fails, LOCAL must be on the line 3 : $ cat /etc/adjtime 0.0 0 0 0 LOCAL
# ls -l /etc/localtime lrwxrwxrwx 1 root root 33 Feb 17 22:35 /etc/localtime -> /usr/share/zoneinfo/Europe/Berlin
For my old Arch Linux install there wasn't this issue. I suspect I make a mistake, I'm missing something now.
I already asked at the German forums, but until now without success: https://bbs.archlinux.de/viewtopic.php?id=23477
FWIW I don't have a Windows installed, this machine is a *NIX multi-boot only. I'm aware about the drawbacks and advantages of both, the usage of UTC and local time and in 10 years I never experienced a drawback using local time. At the moment it's simply more comfortable for me, if I've got local time available for the BIOS. The reason for this should be unimportant for this thread.
Regards, Ralf
On Tue, 19 Feb 2013 15:46:08 +0100, Tuxce <tuxce.net@gmail.com> wrote:
On Mon, 18 Feb 2013 17:50:06 +0100 "Ralf Mardorf" <ralf.mardorf@alice-dsl.net> wrote:
# cat /etc/adjtime LOCAL
That's why timedatectl command fails, LOCAL must be on the line 3 :
$ cat /etc/adjtime 0.0 0 0 0 LOCAL
Thank you :) [root@archlinux etc]# cat adjtime LOCAL [root@archlinux etc]# nano adjtime [root@archlinux etc]# cat adjtime 0.0 0 0 0 LOCAL [root@archlinux etc]# reboot [root@archlinux rocketmouse]# ntpdate ntp.favey.ch 20 Feb 04:13:19 ntpdate[531]: adjust time server 195.34.89.227 offset -0.064442 sec Regards, Ralf
participants (5)
-
Kwpolska
-
Leonid Isaev
-
Ralf Mardorf
-
Tom Gundersen
-
Tuxce