New user's registration have been closed due to high spamming and low trafic on this forum. Please contact forum admins directly if you need an account. Thanks !

server 5 min late

Got problems with your B2 or B3? Share and get helped!
Post Reply
cgl72
Posts: 13
Joined: 25 Oct 2008, 10:17

server 5 min late

Post by cgl72 »

Hi
Please excuse me if the question has been answered before, but my searches came to nothing...
My bubba server is 5 minutes late on world time (i.e. my bubba has time 19.45 and the real time is 19.50. I have it set for automatic time adjustment but this does not help. My question is the following:
A. how is this possible
B. how do I fix this so it will not happen again?
C. how are set the time servers on the interet?

Thanks
Christian
asparak
Posts: 173
Joined: 08 Jun 2009, 07:38

Re: server 5 min late

Post by asparak »

I'd suggest restarting NTP firstly and check the NTP logs.
Sounds like you NTP daemon is not actually connecting to the world NTP service
cgl72
Posts: 13
Joined: 25 Oct 2008, 10:17

Re: server 5 min late

Post by cgl72 »

Thanks Asparak

Here is the only thing I can find in the syslog and deamon log.
Dec 22 13:16:44 bubba ntpd[4340]: synchronized to 195.216.64.208, stratum 2
Dec 22 13:16:44 bubba ntpd[4340]: kernel time sync enabled 0001
Dec 22 13:17:20 bubba ntpd[4340]: synchronized to 212.101.0.10, stratum 2
No errors as far as I can see. I went ahead and did a manual setting and now it seems to be keeping time.
Thanks for pointing me to the logs. I did not know how to see if there was a problem.
Christian
asparak
Posts: 173
Joined: 08 Jun 2009, 07:38

Re: server 5 min late

Post by asparak »

No problem. Its entirely possible for their to be no errors in the log, but NTP to fail to connect. I have seen it a few times, where it appears to be fine and connected, but in fact it is in a partially hung status. Restarting it usually frees up things like that.

Glad its working now.
RandomUsername
Posts: 904
Joined: 09 Oct 2009, 18:49

Re: server 5 min late

Post by RandomUsername »

I think if the time is not manually set accurately enough to begin with ntp fails to set the time (i.e. if the initial time is out by more than a few seconds). That could have been your problem.

If you stop the ntp daemon and run

Code: Select all

ntpdate ntp.whatever.com
that should set your time fairly accurately as a one-off and you can then start the ntp daemon again.
Post Reply