Multiple Servers in 5.0.1

[stinnux]

I am trying to get multiple servers working with Zimbra 5.0.1.

When i try to setup the second server i am unable to finish the setup. What does Address unconfigured (**) items or correct ldap configuration (? - help) mean?


Main menu

1) Common Configuration:
+Hostname: *localhostname*
+Ldap master host: *hostnameofmaster*
+Ldap port: 389
+Ldap Admin password: set
+LDAP Base DN: cn=zimbra
+TimeZone: (GMT+01.00) Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna

2) zimbra-store: Enabled
3) zimbra-mta: Enabled
4) zimbra-snmp: Enabled
5) zimbra-spell: Disabled
6) zimbra-proxy: Enabled
7) Default Class of Service Configuration:
8) Enable default backup schedule: yes
r) Start servers after configuration no
s) Save config to file
x) Expand menu
q) Quit

Address unconfigured (**) items or correct ldap configuration (? - help)

[phoenix]

What does Address unconfigured (**) items or correct ldap configuration (? - help) mean?

It means fix the problems that are highlighted by the '**'. Did you read the documentation for a Multi-Server install?

[stinnux]

Sure, i did.

The problem is - there is nothing marked with ** as you can see in my posting.

[linch]

I am facing the same problem - all configuration settings are in place and there are no *** left.
I am using the open source edition... could this be the issue?

1) Common Configuration:
+Hostname: zimbra2.xxxxxxx
+Ldap master host: zimbra.xxxx
+Ldap port: 389
+Ldap Admin password: set
+LDAP Base DN: uid=zimbra,cn=admins,cn=zimbra
+TimeZone: (GMT+02.00) Helsinki / Kyiv / Riga / Sofia / Tallinn / Vilnius

2) zimbra-store: Enabled
3) zimbra-spell: Enabled
4) Default Class of Service Configuration:
r) Start servers after configuration yes
s) Save config to file
x) Expand menu
q) Quit

[quanah]

1) Common Configuration:
+Hostname: zimbra2.xxxxxxx
+Ldap master host: zimbra.xxxx
+Ldap port: 389
+Ldap Admin password: set

It means that this server cannot talk to the LDAP master. When you install a client, a random password is generate for the "LDAP admin password". You need to go and change it to match what you set on the LDAP master.

[quanah]

correct ldap configuration

As it says, you need to correct the LDAP configuration -- This generally indicates that it cannot talk to the master with the password you've set as the admin password value.

--Quanah

[stinnux]

I am quite sure that i use the correct password.

Can i somehow lookup the password i used?

[rsharpe]

On your main LDAP server use

zmlocalconfig -s | grep pass

It will show you all of the configured passwords.

[stinnux]

I have the correct password and nevertheless tried it again today.

It's still not working.

I'm now waiting for the answer to my support ticket.

[SPremeau]

Having just performed a production 5.0.1 install this weekend, I will agree that the documentation doesn't seem to match the process that worked.

I not only had to reset the LDAP admin password, I needed to check and reset all the LDAP access passwords that didn't match that of my primary server.

Postfix, Amavis, SpamAssassin, etc.

At a minimum, you need to look at them, to ensure they get set right, but in a lot of cases, they didn't for me.

(When installing an MTA/Ldap Replica server, I had to do the install three times to get the settings right.)

Steve.