[SOLVED] Cannot generate CSR

[Dirk]

If I move the zimbra install onto a new server, even if that server has the same hostname etc as the old one; I still need to make new certificates, is that right?

Assuming it is, I'm having a problem generating a CSR. When I try I get a message "Server error encountered" and the following in the mailbox.log

Any advice on how to debug this?

2008-10-02 13:18:23,366 INFO  [btpool0-10] [name=user@domain.com;mid=3;ip=10.100.100.1;ua=ZimbraWebClient - IE7 (Win);] soap - GetCSRRequest
2008-10-02 13:18:23,568 INFO  [btpool0-10] [name=user@domain.com;mid=3;ip=10.100.100.1;ua=ZimbraWebClient - IE7 (Win);] SoapEngine - handler exception
com.zimbra.common.service.ServiceException: system failure: exception during auth {RemoteManager: zimbra.domain.com->zimbra@zimbra.domain.com:22}
ExceptionId:btpool0-10:1222949903568:5fe999f1e693f65d
Code:service.FAILURE
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
        at com.zimbra.cs.rmgmt.RemoteManager.getSession(RemoteManager.java:192)
        at com.zimbra.cs.rmgmt.RemoteManager.execute(RemoteManager.java:126)
        at com.zimbra.cert.GetCSR.handle(GetCSR.java:80)
        at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:411)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:268)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:160)
        at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:266)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:188)
        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 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.content(HttpConnection.java:844)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)
        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: java.io.IOException: auth failed
        at com.zimbra.cs.rmgmt.RemoteManager.getSession(RemoteManager.java:185)
        ... 32 more

[bdial]

you shouldn't need to if your fqdn is the same. certificates don't contain any machine/ip specific stuff.

[Dirk]

That does make sense, I only thought it may need to be done again as when I when to the admin panel and selected the certificates section and picked the "import the commercially signed certificate" option, an error is shown saying no CSR found and telling me that I need to generate a CSR.

Similar errors to the one in the post above are also shown, so it looks like I need to resolve that and then try to import existing cert once that's fixed.

I think it must be this part:

Caused by: java.io.IOException: auth failed
        at com.zimbra.cs.rmgmt.RemoteManager.getSession(RemoteManager.java:185)

[Dirk]

Looking further into it, I think I've seen this before.
Searching for forums I find a post by Mike [SOLVED] Remote Manager, Port 22 issue

The result of

ssh -vi .ssh/zimbra_identity -o strictHostKeyChecking=no zimbra@server.domain.com -p 22

is:

OpenSSH_4.7p1 Debian-8ubuntu1.2, OpenSSL 0.9.8g 19 Oct 2007
Warning: Identity file .ssh/zimbra_identity not accessible: No such file or directory.
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to zimbra.domain.com [10.100.100.2] port 22.
debug1: Connection established.
debug1: identity file /opt/zimbra/.ssh/identity type -1
debug1: identity file /opt/zimbra/.ssh/id_rsa type -1
debug1: identity file /opt/zimbra/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.7p1 Debian-8ubuntu1.2
debug1: match: OpenSSH_4.7p1 Debian-8ubuntu1.2 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-8ubuntu1.2
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
Warning: Permanently added 'zimbra.domain.com,10.100.100.2' (RSA) to the list of known hosts.
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /opt/zimbra/.ssh/identity
debug1: Trying private key: /opt/zimbra/.ssh/id_rsa
debug1: Trying private key: /opt/zimbra/.ssh/id_dsa
debug1: Next authentication method: password
zimbra@zimbra.domain.com's password:

(again with domain obfuscate to domain.com for no very good reason )

I'm going to reboot the server and see what happens to the error and the logs.

[Dirk]

hmm. Looks like I may have been on a bum steer there. That command asks for a password on a known good zimbra server too.

Plus, after the reboot the certification section of the admin panel works without error, it still wont let me just add the cert though, so I'll generate a CSR trying to remember what I used last time and see if the old cert will import!

I should have rebooted the server as soon as I noticed it was not behaving as expected, sorry about that.