[Bug 48182] chrony cannot read RTC

Mon Jun 26 06:42:27 UTC 2006

Public bug reported:

Hello guys,

while upgrading to Dapper from Breezy, chrony got f*cked. Chrony even
can't read the RTC anymore:

-----------------[cut]------------------------------------------------------------
root at Niji|10:58:52:/etc# chronyc rtcdata
RTC ref time (UTC) : Thu Jan  1 00:00:00 1970
Number of samples  : 0
Number of runs     : 0
Sample span period :    0
RTC is fast by     :     0.000000 seconds
RTC gains time at  :     0.000 ppm
------------------[cut]----------------------------------------------------------

Furthermore, hwclock is able to set and show the RTC's time without any problems:

-----------------[cut]------------------------------------------------------------
root at Niji|11:03:56:/etc# hwclock --show --debug
hwclock from util-linux-2.12r
Using /dev/rtc interface to clock.
Last drift adjustment done at 1149323481 seconds after 1969
Last calibration done at 1149323481 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: 2006/06/03 09:03:44
Hw clock time : 2006/06/03 09:03:44 = 1149325424 seconds since 1969
Sa 03 Jun 2006 11:03:44 CEST  -0.748553 seconds
-----------------[cut]------------------------------------------------------------

The /etc/localtime and /etc/timezone is correct.

-----------------[cut]------------------------------------------------------------
root at Niji|11:06:24:/etc# ls -l /etc/localtime
lrwxrwxrwx 1 root root 33 2006-06-01 19:21 /etc/localtime -> /usr/share/zoneinfo/Europe/Berlin
root at Niji|11:07:53:/etc# cat /etc/timezone
Europe/Berlin
-----------------[cut]------------------------------------------------------------

This is my /etc/chrony/chrony.conf:

-----------------[cut]------------------------------------------------------------
# This the default chrony.conf file for the Debian chrony package.  It is
# suitable for a system with an intermittent dial-up connection.  John
# Hasler <jhasler at debian.org> 3 Dec. 1998

# See www.pool.ntp.org for an explanation of these servers.  Please
# consider joining the project if possible.  If you can't or don't want to
# use these servers I suggest that you try your ISPs nameservers.  We mark
# the servers 'offline' so that chronyd won't try to connect when the link
# is down.  Scripts in /etc/ppp/ip-up.d and /etc/ppp/ip-down.d use chronyc
# commands to switch it on when the link comes up and off when it goes
# down.  If you have an always-on connection such as cable or DSL omit the
# 'offline' directive and chronyd will default to online.

server ntp.ubuntulinux.org
# server 141.48.3.15
server 131.188.3.220
server 131.188.3.221
server 131.188.3.222
server 131.188.3.223
server 130.149.17.21
server 130.149.17.8
server 192.53.103.103
server 192.53.103.104
server 129.69.1.153

# Look here for the admin password needed for chronyc.  The initial
# password is generated by a random process at install time.  You may
# change it if you wish.

keyfile /etc/chrony/chrony.keys

# Set runtime command key.  Note that if you change the key (not the
# password) to anything other than 1 you will need to edit
# /etc/ppp/ip-up.d/chrony, /etc/ppp/ip-down.d/chrony, and
# /etc/cron.weekly/chrony as these scripts use it to get the password.

commandkey 1

# I moved the driftfile to /var/lib/chrony to comply with the Debian
# filesystem standard.

driftfile /var/lib/chrony/chrony.drift

# Comment this line out to turn off logging.

log tracking measurements statistics
logdir /var/log/chrony

# Stop bad estimates upsetting machine clock.

maxupdateskew 100.0

# Dump measurements when daemon exits.

dumponexit

# Specify directory for dumping measurements.

dumpdir /var/lib/chrony

# Let computer be a server when it is unsynchronised.

local stratum 10

# Allow computers on the unrouted nets 10 and 192.168 to use the server.

allow 10
allow 192.168

# This directive forces `chronyd' to send a message to syslog if it
# makes a system clock adjustment larger than a threshold value in seconds.

logchange 0.5

# This directive defines an email address to which mail should be sent
# if chronyd applies a correction exceeding a particular threshold to the
# system clock.

# mailonchange root at localhost 0.5

# Specify the file where real-time clock data is stored.  To use this you
# must have enhanced real-time clock support compiled into your kernel.
# Comment out the next line if you do not.  Note: I have seen problems with
# the rtc on some motherboards.  Please file a bug if this bites you.

rtcfile /var/lib/chrony/chrony.rtc

# If the last line of this file reads 'rtconutc' chrony will assume that
# the CMOS clock is on UTC (GMT).  If it reads '# rtconutc' or is absent
# chrony will assume local time.  The line (if any) was written by the
# chrony postinst based on what it found in /etc/default/rcS.  You may
# change it if necessary.  The next line is just a marker for the postinst.
# You can delete it if you wish.
rtconutc
# POSTINSTMARKER
-----------------[cut]------------------------------------------------------------

As I said before, I'm using the final release of Ubuntu Dapper. Everything worked like a charm with Breezy, btw.

Regards, Ionic

** Affects: chrony (Ubuntu)
     Importance: Medium
     Assignee: MOTU
         Status: Unconfirmed

-- 
chrony cannot read RTC
https://launchpad.net/bugs/48182