Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: [SOLVED] Zimbra 6.0.7 to 7.1.0 - I Cant Upgrade version

  1. #1
    Som30ne is offline Junior Member
    Join Date
    May 2011
    Posts
    6
    Rep Power
    4

    Default [SOLVED] Zimbra 6.0.7 to 7.1.0 - I Cant Upgrade version

    Hi.

    I have just (well, for the last 6 hours) tried to upgrade my ZCS from V6.0.7 to 7.1.0.
    At first - it failed because I didnt downgrade my dpkg.
    After I did downgrade my dpkg and installed ZCS, mysql.server did not start (something to do with plugins),
    so I searched the net and foud that I had to add a few lines to my.cnf.

    Now I get the following:
    Code:
    2011-05-07 15:49:31,316 INFO  [main] [] system - Setting mysql connector property: maxActive=100
    2011-05-07 15:49:31,339 INFO  [main] [] system - Setting mysql connector property: maxActive=100
    2011-05-07 15:49:33,814 ERROR [main] [] Versions - DB Version Mismatch: ours="65" from DB="64"
    2011-05-07 15:49:33,814 FATAL [main] [] system - Data version mismatch.  Reinitialize or upgrade the backend data store.
    I tried re-installing ZCS 7.1.0 - and got:
    Code:
    Starting MySql... Done
    I Can't upgrade version
    No version was specified.

    I tried downgrading back to 6.0.7 - but got a message that a downgrade is not possible,

    --- I dont want to uninstall ZCS, since I dont have a backup, and I dont remember exactly what I changed (I enabeld POP before SMTP, and userd pasword for ISPs mail relay,
    and probably some other settings)

    How can I do the DB upgrade ?

    Thanks

  2. #2
    Som30ne is offline Junior Member
    Join Date
    May 2011
    Posts
    6
    Rep Power
    4

    Default

    Quote Originally Posted by Som30ne View Post
    Hi.

    I have just (well, for the last 6 hours) tried to upgrade my ZCS from V6.0.7 to 7.1.0.
    At first - it failed because I didnt downgrade my dpkg.
    After I did downgrade my dpkg and installed ZCS, mysql.server did not start (something to do with plugins),
    so I searched the net and foud that I had to add a few lines to my.cnf.

    Now I get the following:
    Code:
    2011-05-07 15:49:31,316 INFO  [main] [] system - Setting mysql connector property: maxActive=100
    2011-05-07 15:49:31,339 INFO  [main] [] system - Setting mysql connector property: maxActive=100
    2011-05-07 15:49:33,814 ERROR [main] [] Versions - DB Version Mismatch: ours="65" from DB="64"
    2011-05-07 15:49:33,814 FATAL [main] [] system - Data version mismatch.  Reinitialize or upgrade the backend data store.
    I tried re-installing ZCS 7.1.0 - and got:
    Code:
    Starting MySql... Done
    I Can't upgrade version
    No version was specified.

    I tried downgrading back to 6.0.7 - but got a message that a downgrade is not possible,

    --- I dont want to uninstall ZCS, since I dont have a backup, and I dont remember exactly what I changed (I enabeld POP before SMTP, and userd pasword for ISPs mail relay,
    and probably some other settings)

    How can I do the DB upgrade ?

    Thanks
    Oh, well, I looked a bit more and saw that there are zmsetup.pl, and zmupgrade.pl
    I investigared these files, and did a bit messing here and there.

    Finally made them to hard-coded identify prevVersion to be 6.0.7_GA.
    It upgraded and started working,
    but of-course I lost some/most/all (I dont know yet) of my configuration settings.
    (didnt seem to lose any mail though - which is a bit of a comfort . . .)

    I re-set the pop-before-smtp, and the password protected mail-relay.

    Hope that this will end this saga.
    (Dont mark it as "solved" just yet)

  3. #3
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,495
    Rep Power
    56

    Default

    Quote Originally Posted by Som30ne View Post
    ....but of-course I lost some/most/all (I dont know yet) of my configuration settings.
    Configuration changes you make are not preserved across upgrades.

    Quote Originally Posted by Som30ne View Post
    (didnt seem to lose any mail though - which is a bit of a comfort . . .)
    There's no reason why you should but at this stage you should have taken a backup of the /opt/zimbra directory structure before continuing the upgrade.

    Quote Originally Posted by Som30ne View Post
    (Dont mark it as "solved" just yet)
    It's you that marks the thread as Solved.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  4. #4
    Som30ne is offline Junior Member
    Join Date
    May 2011
    Posts
    6
    Rep Power
    4

    Default

    Quote Originally Posted by phoenix View Post
    Configuration changes you make are not preserved across upgrades.
    Really ?
    That's very annoying.
    (And if I recall correctly, when I upgraded from 6.0.6 to 6.0.7 it saved my settings . . . but maybe Im mistaken)

    Quote Originally Posted by phoenix View Post
    There's no reason why you should but at this stage you should have taken a backup of the /opt/zimbra directory structure before continuing the upgrade.
    Well ofcourse I did by then (only of the zimbra/db/ since that was the problematic area),
    but - what good would it have done if It is in the "old" format ? I would still not be able to use it without the conversion, that did not work . . . :-)

    Quote Originally Posted by phoenix View Post
    It's you that marks the thread as Solved.
    Ok, I didnt know that . . .

  5. #5
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,495
    Rep Power
    56

    Default

    Quote Originally Posted by Som30ne View Post
    Really ?
    That's very annoying.
    (And if I recall correctly, when I upgraded from 6.0.6 to 6.0.7 it saved my settings . . . but maybe Im mistaken)
    That's always been the case but I'm talking about modifications to configuration files here.

    Quote Originally Posted by Som30ne View Post
    Well ofcourse I did by then (only of the zimbra/db/ since that was the problematic area),
    but - what good would it have done if It is in the "old" format ? I would still not be able to use it without the conversion, that did not work . . . :-)
    If you backed up the directory structure I suggested and a disaster happened and you lost some or all of your mail you'd have a backup to recover into a new server.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  6. #6
    Som30ne is offline Junior Member
    Join Date
    May 2011
    Posts
    6
    Rep Power
    4

    Default

    Quote Originally Posted by phoenix View Post
    That's always been the case but I'm talking about modifications to configuration files here.
    If you say so, Id believe you (My memory is a bit problematic ), and it was a long time ago

    Quote Originally Posted by phoenix View Post
    If you backed up the directory structure I suggested and a disaster happened and you lost some or all of your mail you'd have a backup to recover into a new server.
    But to my understanding - At that stage, I had a mismatching versions of ZCS and it's DB,
    so a restore would still bring the mismatching with it - and we get nowhere
    (Or am I wrong ? and if so - how ?)

    PS
    Many Thanks for your reply(s)

  7. #7
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,495
    Rep Power
    56

    Default

    Quote Originally Posted by Som30ne View Post
    But to my understanding - At that stage, I had a mismatching versions of ZCS and it's DB,
    so a restore would still bring the mismatching with it - and we get nowhere
    (Or am I wrong ? and if so - how ?)
    First, you did find out how to bypass the problem and continue the upgrade. Second, assuming you were stuck at that stage and lost either the email and/or the database your email is still available in your backup and you can inject that into a new version of Zimbra - it' takes some effort but zmlmtpinject will do it. It depends how important your old email is and whether you wan to preserve it.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  8. #8
    Som30ne is offline Junior Member
    Join Date
    May 2011
    Posts
    6
    Rep Power
    4

    Default

    Quote Originally Posted by phoenix View Post
    First, you did find out how to bypass the problem and continue the upgrade. Second, assuming you were stuck at that stage and lost either the email and/or the database your email is still available in your backup and you can inject that into a new version of Zimbra - it' takes some effort but zmlmtpinject will do it. It depends how important your old email is and whether you wan to preserve it.
    I overcame the problem, by hacking . . . but - well, that's sort of a way too

    I did not know there was a way to import old mail to new installation.
    Now I know.

    Again - many thanks.

  9. #9
    udfc is offline Beginner Member
    Join Date
    May 2011
    Posts
    1
    Rep Power
    4

    Default Can I get a copy of your changes ...

    I am having the same problem you described. You said you edited zmsetup.pl and zmupgrade.pl.

    Could you share what changes you made. I would like to see if your approach fixes my problems.

    Thank You
    Alan

  10. #10
    Som30ne is offline Junior Member
    Join Date
    May 2011
    Posts
    6
    Rep Power
    4

    Default

    Quote Originally Posted by udfc View Post
    I am having the same problem you described. You said you edited zmsetup.pl and zmupgrade.pl.

    Could you share what changes you made. I would like to see if your approach fixes my problems.

    Thank You
    Alan
    Im attaching the modified files here, with ".txt" added to the extension -
    since .pl and .pm is not accepted by the server here.
    (After modifying - I ran zmsetup.pl)

    The diff is (.sav is the original file):
    Code:
     diff zmsetup.pl zmsetup.pl.sav
    122c122
    < my $prevVersion = "6.0.7_GA";
    ---
    > my $prevVersion = "";
    158d157
    < $prevVersion = "6.0.7_GA";
    Code:
    diff zmupgrade.pm zmupgrade.pm.sav
    217c217
    <   "7.1.0_GA" => \&upgrade607GA,
    ---
    >   "7.1.0_GA" => \&upgrade710GA,
    340d339
    <     main::progress("Testing start is: $startVersion");
    343,344d341
    <     $startVersion="6.0.7_GA";
    < main::progress("Testing2 start is: $startVersion");
    355,358c352
    <   my $needMysqlUpgrade = 0;
    <
    < $startVersion="6.0.7_GA";
    <
    ---
    >   my $needMysqlUpgrade = 0;
    383,384d376
    <
    <     main::progress("\nfinally start version is: $startVersion\n");
    Hope this helps.

    ** I take no responsibility as for the outcome
    The fact that it worked for me, and did not mess up the DB,
    is not a guarantee that it will work for you.
    Attached Files Attached Files

Page 1 of 2 12 LastLast

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Replies: 6
    Last Post: 03-14-2011, 04:21 AM
  2. Debian - Upgrade from 4.5.6
    By magikman in forum Installation
    Replies: 1
    Last Post: 01-19-2008, 12:59 PM
  3. Replies: 22
    Last Post: 12-02-2007, 05:05 PM
  4. 4.5 Upgrade failure
    By brained in forum Installation
    Replies: 9
    Last Post: 03-03-2007, 03:30 PM
  5. dspam logrotate errors
    By michaeln in forum Users
    Replies: 7
    Last Post: 02-19-2007, 12:45 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
  •