Do you have a cron-based Drupal event that is off by several hours? Your problem is most likely not with your date settings, as I first suspected when I encountered this problem with the "Recent Popular Content" block resetting at an odd time (5 hours too early, as I wanted it to reset at midnight every night). Rather, it may have to do with cronplus settings.
If you have cronplus installed, you can go into admin -> settings -> cronplus, and under "preferred hour" pick an hour that will negate the time offset you are experiencing. For example, in my case my recent popular content block was resetting 5 hours too early, which means to cronplus it was firing off at what it presumed was midnight. Therefore, if cronplus reset the popular content block 5 hours late, it would in fact be resetting it at midnight my time, which is what I wanted.
Checking Cronplus Offset
You can verify the offset in your cronplus logs (admin -> logs -> cronplus messages). You'll notice an entry like the following:
cronplus | 2006-12-16 18:59 | Processing hourly cron for 2006-12-16 22:59:51 UTC, ... | AnonymousWhat this tells me is that the cronplus event scheduled to fire off at 23 UTC, actually occured at 19 EST (my time zone), which does not account correctly for the timezone difference (there's 5 hours difference between UTC and EST, not 4). This means my server time is one hour different from my actual time zone. You can verify this by running the PHP date() function and having it return the timezone.
All Content © 2005 - 2008 Contract Web Development, Inc. All Rights Reserved. Privacy Policy | Terms of Use | Powered by Drupal
1 day 3 hours ago
1 day 17 hours ago
2 days 4 hours ago
2 days 4 hours ago
2 days 9 hours ago