Results 1 to 8 of 8

Thread: 4.5.6 to 5.0 RC1 update on debian: jetty broken: version mismatch

  1. #1
    Join Date
    Aug 2007
    Posts
    13
    Rep Power
    7

    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

  2. #2
    jholder's Avatar
    jholder is offline Former Zimbran
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    20

    Default

    Can you restore to a backup?

  3. #3
    Join Date
    Aug 2007
    Posts
    13
    Rep Power
    7

    Arrow

    Yes of course, but this won't give me 5.0 RC1, rather 4.5.6 again.

    I have a simple setup. One host for everything.
    How do I upgrade? Just untar, then ./install.sh and
    this should be enough, right? So the data structure, whatever where and
    what this is, should be updated automatically?

    Thanks for your quick answer, jholder.

  4. #4
    jholder's Avatar
    jholder is offline Former Zimbran
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    20

    Default

    Quite honestly, restoring would be your best option.

    Follow the restore instructions in the wiki, and before you upgrade, backup again

    it will probably fail, but when it does, you'll be able to get us the error and logs.

    jh

  5. #5
    Join Date
    Aug 2007
    Posts
    13
    Rep Power
    7

    Lightbulb got it.

    Okay, I figured the error out.

    Bevore I upgraded debian to 4.0 from 3.1 I removed the zimbra-packages to have a clean "debian only" system.

    Of course, the install script did not propose to upgrade anymore. That's why I fiddled about the install script that the packages "seemed to be" installed already. However, the install-script now obviously relies on the information from the systems' package management system and did not roll out the upgrade steps completely (I think I changed it that way that 5 RC1 seems to be installed). This is definetly my fault, but maybe it would be cool to have a litte check in the install script that inspects /opt/zimbra and does not rely on dpkg?

    For now I will reinstall the correct 4.5.6 debs and start over again ;-)

    -ck

  6. #6
    dijichi2 is offline OpenSource Builder & Moderator
    Join Date
    Oct 2005
    Posts
    1,176
    Rep Power
    11

    Default

    i had same problem on debian 4 without touching the OS. I had been running the ubuntu6 version of zimbra on debian 4, then attempted to upgrade to the debian4 version of zimbra and it gave the same results. I think others found the same thing. I wish I could have attempted to debug and help fix it but it was live mailserver so couldn't risk.

  7. #7
    Join Date
    Aug 2007
    Posts
    13
    Rep Power
    7

    Arrow problem with debian 3.1 -> 4.0

    This is getting really messy...

    I can manually install the zcs-4.5.6.debs and restore the backup (4.5.6) but this won't start on debian 4.0 since it is not supported. When I try to upgrade to 5 RC1 it comes to the point where he restores the old config - but everything is empty (LDAPHOST= and so on)

    Since he cannot figure out which version I am using (the 4.5.6 scripts seem to fail on deb 4.0), the upgrade fails (Upgrading from to 5.0.0_RC1) ... UPGRADE FAILED .. end of the show

    I think this is related to zmcontrol not working properly as it also reports Version UNKNOWN (zmcontrol -v) [the zcs-4.5.6 version run on deb-4.0]

    Is there a possibility to do a clean install of 5.0 RC1 and then import the old data?

    ldap, mysql, whatelse?

    Or do you have any other ideas?

  8. #8
    dijichi2 is offline OpenSource Builder & Moderator
    Join Date
    Oct 2005
    Posts
    1,176
    Rep Power
    11

    Default

    you could try installing 4.5.6 by altering /etc/debian_release to 3.1 or using ubuntu6 binary.

    the debian4 binary seems to be broken. I used the ubuntu6 binary on debian 4 which works great. i don't know why the need for all these versions...
    Last edited by dijichi2; 11-02-2007 at 11:39 PM.

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. 4.0.4 to 4.5.6 upgrade failed in network edition
    By chenthil in forum Administrators
    Replies: 1
    Last Post: 08-27-2007, 09:36 AM
  2. Update Received Date in Folder-Listing
    By Oswald-Kolle in forum Installation
    Replies: 25
    Last Post: 08-21-2007, 04:21 PM

Posting Permissions

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