Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 06-30-2008, 09:23 AM
Intermediate Member
 
Posts: 20
Default 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:

admin@xxx:/opt/zimbra/bin$ ps aux|grep zim
zimbra 1002 0.6 0.1 5372 2712 ? Ss 10:04 0:00 /usr/bin/perl /opt/zimbra/libexec/zmstatuslog
zimbra 1009 1.4 0.2 7004 4332 ? S 10:04 0:00 /usr/bin/perl /opt/zimbra/bin/zmcontrol status
zimbra 1105 0.0 0.0 0 0 ? Z 10:04 0:00 [cron]
zimbra 1150 5.0 0.0 4260 1692 ? S 10:04 0:00 sh -c /opt/zimbra/bin/zmstorectl status > /tmp/zmcontrol.status.7imNK 2> /tmp/zmcontrol.error.n0kmZ
zimbra 1151 8.0 0.0 4284 1776 ? R 10:04 0:00 /bin/bash /opt/zimbra/bin/zmstorectl status
admin 1157 0.0 0.0 2880 796 pts/0 R+ 10:04 0:00 grep zim
zimbra 1158 0.0 0.0 2376 412 ? R 10:04 0:00 /bin/bash /opt/zimbra/bin/mysqladmin status
admin@xxx:/opt/zimbra/bin$

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.

Cheers,
Steven White
Milwaukee Institute of Art & Design
__________________
Steven White
Zimbra 6.0.12 on CentOS 5.3 on Dell 1950
at Milwaukee Institute of Art & Design on Earth in Sol
Reply With Quote
  #2 (permalink)  
Old 07-01-2008, 08:47 AM
Former Zimbran
 
Posts: 5,606
Default

Hi Steven,
Hard to say. The logger can get a little skizo sometimes, and it's hard to tell what caused it. A fresh restart should cure what ails you. If you see it again, please post as many logs as you can.
Reply With Quote
  #3 (permalink)  
Old 07-01-2008, 09:26 AM
Intermediate Member
 
Posts: 20
Default

Thanks, the restart did bring things back for the admin account.

Next hurdle: migration from FirstClass 5 to Zimbra. I know there's a migration patht from FC8 but hopefully imapsync will be the only tool I need.
__________________
Steven White
Zimbra 6.0.12 on CentOS 5.3 on Dell 1950
at Milwaukee Institute of Art & Design on Earth in Sol
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.