Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

4.11 Myseriously Changing Time

Status
Not open for further replies.

mwestra

MIS
May 31, 2000
8
We have a single 4.11 server that changes time by itself periodically.&nbsp;&nbsp;It is configured as a single reference.&nbsp;&nbsp;Even though the BIOS clock keeps correct time, the server will change to August 9th, 2009.<br><br>The strange part is when it happens overnight, not only will it change to August 9th, 2009, but it will also change back to the correct date and time several times through out the course of the evening. (according to the system logs)<br><br>To recover, we run DSREPAIR and declare new epoch to remove synthetic time.&nbsp;&nbsp;We run a full DSREPAIR multiple times until no errors were found.<br><br>However, the problem keeps coming back.&nbsp;&nbsp;Sometimes its immediate (1/2 hour).&nbsp;&nbsp;Sometimes its a couple of days.&nbsp;&nbsp;The last time after installing SP8a the problem disappeared for about 3 months.&nbsp;&nbsp;We thought we had it fixed for good.<br><br>Well, it is back again.&nbsp;&nbsp;We have exhausted all our resources and would appreciate any possible sugggestions.
 
OK,&nbsp;&nbsp;Problem number one:&nbsp;&nbsp;You have this server configured as a single reference time server.&nbsp;&nbsp;Since this is the only server in the tree, it wants to synchronize time with a primary server, which you don't have or don't have configured.<br><br>In learning:&nbsp;&nbsp;A singe reference time server negotiates its time with a primary.&nbsp;&nbsp;A single reference server is in fact a primary server itself.&nbsp;&nbsp;So 2 primary's are needed to negotiate time, one of them being a single reference.&nbsp;&nbsp;&nbsp;&nbsp;<br><br>I recommend the following:&nbsp;&nbsp;Set the server to a single time server, not a single reference (especially if their are no other servers available).&nbsp;&nbsp;Second, make sure that the hardware clock is enabled.&nbsp;&nbsp;Restart the server and this should resolve it.<br><br>Novell's recommended guidlines for this is to have one Single time source and all other servers be secondary's up to 30.&nbsp;&nbsp;Then when this number is reached, you would configure time provider groups etc.&nbsp;&nbsp;<br><br>This should resolve it.<br><br>For more information on TIMESYNC.NLM and configuring time sources, check the following TID 2930686 on <A HREF=" TARGET="_new"> and search for the tid number.<br><br>Mark Greenwood, CNE<br> <p>Mark C. Greenwood<br><a href=mailto:m_jgreenwood@yahoo.com>m_jgreenwood@yahoo.com</a><br><a href= > </a><br>
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top