Issue with time not setting correctly, kernel panics and NTP

Ali3n0id · 26. März 2015

I'm using using the RasPi 2 image and have noticed the time doesn't correct itself upon reboot so I have to manually use 'sudo ntpd -gq' to grab the correct time. I have use NTP server unmarked in the OMV interface.

I'm also get random 'kernel panics - not syncing' crashses

I imported my ntp.conf (after making a backup of the original) from another Pi:

Zitat

# /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

Alles anzeigen

The locale and timezone is set correctly with raspi-config and from /usr/share..

The time is still not correcting itself upon reboot

ryecoaaron · 26. März 2015

Strange... It is working on my RPi2. Here is my syslog output. What does your syslog say?

Code

Mar 26 06:23:49 raspberrypi ntpd[3264]: ntpd 4.2.6p5@1.2349-o Mon Feb  9 03:34:42 UTC 2015 (1)
Mar 26 06:23:49 raspberrypi ntpd[3293]: proto: precision = 0.833 usec
Mar 26 06:23:49 raspberrypi ntpd[3293]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Mar 26 06:23:49 raspberrypi ntpd[3293]: Listen and drop on 1 v6wildcard :: UDP 123
Mar 26 06:23:49 raspberrypi ntpd[3293]: Listen normally on 2 lo 127.0.0.1 UDP 123
Mar 26 06:23:49 raspberrypi ntpd[3293]: Listen normally on 3 lo ::1 UDP 123
Mar 26 06:23:49 raspberrypi ntpd[3293]: peers refreshed
Mar 26 06:23:49 raspberrypi ntpd[3293]: Listening on routing socket on fd #20 for interface updates
Mar 26 06:23:49 raspberrypi ntpd[3293]: Deferring DNS for pool.ntp.org 1
Mar 26 06:23:49 raspberrypi ntpd[3299]: signal_no_reset: signal 17 had flags 4000000


Mar 26 06:23:51 raspberrypi ntpdate[3540]: the NTP socket is in use, exiting
Mar 26 06:23:51 raspberrypi ntpd_intres[3299]: DNS pool.ntp.org -> 208.75.88.4


Mar 26 06:23:52 raspberrypi ntpd[3293]: Listen normally on 4 eth0 192.168.1.164 UDP 123
Mar 26 06:23:52 raspberrypi ntpd[3293]: peers refreshed

Alles anzeigen

Ali3n0id · 29. März 2015

Here's an entry under syslog:

Code

Feb  3 18:31:37 box ntpd[3865]: ntpd 4.2.6p5@1.2349-o Mon Feb  9 03:34:42 UTC 2015 (1)
Feb  3 18:31:37 box ntpd[3865]: proto: precision = 1.198 usec
Feb  3 18:31:37 box ntpd[3865]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Feb  3 18:31:37 box ntpd[3865]: Listen and drop on 1 v6wildcard :: UDP 123
Feb  3 18:31:37 box ntpd[3865]: Listen normally on 2 lo 127.0.0.1 UDP 123
Feb  3 18:31:37 box ntpd[3865]: Listen normally on 3 eth0 192.168.0.6 UDP 123
Feb  3 18:31:37 box ntpd[3865]: Listen normally on 4 tun0 10.3.0.1 UDP 123
Feb  3 18:31:37 box ntpd[3865]: Listen normally on 5 lo ::1 UDP 123
Feb  3 18:31:37 box ntpd[3865]: peers refreshed
Feb  3 18:31:37 box ntpd[3865]: Listening on routing socket on fd #22 for interface updates
Mar 26 01:24:39 box ntpd[3865]: ntpd: time set +4344774.922111 s

Alles anzeigen

Time and dates are all wrong until I manually update ntp

pisco · 30. Juli 2015

So how did you fix this problem?

Jetzt mitmachen!