Centos 64bit 6.10 -> 7.0.1 (imapproxy)

[cyber7]

Hi guys
Everything went smoothly, until the machine was brought up. Then I found imapproxy did not want to start. Following phonix's guide:

(imapproxy won't start after upgrade)


	
	
zmproxyctl status
zmprov gs `zmhostname` | grep zimbraServiceEnabled
zmprov gs `zmhostname` | grep zimbraServiceInstalled
 
If it's running, 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
 
ps: My ports are slightly different, so the above command was modified to my needs.
I got my ports prior to installation by running:
  
zmprov -l gs <FQDN> | grep Bind
 
then restart

Everything came up OK.

I would just like to know, by disabling the imapproxy, did I expose my system to any problems? Imapproxy did run prior to the upgrade. (I even went as far as restoring the system to check if it was running prior to the upgrade.)

Times it took me to upgrade (143 users):
Upgrade: 09:09 -> 09:44
SQL Rebuild: 09:46 -> 09:58

Kind regards
Aubrey Kloppers

[phoenix]

You do not need imapproxy (nor memcached) on a single server (I'm assuming that's whjat you have) and it can cause problems, removing them is the correct thing to do and won't cause you any problems.

[cyber7]

Hi phoenix
Thank you for that, yes I am running a single-server. My memcached is running (The machine is running on a vMware ESXi machine), do I need to disable it? What are the advantages/disadvantages?

Kind regards
Aubrey Kloppers

[phoenix]

My memcached is running (The machine is running on a vMware ESXi machine), do I need to disable it? What are the advantages/disadvantages?

It's part of the proxy set-up and isn't needed on a single server, the advantage is less memory footprint and one less service running.