LDAP Upgrade Failures

[Bharanisr]

Originally Posted by dmmincrjr

Zimbra failed to restart this morning after performing the backup. Here is the information from the freshclam.log file

--------------------------------------
ClamAV update process started at Thu Aug  6 05:00:28 2009
ERROR: Problem with internal logger (UpdateLogFile = /opt/zimbra/log/freshclam.log).
ERROR: /opt/zimbra/log/freshclam.log is locked by another process
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.95.1 Recommended version: 0.95.2
DON'T PANIC! Read Clam AntiVirus
Trying host db.us.clamav.net (168.143.19.95)...
Downloading main-51.cdiff [100%]
main.cld updated (version: 51, sigs: 545035, f-level: 42, builder: sven)
WARNING: getfile: daily-9214.cdiff not found on remote server (IP: 168.143.19.95)
WARNING: getpatch: Can't download daily-9214.cdiff from db.us.clamav.net
WARNING: getfile: daily-9214.cdiff not found on remote server (IP: 207.57.106.31)
WARNING: getpatch: Can't download daily-9214.cdiff from db.us.clamav.net
WARNING: getfile: daily-9214.cdiff not found on remote server (IP: 207.57.106.31)
WARNING: getpatch: Can't download daily-9214.cdiff from db.us.clamav.net
WARNING: Incremental update failed, trying to download daily.cvd
Trying host db.us.clamav.net (168.143.19.95)...
Downloading daily.cvd [100%]
daily.cvd updated (version: 9659, sigs: 63539, f-level: 43, builder: ccordes)
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Current functionality level = 42, recommended = 43
DON'T PANIC! Read Clam AntiVirus
Database updated (608574 signatures) from db.us.clamav.net (IP: 168.143.19.95)
WARNING: Clamd was NOT notified: Can't connect to clamd on localhost:3310
--------------------------------------
freshclam daemon 0.95.1-broken-compiler (OS: linux-gnu, ARCH: i386, CPU: i686)
ClamAV update process started at Thu Aug  6 05:05:17 2009
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.95.1 Recommended version: 0.95.2
DON'T PANIC! Read Clam AntiVirus
main.cld is up to date (version: 51, sigs: 545035, f-level: 42, builder: sven)
daily.cvd is up to date (version: 9659, sigs: 63539, f-level: 43, builder: ccordes)
--------------------------------------
Received signal: wake up
ClamAV update process started at Thu Aug  6 07:05:19 2009
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.95.1 Recommended version: 0.95.2
DON'T PANIC! Read Clam AntiVirus
main.cld is up to date (version: 51, sigs: 545035, f-level: 42, builder: sven)
daily.cvd is up to date (version: 9659, sigs: 63539, f-level: 43, builder: ccordes)
--------------------------------------

Here is my clamd.log at the time of the event

