View Single Post
  #1 (permalink)  
Old 11-01-2007, 04:27 PM
christian.kieft christian.kieft is offline
Member
 
Posts: 13
Question 4.5.6 to 5.0 RC1 update on debian: jetty broken: version mismatch

Hello,

until today I used the 4.5.6 OpenSource version with debian sarge (3.1).
Now, I upgraded to debian etch (4.0) and 5.0RC1 OpenSource.

System upgrade worked just fine, but now I am havin trouble with Zimbra.

First, postfix stoped to work. It took me 3 hours to figure out that postfix_version was not updated from 2.2.9 to 2.4.3.3 in zmlocalconfig.

But now I am facing the problem, that 'zmcontrol status' sais that everything is up and
running although i cannot even run 'zmprov':

Code:
zimbra@zimbra $ zmpov

ERROR: zclient.IO_ERROR (invoke cannot determine soap protocol in reply: Error 503 SERVICE_UNAVAILABLE

HTTP ERROR: 503

SERVICE_UNAVAILABLE

RequestURI=/service/admin/soap/

Powered by jetty://

, server: localhost) (cause: com.zimbra.common.soap.SoapParseException cannot determine soap protocol in reply: Error 503 SERVICE_UNAVAILABLE

HTTP ERROR: 503

SERVICE_UNAVAILABLE

RequestURI=/service/admin/soap/

Powered by jetty://

)
in mailbox.log:
Code:
2007-11-01 22:44:26,299 INFO  [main] [] soap - Adding service IMService to AdminServ
let
2007-11-01 22:44:26,299 INFO  [main] [] misc - version=5.0.0_RC1_1538.DEBIAN4.0 rele
ase=20071002235825 builddate=20071003-0002 buildhost=build-debian-etch
2007-11-01 22:44:26,300 INFO  [main] [] misc - LANG environment is set to: C
2007-11-01 22:44:26,300 ERROR [main] [] Versions - DB Version Mismatch: ours="47" fr
om DB="36"
2007-11-01 22:44:26,300 FATAL [main] [] soap - Unable to start servlet
java.lang.RuntimeException: Data version mismatch.  Reinitialize or upgrade the back
end data store.
        at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:87)
        at com.zimbra.soap.SoapServlet.init(SoapServlet.java:107)
        at javax.servlet.GenericServlet.init(GenericServlet.java:241)
        at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:43
3)
Can it be that the update process did not complete (but I cannot remember any errors
during / after running ./install.sh)? This would explain why the postfix_version wasn't updated, wouldn't it?

Anyhow, how do I reinitialize or upgrade the backend data store?

Thanks in advance,
Christian
Reply With Quote