Threaded Mode | Linear Mode

TorodeFuegO · 7th Mar, 2013, 02:29 AM

After a fresh install of xbian 5, time is set to 01/01/1970
Have anyone experienced same problem? ntpd seems to be running but not setting up right date
Help appreciated
Thanks

CurlyMo · 7th Mar, 2013, 02:31 AM

No, never had that problem. It always sets the time at boot time.

2twisty · 7th Mar, 2013, 02:41 AM

Are you connected to the network? Since the Pi does not have a real time clock, it tries to get the time from a server on the network.

kraleksandr · 7th Mar, 2013, 02:42 AM

After reboot, xbmc shows 3:00 as current time (gmt+4) and after few seconds it changes to current time. And other apps which have time-based info shows it like that:

Quote:Active time: 8476d, 5h

(transmission)

TorodeFuegO · 7th Mar, 2013, 02:42 AM

i am connected to network but couldn't get right date and time.
if i stop ntp, ntpdate manages to set time with 0.debian.pool.ntp.org but ntp doesn't set time at boot

Skywatch · 18th Mar, 2013, 07:56 AM

(7th Mar, 2013 02:29 AM)TorodeFuegO Wrote: After a fresh install of xbian 5, time is set to 01/01/1970
Have anyone experienced same problem?

It is happening to me also!

Skywatch

I Solved this one as follows.......

Go into System, Settings, Xbian Config.
Make sure to manually set the network settings (I use static IP).
Check that the DNS has a valid ip address in it (mine was set to my router, but changed it to 8.8.8.8).
Reboot

All is now well again with the time.

Skywatch

TorodeFuegO · 20th Mar, 2013, 04:12 AM

(18th Mar, 2013 07:56 AM)Skywatch Wrote:
(7th Mar, 2013 02:29 AM)TorodeFuegO Wrote: After a fresh install of xbian 5, time is set to 01/01/1970
Have anyone experienced same problem?

It is happening to me also!

Skywatch

I Solved this one as follows.......

Go into System, Settings, Xbian Config.
Make sure to manually set the network settings (I use static IP).
Check that the DNS has a valid ip address in it (mine was set to my router, but changed it to 8.8.8.8).
Reboot

All is now well again with the time.

Skywatch

Thanks for the trick but didn't work for me

rcrisan · 24th Mar, 2013, 02:23 AM

I also have xbian 5. I followed your advice and set up static IP. The internet connection is working fine. However, even after reboot or ntp restart I still have the date set to 1970. What to do?? Weird is that previously raspbmc and openelec were just fine...

Here's the output of ntpq -p

remote refid st t when poll reach delay offset jitter
==========================================
ups.alsys.ro .INIT. 16 u - 64 0 0.000 0.000 0.000
ns2.upcbiz.ro .INIT. 16 u - 64 0 0.000 0.000 0.000
mail.bgs.ro .INIT. 16 u - 64 0 0.000 0.000 0.000
main-fe0.b.astr .INIT. 16 u - 64 0 0.000 0.000 0.000
aurora.dnttm.ro .INIT. 16 u - 64 0 0.000 0.000 0.000

Skywatch · 29th Mar, 2013, 04:29 AM

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

numanoids · 28th May, 2013, 12:33 AM

(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.

mk01 · 2nd Jun, 2013, 05:08 AM

(28th May, 2013 12:33 AM)numanoids Wrote: Anyone able to provide any further troubleshooting tips? I've tried changing DNS to no joy but clearly ntpdate is identifying the difference.

is your ntp service starting at boot? (check "ps aux | grep ntpd" after fresh reboot).

do you have proper config file for ntp (/etc/ntp.conf)?

172pilot · 16th Apr, 2019, 01:33 PM

Wow.. this looks like an old problem, but I dont see a solution.. My NTP is running, and in my ssh session, the time looks right, but with the timezone set in xbian, it still shows off by 4 hours (which is my timezone offset).. I have it set to America/New York in xbian, but it seems to be ignoring it.. Any news on this? Hints?

***Nachteule*** · 16th Apr, 2019, 11:08 PM

(16th Apr, 2019 01:33 PM)172pilot Wrote: Wow.. this looks like an old problem, but I dont see a solution.. My NTP is running, and in my ssh session, the time looks right, but with the timezone set in xbian, it still shows off by 4 hours (which is my timezone offset).. I have it set to America/New York in xbian, but it seems to be ignoring it.. Any news on this? Hints?

Never had such issues. Seems you're doing anything wrong