2

exact with the minutes but wrong with the hours. Mon Sep 8 08:54:44 BST 2014. When actually it is 20:54.
I did : sudo /etc/init.d/ntp restart at least ten times no avail. My raspi activates a timelapse camera and has been working for month without any problem with the correct time and all of a sudden this problem occured without any intervention. Now the camera instead of taking a picture at 10:00, take it at 22:00....Too bad it's dark.

Morgan Courbet
  • 3,703
  • 3
  • 22
  • 38
user3315730
  • 177
  • 1
  • 3
  • 8
  • 2
    Did you set /etc/localtime according to your timezon. E.g. (on Archlinux) ln -s /usr/share/zoneinfo/Europe/Berlin /etc/localtime Ok, your date states BST looks like time is already localized. Mmmh. – Ghanima Sep 08 '14 at 20:17
  • IS this Raspian or another distro? – rob Sep 09 '14 at 07:30
  • My distro is Raspbian wheezy. And the timezone is well configured through Raspi-Config. Never seen this kind of problem ! – user3315730 Sep 09 '14 at 10:04
  • What is the output of ntpdate -du pool.ntp.org – Craig Sep 09 '14 at 16:21
  • Is the pi connected to a network via ethernet cable or wifi? If not, ntpd can't update and the pi has no hardware timeclock. – Tyson Sep 11 '14 at 01:29
  • If it wouldn't have any network connection it wouldn't be Sept, 8th after all... – Ghanima Sep 11 '14 at 15:23

1 Answers1

2

Considering that the RPi has got no Real Time Clock and starts at January, 1st, 1970 every reboot, I assume that your ntpis working fine. Check with date -u the system time in UTC and compare to reality. It's most probably right (unless you used date -s to set the time manually).

The guess would be that your timezone settings are wrong. Please check the symbolic link /etc/localtime or remove it and create it newly according to your timezone by ln -s /usr/share/zoneinfo/<your-timezone-goes-here> /etc/localtime.

Ghanima
  • 15,855
  • 15
  • 61
  • 119