initializing ldap...FAILED(256)ERROR

[gmihey]

I have the same problemm. It appeared after uninstall-install. System : FC3

[zimbra@gmihey gmihey]$ /opt/zimbra/libexec/zmldapinit
ERROR - failed to start slapd

Please, help me

[gmihey]

I fix a problem:
1. ./install.sh /u
2. Remove all from /opt/zimbra/
3. install packages by rpm -i
4. /opt/zimbra/libexec/zmsetup.pm
5. install by ./install.sh
6. all is worked

[tommygun]

well, I've given up on installing Zimbra. I keep getting the same error and haven't been able to fix it. I'm just going back to xmailserver which installs much easier.

[gmihey]

I think it is not a best way - try to setup it like me.
Also uninstall postfix, MYSQL, dspam, tomcat, ldap (that was in your system before installation zimbra). One of this packages was unstalled on my pc. Others not present.
Manage /etc/hosts. Make sure all is ok.

[tommygun]

Originally Posted by gmihey

I think it is not a best way - try to setup it like me.
Also uninstall postfix, MYSQL, dspam, tomcat, ldap (that was in your system before installation zimbra). One of this packages was unstalled on my pc. Others not present.
Manage /etc/hosts. Make sure all is ok.

Mysql took too long to setup to get rid of.

[KevinH]

Originally Posted by tommygun

well, I've given up on installing Zimbra. I keep getting the same error and haven't been able to fix it. I'm just going back to xmailserver which installs much easier.

Can you expand? What is the latest error? You never answered my last question. Are you running the right build for your OS? What OS? and Which build? are you trying to install?

[ewold]

I only have the problem with the beta version.
We have a 3.1.4 on a production server and wanted to test the beta on a vmware machine but i also get the same error. When trying to install the 3.1.4 version there's no problem.

OS : Centos 4.2 (RHEL4 rebuild)

[redhat]

Sounds like I'm having the same problem described here. I'm new to Zimbra and so trying to install the 3.2.0 beta 2 release on a Fedora Core 5 machine.

The install seemed to go along properly until the ldap failure.

The error I'm getting looks like this in the log file:

Write out database with 1 new entries
Data Base Updated
unable to write 'random state'
Signature ok
subject=/C=US/ST=NA/L=NA/O=Zimbra/OU=Zimbra/CN=zimbra.stoeber.us
Getting CA Private Key
unable to write 'random state'
Done

Initializing ldap...
*** Running as zimbra user: /opt/zimbra/libexec/zmldapinit

ERROR - failed to start slapd

FAILED (256)


A lot of things seem to be working properly but I can't figure out what "random state" isn't being written, or where it's trying to write. Is that even meaningful? The new ssl keys, .conf files, and directories are all owned by the zimbra user.

SELinux and iptables are disabled. DNS returns the proper address for the machine this is being installed on.

Any ideas where I should look?


UPDATE:

I found the solution to my own problem - it was a self inflicted wound. My DNS was set up and working properly, but the Zimbra machine had an error in the /etc/hosts file so it must have been picking up a public (external) address for the machine insead of the internal address. I fixed that and reinstalled and the process completed without error - my Zimbra server is now running, and it sends and receives mail with no problem.

[KevinH]

What do you get for "host `hostname`"?

Did you search the wiki for LDAP articles?

[zagman76]

I am kinda new to zimbra and linux as a whole, and as a proof-of-concept we are building a zim server (moved to the 4.0 version just released - was using the 3.x version in the lab before).

I am getting the same LDAP errors - I am a complete DNS/LDAP n00b, and was wondering what the effect of having an alias in DNS that points to a different server which used to be named the same name as the current server would be?

(in other words we had a server named email02 and had to rename it to mail02. We created an alias for email02 which points to mail02 for the clients who didn't have control of their mail filter lists, and stopped receiving mail from us. now the new server is named email02, and is failing on the LDAP portion of the install)

thanks for any assistance!