
Originally Posted by
leog21
Hi,
Thank you for your reply.
Zimbra support director was paged, someone somewhere cleared the mail box and I was able to get in touch with support and fix the issue after 2hrs of uncertainty. I have to say it was a VERY scary two hours when you have a production system down and the people who are supporting you are absent.
Thankfully, the CSR manager at VMWare Tania L. who went above and beyond the call of duty, cut through corporate red tape to reach out other support divisoins inside the VMWARE family and was able to reach the right people and get this sorted out. I advise everyone to call VMWARE if you find Zimbra support to be down and have them page the right people.
Also to help future users, I was getting a " Starting ldap...failed with exit code: 256." when updating zimbra from 5.0.16GA to 6.0.10GA.
Installing LDAP configuration database...done.
Upgrading from 5.0.16_GA_2921 to 6.0.10_GA_2692
Stopping zimbra services...done.
Verifying /opt/zimbra/conf/my.cnf
Starting mysql...done.
This appears to be 5.0.16_GA
Installing LDAP configuration database...done.
Migrating ldap data...done.
Checking ldap status...not running.
Running zmldapapplyldif...failed.
Checking ldap status...not running.
Starting ldap...failed with exit code: 256.
UPGRADE FAILED - exiti ng.
The issue was because I had updated one of the required packages sudo that the updater checks for before the install. If you update sudo, you also need to update a package called audit or else LDAP will not work!
Zimbra tech support made a note to have the installer check for the audit version as a prerequisite to the installed packages before an update is kickstarted.
What a night! I'm going to get a drink.