View Single Post
Old 25th August 2009
plexter plexter is offline
Shell Scout
 
Join Date: May 2008
Posts: 124
Default

Hi all. Thanks for your input.

I'll start from the earlier posts first. (will post new configs...etc at the end)

BSDfan666:

In regards to the listen address...etc I have had all of that set already.

I had modified my NTP servers to be "more" local however I don't see this as being beneficial over a round-robin relay "server 0.ca.pool.ntp.org"

ocicat:

Quote:
If the local time server is not synchronized with the upstream time servers, the local time server will also not be providing any NTP updates to your local clients -- hence it is not surprising that the clients may be exhibiting the wrong time if the local time server itself is not synchronized or configured correctly.
This brings me to notice the following (since I've been away) the BSD1 machine (ntp server) seems to have a time of exactly 1 hour behind. It almost seems like the timezone is incorrect yet I have reset both BSD1 and BSD2 to Canada Eastern and even rebooted. Still show's the clock 1 hour behind and NTP says syncronizing with ntp server. (see below)

Quote:
No log messages has been posted from /var/log/daemon, so it is anyone's guess as to the current state of your local time server.
I have been posting my /var/log/daemon (relevant) since my first post. However if something lacks please feel free to ask.

s2scott:

Thanks your configs look pretty much the same as mine when I started with the exception of your interfaces.

Configs and Logs:


[BSD1]

/etc/ntpd.conf
Code:
listen on 192.168.244.1

server  128.100.56.135     #tick.utoronto.ca
server  128.100.100.128    #tock.utoronto.ca
server  136.159.2.254      #subitaneous.cpsc.ucalgary.ca
server  128.233.3.101      #tock.usask.ca
server  128.233.3.100      #tick.usask.ca
/var/log/daemon (filtered)
I've noticed daemon is getting fairly cluttered. Is it possible to send NTP to it's own log?

Recent Logs of synchronization:
Code:
Aug 25 13:09:17 BSD1 ntpd[24780]: peer 128.100.100.128 now valid
Aug 25 13:13:20 BSD1 ntpd[27339]: adjusting local clock by 4309.229700s
Aug 25 13:13:51 BSD1 ntpd[27339]: adjusting local clock by 4309.074970s
Aug 25 13:18:06 BSD1 ntpd[27339]: adjusting local clock by 4307.826573s

...

Note this seems to be fairly constant and has been going all weekend with no noticeable difference in the actual time

Aprox system date related to logs (minute/sec maybe slightly off)

# date
Tue Aug 25 13:19:50 EDT 2009

Actual time is Tue Aug 25 14:xx:xx EDT 2009
I believe in order to get anything else working properly, BSD1 will first need to be working correctly. However I do not understand what could be causing it to be exactly 1 hour behind! Ideas?

Thanks for your help!
Reply With Quote