chronyd version 1.24 does not support kernel 3.0 or 4.0

[Joey Huckabee]

sudo apt-get update
sudo apt-get install chrony

$ chronyd -v
chronyd (chrony) version 1.24

When I issue the following commands I get the following responses:

$ sudo invoke-rc.d chrony restart
Restarting time daemon: Starting /usr/sbin/chronyd...
chronyd is running and offline.
$

but if I look at 'ps -auxw' I do not see anything releated to chrony and I see the following in the syslog 'tail -f /var/log/syslog':

Jul 20 23:00:10 chronyd[3335]: chronyd version 1.24 starting
Jul 20 23:00:10 chronyd[3335]: Initial txc.tick=10000 txc.freq=0 (0.00000000) txc.offset=0 => hz=100 shift_hz=7
Jul 20 23:00:10 chronyd[3335]: set_config_hz=0 hz=100 shift_hz=7 basic_freq_scale=1.28000000 nominal_tick=10000 slew_delta_tick=833 max_tick_bias=1000
Jul 20 23:00:10 chronyd[3335]: Linux kernel major=4 minor=0 patch=8
Jul 20 23:00:10 chronyd[3335]: Fatal error : Kernel's major version not supported yet, sorry

If you google 'chrony Kernel's major version not supported yet, sorry' then you will see some kernel 3.0 bug reported from 2011... I suspect this is the same case statement 'feature' that we saw back in 2011. (Bug Report # 628919 and 638252)

The fix in the file sys_linux.c for kernel 3.0 was not until version 1.26 according to the files I found in here -> https://github.com/mlichvar/chrony/releases?after=1.30

I was originally going to submit a bug report to Chrony but I can see that it was already fixed and the problem now seems to be the Raspian distro needs to update to a newer version. (Version 2.1).

Thanks,

Joey

[peter green (plugwash)]

"The fix in the file sys_linux.c for kernel 3.0 was not until version 1.26"
That is true upstream but Debian fixed the issue in their packages as can be seen in the debian bug reports you mentioned.

"the Raspian distro needs to update to a newer version. (Version 2.1)."
We would only consider such a thing as a last resort. The point of a stable release is to provide a baseline that changes as little as possible.

In any case it looks like in version 1.30 used in jessie and stretch that the code in question has been completely rewritten and no longer checks for a maximum major version. So this only seems to be an issue for wheezy.

I've uploaded version 1.24-3.1+deb7u3+rpi1 which I believe should fix this issue. Can you test it?

[Diederik (didi-debian)]

Any news on whether the new version by plugwash fixes the issue?

[Joey Huckabee (joey-huckabee)]

Yes I have confirmed that Chrony version 1.24 installs and functions on the raspberry pi.

I started with Raspberry Pi image 2015-05-05-raspbian-wheezy.img
Issued the following commands

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install chrony

RESULT: chronyd is running and offline.

Removed offline directive from /etc/chrony/chrony.conf
sudo invoke-rc.d chrony restart

RESULT: Restarting time daemon: Starting /usr/sbin/chronyd...
chronyd is running and online.