I am running raspbian wheezy, upgraded to all the latest packages. The only custom package installed on it is Oracle's Java 8, everything else and its configuration is stock.
Yesterday I noticed that the rpi time was wrong (after a short power failure). I started digging and found out that the NTPd service is not updating the local time. This is most likely only a recent problem since I had power failures before and never noticed problems with time.
The NTP daemon seems to be running. When I stop the service and run ntpd manually
sudo ntpd -gq
It is supposed to update the time and exit. But it never does. Just continues running without actually doing anything.
/var/log/syslog logs the following:
May 5 07:20:51 autohome ntpd: ntpd firstname.lastname@example.org Fri May 18 20:30:57 UTC 2012 (1) May 5 07:20:51 autohome ntpd: proto: precision = 1.000 usec May 5 07:20:51 autohome ntpd: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 May 5 07:20:51 autohome ntpd: Listen normally on 1 lo 127.0.0.1 UDP 123 May 5 07:20:51 autohome ntpd: Listen normally on 2 eth0 192.168.1.120 UDP 123 May 5 07:20:51 autohome ntpd: peers refreshed May 5 07:20:51 autohome ntpd: Listening on routing socket on fd #19 for interface updates
Networking seems to be working properly and the default NTP servers in
ntp.conf seem to up. The
ntp.conf is standard (I only disabled ipv6):
# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help driftfile /var/lib/ntp/ntp.drift # Enable this if you want statistics to be logged. #statsdir /var/log/ntpstats/ statistics loopstats peerstats clockstats filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable filegen clockstats file clockstats type day enable # You do need to talk to an NTP server or two (or three). #server ntp.your-provider.example # pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will # pick a different set every time it starts up. Please consider joining the # pool: <http://www.pool.ntp.org/join.html> server 0.debian.pool.ntp.org iburst server 1.debian.pool.ntp.org iburst server 2.debian.pool.ntp.org iburst server 3.debian.pool.ntp.org iburst # Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for # details. The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions> # might also be helpful. # # Note that "restrict" applies to both servers and clients, so a configuration # that might be intended to block requests from certain clients could also end # up blocking replies from your own upstream servers. # By default, exchange time with everybody, but don't allow configuration. restrict -4 default kod notrap nomodify nopeer noquery #restrict -6 default kod notrap nomodify nopeer noquery # Local users may interrogate the ntp server more closely. restrict 127.0.0.1 #restrict ::1 # Clients from this (example!) subnet have unlimited access, but only if # cryptographically authenticated. #restrict 192.168.123.0 mask 255.255.255.0 notrust # If you want to provide time to your local subnet, change the next line. # (Again, the address is an example only.) #broadcast 192.168.123.255 # If you want to listen to time broadcasts on your local subnet, de-comment the # next lines. Please do this only if you trust everybody on the network! #disable auth #broadcastclient
The ntpd version that comes with raspbian is compiled without debug, so
ntpd -d doesn't work. Any idea what can possible cause this?