[SOLVED] problem with soap service and port 993/995

[serivo]

I have a very strange problem with my zimbra server on solaris, version 5.0.15, the result of upgrade of 4.5.4 made by dijichi2. May be somebody can help me by pointing out where to look for the problem.

The server 4.5.4 had name different from certificate name, so before doing upgrade I disabled all ssl and tls ports and services.
After upgrade it is working pretty well, zimbraMailMode=mixed, listens on ports 80, 443, 7071, 110 and 143. It recognized the certificate and because I've renamed the server after upgrade, it uses it.
But when I tried to enable Imap SSL or Pop3 SSL services, it results in service soap failure to start.
The most intriguing thing - after changing Imap SSL port to bind to to something like 8993, it starts and works perfectly, with soap service and all others. But when I change port to anything below 1024, like 994 - it fails:
---
2009-04-01 00:02:47,925 FATAL [main] [] soap - Unable to start servlet
com.zimbra.common.service.ServiceException: system failure: Could not bind to port=993 bindaddr=null ssl=true useChannels=false
ExceptionId:main:1238558567923:fa0695a0858a9f7f
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:253)
at com.zimbra.common.util.NetUtil.getServerSocket(Net Util.java:72)
at com.zimbra.common.util.NetUtil.getSslTcpServerSock et(NetUtil.java:44)
at com.zimbra.cs.server.ServerConfig.getServerSocket( ServerConfig.java:110)
at com.zimbra.cs.tcpserver.TcpServer.<init>(TcpServer .java:46)
at com.zimbra.cs.imap.ImapServer.<init>(ImapServer.ja va:50)
at com.zimbra.cs.imap.ImapServer.startServer(ImapServ er.java:91)
at com.zimbra.cs.imap.ImapServer.startupImapSSLServer (ImapServer.java:70)
at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:220)
at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:137)
at com.zimbra.soap.SoapServlet.init(SoapServlet.java: 117)
at javax.servlet.GenericServlet.init(GenericServlet.j ava:241)
at org.mortbay.jetty.servlet.ServletHolder.initServle t(ServletHolder.java:433)
at org.mortbay.jetty.servlet.ServletHolder.doStart(Se rvletHolder.java:256)
at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:40)
at org.mortbay.jetty.servlet.ServletHandler.initializ e(ServletHandler.java:612)
at org.mortbay.jetty.servlet.Context.startContext(Con text.java:139)
at org.mortbay.jetty.webapp.WebAppContext.startContex t(WebAppContext.java:1222)
at org.mortbay.jetty.handler.ContextHandler.doStart(C ontextHandler.java:501)
at org.mortbay.jetty.webapp.WebAppContext.doStart(Web AppContext.java:449)
at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:40)
at org.mortbay.jetty.handler.HandlerCollection.doStar t(HandlerCollection.java:147)
at org.mortbay.jetty.handler.ContextHandlerCollection .doStart(ContextHandlerCollection.java:161)
at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:40)
at org.mortbay.jetty.handler.HandlerCollection.doStar t(HandlerCollection.java:147)
at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:40)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(H andlerWrapper.java:117)
at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:40)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(H andlerWrapper.java:117)
at org.mortbay.jetty.Server.doStart(Server.java:217)
at org.mortbay.setuid.SetUIDServer.doStart(SetUIDServ er.java:100)
at org.mortbay.component.AbstractLifeCycle.start(Abst ractLifeCycle.java:40)
at org.mortbay.xml.XmlConfiguration.main(XmlConfigura tion.java:979)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.mortbay.start.Main.invokeMain(Main.java:183)
at org.mortbay.start.Main.start(Main.java:497)
at org.mortbay.start.Main.main(Main.java:115)
Caused by: java.net.BindException: Permission denied
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java :359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at com.zimbra.common.util.NetUtil.newBoundServerSocke t(NetUtil.java:106)
at com.zimbra.common.util.NetUtil.getServerSocket(Net Util.java:70)
... 38 more
2009-04-01 00:02:47,929 WARN [main] [] log - failed SoapServlet
---
--
Will appreciate any help.
Sergey

[serivo]

The problem was in /opt/zimbra/jetty/etc/jetty.properties, although updated each time by zmmtaconfigctl, but - wrongly, and it did not have zimbraImapSSLServerEnabled=true and zimbraPop3SSLServerEnabled=true, but "falses".