Threaded View

Date/time update killed admin account access

Folks,

I completed installation of Zimbra 5.0.6 on Ubuntu 6.06 last Friday. I successfully batch-created 200+ user accounts and ran a successful LDAP test against my OS/X Open Directory. I'm currently still in pre-production.

Over the weekend I noticed the date/time was *way* off and decided to wait to update it until I came in this morning. I ran the date command at the CLI which fixed the date/time. But at that point I could no longer login as admin via the web I/F either at the user login page or the administrative login page.

After restarting the entire Zimbra suite the problem disappeared.

The error in date/time was significant; it was over 48 hours in the future. One thing I noticed while shutting down Zimbra was the logger refused to stop. After waiting a few minutes I stopped it with a 'kill -9 PID' command and before it died a number of Zimbra processes fired up, ran for <3 secs. and stopped when the logger had stopped.

Here is the output of a process list after initiating the kill command:

Is it simply the date/time inaccuracy that locked something up that caused the admin access to be unusable? Was this a coincidence with something else that was repaired with a restart? I could understand logger becoming confused but why would this break admin web access? Or am I just (un)lucky?

Please let me know what you think. I'm moving closer to production, possibly by the end of this week.