Sat Jul 25 05:00:42 2009 -> +++ Started at Sat Jul 25 05:00:42 2009
Sat Jul 25 05:00:42 2009 -> clamd daemon 0.95.1-broken-compiler (OS: linux-gnu, ARCH: i386, CPU: i686)
Sat Jul 25 05:00:42 2009 -> Log file size limited to 20971520 bytes.
Sat Jul 25 05:00:42 2009 -> Reading databases from /opt/zimbra/data/clamav/db
Sat Jul 25 05:00:42 2009 -> Not loading PUA signatures.
LibClamAV Warning: ***********************************************************
LibClamAV Warning: ***  This version of the ClamAV engine is outdated.     ***
LibClamAV Warning: *** DON'T PANIC! Read Clam AntiVirus ***
LibClamAV Warning: ***********************************************************
LibClamAV Error: cli_load(): Can't open file /opt/zimbra/data/clamav/db/main.cvd
Sat Jul 25 05:00:51 2009 -> ERROR: Can't open file or directory
ERROR: Can't open file or directory
Sat Jul 25 05:05:21 2009 -> +++ Started at Sat Jul 25 05:05:21 2009
Sat Jul 25 05:05:21 2009 -> clamd daemon 0.95.1-broken-compiler (OS: linux-gnu, ARCH: i386, CPU: i686)
Sat Jul 25 05:05:21 2009 -> Log file size limited to 20971520 bytes.
Sat Jul 25 05:05:21 2009 -> Reading databases from /opt/zimbra/data/clamav/db
Sat Jul 25 05:05:21 2009 -> Not loading PUA signatures.
LibClamAV Warning: ***********************************************************
LibClamAV Warning: ***  This version of the ClamAV engine is outdated.     ***
LibClamAV Warning: *** DON'T PANIC! Read Clam AntiVirus ***
LibClamAV Warning: ***********************************************************
Sat Jul 25 05:05:25 2009 -> Loaded 603148 signatures.
Sat Jul 25 05:05:25 2009 -> TCP: Bound to port 3310
Sat Jul 25 05:05:25 2009 -> TCP: Setting connection queue length to 15
Sat Jul 25 05:05:25 2009 -> Limits: Global size limit set to 921600000 bytes.
Sat Jul 25 05:05:25 2009 -> Limits: File size limit set to 921600000 bytes.
Sat Jul 25 05:05:25 2009 -> Limits: Recursion level limit set to 16.
Sat Jul 25 05:05:25 2009 -> Limits: Files limit set to 10000.
Sat Jul 25 05:05:25 2009 -> Archive support enabled.
Sat Jul 25 05:05:25 2009 -> Archive: Blocking encrypted archives.
Sat Jul 25 05:05:25 2009 -> Algorithmic detection enabled.
Sat Jul 25 05:05:25 2009 -> Portable Executable support enabled.
Sat Jul 25 05:05:25 2009 -> ELF support enabled.
Sat Jul 25 05:05:25 2009 -> Mail files support enabled.
Sat Jul 25 05:05:25 2009 -> OLE2 support enabled.
Sat Jul 25 05:05:25 2009 -> PDF support enabled.
Sat Jul 25 05:05:25 2009 -> HTML support enabled.
Sat Jul 25 05:05:25 2009 -> Self checking every 600 seconds.
Sat Jul 25 05:16:20 2009 -> No stats for Database check - forcing reload
Sat Jul 25 05:16:21 2009 -> Reading databases from /opt/zimbra/data/clamav/db
Sat Jul 25 05:16:23 2009 -> Database correctly reloaded (603148 signatures)

Please advise if information from any other log file is needed.

Recently i have migrated zimbra from 4.0.4 to 5.0.18 i am getting the following error.

Thanks in advance



Aug 26 18:03:04 s7solutions postfix/qmgr[2368]: 296B44F86FE: from=<zimbra@s7solutions.com>, size=285, nrcpt=1 (queue active)
Aug 26 18:03:04 s7solutions amavis[2375]: (02375-01) (!)connect_to_ldap: bind failed: LDAP_INVALID_CREDENTIALS
Aug 26 18:03:04 s7solutions amavis[2375]: (02375-01) (!!)TROUBLE in process_request: connect_to_ldap: bind failed at (eval 73) line 108, <DATA> line 633.
Aug 26 18:03:04 s7solutions amavis[2375]: (02375-01) (!)Requesting process rundown after fatal error
Aug 26 18:03:04 s7solutions amavis[2375]: (02375-01) extra modules loaded: /opt/zimbra/zimbramon/lib/x86_64-linux-thread-multi/auto/Net/SSLeay/autosplit.ix, /opt/zimbra/zimbramon/lib/x86_64-linux-thread-multi/auto/Net/SSLeay/randomize.al, IO/Socket/SSL.pm, Net/LDAP/Extension.pm, Net/SSLeay.pm
Aug 26 18:03:04 s7solutions postfix/smtp[8383]: 296B44F86FE: to=<bharani.sr@s7software.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=504, delays=504/0.01/0/0.07, dsn=4.3.2, status=deferred (host 127.0.0.1[127.0.0.1] said: 421 4.3.2 Service shutting down, closing channel (in reply to RCPT TO command))

[NoDoze]

What does the clamlog and freshclam logs have to do with ldap...? Those are two separate issues...

Do a search in here, there are many threads on how to update clamv....

concerning the ldap...looks like u have to re-authorize everything...?

[phoenix]

Originally Posted by Bharanisr

Recently i have migrated zimbra from 4.0.4 to 5.0.18 i am getting the following error.

How exactly did you do the migration?

[Bharanisr]

1. Before copying the mirror copy to the new environment install zimbra with ./install -s option (only software) after installation stop the service and remove the zimbra folder using (rm -rf /opt/zimbra/)

