Clock sync issue

Hello all.

We have just purchased a cluster of 30 Sun x2100 servers in May to do
bioinformatics calculations. We are running CentOS 4.3 on all of them.
All x2100s have identical installations ntp syncing to the node
fileserver, a v240 running Sol10.

Here's the peculiar part:

7 of the x2100s have a clock drift of approximately 10 hours in the
first day. All 7 have a similar drift (+/- 200 seconds). Sometimes it
continues to drift more after it's about 10 hours ahead, but mostly it
stays at approximately 10 hours.
We have tried syncing them to a hardware clock once per day, we've tried
using different ntp servers. This happens with or without ntp enabled.

The motherboard has been replaced on one of the faulty 7 before we saw
this time problem, so at least one of the motherboards is new as of the
middle of June.
Does anyone have any idea what this could be?

I will summarize to the list.

Thanks for your help!

Matt Boes
UNIX Systems Manager
Max Planck Institute for Molecular Cell Biology and Genetics
_______________________________________________
sunmanagers mailing list
sunmanagers@xxxxxxxxxxxxxxx
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

Relevant Pages

  • Re: Setting Up NTP Subnet
    ... > I have questions regarding best practices on architecture of NTP ... > it sufficient to use multiple GPS receivers with ACTS dial ... The lower the stratum the bigger the ... servers and that the servers at this level should peer. ...
    (comp.protocols.time.ntp)
  • Re: Proposed NTP solution for a network
    ... Locations A and B have a large community of Suse 10.x Enterprise servers, each with very stringent requirements to have time be very closely "in sync" with each other at that site, as well as at the other site. ... Each of A, B, and C have a dedicated NTP appliance, with integrated GPS receiver and antenna on the roof. ... there is no provision on the enclosure to accept a PPS or other time source for distribution to the individual blades using a backplane mechanisim. ...
    (comp.protocols.time.ntp)
  • Re: Setting Up NTP Subnet
    ... > I have questions regarding best practices on architecture of NTP ... > it sufficient to use multiple GPS receivers with ACTS dial backup ... me that we should create a stratum 2 tier peer layer a stratum 3 tier ... servers and that the servers at this level should peer. ...
    (comp.protocols.time.ntp)
  • Proposed NTP solution for a network
    ... Locations A and B have a large community of Suse 10.x Enterprise servers, each with very stringent requirements to have time be very closely "in sync" with each other at that site, as well as at the other site. ... Each of A, B, and C have a dedicated NTP appliance, with integrated GPS receiver and antenna on the roof. ... This would enable the appliance to lose the reference source and still be useful to the Stratum 2 servers that are clients of these appliances. ...
    (comp.protocols.time.ntp)
  • Re: handling falseticker
    ... This would lead to a "lost sync" or a "sync to ... recognized by the clients and this NTP path will be ignored. ... Both Stratum 1 will keep being sync with the respective Stratum 0 because ... This means that my Stratum 2 Servers have only 2 servers. ...
    (comp.protocols.time.ntp)