[SOLVED] Initializing ldap...failed. (29440)

[zeus]

Hey!

Just installed 5.0.16 but during Installation I got an error:

Initializing ldap...failed. (29440)

ERROR

Configuration failed

Please address the error and re-run /opt/zimbra/libexec/zmsetup.pl to
complete the configuration.

Errors have been logged to /tmp/zmsetup.05132009-094852.log

I looked at the log file and there was:

Wed May 13 10:00:49 2009 checking isEnabled zimbra-ldap
Wed May 13 10:00:49 2009 zimbra-ldap is enabled
Wed May 13 10:00:49 2009 Initializing ldap...
Wed May 13 10:00:49 2009 *** Running as zimbra user: /opt/zimbra/libexec/zmldapinit
IO::Socket::INET: connect: timeout at /opt/zimbra/libexec/zmldapinit line 160.
Wed May 13 10:03:06 2009 failed. (29440)
Wed May 13 10:03:06 2009

ERROR

Wed May 13 10:03:06 2009

Configuration failed

Wed May 13 10:03:06 2009 Please address the error and re-run /opt/zimbra/libexec/zmsetup.pl to

I tried to stop all zimbra services then i killed all services that were still running.
After that I uninstalled zimbra by using ./install.sh -u

If I install zimbra again i get the same error message!!

Does any one have any items as to how to over come this problem ?

Thx zeus

[phoenix]

Originally Posted by zeus

Does any one have any items as to how to over come this problem ?

This problem has been asked and answered many times in the forums, please search. The problem is likely to the fact you don't have valid DNS A & MX records, you'll need a split DNS set-up.

[zeus]

I know that may people had such a problem but my Server is on a public IP not in a NAT Network. So I can't believe that I need a split DNS set-up.

I have a static Public IP and a Dyndns Domain Name.

[phoenix]

In that case, I guess you have a firewall? If so, you still need a split DNS. Do give full information about your configuration when posting in the forums.

[zeus]

Sorry!

My Configuration:

Debian 4r7 with exim4 removed
Zimbra 5.0.16
Dyndns Domain xxx.selfip.com
static IP
iptables:
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT tcp -- anywhere anywhere tcp dpt:ssh
DROP tcp -- anywhere anywhere
DROP icmp -- anywhere anywhere

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination



Edit:
The Problem is DynDns.org
This service does not support an MX entry to the same Domain Name
abc.selfip.com with MX to abc.selfip.com does not work
you have to add another DNS for MX entry

abc.selfip.com with MX to 123.selfip.com works