Koozali.org: home of the SME Server

Date go creazy

Offline akhilmathema

  • ***
  • 42
  • +0/-0
Re: Date go creazy
« Reply #30 on: December 15, 2008, 04:05:08 AM »
1) Check the NTP variables
config show ntpd
2) Update the "Time Zone" Data package.
yum -y update tzdata
3) If you've changed the NTP Server
signal-event timeserver-update
4) If you've changed time zone
signal-event timezone-update
5) signal-event post-upgrade; signal-event reboot

Offline geoff

  • ***
  • 61
  • +0/-0
Re: Date go creazy
« Reply #31 on: December 15, 2008, 11:59:05 AM »
Bug#: 4798 refers

Offline larieu

  • *****
  • 214
  • +0/-0
Re: Date go creazy
« Reply #32 on: December 19, 2008, 12:41:03 PM »
Thanks to all

sorry for my late reply but I was away for several days for some job duty
between the time I checked also the "hardware issue"
when I upgraded that server (over one year ago) I used one of the 5 MB from the same batch of acquisitions
as I have another 4 identical hardware I asked one of the people there to "change" the MB from the server with one of one computer which works very well in windows environment
the result was: the same time shift is seen

as I saw in some of the previous posts - the issue it is a kernel problem
because the server is far away from me - for the moment I had an crontab which adjust the time each 20 minutes (server time - this is ok if the time on server run faster than the real time)

I'll change the server MB in January when I'll have the scheduled trip for maintenance there
this raise another problem for me
while I use only Intel TM MB (I buy at least 2 for one server - and one is used into an "normal computer" in the same location - this give me "spare parts on site" easy to be replaced by non so technical people)   
can you tell me a good choice from the actual offer of intel products
which replace my "problematic" MB
if everybody's life around you is better, probably yours will be better
just try to improve their life

Offline geoff

  • ***
  • 61
  • +0/-0
Re: Date go creazy
« Reply #33 on: December 20, 2008, 04:20:54 AM »
I had the same issue with a DG965RY Intel Board which I swapped out for a DG915 board and the issue disappeared. The DG945 are OK too. Don't use a DG946 board with SME at all.

Intel 965 has a suspicious frequency here ..