NTP not working on new install. (And more) - Raspberry Pi Forums

hi folks,

didn't want hijack thread on ntp, , problem has become "worse" initial thoughts.

part 1:
have new pi, running jessie , not getting right time @ boot.
/etc/ntp.conf file:
(# lines removed needed - , blank lines also..)

code: select all

# /etc/ntp.conf, configuration ntpd; see ntp.conf(5)  driftfile /var/lib/ntp/ntp.drift  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   server 0 tic.ntp.telstra.net iburst #server 1 192.168.0.99 #server 2 toc.ntp.telstra.net iburst # access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html ## above line not right.  said file not exist.  # default, exchange time everybody, don't allow configuration. restrict -4 default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery  # local users may interrogate ntp server more closely. restrict 127.0.0.1 restrict ::1 

"stuck" on sat 12 august. today monday 14 august.

have 2 ntp servers listed, "tic.ntp.telstra.net" , local ntp server. we'll later.

confused why given ntp.conf file, why not syncing on boot. network connected.
though on that: rpi - 1 of many - if booted no network uses last date/time @ start. if connect network, syncs time after. why isn't other 1 doing that?

install latest jessie few "sudo ap-get update/upgrade"s since done.


have set local stuff sydney oz , stuff. i'm not sure ever did "work" on time, didn't take notice of it.
now, when ssh it, date displayed. after last log in time.





part 2:
ntp machine (192.168.0.99).
putting above problem aside, doesn't seem work either.

starting point:

****************************************************************
* *
* welcome pitime machine. *
* ============================== *
* *
****************************************************************

last login: sun aug 13 17:02:15 2017 piface
monday 14 august 11:08:09 aest 2017
temp=47.6'c
pi@timepi:~ $ ./show_times.sh
---===< start >===---
time on pi is:
monday 14 august 11:08:15 aest 2017

hardware clock time is:
mon 14 aug 2017 11:08:11 aest -0.560490 seconds

=============================================

set pi time rtc (hw clock) enter:
sudo hwclock -s

set rtc (hw clock) time pi time enter:
sudo hwclock -w
---===< end >===---

working.

last logged in on sunday, monday, , both clocks on pi saying that.

however, worrying:

pi@timepi:~ $ sudo ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
0.0.0.0 .init. 16 l - 1024 0 0.000 0.000 0.000
pi@timepi:~ $

pi's /etc/ntp.conf file different, in servers:

server 0 tic.ntp.telstra.net

that's it.

machine using "similar" musicpi example part 1, boots right time.

anyway, not difficult, i'll leave there feel 2 different problems. though both ntp stuff, 1 access , 1 serving out times.

oh, clarity too:
, when power m$ machine ntp check program, happy gets 192.168.0.99 machine, , think nas sees accessible. ok, should check logs, anyway...



me understand why of 2 pi's have 1 syncs time when booted , other doesn't?
ntp.conf files same, 1 has more servers listed.

p.s. (edit)
oops.
logged in , didn't take care @ looking @ machine's time.

seems machine has become ignorant real time.
shall try different ntp server - 1 listed in .conf file.

https://www.eecis.udel.edu/~mills/ntp/h ... tml#server
server lines wrong, there no numeral argument it.

also, can add few well-knowns in there make sure machine finds peer
server pool.ntp.org
server au.pool.ntp.org
server time.nist.gov
server toc.ntp.telstra.net
server tic.ntp.telstra.net prefer

servers not accept iburst client behaviour. commonplace set option irl i'm not sure makes difference.
luck

raspberrypi