[SOLVED] Upgrade from 4.5.5 to 4.5.10 failed, but with no errors

I make this post, with the hope that if some one else has the same problems as I, then they need not waste a whole afternoon chasing it.

I have written it all up here on my blog:

Zimbra upgrade to 4.5.10; Major ldap problems

Was there any log information as to what exactly happened? Did you check the install log?

Yes, checked all the logs.

There was absolutely no errors indicated. Having upgraded a Zimbra installation before (4.5.x -2- 4.5.5) I assumed everything went perfectly.

Only when I tried to use it did I notice the errors popping up. The first sign was naturally I couldn't login with my accounts. Second it was receiving email for no one, bouncing them all.

I rebooted the machine and this is when the ldap errors regarding (can't be a master/replication) started to appear. At that point, my hunch that it was ldap related was confirmed.

So something did slip up in the upgrade process, and whatever it was, failed to produce an entry in the upgrade log file.

Has anyone else reported this issue? I've had to roll back to 4.5.6 after failed upgrade attempts with 4.5.7, 4.5.8, and 4.5.9. Reading that blog I'm now leery of trying 4.5.10. What happened to the upgrade processes that "just worked"? :)

Without logs, there's no way to tell. There are many number of things that can happen.

The most likely is that the VERY first install failed, and he tried repeatedly. The process got mixed up, and the installer did a fresh install.

This is illustrated by the fact he had to copy over localconfig.xml.
Since that file was gone, the installer couldn't connect to ldap, thus recreating the ldap.

Just a thought.

I think the solution for your problem is that you have to change the rights of sudoers.

So for me it helped to type the follwoing command when the starting of the SLAPD was giving an error:

chmod 0440 /etc/sudoers

After that I got the error message that the LDAP is running already - and the installation went trough without any problems. Yippieh.

This was happening on the test machine. Now I will do the migration on our produtional environment. So keep your fingers crossed.

BTW: I updated from 4.5.5 to 4.5.10.