time problem

[numanoids]

(29th Mar, 2013 04:29 AM)Skywatch Wrote:  Yes it is odd. As I said it happened to me too and I found a cure for my case. Since then I have reset the DNS to the router address and guess what, the time is correct! - Previously I had gone for a couple of weeks with the 1970 date and time (usually starts late on 31.12.69 and goes on from there)! I am sorry that I do not have anything else to offer.

Skywatch

Apologies for resurrecting this but I'm finding the same behaviour on an xbian system that had been fine up till now.

I tried manually synching time with ntpdate both while the clcok was 1970 and after manually bringing up to sync.

Code:

xbian@xbian ~ $ sudo ntpdate 0.debian.pool.ntp.org
27 May 15:27:52 ntpdate[2802]: no server suitable for synchronization found
xbian@xbian ~ $ sudo ntpdate -q 0.debian.pool.ntp.org
server 131.234.137.23, stratum 2, offset 67.950734, delay 0.07275
server 94.228.220.14, stratum 2, offset 67.948952, delay 0.05827
server 79.142.192.4, stratum 2, offset 67.946397, delay 0.11832
server 5.39.79.199, stratum 3, offset 67.949876, delay 0.05629
27 May 15:28:03 ntpdate[2814]: step time server 94.228.220.14 offset 67.948952 sec

Removed ntp and installed chrony - no joy.

Just installed the fake-hwclock and its holding close to the right time but suspect future reboots will end up drifting back until it magically bursts back into life (as seen above).

Anyone able to provide any further troubleshooting tips? I've tried changing DNS to no joy but clearly ntpdate is identifying the difference.