OS 4.5.6 upgrade to 5.0.2 mta password error

[dijichi2]

When I was playing around with this, I eventually gave the zimbra user root privilages with a line in the suders file as:
zimbra ALL=(ALL) ALL

This is not a good idea
Nothing went wrong as a result, and it did get passed the erronuous password issues, but there's always a risk running as root and I dont recommend you do it at all!

That said, it did help me to get past the problem, and if you are in a VM with good backups, you may be comfortable trying this.

Warning, this is a horrific security hazard, never do this on a production server, or on a server in a production network that you care about the data contained within

[dijichi2]

newmember, could you post a bit more of that install log that shows the error, even just a few lines before and after? I can't for the life of me see where that output would come from, certainly doesn't look like it could be from mta postinstall. Clearly something has gone horribly wrong. If you're upgrading from sarge to etch, what is your exact upgrade path, both zimbra and OS wise?

[newmember]

dijichi2,

I will be glad to do the upgrade again and provide the install log files.

I have done

4.5.6 to 5.0.2
and
4.5.6 to 4.5.11 to 5.0.2
and
4.5.6 to 4.5.10 to 5.0.2

Could I ask if there is a preferred path for upgrades?

Thanks
Chris

[newmember]

So I am now on 4.5.11
I ran an update to get to 5.0
I tried upgrading direct to 5.1 and 5.2 with the same results.
I am on CentOS 5.0 i386
You will see near the bottom pf the install process some passwords are missing.
LDAPPOSTPW=
LDAPREPPW=
LDAPAMAVISPW=
See below:::



Shutting down zimbra mail

Backing up the ldap database...done.

Removing existing packages

zimbra-ldap...done
zimbra-logger...done
zimbra-mta...done
zimbra-snmp...don
zimbra-store...done
zimbra-spell...done
zimbra-apache...done
zimbra-core...done

Removing deployed webapp directories
Installing packages

zimbra-core......zimbra-core-5.0.0_GA_1869.RHEL5-20071218205219.i386.rpm...done
zimbra-ldap......zimbra-ldap-5.0.0_GA_1869.RHEL5-20071218205219.i386.rpm...done
zimbra-logger......zimbra-logger-5.0.0_GA_1869.RHEL5-20071218205219.i386.rpm...done
zimbra-mta......zimbra-mta-5.0.0_GA_1869.RHEL5-20071218205219.i386.rpm...done
zimbra-snmp......zimbra-snmp-5.0.0_GA_1869.RHEL5-20071218205219.i386.rpm...done
zimbra-store......zimbra-store-5.0.0_GA_1869.RHEL5-20071218205219.i386.rpm...done
zimbra-apache......zimbra-apache-5.0.0_GA_1869.RHEL5-20071218205219.i386.rpm...done
zimbra-spell......zimbra-spell-5.0.0_GA_1869.RHEL5-20071218205219.i386.rpm...done

Setting defaults from saved config in /opt/zimbra/.saveconfig/config.save
HOSTNAME=mail.domain.com
LDAPHOST=mail.domain.com
LDAPPORT=389
SNMPTRAPHOST=mail.domain.com
SMTPSOURCE=admin@domain.com
SMTPDEST=admin@domain.com
SNMPNOTIFY=yes
SMTPNOTIFY=yes
LDAPROOTPW=***************** ( I changed this)
LDAPZIMBRAPW=****************( I changed this)
LDAPPOSTPW=
LDAPREPPW=
LDAPAMAVISPW=
Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...
Operations logged to /tmp/zmsetup.03222008-234524.log
Starting ldap...done.
Setting defaults...done.
Upgrading from 4.5.6_GA_1044 to 5.0.0_GA_1869
Stopping zimbra services
Verifying /opt/zimbra/conf/my.cnf
Starting mysql
Starting logger mysql
UPGRADE FAILED - exiting
[root@mail zcs-5.0.0_GA_1869.RHEL5.20071218205219]#


So now I go try to start it manually:


[root@mail zcs-5.0.0_GA_1869.RHEL5.20071218205219]# su zimbra
[zimbra@mail zcs-5.0.0_GA_1869.RHEL5.20071218205219]$ zmcontrol start
Host mail.superframe.com
Starting ldap...Done.
Starting logger...Done.
Starting mailbox...Done.
Starting antispam...Done.
Starting antivirus...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...Password:


There it is again, its asking for a "Password" for starting mta.

[dijichi2]

there's no point trying to start zimbra if the upgrade process has failed. the reason you're getting asked for a password is that the various upgrade scripts haven't run yet, so your system is in an inconsistent state.

you need to post the bit of the zmsetup.log that shows what is failing, we have nothing to go on at the moment.

also, people have had better success going from 4.5.6 to 4.5.11, then to 5.0.2. certainly when I upgraded from 4.5.6 I went to 4.5.11 first, I believe this is the recommended path.