Problème synchronisation NTP Raspberry Pi
Posté : ven. 20 oct. 2017 17:50
Bonjour à tous,
Je rencontre des difficultés pour synchroniser mon Rasberry Pi avec NTP en automatique au démarrage du système.
J'arrive à synchroniser l'heure en manuel par contre, comme ceci :
root@raspberrypi:/home/pi# sudo ntpdate -u fr.pool.ntp.org
20 Oct 17:42:51 ntpdate[10000]: adjust time server 62.210.211.218 offset -0.001502 sec
Par contre si je redémarre mon Raspberry il a 4 jours de retard
La commande ntpq -p me renvoie ceci :
remote refid st t when poll reach delay offset jitter
==============================================================================
ns3.stoneartpro .INIT. 16 u - 1024 0 0.000 0.000 0.000
147.135.187.131 .INIT. 16 u - 1024 0 0.000 0.000 0.000
support4.russia .INIT. 16 u - 1024 0 0.000 0.000 0.000
bb8.dousse.eu .INIT. 16 u - 1024 0 0.000 0.000 0.000
=> avec ces info, on se rend conpte que la colonne refid reste en INIT => donc pas bon!
Dans mon fichier ntp.conf j'ai bien ceci pour déclaré les serveurs NTP pourtant :
# 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 fr.pool.ntp.org prefer
server 0.fr.pool.ntp.org iburst
server 1.fr.pool.ntp.org iburst
server 2.fr.pool.ntp.org iburst
server 3.fr.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 ... strictions>
# 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
Si vous avez des pistes je suis preneur... Merci.
Je rencontre des difficultés pour synchroniser mon Rasberry Pi avec NTP en automatique au démarrage du système.
J'arrive à synchroniser l'heure en manuel par contre, comme ceci :
root@raspberrypi:/home/pi# sudo ntpdate -u fr.pool.ntp.org
20 Oct 17:42:51 ntpdate[10000]: adjust time server 62.210.211.218 offset -0.001502 sec
Par contre si je redémarre mon Raspberry il a 4 jours de retard
La commande ntpq -p me renvoie ceci :
remote refid st t when poll reach delay offset jitter
==============================================================================
ns3.stoneartpro .INIT. 16 u - 1024 0 0.000 0.000 0.000
147.135.187.131 .INIT. 16 u - 1024 0 0.000 0.000 0.000
support4.russia .INIT. 16 u - 1024 0 0.000 0.000 0.000
bb8.dousse.eu .INIT. 16 u - 1024 0 0.000 0.000 0.000
=> avec ces info, on se rend conpte que la colonne refid reste en INIT => donc pas bon!
Dans mon fichier ntp.conf j'ai bien ceci pour déclaré les serveurs NTP pourtant :
# 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 fr.pool.ntp.org prefer
server 0.fr.pool.ntp.org iburst
server 1.fr.pool.ntp.org iburst
server 2.fr.pool.ntp.org iburst
server 3.fr.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 ... strictions>
# 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
Si vous avez des pistes je suis preneur... Merci.