BlueDragon Launch Date
Get reminded of when BlueDragon Open Source becomes available.
 |
| Subscribe to Open BlueDragon |
| Visit this group |
Alert Email
Get a short email alert whenever a new entry is published.
Confidential, secure it's piece of cake to keep uptodate.
Latest Articles:
Collection of blogs I follow
Zimbra upgrade to 4.5.10; Major ldap problems
We have been running with Zimbra 4.5.5 for some time now, with no problems. The system is running on a Dell server, Fedora 4. Apart from a little hiccup last summer, you can pretty much forget about it.
With version 4.5.10 now released, it was worth looking at upgrading. Since one of our users couldn't access their email via their Nokia handset, and it was confirmed with this bug 21313, now seemed a good time as any to upgrade.
Looking around all the documentation prior to doing this, no major problems was reported. Infact, great play was made at how easy the upgrade process was going to be. Keeping all existing users and mailboxes without any fear of loss. Well, just incase, i made a complete directory backup of /opt/zimbra/ before entrusting the upgrade script.
That was a decision that proved to be my savior.
I shutdown all the services and made sure no processes were running. Next I ran the upgrade script and it took only about 20 minutes, and it was completed. No errors were reported on the console or the upgrade log.
With all services running, everything looked fine, so I logged in. Failed. My heart sunk; all my users had been lost. A quick look at mysql, I confirmed all the users were there. However, I couldn't login in with my admin or personal accounts. That pointed to an ldap problem.
A very handy utility that I found was zmprov. Login as 'zimbra' and run that command. You will then be kicked into a shell, to which you type gaa. This should list all the users you have on your system. If it doesn't then you have a problem with ldap.
To restore the ldap database I performed the following:
- Shutdown all the zimbra services; killing them manually if need be
- Restored the file /opt/zimbra/conf/localconfig.xml from my shadow backup directory
- Deleted everything in the /opt/zimbra/openldap-data/ directory
- Restored that directory from the shadow backup
- Restart zimbra
After doing all that, everything burst into life. The server began accepting email again and users could log back in again. All was well in the world again.
The moral of the tale; make sure you do a backup, you just never know when you will need it!
Related Stories
- Just who is using the Sender Policy Framework (SPF) for determining the origins of email?
- Yahoo! will acquire Zimbra for approximately $350M
- Does software date? Of course not, and don't let them tell you differently
Comments (6)
Hi Alan,
I too am running FC4 with Zimbra 4.5.5. I am trying to move the install to another server (in effect an Upgrade) and I get an LDAP error. Does the error at: http://www.zimbra.com/forums/installation/13439-moving-new-server-error-help.html Look at all like the issues you might have been getting? Quanah mentions LDAP issues with Zimbra editions before 4.5.7 (my case) so I'm wondering if these issues could be related. Thanks, RobHi Alan, had a quick look at bug 21313 & its still UNCONFIRMED your blog says it confirmed - (sorry to be pedantic). Looking a the zimbra forums it seem like other also have problems upgrading to 4.5.10
Unfortunately, there's no way to know what triggered the issue you had, but having to wipe out the data and reload it is always the last resort. There are often easier and better ways to get OpenLDAP happy again. There were a number of bugs that specifically affected Zimbra in the releases prior to 4.5.7, and you very well may have hit one that'd been sitting unnoticed until the upgrade was run. ;)
Sure thing John, I have sent them in a separate email.
I hope you get something out of it. While our setup isn't a huge user base compared to some, it may serve to help others.Hi Alan, This is John from Zimbra.
Can we get a copy of your setup logs to be able to look through them to see what happened? Feel free to send them to my e-mail. The logs that would be useful would be: install.log.xxxx (where xxxx is the pid of the install instance) zmsetup.log .install_history.log (in /opt/zimbra) Thanks, and great post! -john
I also had the same issue. upgraded and could not log in. gaaa nothing. Followed the same steps here and all is well.
Thanks