Difference between revisions of "Proxy error: Address already in use"

(Created page with "=Proxy error: Address already in use= {{KB|{{ZC}}|{{ZCS 8.6}}|{{ZCS 8.5}}|{{ZCS 8.0}}|}} ==Error== # /etc/init.d/zimbra start Host hn.cbl.co.za Starting ldap...Done. St...")
 
(Resolution)
Line 60: Line 60:
 
==Resolution==
 
==Resolution==
 
<br>
 
<br>
A service called '''portreserve''' was running, and it was listening on the UDP ports of 110 143 995 993.
+
A service called [https://linux.die.net/man/1/portreserve '''portreserve'''] was running, and it was listening on the UDP ports of 110 143 995 993.
  
Stopping/disabling it fixed the issue.  
+
Stopping/disabling it fixed the issue.
  
 
==After thoughts==
 
==After thoughts==

Revision as of 15:51, 9 June 2017

Proxy error: Address already in use

   KB 23227        Last updated on 2017-06-9  




0.00
(0 votes)


Error

# /etc/init.d/zimbra start
Host hn.cbl.co.za
Starting ldap...Done.
Starting zmconfigd...Done.
Starting logger...Done.
Starting convertd...Done.
Starting mailbox...Done.
Starting memcached...Done.
Starting imapproxy...Failed.
Starting nginx...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)
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)


$ zmproxyctl restart
Stopping proxy...proxy is not running.
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)

Description


  • After a new installation, no service is listening on 110, 995, 143, 993. If we look in the nginx.log, we will see similar errors as above:
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 
  • Checking /etc/hosts revealed no errors.
  • There was no output running those commands:
fuser 143/tcp 
fuser 110/tcp 
fuser 99/tcp 
  • If we run netstat, there is nothing LISTENING on these ports.

Resolution


A service called portreserve was running, and it was listening on the UDP ports of 110 143 995 993.

Stopping/disabling it fixed the issue.

After thoughts


  • When checking the service on RHEL 6, it appeared to be installed but not running:
$ fuser 993/tcp 
993/tcp: 4132 4133 4134 4135 
$ fuser 993/udp 
$ netstat -putna |grep 993 
(Not all processes could be identified, non-owned process info 
will not be shown, you would have to be root to see it all.) 
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 4132/nginx 
tcp 0 0 0.0.0.0:7993 0.0.0.0:* LISTEN - 

Nothing pointing to 993/udp, zimbra is using 993/tcp.

  • Checking if the service is started:
$ service --status-all | grep -i portreserve 

portreserve is stopped 
  • However, chkconfig is showing:
chkconfig --list 
portreserve 0:off 1:off 2:on 3:on 4:on 5:on 6:off 

We should make sure these are all off If the issue is present.




Verified Against: Zimbra Collaboration 8.6, 8.5, 8.0 Date Created: 9/6/2017
Article ID: https://wiki.zimbra.com/index.php?title=Proxy_error:_Address_already_in_use Date Modified: 2017-06-09



Try Zimbra

Try Zimbra Collaboration with a 60-day free trial.
Get it now »

Want to get involved?

You can contribute in the Community, Wiki, Code, or development of Zimlets.
Find out more. »

Looking for a Video?

Visit our YouTube channel to get the latest webinars, technology news, product overviews, and so much more.
Go to the YouTube channel »


Wiki/KB reviewed by SME1 SME2 COPY EDITOR Last edit by Teodor Vizirov
Jump to: navigation, search