imapproxy won't start after upgrade

[mrambo3501]

Upgraded from 5.0.16 to 5.0.19 this morning on Centos 4.

After the upgrade imapproxy won't start with a nginx error.

Starting nginx...2009/10/02 09:17:54 [emerg] 9699#0: SSL_CTX_use_certificate_chain_file("/opt/zimbra/conf/nginx.crt") failed (SSL: error:02001002:system library:fopen:No such file or directory error:20074002:BIO routines:FILE_CTRL:system lib error:140DC002:SSL routines:SSL_CTX_use_certificate_chain_file:sys)

We have used Zimbra without imapproxy for several years. When the new version offered to install that service after a little googling I decided it was probably the thing to do. Now we're down.

What can I do to either fix this or remove it and revert to our old way of operating?

Thanks.

[phoenix]

You should not use the proxy on a single server install. Have a search of the forums for posts by me that describe how to remove and disable the proxy.

[phoenix]

Originally Posted by mrambo3501

Upgraded from 5.0.16 to 5.0.19 this morning on Centos 4.

BTW, you should also update your forum profile to reflect the version of Zimbra that you're using.

[y@w]

You can go back by following this thread:
remove/disable imapproxy

In essence, what you want to do is disable the service from starting and change the IMAP ports to listen on the standard ones. If you have a firewall handling NAT in front of your Zimbra server, you can also just forward up to the actual IMAP ports for now, bypassing the proxy until you can get it fixed.

You can find the ports via:

zmprov gs host.zimbra.com | grep Imap

to find the bind ports and use something like:

zmprov ms host.zimbra.com zimbraImapBindPort 143
zmprov ms host.zimbra.com zimbraImapSSLBindPort 443

Be sure to modify your ImapProxy bind ports the same way so they don't conflict.

[mrambo3501]

I have.

Schemers said this:
zmprov -- ms server.example.com -zimbraServiceEnabled imapproxy

and it was followed with this:
1.) [zimbra@mail ~]$ zmprov [enter]
2.) prov> ms server.example.com -zimbraServiceEnabled imapproxy [enter]
3.) prov> gs server.example.com [enter] and item is not listed....)
4.) prov> quit [enter]

Unfortunately zmprov won't respond.

Even a zmprov gs `zmhostname` just sits there forever (or at least for the last five minutes since I ran it).

I also found this:
[zimbra@pandora ~]$ zmprov -l ms `zmhostname` -zimbraServiceEnabled imapproxy

Which results in this error:

ERROR: service.FAILURE (system failure: ZimbraLdapContext) (cause: java.net.SocketException Broken pipe)

With zmprov broken how does one fix this?

Even after I get it disabled (which at this point I be very thankful for), thus far I haven't found anything for removing it entirely. Sure wish I had searched better before saying yes...

[y@w]

What Zimbra services are starting?

zmcontrol status

[mrambo3501]

Ok. Looks like I may have found a link that tells how to both disable and actually remove imapproxy but it still depends upon zmprov which doesn't work. zmprov with the -l results in an error and with the -l just hangs.

What do I do to fix zmprov? Have I somehow ended up with two separate problems?

(I have updated my profile too - something easy to forget about.)

[mrambo3501]

[zimbra@pandora ~]$ zmcontrol status
Unable to determine enabled services from ldap.
Enabled services read from cache. Service list may be inaccurate.
Host pandora.lsd.k12.mi.us
antispam Running
antivirus Running
imapproxy Stopped
zmnginxctl is not running
ldap Running
logger Running
mailbox Running
mta Running
snmp Running
spell Running
stats Running

[mrambo3501]

FWIW (in case others find themselves in this circumstance).

I have it back up and running though I'm not entirely sure which of the steps I took actually fixed it.

I think there were two problems. The original imapproxy thing and then a problem which caused zmprov to be non-functional. The latter seems to have been due to the self signed certificates being bad. It looked like they were generated ok during the upgrade but after I recreated them per the wiki zmprov started working. I was then able to disable imapproxy and reset the imap ports to proper values after which it all started to work again. But who knows... I tried lots of things trying to get this to work and any of the other steps could have had some effect too.

In regard to the imapproxy the best I have been able to do is disable it. The last time I shut down the zimbra service it was still listed as being a service which was shutdown. I wish there was a way to remove all vestages of it but I haven't found one as of yet.

I do wonder why the installer suggested installing the proxy on a system that didn't already have it though - especially when the consequences can be so dire. It doesn't offer to install other optional modules. With no guidance provided and a quick (obviously too quick) google search giving no reason not to install it I went ahead and let it break my setup. I just assumed Zimbra was moving to new ways of doing things which was a clearly wrong assumption.

But I am glad to have it running again and am thankful for the community edition being available and for the attempts to help that were found here.

[phoenix]

Complete details for disabling the proxy are in several recent posts by me but here they are again. Check if the proxy is installed/running:

zmproxyctl status
zmprov gs `zmhostname` | grep zimbraServiceEnabled
zmprov gs `zmhostname` | grep zimbraServiceInstalled

If it's in, then run this:

zmproxyctl stop
zmprov ms `zmhostname` -zimbraServiceEnabled imapproxy
zmcontrol stop
zmcontrol start

To reset the ports run the following (on one line):

zmprov -l ms `zmhostname` zimbraPop3BindPort 110 zimbraPop3SSLBindPort 995 zimbraPop3ProxyBindPort 7110 zimbraPop3SSLProxyBindPort 7995 zimbraImapBindPort 143 zimbraImapSSLBindPort 993 zimbraImapProxyBindPort 7143 zimbraImapSSLProxyBindPort 7993

then restart