Disabling Imapproxy: Difference between revisions
(New page: In ZCS if you are running the Zimbra server with standard Imap and POP services i.e no proxy is running and if you enable ImapProxy then the Zimbra server will detect port conflicts. Th...) |
No edit summary |
||
(14 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
In ZCS if you are running the Zimbra server with standard Imap and POP services i.e no proxy is running and if you enable ImapProxy then the Zimbra server will detect port conflicts. | {{Archive}}{{Article Infobox|{{admin}}|||{{ZCS 4.5}}}}In ZCS if you are running the Zimbra server with standard Imap and POP services i.e no proxy is running and if you enable ImapProxy then the Zimbra server will detect port conflicts. | ||
The ports 110 and 143 will | The ports 110 and 143 will become occupied by the Imapproxy services. | ||
Tomcat will not be able to start itself and | Tomcat will not be able to start itself because when it starts it will try to bind to POP and Imap services on port 110 and 143 which are occupied by the proxy services and because of which the following error is received in the catalina.out file: | ||
Error from /opt/zimbra/tomcat/logs/catalina.out:- | |||
Zimbra server reserving server socket port=110 bindaddr=null ssl=false | |||
Fatal error: terminating: PrivilegedServlet init failed | |||
java.net.BindException: Address already in use | |||
'''Solution''': | |||
Disable ImapProxy using:- | |||
- | 1) su - zimbra | ||
2) zmprov -l ms `zmhostname` -zimbraServiceEnabled imapproxy | |||
[-l option will modify the configuration in LDAP as the normal zmprov command will not run, as tomcat is not running and it will give Java errors.] | |||
Restart Zimbra Services. | |||
zmcontrol stop | zmcontrol stop | ||
zmcontrol start | zmcontrol start | ||
Check if the services are running. | Check if the services are running. | ||
zmcontrol status. | zmcontrol status. | ||
{{Article Footer|Zimbra Collaboration Suite 4.5.x|12/19/2007}} | |||
[[Category:Troubleshooting MTA]] | |||
[[Category:Troubleshooting Server]] | |||
== Headline text == |
Latest revision as of 17:12, 24 March 2015
Article Information |
---|
This article applies to the following ZCS versions. |
In ZCS if you are running the Zimbra server with standard Imap and POP services i.e no proxy is running and if you enable ImapProxy then the Zimbra server will detect port conflicts.
The ports 110 and 143 will become occupied by the Imapproxy services.
Tomcat will not be able to start itself because when it starts it will try to bind to POP and Imap services on port 110 and 143 which are occupied by the proxy services and because of which the following error is received in the catalina.out file:
Error from /opt/zimbra/tomcat/logs/catalina.out:-
Zimbra server reserving server socket port=110 bindaddr=null ssl=false Fatal error: terminating: PrivilegedServlet init failed java.net.BindException: Address already in use
Solution:
Disable ImapProxy using:-
1) su - zimbra
2) zmprov -l ms `zmhostname` -zimbraServiceEnabled imapproxy
[-l option will modify the configuration in LDAP as the normal zmprov command will not run, as tomcat is not running and it will give Java errors.]
Restart Zimbra Services.
zmcontrol stop
zmcontrol start
Check if the services are running.
zmcontrol status.