M1 -> M2 Upgrade Scripts
-
- Ambassador
- Posts: 4558
- Joined: Fri Sep 12, 2014 9:52 pm
M1 -> M2 Upgrade Scripts
Thanks to Marcmac we now have upgrade scripts(released under the terms of the MPL), which are attached to this message.
Here are the steps to upgrade if the new M2 build has not been installed:
1. As the zimbra user:
2. untar the upgrade.tgz file (tar xzvf upgrade.tgz)
3. find the upgrade script (cd Upgrade)
4. execute the upgrade script (upgradeM1M2.pl)
5. Install the new build. Answer "Y" to do you wish to upgrade.
6. Done!
If the new M2 build has already been installed:
1. As the zimbra user:
2. stop the zimbra software (zmcontrol shutdown)
3. make sure it stopped (ps -ef | grep zimbra)
4. untar the upgrade.tgz file (tar xzvf upgrade.tgz)
5. find the upgrade script (cd Upgrade)
6. execute the upgrade script (upgradeM1M2.pl)
7. start the zimbra software (zmcontrol start)
8. Done!
Notes:
The following error may be displayed during the install.sh process: "M2: integer expression expected". This error can be ignored. The install will complete normally.
upgrade.tgz
Here are the steps to upgrade if the new M2 build has not been installed:
1. As the zimbra user:
2. untar the upgrade.tgz file (tar xzvf upgrade.tgz)
3. find the upgrade script (cd Upgrade)
4. execute the upgrade script (upgradeM1M2.pl)
5. Install the new build. Answer "Y" to do you wish to upgrade.
6. Done!
If the new M2 build has already been installed:
1. As the zimbra user:
2. stop the zimbra software (zmcontrol shutdown)
3. make sure it stopped (ps -ef | grep zimbra)
4. untar the upgrade.tgz file (tar xzvf upgrade.tgz)
5. find the upgrade script (cd Upgrade)
6. execute the upgrade script (upgradeM1M2.pl)
7. start the zimbra software (zmcontrol start)
8. Done!
Notes:
The following error may be displayed during the install.sh process: "M2: integer expression expected". This error can be ignored. The install will complete normally.
upgrade.tgz
M1 -> M2 Upgrade Scripts
Our upgrade seemed to go ok, everything appeared to be imported, but upon stopping and trying to start zcs on the primary server, we're getting:
zmcontrol -v
Release 3.0.0_M2_744.RHEL4_20051116095201 installed Fri Nov 18 12:45:05 2005
[zimbra@mail1 ~]$ zmcontrol startup
Host xxxxx.test.uwm.edu
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException xxxxx.test.uwm.edu:389)
Our slave servers that auth off the primary server are also throwing errors. I don't see any way to just fire up the LDAP server to try to troubleshoot this more.. Any ideas?
Dan
[quote user="14319KevinH"]Thanks to Marcmac we now have upgrade scripts, which are attached to this message.
Here are the steps to upgrade if the new M2 build has not been installed:
1. As the zimbra user:
2. untar the upgrade.tgz file (tar xzvf upgrade.tgz)
3. find the upgrade script (cd Upgrade)
4. execute the upgrade script (upgradeM1M2.pl)
5. Install the new build. Answer "Y" to do you wish to upgrade.
6. Done!
If the new M2 build has already been installed:
1. As the zimbra user:
2. stop the zimbra software (zmcontrol shutdown)
3. make sure it stopped (ps -ef | grep zimbra)
4. untar the upgrade.tgz file (tar xzvf upgrade.tgz)
5. find the upgrade script (cd Upgrade)
6. execute the upgrade script (upgradeM1M2.pl)
7. start the zimbra software (zmcontrol start)
8. Done!
Notes:
The following error may be displayed during the install.sh process: "M2: integer expression expected". This error can be ignored. The install will complete normally.[/QUOTE]
zmcontrol -v
Release 3.0.0_M2_744.RHEL4_20051116095201 installed Fri Nov 18 12:45:05 2005
[zimbra@mail1 ~]$ zmcontrol startup
Host xxxxx.test.uwm.edu
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException xxxxx.test.uwm.edu:389)
Our slave servers that auth off the primary server are also throwing errors. I don't see any way to just fire up the LDAP server to try to troubleshoot this more.. Any ideas?
Dan
[quote user="14319KevinH"]Thanks to Marcmac we now have upgrade scripts, which are attached to this message.
Here are the steps to upgrade if the new M2 build has not been installed:
1. As the zimbra user:
2. untar the upgrade.tgz file (tar xzvf upgrade.tgz)
3. find the upgrade script (cd Upgrade)
4. execute the upgrade script (upgradeM1M2.pl)
5. Install the new build. Answer "Y" to do you wish to upgrade.
6. Done!
If the new M2 build has already been installed:
1. As the zimbra user:
2. stop the zimbra software (zmcontrol shutdown)
3. make sure it stopped (ps -ef | grep zimbra)
4. untar the upgrade.tgz file (tar xzvf upgrade.tgz)
5. find the upgrade script (cd Upgrade)
6. execute the upgrade script (upgradeM1M2.pl)
7. start the zimbra software (zmcontrol start)
8. Done!
Notes:
The following error may be displayed during the install.sh process: "M2: integer expression expected". This error can be ignored. The install will complete normally.[/QUOTE]
-
- Ambassador
- Posts: 4558
- Joined: Fri Sep 12, 2014 9:52 pm
M1 -> M2 Upgrade Scripts
/opt/zimbra/bin/ldap is the start/stop script for LDAP.
M1 -> M2 Upgrade Scripts
[zimbra@ghostrider Upgrade]$ ./upgradeM1M2.pl
Fri Nov 18 14:28:58 2005: Finding installed version of ZCS
Fri Nov 18 14:28:58 2005: Stopping zimbra services
Fri Nov 18 14:29:08 2005: Checking mysql status
Fri Nov 18 14:29:09 2005: SELECT value FROM config WHERE name = 'db.version'
sh: mysql.out: No such file or directory
Error while running 'mysql --user=zimbra --password=6R9sU0aUeWuBtK4oqaTbyazHSCYr --database=zimbra --batch --skip-column-names'. at scripts/Migrate.pm line 101.
[zimbra@ghostrider Upgrade]
is what I get
Fri Nov 18 14:28:58 2005: Finding installed version of ZCS
Fri Nov 18 14:28:58 2005: Stopping zimbra services
Fri Nov 18 14:29:08 2005: Checking mysql status
Fri Nov 18 14:29:09 2005: SELECT value FROM config WHERE name = 'db.version'
sh: mysql.out: No such file or directory
Error while running 'mysql --user=zimbra --password=6R9sU0aUeWuBtK4oqaTbyazHSCYr --database=zimbra --batch --skip-column-names'. at scripts/Migrate.pm line 101.
[zimbra@ghostrider Upgrade]
is what I get
M1 -> M2 Upgrade Scripts
The zimbra user must be able to write to the directory in which you've got the upgrade script.
M1 -> M2 Upgrade Scripts
Duh me. I was looking for some zmldapctl like everything else has..
OK. I fired up ldap manually, then ran zmcontrol start and everything works on both servers. Bug in the startup script?
Dan
[quote user="14319KevinH"]/opt/zimbra/bin/ldap is the start/stop script for LDAP.[/QUOTE]
OK. I fired up ldap manually, then ran zmcontrol start and everything works on both servers. Bug in the startup script?
Dan
[quote user="14319KevinH"]/opt/zimbra/bin/ldap is the start/stop script for LDAP.[/QUOTE]
M1 -> M2 Upgrade Scripts
I upgraded using the scripts and all went well. (After I figured out you had to use a directory that zimbra owned) This was from M1 with no M2 install. Thankyou for the scripts -- you saved me some work! Anyway, I ran the scripts, then upgraded to M2. The server starts up just fine with no errors like DanCody had.
I do have one question though... My admin panel shows "Your Zimbra Network trial expires on 1/17/06". I did not intall the network version. Will my M2 Open Source version expire on 1/17/06?
- Rob
I do have one question though... My admin panel shows "Your Zimbra Network trial expires on 1/17/06". I did not intall the network version. Will my M2 Open Source version expire on 1/17/06?
- Rob
M1 -> M2 Upgrade Scripts
Nope - that's a bug in the upgrade script (and the server) - you can disregard the trial expiration date.
M1 -> M2 Upgrade Scripts
Does the upgrade script have to be in the same dir as the untar-ed upgrade download?
Also, all I do is run the upgrade script only?
thx!
Also, all I do is run the upgrade script only?
thx!
M1 -> M2 Upgrade Scripts
No, it doesn't have to be in the same directory - any directory, as long as zimbra can write to that dir.
And no, it doesn't perform the software upgrade, just prepares the db and config for it (or fixes the db and config after an upgrade) - so you'll have to run install.sh for M2 at some point.
(Next release, this will all be one step - I promise )
And no, it doesn't perform the software upgrade, just prepares the db and config for it (or fixes the db and config after an upgrade) - so you'll have to run install.sh for M2 at some point.
(Next release, this will all be one step - I promise )