Difference between revisions of "Troubleshooting zimbra issues"
m |
m |
||
| Line 4: | Line 4: | ||
==ldap fails to start== | ==ldap fails to start== | ||
If ldap server does not starts and gives this error | |||
<pre> | |||
Failed to start slapd. Attempting debug start to determine error. | |||
bdb_db_close: database "": txn_checkpoint failed: Invalid argument (22). | |||
backend_startup_one (type=hdb, suffix=""): bi_db_open failed! (22) | |||
bdb_db_close: database "": alock_close failed | |||
</pre> | |||
First verify that domain to IP mapping in /etc/hosts file is correct. If domain to IP mapping in /etc/hosts is not correct then Zimbra will not be able to start listening socket on incorrect IP and hence ldap may fail to start. Also zimbra must be stopped before changing machine IP. Then IP should be changed on system and in /etc/hosts. Then zimbra should be started. | |||
If problem is not due to incorrect IP then: | |||
#Login as root | |||
#Go to dir '<tt>/opt/zimbra/data/ldap/hdb/db</tt>' | |||
#Use command '<tt>/opt/zimbra/bdb/bin/db_recover</tt>' | |||
| Line 22: | Line 34: | ||
'''The same steps can be used for upgrading Zimbra to a higher version also''' | '''The same steps can be used for upgrading Zimbra to a higher version also''' | ||
==Fixing permisssions on zimbra files== | |||
If permissions on zimbra directory could be wrong then following can be use to fix permissions: | |||
<pre> | |||
chown -R zimbra:zimbra /opt/zimbra | |||
/opt/zimbra/libexec/zmfixperms -verbose -extended | |||
</pre> | |||
<yambe:breadcrumb>Zimbra server configuration|Zimbra</yambe:breadcrumb> | |||
Revision as of 11:46, 13 February 2016
<yambe:breadcrumb>Zimbra server configuration|Zimbra</yambe:breadcrumb>
Troubleshooting zimbra issues
ldap fails to start
If ldap server does not starts and gives this error
Failed to start slapd. Attempting debug start to determine error. bdb_db_close: database "": txn_checkpoint failed: Invalid argument (22). backend_startup_one (type=hdb, suffix=""): bi_db_open failed! (22) bdb_db_close: database "": alock_close failed
First verify that domain to IP mapping in /etc/hosts file is correct. If domain to IP mapping in /etc/hosts is not correct then Zimbra will not be able to start listening socket on incorrect IP and hence ldap may fail to start. Also zimbra must be stopped before changing machine IP. Then IP should be changed on system and in /etc/hosts. Then zimbra should be started.
If problem is not due to incorrect IP then:
- Login as root
- Go to dir '/opt/zimbra/data/ldap/hdb/db'
- Use command '/opt/zimbra/bdb/bin/db_recover'
Complete reinstallation without affecting data
If Zimbra stops working and normal troubleshooting is not working, then we can reinstall zimbra without affecting data using following steps:
- Download the same version of zimbra and extract the contents.
- Run './install.sh -s --platform-override' . The '-s' option is used to reinstall zimbra without touching the data.
- Then run '/opt/zimbra/libexec/zmsetup.pl' script as root to re-initialize the ldap and other settings.
- If permissions could be incorrect then they can be fixed using
- chown -R zimbra:zimbra /opt/zimbra
- /opt/zimbra/libexec/zmfixperms -verbose -extended
The same steps can be used for upgrading Zimbra to a higher version also
Fixing permisssions on zimbra files
If permissions on zimbra directory could be wrong then following can be use to fix permissions:
chown -R zimbra:zimbra /opt/zimbra /opt/zimbra/libexec/zmfixperms -verbose -extended
<yambe:breadcrumb>Zimbra server configuration|Zimbra</yambe:breadcrumb>
