Each line then refers to a set of hourly-changing random servers that provide your server with the correct time.

tinker panic 0 # Local users may interrogate the ntp server more closely.

restrict 127.0.0.1 restrict ::1 # Specify one or more NTP servers. server 0Jun 20 vg ntpd[7239]: ntpd [email protected] Tue Jun 5 UTC 2012 (1) Jun 20 vg ntpd[7240]: proto: precision = 0.191 usec Jun 20 vg ntpd[7240]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Jun 20 vg ntpd[7240]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Jun 20 vg ntpd[7240]: Listen and drop on 1 v6wildcard :: UDP 123 Jun 20 vg ntpd[7240]: Listen normally on 2 lo 127.0.0.1 UDP 123 Jun 20 vg ntpd[7240]: Listen normally on 3 eth0 10.0.2.15 UDP 123 Jun 20 vg ntpd[7240]: Listen normally on 4 eth1 192.1 UDP 123 Jun 20 vg ntpd[7240]: Listen normally on 5 eth2 192.168.0.156 UDP 123 Jun 20 vg ntpd[7240]: Listen normally on 6 eth0 fe80::aff:fea44 UDP 123 Jun 20 vg ntpd[7240]: Listen normally on 7 eth2 fe80::aff:fe1c:18ae UDP 123 Jun 20 vg ntpd[7240]: Listen normally on 8 eth1 fe80::aff:fe02:b8f6 UDP 123 Jun 20 vg ntpd[7240]: Listen normally on 9 lo ::1 UDP 123 Jun 20 vg ntpd[7240]: peers refreshed Jun 20 vg ntpd[7240]: Listening on routing socket on fd #26 for interface updates In the above logs, the date is a full 14 hours behind.

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

Try moving the tinker option to the top of the file and also make sure that you're following the recommendations in that SO Q&A too.

I am running raspbian wheezy, upgraded to all the latest packages.However, ntpdate is not an action that should be taken regularly because it syncs the virtual server’s time so quickly, the jump in time may cause issues with time sensitive software.Therefore, it is best to run this only once, prior to setting up NTP, and then let NTP take over—otherwise, if the server’s time is too far off, NTP may not launch altogether.# 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.This can be set up by installing the ntp daemon on the VPS— the program will automatically, slowly shift the server clock to match the reference one.