problems with zimbra restar after backup

[S.Lord]

Hi!!

I have zimbra v 6.0.3 running for over a year, but lately every night after my backup process finishes my zimbra doesn't restart. I've been solving lot of problems lately due to clamd corrupted bd or disck space problems for my backup files; after resolving those issues, my zimbra keeps on no restarting every night after backup process, whats more every morning after we try to restart manually with zmcontrol start, altough it seems like everything runs properly, once we try to acces by web there is no acces; then we have to restart the server and start zimbra services manually with zmcontrol start, and everything works out perfectly until night comes and the backup process begins again, once it finishes we have the next error log:

Oct 27 01:27:03 tierra backup-manager[23160]: debug * DEBUG: Running post-command
Oct 27 01:27:03 tierra backup-manager[23160]: debug * DEBUG: exec_post_command()
Oct 27 01:27:03 tierra backup-manager[23160]: debug * DEBUG: Releasing lock
Oct 27 01:27:03 tierra backup-manager[23160]: debug * DEBUG: release_lock()
Oct 27 01:27:03 tierra backup-manager[23160]: debug * DEBUG: Exiting
Oct 27 01:27:34 tierra zimbramon[26841]: 26841:info: zmmtaconfig: zmmtaconfig started on tierra.abc.gob.bo with loglevel=3 pid=26841
Oct 27 01:27:36 tierra zimbramon[26841]: 26841:info: zmmtaconfig: Skipping Global system configuration update.
Oct 27 01:27:36 tierra zimbramon[26841]: 26841:info: zmmtaconfig: gacf ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException tierra.abc.gob.bo:389)
Oct 27 01:27:38 tierra zimbramon[26841]: 26841:info: zmmtaconfig: Skipping All Reverse Proxy URLs update.
Oct 27 01:27:38 tierra zimbramon[26841]: 26841:info: zmmtaconfig: Skipping getAllReverseProxyURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException tierra.abc.gob.bo:389)
Oct 27 01:27:41 tierra zimbramon[26841]: 26841:info: zmmtaconfig: Skipping All Reverse Proxy Backends update.
Oct 27 01:27:41 tierra zimbramon[26841]: 26841:info: zmmtaconfig: Skipping getAllReverseProxyBackends ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException tierra.abc.gob.bo:389)
Oct 27 01:27:43 tierra zimbramon[26841]: 26841:info: zmmtaconfig: Skipping All Memcached Servers update.
Oct 27 01:27:43 tierra zimbramon[26841]: 26841:info: zmmtaconfig: Skipping getAllMemcachedServers ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException tierra.abc.gob.bo:389)
Oct 27 01:27:45 tierra zimbramon[26841]: 26841:info: zmmtaconfig: Skipping All MTA Authentication Target URLs update.
Oct 27 01:27:45 tierra zimbramon[26841]: 26841:info: zmmtaconfig: Skipping getAllMtaAuthURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException tierra.abc.gob.bo:389)
Oct 27 01:27:47 tierra zimbramon[26841]: 26841:info: zmmtaconfig: Skipping Configuration for server tierra.abc.gob.bo update.
Oct 27 01:27:47 tierra zimbramon[26841]: 26841:info: zmmtaconfig: gs:tierra.abc.gob.bo ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException tierra.abc.gob.bo:389)
Oct 27 01:27:47 tierra zimbramon[26841]: 26841:info: zmmtaconfig: Sleeping...Key lookup failed.

While making the back up there is just one problemM; after that everything is ok, the problem is:

Oct 27 01:25:32 tierra /opt/respaldar_zimbra/backup_zimbra.sh: creating a LV called zimbra.snapshot
Oct 27 01:25:32 tierra /opt/respaldar_zimbra/backup_zimbra.sh: creating a LV called zimbra.snapshot
Oct 27 01:25:33 tierra /opt/respaldar_zimbra/backup_zimbra.sh: error creating snapshot, exiting
Oct 27 01:25:33 tierra /opt/respaldar_zimbra/backup_zimbra.sh: error creating snapshot, exiting
Oct 27 01:25:33 tierra backup-manager[23160]: debug * DEBUG: Sanitizing the configuration file.

Another problem is that I have not installed zimbra, and the person who did it no longer works here, so I'm almost new to Zimbra world, linux and all the configuration left for this server...

I hope you can help me, although every one is working just fine with e-mail services, is annoying to restart the server and services every morning...

