Zimbra

jkoyle · #1 (**permalink**) 01-21-2008, 01:12 PM

I successfully updated our install this weekend from v4.5.9 32bit on RH4 to 64bit on RH5 (then to v5.0.1 NE) following the documentation here:

Network Edition: Moving from 32-bit to 64-bit Server - Zimbra :: Wiki

However, there's a couple of edits to that doc that should be made.

1 - Step 2a on the new server tells you to rm -rf /opt/zimbra/openldap-data/* . Don't do that - delete all contents except DB_CONFIG.

2 - This doc doesn't discuss migrating your postfix queue which should be copied over from /opt/zimbra/postfix/spool in step 5.

John

mmorse · #2 (**permalink**) 01-21-2008, 04:27 PM

Thanks, I've added your notes to the talk page

Talk:Network Edition: Moving from 32-bit to 64-bit Server - Zimbra :: Wiki

Hivos · #3 (**permalink**) 09-23-2010, 03:25 AM

We successfully completed the procedure for an Ubuntu 8.0.4 32b to Ubuntu 8.0.4 64b single server install last month.

However, I'm currently expanding our zimbra install to some of our other offices abroad. While installing a slave-ldap server I ran into a nasty certificate issue, which seems to have been caused by this procedure, which is not complete.

The issue is that when the 64b server is installed, new CA and certificates are created. However, when you restore the old LDAP, this contains the OLD CA (zmprov gacf) values. For a single server this is not an issue apparently. However when you try to install a new node, the CA is pulled from LDAP during installation, and therefore doesn't match with the CA in /opt/zimbra/conf/ca.

I guess, but I have not tried it yet (waiting for Zimbra Support advice), you can simply update the CA values in LDAP to fix this. Please verify and add this step to the procedure.

Hivos · #4 (**permalink**) 09-24-2010, 01:40 AM

I've manually updated the CA key and cert in LDAP with the following commands:

Code:

zmprov mcf zimbraCertAuthorityKeySelfSigned "`cat /opt/zimbra/conf/ca/ca.key`"
zmprov mcf zimbraCertAuthorityCertSelfSigned "`cat /opt/zimbra/conf/ca/ca.pem`"

And flush the config cache

Code:

zmprov fc config

mkuchin · #5 (**permalink**) 03-01-2011, 02:46 AM

Im successfully completed for an CentOS 5.4 32b OSS to CentOS 5.5 64b NE single server.

But when I have started the server there was a problem with the certificate in the administrative interface.
Has solved by means of start of following commands:

zmsshkeygen
zmupdateauthkeys

FriX · #6 (**permalink**) 10-15-2011, 02:38 AM

In the Server section / LDAP import you say

Step e. If this is an ldap master with replicas:

mkdir -p /opt/zimbra/data/ldap/accesslog/db /opt/zimbra/data/accesslog/logs

i think the latter one should be

/opt/zimbra/data/ldap/accesslog/logs

otherwise the migration fails with ldap not starting

Starting ldap...Done.
Failed.
Failed to start slapd. Attempting debug start to determine error.
bdb_db_close: database "cn=accesslog": txn_checkpoint failed: Invalid argument (22).
backend_startup_one (type=hdb, suffix="cn=accesslog"): bi_db_open failed! (-30974)
bdb_db_close: database "cn=accesslog": alock_close failed