I ran the update for the DST change and everything seemed to go okay. But cron is running 1 hour late (what should run at 4:00am is instead being run at 5:00am and so on). I'm running Plesk on a Total Control Server, RHEL3.

[root@ded01 root]# zdump -v /etc/localtime | grep 2007
/etc/localtime Sun Mar 11 06:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 EST isdst=0 gmtoff=-18000
/etc/localtime Sun Mar 11 07:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 EDT isdst=1 gmtoff=-14400
/etc/localtime Sun Nov 4 05:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 EDT isdst=1 gmtoff=-14400
/etc/localtime Sun Nov 4 06:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 EST isdst=0 gmtoff=-18000
[root@ded01 root]# date
Mon Mar 12 14:22:26 EDT 2007

File time stamps and logs show the correct time. Any ideas?

Try restarting crond. We had a few things around here that needed to be killed and restarted before they caught up with the time(s).

As it were.

Thanks! - restarting crond fixed the cron issue.

I also noticed that while the apache logs show the correct time, some of the system logs (maillog, secure log) do not. They are still an hour "slow". Anything short of rebooting the server that can fix this?

Also seeing Urchin stats being run at 5:00am instead of 4:00am as they should. But the Urchin config for each report still shows 4:00am.... is there more than one system clock that must be set?

Update: rebooting the server ("shutdown -rf now") fixed the remaining time disparities.