Zimbra mail server zmmtaconfig error

tezarin · 01-13-2012, 01:16 PM

Hi all,

I've noticed my Zimbra mail server will be accessible at 7:15 ish every morning. It goes down sometimes at night (due to bacula backup process) but the backup process ends around 5 AM so I am not sure why the mail server stays down for two three hours after the backup process ended. This is the log I found on the mail server, could you please help me with this problem?

Thanks in advance

Code:

Jan 13 07:15:18 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping Global system configuration update. 
Jan 13 07:15:18 mail zimbramon[31338]: 31338:info: zmmtaconfig: gacf ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
Jan 13 07:15:19 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All Reverse Proxy URLs update. 
Jan 13 07:15:19 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllReverseProxyURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
Jan 13 07:15:19 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All Reverse Proxy Backends update. 
Jan 13 07:15:19 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllReverseProxyBackends ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
Jan 13 07:15:20 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All Memcached Servers update. 
Jan 13 07:15:20 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllMemcachedServers ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
Jan 13 07:15:21 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All MTA Authentication Target URLs update. 
Jan 13 07:15:21 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllMtaAuthURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
Jan 13 07:15:21 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping Configuration for server gauss.domain.com update. 
Jan 13 07:15:21 mail zimbramon[31338]: 31338:info: zmmtaconfig: gs:gauss.domain.com ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
Jan 13 07:15:21 mail zimbramon[31338]: 31338:info: zmmtaconfig: Sleeping...Key lookup failed. 
Jan 13 07:15:26 mail zimbramon[6828]: 6828:info: Starting services initiated by zmcontrol 
Jan 13 07:15:27 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping Global system configuration update. 
Jan 13 07:15:27 mail zimbramon[31338]: 31338:info: zmmtaconfig: gacf ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
Jan 13 07:15:28 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All Reverse Proxy URLs update. 
Jan 13 07:15:28 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllReverseProxyURLs ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
Jan 13 07:15:28 mail slapd[7019]: @(#) $OpenLDAP: slapd 2.3.42 (May 29 2008 13:41:01) $ 	build@build11:/home/build/p4/main/ThirdParty/openldap/openldap-2.3.42.6z/servers/slapd 
Jan 13 07:15:28 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping All Reverse Proxy Backends update. 
Jan 13 07:15:28 mail zimbramon[31338]: 31338:info: zmmtaconfig: Skipping getAllReverseProxyBackends ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: javax.naming.CommunicationException gauss.domain.com:389)  
Jan 13 07:15:29 mail slapd[7131]: slapd starting 
Jan 13 07:15:33 mail zimbramon[31338]: 31338:info: zmmtaconfig: Sleeping...Key lookup failed. 
Jan 13 07:15:35 mail zimbramon[6828]: 6828:info: Rewriting configs  antispam amavis antivirus amavis imapproxy   webxml mailbox amavis antispam antivirus mta sasl    
Jan 13 07:15:47 mail zimbramon[6828]: 6828:info: Starting logger via zmcontrol 
Jan 13 07:15:47 mail zimbramon[6828]: 6828:info: Starting mailbox via zmcontrol 
Jan 13 07:15:48 mail zimbramon[8086]: 8086:info: zmmtaconfig: zmmtaconfig already running at 31338 
Jan 13 07:16:09 mail zmmailboxdmgr[9041]: status requested
Jan 13 07:16:09 mail zmmailboxdmgr[9041]: file /opt/zimbra/log/zmmailboxd_manager.pid does not exist
Jan 13 07:16:09 mail zmmailboxdmgr[9041]: assuming no other instance is running
Jan 13 07:16:09 mail zmmailboxdmgr[9041]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Jan 13 07:16:09 mail zmmailboxdmgr[9041]: assuming no other instance is running
Jan 13 07:16:09 mail zmmailboxdmgr[9041]: no manager process is running
Jan 13 07:16:09 mail zmmailboxdmgr[9048]: start requested
Jan 13 07:16:09 mail zmmailboxdmgr[9048]: checking if another instance of manager is already running
Jan 13 07:16:09 mail zmmailboxdmgr[9048]: file /opt/zimbra/log/zmmailboxd_manager.pid does not exist
Jan 13 07:16:09 mail zmmailboxdmgr[9048]: assuming no other instance is running
Jan 13 07:16:09 mail zmmailboxdmgr[9048]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Jan 13 07:16:09 mail zmmailboxdmgr[9048]: assuming no other instance is running
Jan 13 07:16:09 mail zimbramon[6828]: 6828:info: Starting imapproxy via zmcontrol 
Jan 13 07:16:09 mail zmmailboxdmgr[9049]: wrote manager pid 9049 to /opt/zimbra/log/zmmailboxd_manager.pid
Jan 13 07:16:09 mail zmmailboxdmgr[9049]: manager started mailboxd/JVM with pid 9052
Jan 13 07:16:09 mail zmmailboxdmgr[9052]: wrote java pid 9052 to /opt/zimbra/log/zmmailboxd_java.pid
Jan 13 07:16:10 mail zimbramon[6828]: 6828:info: Starting antispam via zmcontrol 
Jan 13 07:16:11 mail zimbramon[9106]: 9106:info: zmmtaconfig: zmmtaconfig already running at 31338 
Jan 13 07:16:13 mail amavis[9170]: starting.  /opt/zimbra/amavisd/sbin/amavisd at gauss.domain.com amavisd-new-2.5.4 (20080312), Unicode aware, LANG="en_US.UTF-8"
Jan 13 07:16:13 mail amavis[9170]: user=500, EUID: 500 (500);  group=, EGID: 500 501 500 5 4 (500 501 500 5 4)
Jan 13 07:16:13 mail amavis[9170]: Perl version               5.008008
Jan 13 07:16:16 mail amavis[9170]: SpamControl: init_pre_chroot done
Jan 13 07:16:16 mail amavis[9186]: Net::Server: Process Backgrounded
Jan 13 07:16:16 mail amavis[9186]: Net::Server: 2012/01/13-07:16:16 Amavis (type Net::Server::PreForkSimple) starting! pid(9186)
Jan 13 07:16:16 mail amavis[9186]: Net::Server: Binding to UNIX socket file /opt/zimbra/data/amavisd/amavisd.sock using SOCK_STREAM
Jan 13 07:16:16 mail zimbramon[6828]: 6828:info: Starting antivirus via zmcontrol 
Jan 13 07:16:16 mail amavis[9186]: Net::Server: Binding to TCP port 10024 on host 127.0.0.1