2 . Copy the mirror copy and install software using ./install -s option (which won't over write the existing configuration) once installed without errors stop and start the services and verify from the browser.

3. On the same environment migrated zimbra from 4.0.4v to 4.0.10v run ./install from 4.0.10 tar ball for upgradation (zimbra 4.0.10 v has a built in scripts which will upgrade schema level to 34)
create tar file (tar -cvf zimbra.tar zimbra)

3. On RHEL 4 32 bit install zimbra with ./install -s option (only software) and remove the zimbra folder using (rm -rf /opt/zimbra/) copy the zimbra tar file under /opt dir and untar it (tar -xvf zimbra.tar)
and install zimbra same version (4.0.10) using ,/intall -s option once installation done stop and start the zimbra services and verify from the browser..

4. Migrate from 4.0.10 v to 4.0.11v and then migrate to 5.0.2v. (using ./install option)

5. Migrate from 5.0.2 v to 5.0.18 (Schema Level 54)

6. Configure zimbra 5.0.18 on RHEL 5 64 bit ( Configure Bind, check for prerequisites and install zimbra using ./install)

Step 7
Moving Zimbra from 32-bit to 64-bit Server


Preparing the 32-bit Server

1. Block client access to the server's IP address with firewall rules.
2. Create an LDAP dump directory. As root, type mkdir /backup.
3. As root, type chown zimbra:zimbra /backup.
4. Backup the LDAP data, as zimbra, type /opt/zimbra/libexec/zmslapcat /backup
5. Stop the 32-bit server, type zmcontrol stop.
6. Change the hostname and IP address on the old server to something else. Do not turn off the server.


Preparing the 64-bit Server

1. Prepare the 64-bit server and install ZCS.

The ZCS installation on the new server must be configured exactly as the ZCS configuration on the original server. You go through the complete menu driven installation process, making changes to the configuration setting to match the settings on the original server.
a. Copy your ZCSLicense.xml file to a directory on the new server. You will not be able to complete the ZCS installation if the license is not on the new server.
b. Follow the directions in the ZCS single server installation guide to install ZCS. Make sure that you configure the same domain, hostname, passwords as on the old server. During ZCS install, the following settings must be changed to match the original server settings:

* Zimbra LDAP Server - For Domain to create - identify the same default domain as on the original server.
* Zimbra Mailbox Server - An administrator's account is automatically created.

* Make sure that the account name for Admin user to create is the same name as on the original server.
* Set the admin password.
* Change the Spam training user and the Non-spam (HAM) training user account names to be the same as the spam account names on the original server.
* Global Document Account - This account name is automatically generated. Change the Global Document Account name to be the same account name as on the original server.

* Change any other settings on the new server to match the configuration on the original server.

ZCS is installed. To continue:

1. Stop the ZCS services, type zmcontrol stop.

2. Restore the LDAP data to the 64-bit server. As zimbra, type

a. rm -rf /opt/zimbra/openldap-data/*
b. Copy the file /opt/zimbra/openldap-data/DB_CONFIG from the 32-bit server to /opt/zimbra/openldap-data/ on the 64-bit server. Note: If this file does not exist, or is empty, creating it may improve ldap performance; see the Performance Tuning Guide for more information.
c. Create the necessary directory structure. Type mkdir -p /opt/zimbra/openldap-data/logs /opt/zimbra/openldap-data/accesslog/db /opt/zimbra/openldap-data/accesslog/logs Type chown -R zimbra:zimbra /opt/zimbra/openldap-data
d. Copy from the 32-bit server to the 64-bit server the /backup/ldap.bak file. Type /opt/zimbra/openldap/sbin/slapadd -q -b "" -f /opt/zimbra/conf/slapd.conf -cv -l /backup/ldap.bak

3. Edit /opt/zimbra/conf/localconfig.xml to update the zimbra_mysql_password, mysql_root_password, zimbra_ldap_password and the ldap_root_password values to the values from the localconfig.xml file
on the 32-bit server.

4. Delete the MySQL data on the 64-bit server and copy the MySQL data from the 32-bit server.

a. Type rm -rf /opt/zimbra/db/data/*
b. Copy the /opt/zimbra/db/data/*
from the 32-bit server to the 64-bit server.


5. Copy the following files from the 32-bit server to the 64-bit server

* /opt/zimbra/store/*
* /opt/zimbra/index/*

# As root, run /opt/zimbra/libexec/zmfixperms to repair any potential permissions problems with files under /opt/zimbra.
# Start ZCS, type zmcontrol start.

[Bharanisr]

Thanks for the quick reply,

followed the below procedure.

1. Before copying the mirror copy to the new environment install zimbra with ./install -s option (only software) after installation stop the service and remove the zimbra folder using (rm -rf /opt/zimbra/)

2 . Copy the mirror copy and install software using ./install -s option (which won't over write the existing configuration) once installed without errors stop and start the services and verify from the browser.

3. On the same environment migrated zimbra from 4.0.4v to 4.0.10v run ./install from 4.0.10 tar ball for upgradation (zimbra 4.0.10 v has a built in scripts which will upgrade schema level to 34)
create tar file (tar -cvf zimbra.tar zimbra)

3. On RHEL 4 32 bit install zimbra with ./install -s option (only software) and remove the zimbra folder using (rm -rf /opt/zimbra/) copy the zimbra tar file under /opt dir and untar it (tar -xvf zimbra.tar)
and install zimbra same version (4.0.10) using ,/intall -s option once installation done stop and start the zimbra services and verify from the browser..

4. Migrate from 4.0.10 v to 4.0.11v and then migrate to 5.0.2v. (using ./install option)

5. Migrate from 5.0.2 v to 5.0.18 (Schema Level 54)

6. Configure zimbra 5.0.18 on RHEL 5 64 bit ( Configure Bind, check for prerequisites and install zimbra using ./install)

Step 7
Moving Zimbra from 32-bit to 64-bit Server


Preparing the 32-bit Server

1. Block client access to the server's IP address with firewall rules.
2. Create an LDAP dump directory. As root, type mkdir /backup.
3. As root, type chown zimbra:zimbra /backup.
4. Backup the LDAP data, as zimbra, type /opt/zimbra/libexec/zmslapcat /backup
5. Stop the 32-bit server, type zmcontrol stop.
6. Change the hostname and IP address on the old server to something else. Do not turn off the server.


Preparing the 64-bit Server

1. Prepare the 64-bit server and install ZCS.

The ZCS installation on the new server must be configured exactly as the ZCS configuration on the original server. You go through the complete menu driven installation process, making changes to the configuration setting to match the settings on the original server.
a. Copy your ZCSLicense.xml file to a directory on the new server. You will not be able to complete the ZCS installation if the license is not on the new server.
b. Follow the directions in the ZCS single server installation guide to install ZCS. Make sure that you configure the same domain, hostname, passwords as on the old server. During ZCS install, the following settings must be changed to match the original server settings:

* Zimbra LDAP Server - For Domain to create - identify the same default domain as on the original server.
* Zimbra Mailbox Server - An administrator's account is automatically created.

* Make sure that the account name for Admin user to create is the same name as on the original server.
* Set the admin password.
* Change the Spam training user and the Non-spam (HAM) training user account names to be the same as the spam account names on the original server.
* Global Document Account - This account name is automatically generated. Change the Global Document Account name to be the same account name as on the original server.

* Change any other settings on the new server to match the configuration on the original server.

ZCS is installed. To continue:

1. Stop the ZCS services, type zmcontrol stop.

2. Restore the LDAP data to the 64-bit server. As zimbra, type

a. rm -rf /opt/zimbra/openldap-data/*
b. Copy the file /opt/zimbra/openldap-data/DB_CONFIG from the 32-bit server to /opt/zimbra/openldap-data/ on the 64-bit server. Note: If this file does not exist, or is empty, creating it may improve ldap performance; see the Performance Tuning Guide for more information.
c. Create the necessary directory structure. Type mkdir -p /opt/zimbra/openldap-data/logs /opt/zimbra/openldap-data/accesslog/db /opt/zimbra/openldap-data/accesslog/logs Type chown -R zimbra:zimbra /opt/zimbra/openldap-data
d. Copy from the 32-bit server to the 64-bit server the /backup/ldap.bak file. Type /opt/zimbra/openldap/sbin/slapadd -q -b "" -f /opt/zimbra/conf/slapd.conf -cv -l /backup/ldap.bak

3. Edit /opt/zimbra/conf/localconfig.xml to update the zimbra_mysql_password, mysql_root_password, zimbra_ldap_password and the ldap_root_password values to the values from the localconfig.xml file
on the 32-bit server.

4. Delete the MySQL data on the 64-bit server and copy the MySQL data from the 32-bit server.

a. Type rm -rf /opt/zimbra/db/data/*
b. Copy the /opt/zimbra/db/data/*
from the 32-bit server to the 64-bit server.


5. Copy the following files from the 32-bit server to the 64-bit server

* /opt/zimbra/store/*
* /opt/zimbra/index/*

# As root, run /opt/zimbra/libexec/zmfixperms to repair any potential permissions problems with files under /opt/zimbra.
# Start ZCS, type zmcontrol start.