Re: [opensuse] Re: ntp client not syncing with the server
Jay Jesus Amorin wrote:
On Tue, Apr 29, 2008 at 9:22 AM, Joe Sloan <joe@tmsusa.com> wrote:
Is ntpd running? What is the output of "ntpq -pn"?
# ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== 127.127.1.0 LOCAL(0) 10 l 12 64 3 0.000 0.000 0.001 192.168.1.179 .GPS. 1 u 9 64 3 5.307 -23.183 51.587
OK, it sees the time servers but doesn't seem to be able to lock on. I'd expect to see some syslog messages about lost ticks etc. Just as a sanity check, this wouldn't happen to be a vmware instance would it? In that case, ntp problems are a known fact. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Apr 28, 2008 at 8:54 PM, Joe Sloan <joe@tmsusa.com> wrote:
Jay Jesus Amorin wrote:
On Tue, Apr 29, 2008 at 9:22 AM, Joe Sloan <joe@tmsusa.com> wrote:
Is ntpd running? What is the output of "ntpq -pn"?
# ntpq -pn remote refid st t when poll reach delay offset
jitter
==============================================================================
127.127.1.0 LOCAL(0) 10 l 12 64 3 0.000 0.000 0.001 192.168.1.179 .GPS. 1 u 9 64 3 5.307 -23.183 51.587
OK, it sees the time servers but doesn't seem to be able to lock on.
I'd expect to see some syslog messages about lost ticks etc. Just as a sanity check, this wouldn't happen to be a vmware instance would it? In that case, ntp problems are a known fact.
Joe --
Doesn't look like any external clocks have been configured. Edit /etc/ntp.conf and add some server lines -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Andersen wrote:
On Mon, Apr 28, 2008 at 8:54 PM, Joe Sloan <joe@tmsusa.com> wrote:
Jay Jesus Amorin wrote:
On Tue, Apr 29, 2008 at 9:22 AM, Joe Sloan <joe@tmsusa.com> wrote:
Is ntpd running? What is the output of "ntpq -pn"?
# ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== 127.127.1.0 LOCAL(0) 10 l 12 64 3 0.000 0.000 0.001 192.168.1.179 .GPS. 1 u 9 64 3 5.307 -23.183 51.587 OK, it sees the time servers but doesn't seem to be able to lock on.
I'd expect to see some syslog messages about lost ticks etc. Just as a sanity check, this wouldn't happen to be a vmware instance would it? In that case, ntp problems are a known fact.
Joe --
Doesn't look like any external clocks have been configured. Edit /etc/ntp.conf and add some server lines
Looks to me like he has 192.168.1.179 set up as a server... Jo -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
how can i tell if the ntp client is not locking on with the server? cat /var/log/messages | grep ntpd Apr 29 11:05:24 192.168.1.179 ntpd[1209]: frequency initialized -73.305 PPM from /var/lib/ntp/drift/ntp.drift Apr 29 11:06:46 192.168.1.179 ntpdate[1241]: step time server 172.23.8.179 offset 33.388710 sec Apr 29 11:06:46 192.168.1.179 ntpd[1246]: ntpd 4.2.0a@1.1196-r Thu Jun 29 17:40:03 UTC 2006 (1) Apr 29 11:06:46 192.168.1.179 ntpd[1246]: precision = 1.000 usec Apr 29 11:06:46 192.168.1.179 ntpd[1246]: Listening on interface wildcard, 0.0.0.0#123 Apr 29 11:06:46 192.168.1.179 ntpd[1246]: Listening on interface wildcard, ::#123 Apr 29 11:06:46 192.168.1.179 ntpd[1246]: Listening on interface lo, 127.0.0.1#123 Apr 29 11:06:46 192.168.1.179 ntpd[1246]: Listening on interface eth0, 172.23.12.123#123 Apr 29 11:06:46 192.168.1.179 ntpd[1246]: kernel time sync status 0040 Apr 29 11:06:46 192.168.1.179 ntpd[1246]: frequency initialized -73.305 PPM from /var/lib/ntp/drift/ntp.drift Apr 29 13:29:44 192.168.1.179 ntpdate[2830]: adjust time server 172.23.8.179 offset -0.048573 sec Apr 29 13:29:44 192.168.1.179 ntpd[2835]: ntpd 4.2.0a@1.1196-r Thu Jun 29 17:40:03 UTC 2006 (1) Apr 29 13:29:44 192.168.1.179 ntpd[2835]: precision = 1.000 usec Apr 29 13:29:44 192.168.1.179 ntpd[2835]: Listening on interface wildcard, 0.0.0.0#123 Apr 29 13:29:44 192.168.1.179 ntpd[2835]: Listening on interface wildcard, ::#123 Apr 29 13:29:44 192.168.1.179 ntpd[2835]: Listening on interface lo, 127.0.0.1#123 Apr 29 13:29:44 192.168.1.179 ntpd[2835]: Listening on interface eth0, 172.23.12.123#123 Apr 29 13:29:44 192.168.1.179 ntpd[2835]: kernel time sync status 0040 Apr 29 13:29:44 192.168.1.179 ntpd[2835]: frequency initialized -73.305 PPM from /var/lib/ntp/drift/ntp.drif Please help. ntp client is running fine but when i return the next morning and check the time, the 3 client is not in sync with the server. is there a problem running ntp client on vmware instance? Thanks, J On Tue, Apr 29, 2008 at 11:54 AM, Joe Sloan <joe@tmsusa.com> wrote:
Jay Jesus Amorin wrote:
On Tue, Apr 29, 2008 at 9:22 AM, Joe Sloan <joe@tmsusa.com> wrote:
Is ntpd running? What is the output of "ntpq -pn"?
# ntpq -pn remote refid st t when poll reach delay offset
jitter
==============================================================================
127.127.1.0 LOCAL(0) 10 l 12 64 3 0.000 0.000 0.001 192.168.1.179 .GPS. 1 u 9 64 3 5.307 -23.183 51.587
OK, it sees the time servers but doesn't seem to be able to lock on.
I'd expect to see some syslog messages about lost ticks etc. Just as a sanity check, this wouldn't happen to be a vmware instance would it? In that case, ntp problems are a known fact.
Joe
-- Ang nagtanong ay tanga. Ang hindi nagtanong ay nanatiling tanga. -jayamorin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jay Jesus Amorin wrote:
how can i tell if the ntp client is not locking on with the server?
If the client is synched up, ntpq -p output looks like this: toro: /home/jjs (tty/dev/pts/0): bash: 1083 > ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== 127.127.1.0 .LOCL. 10 l 3 64 377 0.000 0.000 0.001 *164.67.62.194 .GPS. 1 u 157 1024 377 16.526 0.845 1.100 +128.9.176.30 .GPS. 1 u 149 1024 167 67.019 21.191 10.917 Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
as i can see it, my clients are syncing, after a long time the when i check the server the time are not syncronized, the two clients would be like 5 seconds delay while the other client is 30 mins late. On Tue, Apr 29, 2008 at 2:34 PM, Joe Sloan <joe@tmsusa.com> wrote:
Jay Jesus Amorin wrote:
how can i tell if the ntp client is not locking on with the server?
If the client is synched up, ntpq -p output looks like this:
toro: /home/jjs (tty/dev/pts/0): bash: 1083 > ntpq -pn
remote refid st t when poll reach delay offset jitter ============================================================================== 127.127.1.0 .LOCL. 10 l 3 64 377 0.000 0.000 0.001 *164.67.62.194 .GPS. 1 u 157 1024 377 16.526 0.845 1.100 +128.9.176.30 .GPS. 1 u 149 1024 167 67.019 21.191 10.917
Joe
-- Ang nagtanong ay tanga. Ang hindi nagtanong ay nanatiling tanga. -jayamorin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Sloan wrote:
Jay Jesus Amorin wrote:
how can i tell if the ntp client is not locking on with the server?
If the client is synched up, ntpq -p output looks like this:
toro: /home/jjs (tty/dev/pts/0): bash: 1083 > ntpq -pn remote refid st t when poll reach delay offset jitter ==============================================================================
127.127.1.0 .LOCL. 10 l 3 64 377 0.000 0.000 0.001 *164.67.62.194 .GPS. 1 u 157 1024 377 16.526 0.845 1.100 +128.9.176.30 .GPS. 1 u 149 1024 167 67.019 21.191 10.917
Joe
Thanks Joe, Now I have a new check to add to my 10.3 server setup quick reference ;-) -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
[ Top-posting corrected ] On Tue, Apr 29, 2008 at 11:54 AM, Joe Sloan <joe@tmsusa.com> wrote:
Just as a sanity check, this wouldn't happen to be a vmware instance would it? In that case, ntp problems are a known fact.
Jay Jesus Amorin wrote:
is there a problem running ntp client on vmware instance?
Err, Joe asked first! :) Are you running vmware instances? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-04-29 at 14:12 +0800, Jay Jesus Amorin wrote:
is there a problem running ntp client on vmware instance?
Yes. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIFvJ6tTMYHG2NR9URAukzAJ9iXzk9gTOUse/TFTfCcI4YvWSIHgCfciKL dm8MPiIZx27DWamtWAv6oL0= =7Or1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Carlos E. R. -
Dave Howorth -
David C. Rankin -
Jay Jesus Amorin -
Joe Sloan -
John Andersen