![](https://seccdn.libravatar.org/avatar/7161c31f2f0bc6dd8bad782a82ba1a26.jpg?s=120&d=mm&r=g)
Hello all! I am trying to set up my own local timeserver. I followed the how-to and entered "server xxx.xxx.xxx.xxx" in the /etc/ntp.conf as i use a external ntp server for synchronization. I keep getting this in the log: 3 Jul 14:10:43 xntpd[18042]: synchronisation lost 3 Jul 14:32:15 xntpd[18042]: time reset -0.596435 s 3 Jul 14:32:15 xntpd[18042]: synchronisation lost 3 Jul 14:53:54 xntpd[18042]: time reset -0.600191 s 3 Jul 14:53:54 xntpd[18042]: synchronisation lost 3 Jul 15:15:30 xntpd[18042]: time reset -0.595681 s 3 Jul 15:15:30 xntpd[18042]: synchronisation lost I have followed the FAQ's troubleshhoting and set the hwcklock manually to compensate for the large time difference, but the problem still remains.. What am i doing wrong? Am i just missing something stupid? Tell me what files to list and what command output you need to help me on this... -- /Rikard ------------------------------------------------------------------------------------ Rikard Johnels email : rjhn@linux.nu Web : http://www.rikjoh.com Mob : +46 70 464 99 39 ------------------------ Public PGP fingerprint ---------------------------- < 15 28 DF 78 67 98 B2 16 1F D3 FD C5 59 D4 B6 78 46 1C EE 56 >
![](https://seccdn.libravatar.org/avatar/d70f8a8240c69007852b9d1bf27e170b.jpg?s=120&d=mm&r=g)
* Rikard Johnels (rjhn@linux.nu) [030703 06:40]:
I keep getting this in the log: 3 Jul 14:10:43 xntpd[18042]: synchronisation lost 3 Jul 14:32:15 xntpd[18042]: time reset -0.596435 s 3 Jul 14:32:15 xntpd[18042]: synchronisation lost 3 Jul 14:53:54 xntpd[18042]: time reset -0.600191 s 3 Jul 14:53:54 xntpd[18042]: synchronisation lost 3 Jul 15:15:30 xntpd[18042]: time reset -0.595681 s 3 Jul 15:15:30 xntpd[18042]: synchronisation lost
That's not nec. a problem. It just means that your clock has drifted from the source more than (I think) 128ms and the whole synchronization process starts over. If you reboot more than once per week or so there's not much you can do to avoid this. Otherwise you might want to try some better (e.g., closer) time servers. -- -ckm
participants (2)
-
Christopher Mahmood
-
Rikard Johnels