Zimbra Proxy 8.7.9 Connection Refused 110, 143 etc

[wilsonneil]

Hi guys,

I've got a fresh install of zcs-8.7.9_GA_1794.RHEL6_64.20170505054622 on Centos 6.9

At the end of the install when the Zimbra proxy configuration screen came up, I was careful to ensure I had no conflicting ports, I did change port 8080 to 8081 to ensure it didn't conflict with my existing Squid proxy on port 8080, so all other ports were fine. After the install finished I noticed that nothing was listening on port 110, 143, 993 or 995.

I then assumed that the proxy hadn't started, so I tried starting it, but it complained that the ports were already in use....

As you can see in my netstat, nothing is currently listening on these ports...

[root@mail src]# netstat -pnvat | grep LISTEN | grep 110
tcp 0 0 0.0.0.0:7110 0.0.0.0:* LISTEN 18925/java
[root@mail src]# netstat -pnvat | grep LISTEN | grep 143
tcp 0 0 0.0.0.0:7143 0.0.0.0:* LISTEN 18925/java
[root@mail src]# netstat -pnvat | grep LISTEN | grep 99
tcp 0 0 0.0.0.0:7993 0.0.0.0:* LISTEN 18925/java
tcp 0 0 0.0.0.0:7995 0.0.0.0:* LISTEN 18925/java

...but if I try and start zimbra proxy it indicates that this isn't the case...

[zimbra@mail src]$ zmproxyctl start
Starting proxy...nginx: [emerg] bind() to 0.0.0.0:143 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:993 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:110 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:995 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:143 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:993 failed (98: Address already in use)

If I look in the nginx.log it indicates the same...

2017/05/22 11:28:23 [debug] 2232#0: bind() 0.0.0.0:143 #6
2017/05/22 11:28:23 [emerg] 2232#0: bind() to 0.0.0.0:143 failed (98: Address already in use)
2017/05/22 11:28:23 [debug] 2232#0: bind() 0.0.0.0:993 #6
2017/05/22 11:28:23 [emerg] 2232#0: bind() to 0.0.0.0:993 failed (98: Address already in use)
2017/05/22 11:28:23 [debug] 2232#0: bind() 0.0.0.0:110 #6
2017/05/22 11:28:23 [emerg] 2232#0: bind() to 0.0.0.0:110 failed (98: Address already in use)
2017/05/22 11:28:23 [debug] 2232#0: bind() 0.0.0.0:995 #6
2017/05/22 11:28:23 [emerg] 2232#0: bind() to 0.0.0.0:995 failed (98: Address already in use)
2017/05/22 11:28:23 [debug] 2232#0: bind() 0.0.0.0:443 #6
2017/05/22 11:28:23 [notice] 2232#0: try again to bind() after 500ms
2017/05/22 11:28:23 [debug] 2232#0: bind() 0.0.0.0:143 #7
2017/05/22 11:28:23 [emerg] 2232#0: bind() to 0.0.0.0:143 failed (98: Address already in use)
2017/05/22 11:28:23 [debug] 2232#0: bind() 0.0.0.0:993 #7
2017/05/22 11:28:23 [emerg] 2232#0: bind() to 0.0.0.0:993 failed (98: Address already in use)
2017/05/22 11:28:23 [debug] 2232#0: bind() 0.0.0.0:110 #7
2017/05/22 11:28:23 [emerg] 2232#0: bind() to 0.0.0.0:110 failed (98: Address already in use)
2017/05/22 11:28:23 [debug] 2232#0: bind() 0.0.0.0:995 #7
2017/05/22 11:28:23 [emerg] 2232#0: bind() to 0.0.0.0:995 failed (98: Address already in use)
2017/05/22 11:28:23 [notice] 2232#0: try again to bind() after 500ms
2017/05/22 11:28:23 [debug] 2232#0: bind() 0.0.0.0:143 #7

As you can see, nothing is listening on these ports....

[root@mail src]# telnet 192.168.0.254
Trying 192.168.0.254...
telnet: connect to address 192.168.0.254: Connection refused
[root@mail src]# telnet 192.168.0.254 110
Trying 192.168.0.254...
telnet: connect to address 192.168.0.254: Connection refused
[root@mail src]# telnet 127.0.0.1 110
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
[root@mail src]# telnet 127.0.0.1 143
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused

My /etc/hosts looks as follows...

[root@mail src]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.0.254 mail.mydomain.co.za mail

[root@mail src]# ping mail.mydomain.co.za
PING mail.mydomain.co.za (192.168.0.254) 56(84) bytes of data.
64 bytes from mail.mydomain.co.za (192.168.0.254): icmp_seq=1 ttl=64 time=0.035 ms

I have tried disabling and stopping the zimbra proxy too, and configuring mailboxd to rather listen on the default ports (110, 143 etc) but this also complains about the same issue and yet as you can see, nothing runs on these ports.

Below is more info if required....

[zimbra@mail src]$ zmprov gs `zmhostname` | grep -i serviceenabled
zimbraChatServiceEnabled: TRUE
zimbraServiceEnabled: amavis
zimbraServiceEnabled: antivirus
zimbraServiceEnabled: antispam
zimbraServiceEnabled: opendkim
zimbraServiceEnabled: logger
zimbraServiceEnabled: service
zimbraServiceEnabled: zimbra
zimbraServiceEnabled: zimbraAdmin
zimbraServiceEnabled: zimlet
zimbraServiceEnabled: mailbox
zimbraServiceEnabled: memcached
zimbraServiceEnabled: mta
zimbraServiceEnabled: stats
zimbraServiceEnabled: proxy
zimbraServiceEnabled: snmp
zimbraServiceEnabled: ldap
zimbraServiceEnabled: spell
zimbraServiceEnabled: imapproxy

I've tried running through the steps here (https://wiki.zimbra.com/wiki/Enabling_Z ... ng_servers ) to reconfigure the proxy too, without any success.

Can anyone offer any assistance or guidance here please?

Thanks.

Neil Wilson

[Raun]

Check the value of zimbraReverseProxyImapStartTlsMode and zimbraReverseProxyPop3StartTlsMode . Set it to "on" if not already and you should be up and running in no time . Let me know if this helps .

Cheers
Raun