There seem to be some VERY weird time related things going on with
SLES9. I manage a number of SLES9 boxes in different environments,
and not one of them will correctly synchronise to its configured time
server, although the ntpd start script does ntpdate against the
configured server, and that works. Also, in each environment there
are other boxes running various other Linux and Unix versions which
are happily syncing to the time servers.
In nearly every case, ntptrace only returns a line for localhost
(which is normal if ntp hasn't been running for long, but some of
these boxes have been running for months - long enough to sync, I'd
imagine).
In one box I have seen a line printed for the time server, but then
the message
timed out, nothing received
The other weirdness is even weirder :-) When you enter the command
ps -ef|grep ps ; date
and look at the stime of the process, you will see that the process
apparently started some time in the future, which is interesting. I
did get pointed at a possible explanation of this at http://
www.thisishull.net/archive/index.php/t-23254.html and it seems later
kernels may solve this, but 2.6.5-7.244 is the latest SLES kernel,
and that is on some of the affected boxes.
Are any of you running SLES9 and successfully syncing to a time server?
Niall
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
