After upgrade, Civi complains about timezone

[CityBloc]

After I upgraded from 4.4 to 4.5, Civi complained about timezone being wrong

"Timestamps reported by MySQL (eg "2014-04-21 14:50") and PHP (eg "2014-04-21 19:50" ) are mismatched."

I fixed this by noticing that WP's time zone was wrong, but only after chasing around inside PHP, where phpinfo() was reporting the correct timezone.

So: is the above warning message in need of an update to include mentioning that host application time might also be wrong?

[pcoutas]

We're having the same problem too -

http://forum.civicrm.org/index.php/topic,32549.0.html

But my WP install is on the same timezone as MySQL - seems like CiviCRM is doing its own thing. I have no idea how to correct it. Ideas? The help files helpfully suggest turning "automatic sync" on but I don't know where to find it (CiviCRM? WP? MySQL?)

[CityBloc]

Long story short, WP ignores the timezone from the server and from PHP.  An administrative WP user has to set the time zone explicitly under Settings > General.

Sorry I didn't update this thread sooner.  Good luck!

[pcoutas]

Yup, I've done that - there's still a mismatch between the two. My WP and Server are on UTC/GMT + 8 but CiviCRM is not.

[questions]

Maybe I should create a new issue.  I'm getting the same error after upgrading our test instance from 4.3.5 to 4.4.5 but the time difference is only 4 minutes.

Timestamps reported by MySQL (eg "2014-05-15 08:58") and PHP (eg "2014-05-15 08:54" ) are mismatched.

MySQL time is fast by not quite 4 mins.   I think the php time matches system time; though, I haven't a clue how to get it to give me back php time.   (My background is sql)

I'm guessing this check is new since I see the same mysql time difference on the unupgraded production instance (4.3.5).

[questions]

Hmm, we are running on Dreamhost and I believe the mysql doesn't really run on the same box as the php even though it feels like it.  I'll have to bug dreamhost or figure out the sync php sql stuff.

[JoeMurray]

Agreed that a) Dreamhost runs MySQL on a different server and b) being out by 4 minutes between PHP and MySQL would only happen in a case like that.