Reinstall with 4.0.5 MTA fails to start (saslauthd error)

[dlochart]

I installed 4.0.2 just fine in a multi machine configuration. Then our license expired so I downloaded a new one to use while we are purchasing our real license.

I tried to repeat the same installation with 4.0.5 and I get this error when starting up the MTA services.

saslauthd[24346] :set_auth_mech : failed to initialize mechanism zimbra

I am running a split config
machineA: everything but MTA
machineB: MTA

(no changes to the machines from the prior installation. Yes SELinux is disabled)

Machine A everything seems to be running fine. I can log in as administrator and as a user.

I made the following changes before I installed my MTA machine.

Set auth fallback

zmprov md capetestinternal.com zimbraAuthFallbackToLocal TRUE

Set mail access to SSL

 zmtlsctl https

I also changed the root and default LDAP passwords

Then I went to machineB and proceeded to install the MTA. It completed and it did not complain about any LDAP communication during installation. I provided the new passwords I entered. However when I stop and restart the MTA system I get this error.

[zimbra@mail ~]$ bin/zmcontrol start
Host mail.capeinternal.com
        Starting antispam...Done.
        Starting antivirus...Done.
        Starting snmp...Done.
        Starting mta...FAILED
saslauthd[24346] :set_auth_mech   : failed to initialize mechanism zimbra
zmsaslauthdctl failed to start

I also tried starting it manually and it did not work.

1) Could someone please do the following:
explain what saslauthd is and what it is doing

2) What else I can look for to either figure it out or assist others in helping me out.

I looked through the forum but all proposed remedies either did not fit or did not work.

thanks

Doug

[phoenix]

Check your sasldauth.conf and see if it's correct, make sure the zimbra_url is https. Let us know if that's the problem.

You won't be able to use another trial license from the support portal if that's what you're trying to do, if you need an extension to the trial you should contact your sales contact.

[dlochart]

Thanks phoenix. Actually I already tried that trick of using a new license on an expired system. I was reinstalling the whole shebang to use the new license. I decided to try a clean install of the the ldap/mail store machine but then I decided to try to upgrade the MT machine. Anyway that may have been the problem. I could not wait any longer (I am under a tight time line) so I reinstalled both from scratch and got it working again.

I will use this trial license server as our test server and I believe my manager will also purchase a license for this one so that we can have one internal to test things out on.

thanks

[phoenix]

OK, glad you got things working again.

[marcos.gw]

Hi,

I`m with the same problem.

I installed two servers ( same name, same SO, same zimbra version ).
I used rsync for replicate information.
When I start the second server:
Host virtual.dominio.local
Starting ldap...Done.
Starting logger...Done.
Starting mailbox...Done.
Starting antispam...Done.
Starting antivirus...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...FAILED
Starting zmmtaconfig...zmmtaconfig is already running.
Starting saslauthd...saslauthd[5026] :set_auth_mech : failed to initialize mechanism zi mbra
failed.
zmsaslauthdctl failed to start

[veronica]

check your sasldauth.conf file

[marcos.gw]

zimbra_urli: virtual.dominio.local
zimbra_cert_file: /opt/zimbra/conf/smtpd.crt
zimbra_cert_check: off

########################
And smtpd.crt it`s ok ( it exist in /opt/zimbra/conf/ )

Att,
Marcos.

[veronica]

Here is the problem:-

zimbra_urli: virtual.dominio.local
zimbra_cert_file: /opt/zimbra/conf/smtpd.crt
zimbra_cert_check: off

zimbra_url should be https://servername:7071/service/admin/soap/

w/o https it doesnt work.

[marcos.gw]

I changeg my file.
When I restart the service dissapear my changed.

[veronica]

need to change in sasldauth.conf.in :-)