eco · 01-16-2012, 02:31 AM

You might be better off posting on a zimbra forum.

You might also want to review their wiki on how to backup your ZCS OS. I also take the server down to back up the files but it only takes me 5 minutest for the rsync to copy the latest files. Then I backup the synced folder.

You should maybe have a look at your backup logs or have a cron that reports the status of 'zmcontrol status' so you get a clearer picture of what is down and when. Could the monitoring process be down rather than all the zimbra processes?

Sorry I can't be of more help.

tezarin · 01-25-2012, 09:14 AM

Thank you for your reply and sorry it took me so long to report back.

Are you saying that you use rsync to backup your Zimbra server? What directories do you get a backup of? Only the /opt directory?

Thanks

eco · 01-26-2012, 02:21 AM

Yup, I rsync /opt/zimbra to /opt/backup, then backup /opt/backup.

This wiki page will help you get started:
http://wiki.zimbra.com/wiki/Open_Sou...ckup_Procedure

I have been using a variation of the following script for zimbra 7.1.1 and did a test restore which was successful.
http://wiki.zimbra.com/wiki/Open_Sou..._Script_Method

I'd recommend you try a restore of the system once your backup is in place. It helped me sleep better at night

tezarin · 01-26-2012, 08:00 AM

eco, Thanks for your reply. Will look at it.

Do you happen to have your rsync manual handy? Also, what procedure do you use to back up the /opt/backup?

eco · 01-27-2012, 01:42 AM

Quote:

Originally Posted by tezarin

eco, Thanks for your reply. Will look at it.

Do you happen to have your rsync manual handy? Also, what procedure do you use to back up the /opt/backup?

A "man rsync" should give you all the info you need. You should however find all you need to get started in the scripts.

I use my own off-site backup to transfer the data but you could use rsync/scp and any other tool to get your backup of the server. I believe the script provides a solution for that.