[SOLVED] a little bump in the zimbra road

[bluethundr_]

I am trying to setup an MTA server in a zimbra cluster. I have set the postfix and amavis users passwords but in the install screen they are listed as "Not Verified".


How do I get past this point?

   2) zimbra-mta:                              Enabled                       
        +MTA Auth host:                        cloud5.example.com         
        +Enable Spamassassin:                  yes                           
        +Enable Clam AV:                       yes                           
        +Notification address for AV alerts:   admin@cloud5.example.com   
******* +Bind password for postfix ldap user:  Not Verified                  
******* +Bind password for amavis ldap user:   Not Verified

[bdial]

you should be able to get these from the localconfig on your ldap server

zmlocalconfig -s | grep ldap_postfix_password
zmlocalconfig -s | grep ldap_amavis_password

[bluethundr_]

ah! thanks for hipping me to zmlocalconfig!

I was able to set the ldap_postfix_password and ldap_amavis_password respectively.

however I ran into a new wrinkle. Turns out I have to set the overall ldap password as well and that just ain't happening.

zimbra@cloud3:~$ zmlocalconfig -e zimbra_ldap_password=myPass
Error: can not edit key zimbra_ldap_password

May I have a hint as to how to proceed?

[bdial]

you can edit the file manually /opt/zimbra/conf/localconfig.xml to modify that entry

[bluethundr_]

hmm.. ok I was able to set the password in the specified file on the ldap server (cloud3)

zmlocalconfig -s | zimbra_ldap_password

zimbra_ldap_password = myPass

And over on cloud4 (my mailbox host) I am still stuck on verifying the ldap password

Common configuration

   1) Hostname:                                example.com                
   2) Ldap master host:                        cloud3.example.com         
   3) Ldap port:                               389                           
** 4) Ldap Admin password:                     Not Verified                  
   5) LDAP Base DN:                            cn=zimbra                     
   6) Secure interprocess communications:      yes                           
   7) TimeZone:                                America/New_York

I even went so far as to add each server in the local DNS zone files of each machine and no dice...

[bluethundr_]

This is getting weirder and weirder. I have verified that LDAP is reachable on the LDAP host by telnetting to it from the mailbox host:

root@cloud4:~# telnet cloud3.example.com 389
Trying 123.45.67.67...
Connected to cloud3.example.com.
Escape character is '^]'.

And I have further verified the fact that ldap is running on the ldap host with with command.

zimbra@cloud3:~$ ps -ef | grep zimbra | grep slapd
zimbra    2973     1  0 May20 ?        00:00:11 /opt/zimbra/openldap/sbin/slapd -l LOCAL0 -4 -u zimbra -h ldap://cloud3.example.com:389 ldapi:/// -F /opt/zimbra/data/ldap/config
zimbra   27784 12789  0 07:40 pts/0    00:00:00 grep slapd

Yet this condition persists and it's driving me nuts!!!

1) Common Configuration:                                                  
        +Hostname:                             example.com                
        +Ldap master host:                     cloud3.example.com         
        +Ldap port:                            389                           
******* +Ldap Admin password:                  Not Verified                  
        +LDAP Base DN:                         cn=zimbra                     
        +Secure interprocess communications:   yes                           
        +TimeZone:                             America/New_York

[bdial]

when you set it in the file, you're not setting the actual password you're setting the password zimbra will use to bind to the ldap server with. the actual password is encrypted and stored within the ldap database.

the password in the localconfig.xml on the ldap server should be whats in the database, but if it isn't you can always go about resetting it

first on hte ldap server do

zmldappasswd yournewpassword

then update teh zimbra_ldap_password in the localconfig.xml of every server in your multiserver install iwth hte new password, it may require restarting the services as well.

[bluethundr_]

dude.. you're brilliant... it's working (finally).. and thank you!

tim