Server Time jumped forward 12 hours.

[eagle]

Strange, two servers today, one on CPanel Stable and one on Release ....

Any idea what causes this?

[simonpearce]

Ditto - we've found this problem on three of nine servers so far . . .

Fixed with server time update in WHM but a very bizarre error from cPanel!

[mrcbrown]

When I sync with the WHM update, it stays wrong, I had to sync to an time server elsewhere other than the cpanel one it sync's to by default.

Is there a way to take the cPanel one out of the equation that anyone knows of?

[rpmws]

When I sync with the WHM update, it stays wrong, I had to sync to an time server elsewhere other than the cpanel one it sync's to by default.

Is there a way to take the cPanel one out of the equation that anyone knows of?

cpanel's time server is now correct. I just tested it. use teh time update in WHM again see what you get.

[zigzam]

I had this happen a few days back and now again.

[gantz]

For those with vB forums [...] you can run the following queries:

UPDATE post SET dateline = dateline - 43200 WHERE postid <= ID OF LAST AFFECTED POST and postid >= ID OF FIRST AFFECTED POST

Then you'll need to update your thread and forum counters in the vBulletin Admin CP

I post these with no guarantee that they won't blow your server up, ruin your forum, steal your girlfriend, kill your fish etc! I recommend you do a backup and do a SELECT first to make sure you're affecting the right entries the database!

Edit: You can check the times of the timestamps in the database by using this convertor; http://www.onlineconversion.com/unix_time.htm

Worked fine for me using

UPDATE `vb3_post`
SET dateline = dateline - 43200
WHERE dateline > time of first bad post

Maybe 'cause I had no redfish.
Neither girlfriend that could be lost.

But it would really be nice to nevermore face that situation...

[Gavster]

This problem seems to have cropped up amongst several of our cPanel boxes. (we have 200+)

One thing that seems to be a common denominator on our servers. All servers experiencing the problem are servers whose time zone was modified from the default install TZ (PST).

Servers that have retained the PST time zone do not appear to be affected.

[borealphil]

Same for me, one on RHLE, and another on FC.
I changed the time zone in WHM, and then sync the clock in WHM this morning when I noticed it. It worked for a couple of hours, and now I have clients complaining about it .

[gecker]

An initial scan of our servers show that only servers that had a timezone set differently than PST had their clocks changed by 12 hours. All servers that had a PST timezone were not affected. Has anyone else found this to be true?

[Pyrix]

We have two servers both set to GMT - only one was affected, the other was fine.

[nbento]

This also affected 4 out of 10 servers
Like I said on previous post go to the shell and execute this:

rdate -s rdate.cpanel.net

This has fixed my time issue on the servers that were affected

Now, you better start checking the clients stats, because on ALL servers that were affected by this issue the stats simply stopped working.
Still trying to figure it out why and how to get them back on track.

[westhost-neil]

We also have two servers both set to GMT, one fine the other not.

There is some issues following this problem with customers receiving emails. Customers are reporting that they can't receive through Outlook but can see all the emails fine in webmail.

When they click send/receive it just says there are no messages.

Could this be that customers who have there client set to leave a copy on the server, the client receives a message from say 8pm, so all previous messages are classed as old or already recieved?

Just a guess

[joshstein]

This happened to a few of my company's servers. Any word from cPanel as to what happened and what has been done to fix/mitigate the issue?

[jetsetter]

This totally screwed up my vB boards this morning. :[ There's no way I'm going to run that query on my db's so we'll just live with a full day of crazy time posts.

[eth00]

We had the same problem and it has happened before. The problem came from the cpanel timeservers, apparently it was reporting a bad time for awhile.

Perhaps in the future they will do something like check 2 timeservers, one being time.nist.gov, and then verify they are both close to the same time. That would help prevent this from happening again.