Multi-Server installation of 5.0.8 - anybody successful?

[rainer_d]

Hi,

we're trying to do a fresh install of the "Network Professional Edition" 5.0.8 on CentOS5, distributed on multiple servers (LDAP master+slave, 2* frontend, 2*backend).
We already have a working version that was updated from 5.0.6 over 5.0.7 to 5.0.8.

But with 5.0.8, we seem to experience the problem that the installer doesn't accept a hostname different from the ldap-master host.
Described here: Bug 30413 – Make the install case insensitive on hostname
and in an official ticket (I can share the ticketnumber on request) that we haven't heard of in the last days.
Would someone from Zimbra please look into this?


Rainer

[Klug]

I've just spent several days on setting up three servers in a ZCS infrastructure.

One MTA/LDAP and one Mailstore were upgraded from 4.5.10 to 5.0.8 without any problem (RHEL4 32 bits).

I added a zimbra-proxy server to that pair. It's a 5.0.8 server (Ubuntu6 32 bits) and I obviously had to specify an LDAP server different from the hostname. No problem at all.

BTW, CentOS is not a supported OS for NE, but I think you already know it.

[rainer_d]

Yes, the upgrade worked (in a VPS of CentOS5 - our test-environment).
But we don't want to install an old version and then update.
Unless somebody from Zimbra tells us that this is the only supported way to install 5.0.8.
Besides, this is a regression, IMHO.

BTW: CentOS5 AMD64 version...

Best Regards,
Rainer

[jwriteclub]

I recently added a server to an install with 5.0.8 and had no difficulty. This was a clean install on Fedora 7.

~ Christopher

[Klug]

And, as I said, I had no problem with _adding_ a 5.0.8 server to a 5.0.8 infrastructure...

[rainer_d]

OK, so I have to resolve this.
The problem is, we wanted to route the LDAP-traffic over the 2nd interface and made a hosts-file entry.
But OpenLDAP in Zimbra is the only service that doesn't listen on all ports...so this went off-target as OpenLDAP didn't even listen on the IP we were pointing clients and the Slave LDAP to....
Unfortunately, the error-messages for that were only displayed in the logfile - what was displayed on screen was not very helpful.

After some ping-pong with the support, we came up with:
zmcontrol stop
zmlocalconfig -e ldap_bind_url=ldap:///
zmcontrol start

which results in the LDAP-server listening on all interfaces...