M2 -> M3 upgrade

[chanck]

Can I upgrade directly from M1 to M3?

In fact, I have tried it and found it was not smooth in my environment. Any idea?

Thomas

=====LOG====
Installing packages

zimbra-core......zimbra-core-3.0.0_M3_436.FC3-20060106155057.i386.rpm...done
zimbra-ldap......zimbra-ldap-3.0.0_M3_436.FC3-20060106155057.i386.rpm...done
zimbra-logger......zimbra-logger-3.0.0_M3_436.FC3-20060106155057.i386.rpm...done
zimbra-mta......zimbra-mta-3.0.0_M3_436.FC3-20060106155057.i386.rpm...done
zimbra-snmp......zimbra-snmp-3.0.0_M3_436.FC3-20060106155057.i386.rpm...done
zimbra-store......zimbra-store-3.0.0_M3_436.FC3-20060106155057.i386.rpm...done
zimbra-apache......zimbra-apache-3.0.0_M3_436.FC3-20060106155057.i386.rpm...done
zimbra-spell......zimbra-spell-3.0.0_M3_436.FC3-20060106155057.i386.rpm...done

Setting defaults from saved config in /opt/zimbra/.saveconfig/config.save
HOSTNAME=mailsrv.safpsrv.gov.mo
LDAPHOST=mailsrv.safpsrv.gov.mo
LDAPPORT=389
SNMPTRAPHOST=mailsrv.safpsrv.gov.mo
SMTPSOURCE=none
SMTPDEST=none
SNMPNOTIFY=0
SMTPNOTIFY=0
LDAPROOTPW=1GrFpFdMJCCmc3fAUE3x3tUZ
LDAPZIMBRAPW=kiWOSLhSHzMOGxN_OCka11gvSS
Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
chown: cannot access `/opt/zimbra/conf/slapd.crt': No such file or directory
Operations logged to /tmp/zmsetup.log.6361
Setting defaults...Setting defaults from existing config...Warning: null valued key 'mysql_logger_root_password'
Done
Checking for port conflicts
Starting ldap...Done
Setting defaults from ldap...ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException mailsrv.safpsrv.gov.mo:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException mailsrv.safpsrv.gov.mo:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException mailsrv.safpsrv.gov.mo:389)
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException mailsrv.safpsrv.gov.mo:389)
Done
Checking ldap on localhost:389...FAILED
Checking ldap on localhost:389...FAILED

Main menu

1) Hostname: mailsrv.safpsrv.gov.mo
2) Ldap master host: mailsrv.safpsrv.gov.mo
3) Ldap port: 389
4) Ldap password: set
5) zimbra-ldap: Enabled
6) zimbra-store: Enabled
7) zimbra-mta: Enabled
8) zimbra-snmp: Enabled
9) zimbra-logger: Enabled
10) zimbra-spell: Enabled
r) Start servers after configuration yes
s) Save config to file
x) Expand menu
q) Quit

Address unconfigured (**) items or correct ldap configuration (? - help)
Checking ldap on localhost:389...FAILED
Checking ldap on localhost:389...FAILED

[marcmac]

Exactly which version of M1? This may not work smoothly - it looks like you've lost the ldap password - you'll want to set that and re-run zmsetup.pl

[chanck]

Thank you. Since it is just testing period, I gave up the tracking and reinstall it. But I will recreate it again later because I will test the migration script again to ensure that it is smooth for my environment.

Originally Posted by marcmac

Exactly which version of M1? This may not work smoothly - it looks like you've lost the ldap password - you'll want to set that and re-run zmsetup.pl

[slayer]

Still generating lots of

bin/bash /bin/unicode_start latarcyrheb-sun16

which is eating all my memory. I never experienced this with M2.

Originally Posted by marcmac

Try export LANG=C before you run the script

[rjedge]

Originally Posted by marcmac

Exactly which version of M1? This may not work smoothly - it looks like you've lost the ldap password - you'll want to set that and re-run zmsetup.pl

I ran into the same thing when upgrading from M2 to M3 but I don't recall the M2 installation asking for or setting an ldap password. Anyway, I performed the steps you suggested and although the installation says it succeeded when I run zmcontrol start I get the following:

[zimbra@zimbra root]$ zmcontrol start
Host zimbra.twu.ca
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.CommunicationException zimbra.twu.ca:389)

Now when you said the ldap password needed to be set is this though zmldappasswd or with the --root option?

I forgot to add the setup log out put. Here it is:


[zimbra@zimbra root]$ zmsetup.pl
bash: zmsetup.pl: command not found
[zimbra@zimbra root]$ perl zmsetup.pl
Can't open perl script "zmsetup.pl": Permission denied.
Use -S to search $PATH for it.
[zimbra@zimbra root]$ cd ..
[zimbra@zimbra /]$ perl zmsetup.pl
Can't open perl script "zmsetup.pl": No such file or directory.
Use -S to search $PATH for it.
[zimbra@zimbra /]$ exit
exit
[root@zimbra ~]# perl zmsetup.pl
Can't open perl script "zmsetup.pl": No such file or directory.
Use -S to search $PATH for it.
[root@zimbra ~]# locate zmsetup.pl
warning: locate: warning: database /var/lib/slocate/slocate.db' is more than 8 days old
/opt/zimbra/libexec/zmsetup.pl
[root@zimbra ~]# /opt/zimbra/libexec/zmsetup.pl
Operations logged to /tmp/zmsetup.log.21507
Setting defaults...Setting defaults from existing config...Warning: null valued key 'mysql_logger_root_password'
Done
Checking for port conflicts
Starting ldap...Done
Setting defaults from ldap...Done
Checking ldap on localhost:389...Success

Main menu

1) Hostname: zimbra.twu.ca
2) Ldap master host: zimbra.twu.ca
3) Ldap port: 389
4) Ldap password: set
5) zimbra-ldap: Enabled
6) zimbra-store: Enabled
7) zimbra-mta: Enabled
8) zimbra-snmp: Enabled
9) zimbra-logger: Enabled
10) zimbra-spell: Enabled
r) Start servers after configuration yes
s) Save config to file
x) Expand menu
q) Quit

*** CONFIGURATION COMPLETE - press 'a' to apply
Select from menu, or press 'a' to apply config (? - help) s^Ha
Invalid selection! - press any key to continue


Checking ldap on localhost:389...Success

Main menu

1) Hostname: zimbra.twu.ca
2) Ldap master host: zimbra.twu.ca
3) Ldap port: 389
4) Ldap password: set
5) zimbra-ldap: Enabled
6) zimbra-store: Enabled
7) zimbra-mta: Enabled
8) zimbra-snmp: Enabled
9) zimbra-logger: Enabled
10) zimbra-spell: Enabled
r) Start servers after configuration yes
s) Save config to file
x) Expand menu
q) Quit

*** CONFIGURATION COMPLETE - press 'a' to apply
Select from menu, or press 'a' to apply config (? - help) a
Save configuration data to a file? [Yes]
Save config in file: [/opt/zimbra/config.21507]
Saving config in /opt/zimbra/config.21507...Done
The system will be modified - continue? [No] Yes
Operations logged to /tmp/zmsetup.log.21507
Setting local config values...Done
Creating SSL certificate...Done
Starting ldap...Done
Saving CA in ldap...Done
Installing SSL certificate...Done
Creating server entry for zimbra.twu.ca...Done
Setting spell check URL...Done
Setting service ports on zimbra.twu.ca...Done
Adding zimbra.twu.ca to zimbraMailHostPool in default COS...Done
Installing zimlets... com_zimbra_bugz... com_zimbra_sforce... com_zimbra_domainadmin... com_zimbra_phone... com_zimbra_po... com_zimbra_amzn... com_zimbra_url... com_zimbra_ymaps... com_zimbra_tracking... Done
Setting MTA auth host...Done
Initializing mta config...Done
Configuring SNMP...Done
Setting services on zimbra.twu.ca...Done
Setting up zimbra crontab...cron/zimbra: Permission denied
ERROR: Backup cron corrupted - rebuilding

Done
Warning: null valued key 'trial_expiration_date'
Starting servers...Done.


Operations logged to /tmp/zmsetup.log.21507


Configuration complete - press return to exit


[root@zimbra ~]# less /tmp/zmsetup.log.21507
Setting defaults...Setting defaults from existing config...Getting local config
zimbra_server_hostname
Getting local config ldap_url
Getting local config ldap_port
Getting local config ldap_host
Getting local config ldap_root_password
Getting local config mysql_root_password
Getting local config mysql_logger_root_password
Getting local config zimbra_mysql_password
Getting local config zimbra_logger_mysql_password
Done
Checking for port conflicts
Starting ldap...*** Running as zimbra user: /opt/zimbra/openldap/sbin/slapindex
-f /opt/zimbra/conf/slapd.conf
*** Running as zimbra user: ldap start
*** Running as zimbra user: zmldapapplyldif
Done
Setting defaults from ldap...Done
Checking ldap on localhost:389...Success
Checking ldap on localhost:389...Success
Saving config in /opt/zimbra/config.21507...Done
Operations logged to /tmp/zmsetup.log.21507
Setting local config values...Setting local config zimbra_server_hostname to zim
/tmp/zmsetup.log.21507

[marcmac]

zmldappasswd --root is the correct command.

On install, we auto-gen an ldap password, which you can change.

It's also likely that the sql password is gone - after you start, run
su - zimbra
mysql
use zimbra
show tables

If it doesn't let you in, you're going to have to reset the sql root password:
stop sql: mysql.server stop
Check /opt/zimba/bin/mysql.server for the syntax of the start line (mysqld_safe), and run that manually, adding the arg "--skip-grant-tables"
/opt/zimbra/mysql/bin/mysql -S /opt/zimbra/db/mysql.sock -u root mysql
update user set password=PASSWORD('new_pass') where user='root';
update user set password=PASSWORD('new_pass') where user='zimbra';
flush privileges;
exit

zmlocalconfig -e -f mysql_root_password='new_pass';
zmlocalconfig -e -f mysql_logger_root_password='new_pass';
zmlocalconfig -e -f zimbra_mysql_password='new_pass';
zmlocalconfig -e -f zimbra_logger_mysql_password='new_pass';

mysql.server start

mysqadmin status

[rhostager]

M2 to M3 upgrade went well. The only issue I see so far is that the admin interface shows an error when you select "Server Status". Here is the error:

Message: Csfe service error
Error code: service.FAILURE
Method: ZmCsfeCommand.invoke
Details:system failure: getting database logger connection

- Rob

[marcmac]

Is the logger service running?

[rjedge]

Originally Posted by marcmac

zmldappasswd --root is the correct command.

On install, we auto-gen an ldap password, which you can change.

Several other error messages came up and I was also low on disk space. Since this is a test environment I decided to give the system more disk space and re-install zimbra from scratch. We only had a few test users anyways.

[marcmac]

is this a virtual server? Zimbra doesn't perform well in veritual environments.