Page 1 of 3 123 LastLast
Results 1 to 10 of 22

Thread: Zimbra 3 on FC4 having problems with zimbraMailPort and SOAP service

Hybrid View

  1. #1
    Join Date
    Mar 2006
    Posts
    16
    Rep Power
    9

    Exclamation Zimbra 3 on FC4 having problems with zimbraMailPort and SOAP service

    Hello all.

    Thanks in advance for the help found on this forum. Here is my situation.

    Zimbra is installed on a FC4 system. I have the base FC4 Apache running on port 80. This serves a small website. I want the users to hit Zimbra using mod_jk through Apache. Thus, I installed FC4 and changed the default http port to 88 and https to 8889. I've setup mod_jk, and added the connector line to the server.xml.in (tomcat conf directory under /opt/zimbra). The appropiate changes have been made to the base Apache (running on port 80) httpd.conf file. I have a virtual host setup in Apache called mail.mydomain.com. This sub-domain/virtual host forwards all traffic to the ajp13 connector eg:
    JkMount /zimbra/mail ajp13
    JkMount /zimbra/auth/ ajp13
    JkMount /zimbra/js/*.jgz ajp13
    JkMount /zimbra/ ajp13
    JkMount /service/* ajp13

    I can hit mail.mydomain.com/zimbra/ from outside the firewall. It correctly brings up the Zimbra login screen. Great! Except, when I login I get this error:
    An unknown application error has occurred. Please correct any errors and retry. If the problem persists, please contact your System Aministrator. (service.FAILURE)

    Using the debug tool (http://mail.mydomain.com/zimbra/?debug=1) I see this error:
    code: "service.FAILURE",
    detail: "system failure: Request not allowed on port 80",
    method: "ZmCsfeCommand.prototype.invoke",
    msg: "Csfe service error"

    com.zimbra.cs.service.ServiceException: system failure: Request not allowed on port 80 at com.zimbra.cs.service.ServiceException.FAILURE(Ser viceException.java:131) at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:142) at javax.servlet.http.HttpServlet.service(HttpServlet .java:802) at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107) at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:526) at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyo teHandler.java:306) at org.apache.jk.common.HandlerRequest.invoke(Handler Request.java:385) at org.apache.jk.common.ChannelSocket.invoke(ChannelS ocket.java:745) at org.apache.jk.common.ChannelSocket.processConnecti on(ChannelSocket.java:675) at org.apache.jk.common.SocketConnection.runIt(Channe lSocket.java:868) at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595)


    Which tells me it is still looking for some service on port 80. I assume it's looking for the soap service...

    zmcontrol status shows everything is running ok.

    running zmprov GetConfig zimbraMailPort shows:
    zimbraMailPort: 80 <-- which is probably the problem.

    Using this forum I saw to use zmprov to change the zimbraMailPort. I did that and it never changes.

    PLEASE HELP!!! What do I need to configure to make Zimbra login work???

    Two more things -- going directly to Tomcat on port 88 I can login and work just fine; I have uninstalled and reinstalled just for kicks. No dice.

    Justin

  2. #2
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default

    Try changing the zimbra mail port on the server (with ms) instead of the global value (via mcf)

  3. #3
    Join Date
    Mar 2006
    Posts
    16
    Rep Power
    9

    Default Don't quite understand...

    marmac: What is 'ms' and 'mcf' standfor? How do I change it with 'ms'?

  4. #4
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default

    zmprov --help will give you the full command list.

    ms is modifyServer
    mcf is modifyConfig (which is what you used the first time)

    so
    zmprov ms SERVERNAME zimbraMailPort 88
    with your servername in for SERVERNAME should fix this.

  5. #5
    Join Date
    Mar 2006
    Posts
    16
    Rep Power
    9

    Default zmprov

    marcmac:

    I did as you said...

    zmprov mcf fw.lakeviewbc.info zimbraMailPort 88
    AND
    zmprov ms fw.lakeviewbc.info zimbraMailPort 88

    The first command failed (just spit back the syntax of zmprov); I stopped and started Tomcat after making the changes.

    Note: Issuing the command zmprov gcf fw.lakeviewbc.info zimbraMailPort spit nothing back! Issuing zmprov gs fw.lakeviewbc.info zimbraMailPort spit back the syntax of zmprov.

    Tried logging in again and same result! Still getting this in the debug window:
    code: "service.FAILURE",
    detail: "system failure: Request not allowed on port 80",
    method: "ZmCsfeCommand.prototype.invoke",
    msg: "Csfe service error"

    Other ideas? I have fought this for 2 days now...

  6. #6
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default

    From the help text that it's "spitting" out:

    ModifyServer(ms) {name|id} [attr1 value1 [attr2 value2...]]
    ModifyConfig(mcf) attr1 value1 [attr2 value2...]

    So, ms takes the server name as it's first arg, then a list of key value pairs.

    mcf, on the other hand, takes no server name argument.

    soooo

    zmprov ms SERVER zimbraMailPort 88
    zmprov gs SERVER | grep zimbraMailPort
    tomcat stop
    tomcat start

  7. #7
    Join Date
    Mar 2006
    Posts
    16
    Rep Power
    9

    Default hit me

    Well, I learned an important lesson. READ. READ. READ. RTFM.


    [zimbra@fw ~]$ zmprov gcf zimbraMailPort
    zimbraMailPort: 80
    [zimbra@fw ~]$ zmprov mcf zimbraMailPort 88
    [zimbra@fw ~]$ zmprov gcf zimbraMailPort
    zimbraMailPort: 88
    [zimbra@fw ~]$ zmprov ms myserver zimbraMailPort 88
    [zimbra@fw ~]$ zmprov gs myserver | grep zimbraMailPort
    zimbraMailPort: 88

    Restarted tomcat - even restarted Zimbra - and I am still getting the same error.

    From the debug screen...

    code: "service.FAILURE",
    detail: "system failure: Request not allowed on port 80",
    method: "ZmCsfeCommand.prototype.invoke",
    msg: "Csfe service error"

    Thank you for your help. Other ideas?

  8. #8
    Join Date
    Mar 2006
    Posts
    16
    Rep Power
    9

    Default One more thing...

    FYI - I have also set 'zmtlsctl http' per a comment I saw on the forum and the wiki.

    Ideas???

  9. #9
    Join Date
    Sep 2005
    Posts
    2,103
    Rep Power
    14

    Default

    This error shows up on login straight to zimbra, or thru apache?

  10. #10
    Join Date
    Mar 2006
    Posts
    16
    Rep Power
    9

    Default Through Apache...

    Through Apache...

    I can login directly to port 88 just fine.

    jh

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •