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:
|
Originally Posted by KevinH 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. |