OS 4.5.6 upgrade to 5.0.2 mta password error

[newmember]

I am asked for a "password" when I try to start the mta process.
I have no idea what the password is or where to find it.

Thanks
chris

[zimbra@mail zcs-5.0.2_GA_1975.RHEL5.20080130221917]$ zmcontrol start
Host mail.XXXXXXXXXXX.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:
Password:
Password:
Password:
Password:
FAILED
/opt/zimbra/bin/postfix: line 56: /opt/zimbra/postfix-2.2.9/sbin/postmap: No such file or directory
Sorry, try again.
sudo: 1 incorrect password attempt
Sorry, try again.
Sorry, try again.
Sorry, try again.
sudo: 3 incorrect password attempts
postfix failed to start

[Dirk]

Check the /etc/sudoers file, look for the postfix entry and ensure that it's there and that the path to postfix is correct.

[newmember]

How does this look?


/etc/sudoers

%zimbra ALL=NOPASSWD:/opt/zimbra/openldap/libexec/slapd
%zimbra ALL=NOPASSWD:/opt/zimbra/libexec/zmslapd
%zimbra ALL=NOPASSWD:/opt/zimbra/postfix-2.4.3.4z/sbin/postfix, /opt/zimbra/po stfix-2.4.3.4z/sbin/postalias, /opt/zimbra/postfix-2.4.3.4z/sbin/qshape.pl, /opt /zimbra/postfix-2.4.3.4z/sbin/postconf,/opt/zimbra/postfix-2.4.3.4z/sbin/postsup er
%zimbra ALL=NOPASSWD:/opt/zimbra/libexec/zmqstat,/opt/zimbra/libexec/zmmtastat us
%zimbra ALL=NOPASSWD:/opt/zimbra/libexec/zmmailboxdmgr
%zimbra ALL=NOPASSWD:/opt/zimbra/bin/zmcertmgr
%zimbra ALL=NOPASSWD:/opt/zimbra/nginx/sbin/nginx

It looks like its there.

[zimbra@mail sbin]$ ls -al /opt/zimbra/postfix-2.4.3.4z/sbin/postfix
-rwxr-xr-x 1 root root 287663 Jan 25 10:35 /opt/zimbra/postfix-2.4.3.4z/sbin/postfix

[Dirk]

Something looks wrong here, the log shows it's trying to execute postfix-2.2.9, but the sudoers file is assigning rights to postfix-2.4.3.4z.

I've had the same problem when dealing with a dodgy upgrade, but you have the postfix folder that sudoers is looking for. I guess you could duplicate the line and change the path so it has rights for both, but that wont deal with the underlying issue.

I dont have the final answer I'm afraid; stick around, I'm sure someone will come up with something.

You should revert to your backup if youve not already done so.

[newmember]

Thanks Dirk.

I gotta love vmware.
All I did was copy the zimbra vmware image and tried the update on the copy.
Without success and turned the old copy of zimbra back on.

I still have the old version to refer too for log files etc.

Luck y I have 20G of space on my vmware server to copy the zimbra image.
Next step will be to use rsync and replicate the zimbra vmware to another server.

Cheers
Chris

[newmember]

Dirk to your comment:

The upgrade tries to use postfix-2.2.9 and it looks like it should try to use postfix-2.4.3.4z.


Chris

[newmember]

Looking through the install.log files I see this:

install.log.11107:COMMAND: zmlocalconfig -f -e postfix_version='2.2.9'

It looks like this sets the version for the install. In this case the version should be 2.4.3.4z instead of 2.2.9

Chris

[newmember]

OK, so I ran:

zimbra@mail tmp]$ zmlocalconfig | grep postfix_version
postfix_version = 2.2.9

So I manually updated the version of postfix.

zmlocalconfig -f -e postfix_version='2.4.3.4z'

This changed the config file to use the new postfix starts without the password request

mta running

It was suggest by "dom_" that upgrades should include upgrading to 4.5.10/11 then to 5.0.2. I think there are other comments to the same in the forums. Just to make sure that nothing else was missed.

Always be safe!!

I will try this and get back to the forum.

Chris

[newmember]

I tried upgrading from 4.5.6 to 4.5.11 then to 5.0.2
I had the same mta password request.

Then I found this comment about sunsets:

"You MUST update the server OS on 4.5.x before you begin the upgrade to ZCS 5.0. To do this you must first upgrade from 4.5.x to 4.5.10 (which has the current server OS) and THEN you can safely run an upgrade to ZCS 5.0. Not doing so will fail the install."

I found this comment on http://www.zimbra.com/products/sunset_binaries.html

I found a link to this page called "Important information about Sunset binaries." on this page http://www.zimbra.com/community/downloads.html

Can you see the link?


Going from 4.5.6 to 4.5.10 then to 5.0.2 gave me the same 'password' request from mta.

Chris

[Dirk]

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.