| Re: AW: [chrony-users] chronyd: Can' Synchronize WHY ? |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On Tue, Sep 13, 2011 at 12:43:54PM +0000, thomas.schmid@xxxxxxxxx wrote:
> PC6: noselect on all servers:
> chronyc> sourcestats
> 210 Number of sources = 3
> Name/IP Address NP NR Span Frequency Freq Skew Offset Std Dev
> ==============================================================================
> <WAN-IP1> 9 7 137m -5.780 0.007 -544ms 9937ns
> <WAN-IP3> 7 5 778 -5.871 0.135 -544ms 15us
> SU-Server3 18 12 18m 277.409 26.284 -186ms 7301us
Ok, with noselect the WAN-IP1 and WAN-IP3 servers are tracked very
well, the third server is the one in virtual machine, so no surprise
it's a bit off.
Well, this means there is a serious problem in the clock discipline.
Your log says the kernel version is 2.6.27, which was the first one
with support for the readonly adjtime and nanosecond PLL mode. It is
the vanilla 2.6.27 kernel or are there any patches included or perhaps
it's only a pre-release?
My first guess would be that your kernel doesn't really support the
readonly adjtime and every call cancels the previous adjustment. Can
you please try it again without noselect and with this patch included?
Again, the sourcestats output after 15 minutes should be enough.
diff --git a/sys_linux.c b/sys_linux.c
index f3bb5f7..5a90de7 100644
--- a/sys_linux.c
+++ b/sys_linux.c
@@ -1011,7 +1011,7 @@ get_version_specific_details(void)
if (kernelvercmp(major, minor, patch, 2, 6, 27) < 0) {
have_readonly_adjtime = 0;
} else {
- have_readonly_adjtime = 1;
+ have_readonly_adjtime = 0;
}
/* ADJ_NANO support */
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.