Unfortunately, I ran into the same "Initializing ldap...FAILED (256)" problem as above, but removing ldaps:// from/opt/zimbra/bin/ldap and the 4 TLS lines from both slapd.conf files did not fix the slapd errors.
I'm running OS X Server 10.4.5. My process is to download all Java updates, set symlink to CurrentJDK to 1.5.0, install Zimbra 3.0GA package, chmod 777 on /opt/zimbra/ssl, change the ldap configs listed above, and then ran zmsetup.pl.
Here's the zmsetup log:
-----------------
** Importing CA
Certificate was added to keystore
keytool error: java.io.FileNotFoundException: /System/Library/Frameworks/JavaVM.framework/Versions/1.5/Home/lib/security/cacerts (Permission denied)
** Creating keystore
** Creating server cert request
Generating a 1024 bit RSA private key
........++++++
...................................++++++
unable to write 'random state'
writing new private key to '/opt/zimbra/ssl/ssl/server/server.key'
-----
** Signing cert request
Using configuration from /opt/zimbra/ssl/ssl/zmssl.cnf
Check that the request matches the signature
Signature ok
Certificate Details:
Serial Number: 8 (0x8)
Validity
Not Before: Feb 16 15:57:15 2006 GMT
Not After : Feb 16 15:57:15 2007 GMT
Subject:
countryName = US
stateOrProvinceName = N/A
organizationName = Zimbra Collaboration Suite
commonName = ldap.rcps.info
X509v3 extensions:
X509v3 Basic Constraints:
CA:FALSE
Netscape Comment:
OpenSSL Generated Certificate
X509v3 Subject Key Identifier:
A6:6A:35:A9:B7:7A:9A:C6:A7:52

8

F:2E:0B:62:4B:98 :67:52:F5
X509v3 Authority Key Identifier:
DirName:/C=US/ST=N/A/L=N/A/O=Zimbra Collaboration Suite/CN=ldap.rcps.info
serial:C6:20:EF:73:EB:A7:F5:C3
Certificate is to be certified until Feb 16 15:57:15 2007 GMT (365 days)
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=ldap.rcps.info
Getting CA Private Key
unable to write 'random state'
ERROR - failed to start slapd
-------------
I also tried the manual zmcreateca/zmcreatecert and hand-start ldap fix.
Any other ideas?
Britt