Reinforce Media, LLC

Well, it was this morning.  I didn’t realize it until I went to schedule a blog post for 12 hours later and it published immediately. I was concerned and actually went to blame WordPress first (I’m really not sure why).  However, when I was looking at the time preferences in the General settings area of the site I noticed something really strange.  My timezone was correct, but the date WP was showing was way off. This meant that my CentOs5 server’s time was way off.

I did a little research and found an article called “Setting the time of your system“.  They gave me some good solutions on how to fix the issue, after reading it I was ready to go.  I tried a couple things in the order they said and found myself a little confused. So naturally, I started trying things till they worked.  This is not always the best solution, but I figured I could deal with a timing issue if I messed it up worse than it was.

For my CentOs 5 server I did the following, which actually worked and set the time perfectly.

First, I checked the date the server had, which turned out to be way off.

Then I looked to see if ntpd (the automatic time adjustment service) was running, it was.

I tried ntpdate to reset the time on the server, but it complained about the socket being in use.

My solution was to stop ntpd and then run ntpdate again, which worked!

A simple restart of the ntpd service and the time was correct!

So, the solution was to do the following steps:

I added “date” on the end, because you want to verify that the time actually did reset. Best of Luck!

Tags: automatic time, best solution, centos 5, ntpdate, step time, time adjustment, time preferences, time server, timezone, timing issue

Sphere: Related Content

Tagged: automatic time, best solution, centos 5, ntpdate, step time, time adjustment, time preferences, time server, timezone, timing issue