• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Weird time problem

DRY411S

Basic Pleskian
In PLESK I have set the time to GMT and synced with pool.ntp.org. The time being displayed in the GUI is GMT.

At command line I have verified date and hwclock. Both are set to GMT.

But if I look in the postfix maillog, timestamps are EST.

This is also affecting when things run in CRON and when Backups run.

Anybody help with what is going on here?

(PLESK 11.5 on Centos 6.5)
 
Thank you but neither of those helps.

The first of those links is for PLESK 9 the second is for PLESK 10. I am running PLESK 11.

My host says:

I did some digging and it looks like Postfix uses the bash variable TZ to govern its timestamps. It loads this on startup from /etc/sysconfig/clock.

[root@goofy1 ~]# postconf -d|grep TZ
export_environment = TZ MAIL_CONFIG LANG
import_environment = MAIL_CONFIG MAIL_DEBUG MAIL_LOGTAG TZ XAUTHORITY DISPLAY LANG=C


I believed this tied to:
[root@goofy1 ~]# cat /etc/sysconfig/clock
ZONE="America/Chicago"

I tried setting this to GMT however restarting the service seems insufficient.

To be honest, I don't much care about the timestamp on the maillog.

I am much more concerned that it is now 26 hours since I posted here about a time problem, and a scheduled DAILY backup controlled by PLESK still has not run.
 
The old 'turn it off and turn it back on again' solution. :)

Which is precisely what I did eventually. History was that host installed CentOS 6.5 on a new server, then PLESK 11.5, then I migrated all my domains over from another PLESK 11.5 install, and changed the system time (through PLESK).

At the end of that, the time was out of sync, and crond had stopped!
 
Back
Top