Juan C. Gonzalez wrote: > Hello > > I have a two computers, A and B. Version xntp 4.1.1. I have too a > server ntp (S). > > My problem is the following one: > > Computer A, run xntpd start, connect with server (S), update the hour > and It works correctly. > > Computer B, run xntpd start, connect with server (S), It updates the > hour but alone this time. > > Computer A: > > ntpq> pe > remote refid st t when poll reach delay > offset jitter > ====================================================================== > emaddns1.endesa 0.0.0.0 16 u - 64 0 0.000 0.000 > 4000.00 > emaddns3.endesa 0.0.0.0 16 u - 64 0 0.000 0.000 > 4000.00 > > ntpq> rv > status=c011 sync_alarm, sync_unspec, 1 event, event_restart, > version="ntpd [EMAIL PROTECTED] Wed Oct 16 12:55:05 UTC 2002 (1)", > processor="i686", system="Linux2.4.21-278-default", leap=11, > stratum=16, > precision=-16, rootdelay=0.000, rootdispersion=0.375, peer=0, > refid=0.0.0.0, reftime=00000000.00000000 Thu, Feb 7 2036 > 7:28:16.000, > poll=4, clock=c97e9c6f.89437c56 Thu, Feb 15 2007 9:46:39.536, > state=0, > offset=0.000, frequency=0.000, jitter=0.015, stability=0.000 > > > Computer B: > ntpq> pe > remote refid st t when poll reach delay > offset jitter > ====================================================================== > emaddns1.endesa emball601.endes 2 u 46 64 7 1.807 69662.4 > 15236.6 > emaddns3.endesa 0.0.0.0 16 u - 64 0 0.000 0.000 > 4000.00 > > ntpq> rv > status=c011 sync_alarm, sync_unspec, 1 event, event_restart, > version="ntpd [EMAIL PROTECTED] Wed Oct 16 12:55:05 UTC 2002 (1)", > processor="i686", system="Linux2.6.5-7.244-smp", leap=11, stratum=16, > precision=-16, rootdelay=0.000, rootdispersion=2.790, peer=0, > refid=0.0.0.0, reftime=00000000.00000000 Thu, Feb 7 2036 > 7:28:16.000, > poll=4, clock=c97e98d4.1fa14cec Thu, Feb 15 2007 9:31:16.123, > state=0, > offset=0.000, frequency=0.000, jitter=0.015, stability=0.000 > > Can someone help me? > > Sorry my English. > > Thanks >
69662.4 seconds exceeds the panic threshold. ntpd decides that the situation is hopeless and gives up! Your clock appears to be off by almost 20 hours!! Try starting ntpd with the -g switch! That will cause it to set the time unconditionally when it starts. If, for any reason, you can't use the -g switch, use ntpdate to set the clock. If you can't use ntpdate, set it by hand! _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
