Results 1 to 3 of 3

Thread: Error Deploying CA

  1. #1
    jimbo is offline Special Member
    Join Date
    Nov 2005
    Posts
    108
    Rep Power
    9

    Default Error Deploying CA

    Need some help. Have searched the forums and Google for a resolution but can't seem to find one that works.

    Running Zimbra ZCS 6.08 on Ubuntu 8.04

    When generating and deploying a new self-signed certificate, I get the following error:

    Code:
    ./zmcertmgr deploycrt self
    ** Saving server config key zimbraSSLCertificate...done.
    ** Saving server config key zimbraSSLPrivateKey...done.
    ** Installing mta certificate and key...done.
    ** Installing slapd certificate and key...done.
    ** Installing proxy certificate and key...done.
    ** Creating pkcs12 file /opt/zimbra/ssl/zimbra/jetty.pkcs12...done.
    ** Creating keystore file /opt/zimbra/mailboxd/etc/keystore...done.
    ** Installing CA to /opt/zimbra/conf/ca...unable to load certificate
    8973:error:0906D06C:PEM routines:PEM_read_bio:no start line:pem_lib.c:650:Expecting: TRUSTED CERTIFICATE
    done.
    Cant' start the server as the mailbox won't start.

    Any ideas what could be going on here?

    [Update]

    Tried everything I can think of. Still get the same error. Server still down.

    I tried upgrading too 6.0.12 but upgrade failed when it was trying to update mysql...

    Code:
    UPGRADE FAILED - exiting
    restored from backup and back to the original problem.

    ANY help would be very much appreciated!

    jimbo
    Last edited by jimbo; 05-16-2011 at 04:56 PM. Reason: Update

  2. #2
    jimbo is offline Special Member
    Join Date
    Nov 2005
    Posts
    108
    Rep Power
    9

    Default

    anybody have a place to start on this?

    ANY help... ANY. Will be appreciated!

  3. #3
    jimbo is offline Special Member
    Join Date
    Nov 2005
    Posts
    108
    Rep Power
    9

    Default

    OK I've managed to battle my way back to having an ALMOST working system.

    I've got all the service starting with now errors, however when I try to log into the webclient or admin client from any system I get a zmclient/io error on the login page.

    zmmailbox.out reveals...
    Code:
    com.zimbra.cs.zclient.ZClientException: invoke cannot determine soap protocol in reply: <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/><title>Error 503 SERVICE_UNAVAILABLE</title></head><body><h2>HTTP ERROR: 503</h2><pre>SERVICE_UNAVAILABLE</pre><p>RequestURI=/service/admin/soap/</p></body></html>, server: localhost
    ExceptionId:btpool0-2:1305752296127:b1d8a6306924a63a
    Code:zclient.IO_ERROR
    	at com.zimbra.cs.zclient.ZClientException.IO_ERROR(ZClientException.java:47)
    	at com.zimbra.cs.account.soap.SoapProvisioning.invoke(SoapProvisioning.java:196)
    	at com.zimbra.cs.account.soap.SoapProvisioning.getDomainInfo(SoapProvisioning.java:876)
    	at com.zimbra.cs.taglib.tag.GetDomainInfoTag.getInfo(GetDomainInfoTag.java:90)
    	at com.zimbra.cs.taglib.tag.GetDomainInfoTag.checkCache(GetDomainInfoTag.java:77)
    	at com.zimbra.cs.taglib.tag.GetDomainInfoTag.doTag(GetDomainInfoTag.java:66)
    	at org.apache.jsp.public_.login_jsp._jspService(login_jsp.java:488)
    	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:93)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373)
    	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:477)
    	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:371)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    	at com.zimbra.webClient.servlet.JspServlet.service(JspServlet.java:50)
    	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
    	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
    	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:716)
    	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406)
    	at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:268)
    	at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126)
    	at org.mortbay.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:465)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)
    	at com.zimbra.webClient.filters.SetHeaderFilter.doFilter(SetHeaderFilter.java:305)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
    	at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
    	at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
    	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
    	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:716)
    	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406)
    	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
    	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
    	at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:350)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
    	at org.mortbay.jetty.Server.handle(Server.java:313)
    	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
    	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:830)
    	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514)
    	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
    	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
    	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
    	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
    Caused by: com.zimbra.common.soap.SoapParseException: cannot determine soap protocol in reply: <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/><title>Error 503 SERVICE_UNAVAILABLE</title></head><body><h2>HTTP ERROR: 503</h2><pre>SERVICE_UNAVAILABLE</pre><p>RequestURI=/service/admin/soap/</p></body></html>
    	at com.zimbra.common.soap.SoapTransport.extractBodyElement(SoapTransport.java:246)
    	at com.zimbra.common.soap.SoapTransport.parseSoapResponse(SoapTransport.java:224)
    	at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:277)
    	at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:226)
    	at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:315)
    	at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:279)
    	at com.zimbra.cs.account.soap.SoapProvisioning.invoke(SoapProvisioning.java:192)
    	... 48 more
    I can feel I'm SO close but at a loss as how to solve this last problem.

    I really could use some help sorting this one out. I will be ever grateful for any help or just a hint of what direction to go.

    Thank you so much for any help!

    jimbo

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

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