zmmailboxdmgr refuses to run after 6.0.6 to 6.0.7 upgrade

btrudeau · Post by **btrudeau** » Wed Jun 16, 2010 12:24 pm

[quote user="uxbod"]Well, if you are going to do that make sure you at least back up /opt/zimbra/store. You can then use 'find' for anything that has come in overnight, since the backup, and use zmlmtlpinject to push them back into Zimbra. In theory you should not loose any email; only changes made by the users since the backup.[/QUOTE]
yep, all back up and working... Now to give zmlmtpinject a look see, thanks uxbod!

subversionpdx · Post by **subversionpdx** » Wed Jun 16, 2010 3:30 pm

I tried the IPTABLES trick you mentioned, using port 9143 and had the exact same issue as with just 143:

2010-06-16 13:26:49,581 FATAL [main] [] system - Exception during startup, aborting server, please check your config

com.zimbra.common.service.ServiceException: system failure: Could not bind to port=9143 bindaddr=209.20.91.50 ssl=false useChannels=false

ExceptionId:main:1276720009580:bab79eae7f1c97ba

Code:service.FAILURE

I tried it with / without SSL enabled
Ubuntu 8.04 LTS / Zimbra 6.0.7
I'll mess with it some more...

mlo · Post by **mlo** » Wed Jun 16, 2010 4:51 pm

We're able to repro the problem by setting zimbraPop3BindAddress.
Can someone confirm if unsetting zimbraPop3BindAddress resolves the issue?

bbos · Post by **bbos** » Wed Jun 16, 2010 5:51 pm

Setting a empty string for zimbraPop3BindAddress.
[zimbra@mail ~]$ zmprov -l ms your_mailserver -zimbraPop3BindAddress your_mailserver or ip

[zimbra@mail ~]$ zmcontrol restart
and zimbra is working after the upgrade -
Release 6.0.7_GA_2470.RHEL5_64_20100610220647 CentOS5_64 FOSS edition.

mlo · Post by **mlo** » Wed Jun 16, 2010 5:52 pm

Thanks for confirming. Since the server failed to restart during the upgrade, you should also run /opt/zimbra/libexec/zmsetup.pl as root to complete the upgrade.

liverpoolfcfan · Post by **liverpoolfcfan** » Wed Jun 16, 2010 5:58 pm

[quote]I am also able to repro. And just to be clear, if you have zimbraPop3BindAddress set, you will still get an error in mailbox.log reflecting IMAP:

[/QUOTE]
So does this mean that IMAP will work - but at the expense of POP3 ?
Or does POP3 still work regardless ?

mlo · Post by **mlo** » Wed Jun 16, 2010 6:11 pm

[quote user="liverpoolfcfan"]So does this mean that IMAP will work - but at the expense of POP3 ?
Or does POP3 still work regardless ?[/QUOTE]
Nothing will work. This is a FATAL error and will prevent the server from starting. We're working on a fix now. The workaround is to unset zimbraPop3BindAddress for now. When zimbraPop3BindAddress is not set (i.e. empty), the server will bind to all interfaces. The default setting is not set.

subversionpdx · Post by **subversionpdx** » Wed Jun 16, 2010 6:57 pm

I removed the pop3 address as indicated above, re-enabled all my IMAP stuff and restarted, everything working properly now... thank you!
Looking forward to the fix..
Joe