[SOLVED] zmbackupquery unknown document failure

[jmarriott]

Hi all,

I've just moved a Zimbra install between an old install and a fresh install of Ubuntu 8.04. My method was to stop Zimbra, rsync the entire /opt/zimbra directory to external storage, reinstall the OS, clean install of the same version of Zimbra (same arch too), start it, stop it, move it to zimbra.fresh, copy the old Zimbra install in its place and start it.

The move seems to have gone without a hitch apart from one thing, backups don't work!

If I run zmbackupquery or try to use the admin Web UI to investigate backups I get this in mailbox.log:

2009-08-28 09:46:06,251 INFO  [btpool0-3331] [ip=127.0.0.1;] soap - AuthRequest
2009-08-28 09:46:06,311 INFO  [btpool0-3331] [name=zimbra;ip=127.0.0.1;] soap - BackupQueryRequest
2009-08-28 09:46:06,311 WARN  [btpool0-3331] [name=zimbra;ip=127.0.0.1;] SoapEngine - cannot dispatch request
com.zimbra.common.service.ServiceException: unknown document: BackupQueryRequest
ExceptionId:btpool0-3331:1251449166311:ac119bef2994a858
Code:service.UNKNOWN_DOCUMENT
	at com.zimbra.common.service.ServiceException.UNKNOWN_DOCUMENT(ServiceException.java:267)
	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:342)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:286)
	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:160)
	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:275)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:187)
	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:145)
	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: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)

Any ideas anyone? I found a thread about a related error here but the suggested fix doesn't seem to work for me, although I've not restart Zimbra yet because I can't do it during business hours.

Input much appreciated!

Thanks,
Jon

[phoenix]

Originally Posted by jmarriott

I've just moved a Zimbra install between an old install and a fresh install of Ubuntu 8.04. My method was to stop Zimbra, rsync the entire /opt/zimbra directory to external storage, reinstall the OS, clean install of the same version of Zimbra (same arch too), start it, stop it, move it to zimbra.fresh, copy the old Zimbra install in its place and start it.

Did you follow any of the 'how to' articles for migrating to another server? Did you also create the new server with the same FQDN and point the DNS A & MX records at it?

[jmarriott]

Originally Posted by phoenix

Did you follow any of the 'how to' articles for migrating to another server? Did you also create the new server with the same FQDN and point the DNS A & MX records at it?

Hi Phoenix, thanks for replying.

I didn't follow any 'how to' articles, no.

The server has the same IP, FQDN, DNS A record and OS. The MX records were never pointed at it and still are not. Mail delivery is working fine though.

[phoenix]

Originally Posted by jmarriott

The MX records were never pointed at it and still are not.

Why not?

Originally Posted by jmarriott

Mail delivery is working fine though.

You do surprise me with that statement.

What's the output of the following:

su - zimbra
zmcontrol -v

Please update your forum profile with the output of that command.

[jmarriott]

Originally Posted by phoenix

Why not? You do surprise me with that statement.

What's the output of the following:

su - zimbra
zmcontrol -v

Please update your forum profile with the output of that command.

I use a border relay that forward mail to Zimbra. Profile updated as requested.

[jmarriott]

After a Zimbra restart the fix in the thread I mentioned seems to have taken effect and it's working now.

Bill, you seemed surprised that my new server works at all? Is there something specific that should be broken or that I should check?

Thanks,
Jon