Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 02-13-2009, 01:02 AM
Intermediate Member
 
Posts: 21
Default [SOLVED] zmmtaconfigctl not running after upgrade to 5.0.13

After upgrading from 5.0.11 to 5.0.13 on Ubuntu 8.04 zmmtaconfigctl will not start which results in many of the services, including the mailbox and mta, not running.

Code:
zimbra@ml:~$ zmcontrol start
Host ml.example.com
        Starting ldap...Done.
        Starting logger...Done.
        Starting mailbox...FAILED
Starting zmmtaconfig...failed.
Starting mysqld...done.
Starting mailboxd...done.


        Starting antispam...Done.
        Starting antivirus...Done.
        Starting snmp...Done.
        Starting spell...Done.
        Starting mta...FAILED
Starting zmmtaconfig...failed.
zmmtaconfigctl failed to start
Starting saslauthd...done.


        Starting stats...Done.
The log for zmmtaconfigctl is:
Code:
Fri Feb 13 02:09:19 2009  zmmtaconfig already running at 
Fri Feb 13 02:11:31 2009  zmmtaconfig already running at 
Fri Feb 13 02:12:15 2009  zmmtaconfig already running at 
Fri Feb 13 02:13:03 2009  zmmtaconfig already running at 
Fri Feb 13 02:39:36 2009  zmmtaconfig already running at 
Fri Feb 13 02:41:25 2009  zmmtaconfig already running at 
Fri Feb 13 02:42:02 2009  zmmtaconfig already running at
There isn't any instance of it actually starting though.

There is also an error shown in zimbra.log for sshd:

Code:
Feb 13 00:53:38 ml sshd[5430]: Received SIGHUP; restarting.
Feb 13 00:53:38 ml sshd[27519]: Server listening on :: port 22.
Feb 13 00:53:38 ml sshd[27519]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Feb 13 00:54:04 ml slapd[6815]: conn=129 fd=21 ACCEPT from IP=192.168.1.104:38780 (IP=192.168.1.104:389)
sshd is running and using port 22.

Any help is appreciated!

Thanks
Bob
Reply With Quote
  #2 (permalink)  
Old 02-13-2009, 01:34 AM
Zimbra Consultant & Moderator
 
Posts: 20,316
Default

Shutdown Zimbra then check to see if there's any other zimbra processes running. If there are any processes then kill them and restart Zimbra, post again with the errors you get from that.
__________________
Regards


Bill
Reply With Quote
  #3 (permalink)  
Old 02-13-2009, 05:46 AM
Intermediate Member
 
Posts: 21
Default

I had already done this multiple times, even rebooting the computer, but get the same errors. I stopped zimbra, did ps aux |grep zimbra and ps aux |grep logger then tried starting zimbra and got the errors posted previously.
Reply With Quote
  #4 (permalink)  
Old 02-13-2009, 05:49 AM
Moderator
 
Posts: 7,928
Default

Please use the init script to shutdown ZCS
Code:
/etc/init.d/zimbra stop
Then ensure all processes have indeed died using
Code:
ps aux | grep zimbra
and if so try starting ZCS again. Also check /var/log/zimbra.log for any error messages from Postfix.
__________________
Reply With Quote
  #5 (permalink)  
Old 02-13-2009, 07:12 AM
Intermediate Member
 
Posts: 21
Default

I had already tried shutting down using the init script as well since I had found that in the forums as a procedure. I still had the same result. I couldn't find any errors from Postfix in zimbra.log.

Here's what's odd. Even though zmcontrol status still shows that antispam, antivirus, mailbox and mta are all stopped with zmmtaconfigctl not running, everything appears to be working when I use the web interface and postfix is running according to ps aux |grep postfix. I'm receiving emails and can send emails and emails are even getting sent to the Junk folder as appropriate. I wouldn't know that there was anything wrong if it wasn't for the status output.

Any idea why it would act this way?
Reply With Quote
  #6 (permalink)  
Old 02-13-2009, 07:23 PM
Intermediate Member
 
Posts: 21
Default

I shut down zimbra using /etc/init.d/zimbra then checked for any stray processes but could not find any. I then ran zmcontrol start. I got the same start messages I got before. Here is the zimbra.log from the startup with most slapd messages removed:

Code:
Feb 13 21:02:27 mythliving zimbramon[17550]: 17550:info: Starting services initiated by zmcontrol 
Feb 13 21:02:28 mythliving slapd[17613]: @(#) $OpenLDAP: slapd 2.3.43 (Dec  3 2008 10:56:57) $ ^Iroot@build25.lab.zimbra.com:/home/build/p4/FRANKLIN/ThirdParty/openldap/openldap-2.3.43.7z/servers/slapd 
Feb 13 21:02:30 mythliving slapd[17614]: slapd starting 
slapd info removed
Feb 13 21:02:40 mythliving zimbramon[17550]: 17550:info: Rewriting configs  antispam amavis antivirus amavis   webxml mailbox amavis antispam antivirus mta sasl    
slapd info removed
Feb 13 21:03:07 mythliving zimbramon[17550]: 17550:info: Starting logger via zmcontrol 
Feb 13 21:03:09 mythliving zimbramon[17550]: 17550:info: Starting mailbox via zmcontrol 
Feb 13 21:03:11 mythliving zimbramon[18119]: 18119:info: zmmtaconfig: zmmtaconfig already running at  
many more lines
Note that the very first time zmmtaconfig is mentioned it states that it is already running (it wasn't) and it truncates the pid (because of course there isn't one). What makes it think it is already running?

Bob
Reply With Quote
  #7 (permalink)  
Old 02-13-2009, 08:20 PM
Intermediate Member
 
Posts: 21
Default

The problem was that the file /opt/zimbra/log/zmmtaconfig.pid was never deleted when zimbra was shut down (though it was a 0 byte file), so zmmtaconfigctl thought it was running. After removing the file, zmmtaconfig started and all was well.
Reply With Quote
  #8 (permalink)  
Old 04-29-2009, 03:59 PM
Starter Member
 
Posts: 2
Default

Thank You! I was having the same problem and spent a couple of hours dealing with it..... You are awesome
Reply With Quote
  #9 (permalink)  
Old 05-01-2009, 09:48 AM
Active Member
 
Posts: 30
Default

You've saved me a ton of grief. Thanks!
Reply With Quote
  #10 (permalink)  
Old 08-09-2009, 07:11 AM
Senior Member
 
Posts: 69
Default

Thank you.

Is this a known bug or is this related to unclean reboots or somesuch ? If this is a bug, has this been submitted to bug tracking ?
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.