[phoenix]

Did you try some of the solutions found in a forum search: site:zimbra.com +"cause: javax.naming.CommunicationException" - Yahoo! Search Results

[S.Lord]

I've tried but the problem still remains I have seen another possible problem, but the solutions listed didn't work, I'm fearing that mi corrupted ldap bd and little solution dind't work well... Let me discribe the problem I had and how I resolved. Around two weeks ago my ldap bd was corrupted tried to make a recovery action with methoods shown in other posts but eventhough the db was corrupted, so I found an old backup of my ldap db (almost 1 year ago) replace it, then restart zmcontrol and finally al my problems seem to be solved, now the syslog has the next register:

Oct 27 01:25:27 tierra zimbramon[22734]: 22734:info: Stopping ldap via zmcontrol
Oct 27 01:25:27 tierra slapd[2963]: daemon: shutdown requested and initiated.
Oct 27 01:25:27 tierra slapd[2963]: slapd shutdown: waiting for 0 operations/tasks to finish
Oct 27 01:25:27 tierra slapd[2963]: bdb(cn=accesslog): PANIC: fatal region error detected; run recovery
Oct 27 01:25:27 tierra last message repeated 8 times
Oct 27 01:25:27 tierra slapd[2963]: bdb_db_close: database "cn=accesslog": txn_checkpoint failed: DB_RUNRECOVERY: Fatal error, run database recovery (-30974)
.
Oct 27 01:25:27 tierra slapd[2963]: bdb(cn=accesslog): File handles still open at environment close
Oct 27 01:25:27 tierra slapd[2963]: bdb(cn=accesslog): Open file handle: /opt/zimbra/data/ldap/accesslog/db/id2entry.bdb
Oct 27 01:25:27 tierra slapd[2963]: bdb(cn=accesslog): Open file handle: /opt/zimbra/data/ldap/accesslog/db/dn2id.bdb
Oct 27 01:25:27 tierra slapd[2963]: bdb(cn=accesslog): Open file handle: /opt/zimbra/data/ldap/accesslog/db/objectClass.bdb
Oct 27 01:25:27 tierra slapd[2963]: bdb(cn=accesslog): Open file handle: /opt/zimbra/data/ldap/accesslog/logs/log.0000000033
Oct 27 01:25:27 tierra slapd[2963]: bdb(cn=accesslog): PANIC: fatal region error detected; run recovery
Oct 27 01:25:27 tierra slapd[2963]: bdb_db_close: database "cn=accesslog": close failed: DB_RUNRECOVERY: Fatal error, run database recovery (-30974)
Oct 27 01:25:27 tierra slapd[2963]: slapd stopped.
Oct 27 01:25:32 tierra /opt/respaldar_zimbra/backup_zimbra.sh: creating a LV called zimbra.snapshot
Oct 27 01:25:32 tierra /opt/respaldar_zimbra/backup_zimbra.sh: creating a LV called zimbra.snapshot
Oct 27 01:25:33 tierra /opt/respaldar_zimbra/backup_zimbra.sh: error creating snapshot, exiting
Oct 27 01:25:33 tierra /opt/respaldar_zimbra/backup_zimbra.sh: error creating snapshot, exiting
Oct 27 01:25:33 tierra backup-manager[23160]: debug * DEBUG: Sanitizing the configuration file.
Oct 27 01:25:33 tierra backup-manager[23160]: debug * DEBUG: replace_deprecated_booleans()

Well I suppose that's the problem, but I tried before to recover the DB and nothing happened, I'm worried because if my ldap is corrupted and I can't recover it, then I had to re instal my BD... I hope not

[dalmate]

Can you run Nmap (if you did not installed it, please installe it) and print ít output here, maybe your ldap server did not run

[S.Lord]

I'm not familiarize with nmap, although it's installed, anyway I've run it and the results are:

Starting Nmap 4.62 ( Nmap - Free Security Scanner For Network Exploration & Security Audits. ) at 2011-11-03 08:46 BOT
Interesting ports on tierra.abc.gob.bo (192.168.4.10):
Not shown: 1704 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
80/tcp open http
110/tcp open pop3
143/tcp open imap
389/tcp open ldap
443/tcp open https
465/tcp open smtps
587/tcp open submission
993/tcp open imaps
995/tcp open pop3s

Nmap done: 1 IP address (1 host up) scanned in 0.089 seconds

It looks like my ldap is running normally