Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 11-21-2006, 09:55 AM
Advanced Member
 
Posts: 177
Default First Time New Installation ldap failure (512)

I am installing Zimbra 4.0 on CentOS 4.4.

Supposedly we an internal domain setup with MX record mail.myinternal.com and an A record for mail.myinternal.com as well as an A record for zimbra.myinternal.com

I verified these with nslookup and dig.

During the installation I get an error message
about the MX record missing. The zmsetup log shows this:

DNS ERROR resolving MX for mail.myinternal.com

So I continue anyway knowing (hoping) it is really setup.

I accept most of all the defaults (I added POP support for IMAP).

Then I get this message:
...
reating SSL certificate...Done
Initializing ldap...FAILED (512)
ERROR
Configuration failed

I found other posts about this and tried what I read. I checked the hostname and verified that all so links (ldd) for ldap were resolved. I can rerun these and post them if necessary.

I also saw other errors in the zmsetup log. Here is the log in case it will help.

Am I mistaken in testing DNS with nslookup and dig?

thanks in advance I am anxious to get this thing running. If we can we are already set to purchase a network license.

Doug

(zmsetup log)


Code:
Setting defaults...


DNS ERROR resolving MX for mail.capeinternal.com

It is suggested that the domain name have an MX record configured in DNS

Done

Checking for port conflicts

Saving config in /opt/zimbra/config.12120...
Done

Operations logged to /tmp/zmsetup.log.12120

Setting local config values...
Setting local config zimbra_server_hostname to mail.capeinternal.com

*** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e zimbra_server_hostname=mail.capeinternal.com

Setting local config ldap_master_url to ldap://mail.capeinternal.com:389

*** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e ldap_master_url=ldap://mail.capeinternal.com:389

Setting local config ldap_url to ldap://mail.capeinternal.com:389

*** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e ldap_url=ldap://mail.capeinternal.com:389

Setting local config ldap_port to 389

*** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e ldap_port=389

Setting local config ldap_host to mail.capeinternal.com

*** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e ldap_host=mail.capeinternal.com

Setting local config zimbra_uid to 501

*** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e zimbra_uid=501

Setting local config zimbra_gid to 501

*** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e zimbra_gid=501

Setting local config zimbra_user to zimbra

*** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e zimbra_user=zimbra

Setting local config av_notify_user to admin@mail.capeinternal.com

*** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e av_notify_user=admin@mail.capeinternal.com

Setting local config ssl_allow_untrusted_certs to TRUE

*** Running as zimbra user: /opt/zimbra/bin/zmlocalconfig -f -e ssl_allow_untrusted_certs=TRUE

Done

Setting up CA...
*** Running as zimbra user: cd /opt/zimbra; zmcreateca

** Creating CA private key

Generating a 1024 bit RSA private key
..................++++++
.........++++++
unable to write 'random state'
writing new private key to '/opt/zimbra/ssl/ssl/ca/ca.key'
-----
** Creating CA cert
Signature ok
subject=/C=US/ST=N/A/L=N/A/O=Zimbra Collaboration Suite
Getting Private key
unable to write 'random state'
Done




Creating SSL certificate...
chmod: cannot access `/jre/lib/security/cacerts': No such file or directory
*** Running as zimbra user: cd /opt/zimbra; zmcreatecert

** Importing CA

Certificate was added to keystore
keytool error: java.io.FileNotFoundException: /opt/zimbra/java/jre/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: 2 (0x2)
        Validity
            Not Before: Nov 21 16:05:35 2006 GMT
            Not After : Nov 21 16:05:35 2007 GMT
        Subject:
            countryName               = US
            stateOrProvinceName       = N/A
            organizationName          = Zimbra Collaboration Suite
            commonName                = mail.capeinternal.com
        X509v3 extensions:
            X509v3 Basic Constraints:
            CA:FALSE
            Netscape Comment:
            OpenSSL Generated Certificate
            X509v3 Subject Key Identifier:
            A5:0E:27:52:8D:99:ED:A8:BD:5C:9D:90:1D:FD:A4:33:4D:10:28:2D
            X509v3 Authority Key Identifier:
            DirName:/C=US/ST=N/A/L=N/A/O=Zimbra Collaboration Suite
            serial:00

            X509v3 Key Usage:
            Digital Signature, Non Repudiation, Key Encipherment
Certificate is to be certified until Nov 21 16:05:35 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=mail.capeinternal.com
Getting CA Private Key
unable to write 'random state'
chmod: cannot access `/jre/lib/security/cacerts': No such file or directory
Done

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

Started slapd: pid 13447
ldap_bind: Can't contact LDAP server (-1)
ldap_bind: Can't contact LDAP server (-1)
ldap_bind: Can't contact LDAP server (-1)
FAILED (512)



ERROR
Reply With Quote
  #2 (permalink)  
Old 11-29-2006, 04:28 AM
Starter Member
 
Posts: 1
Default

I fixed this last night by editing my /etc/sudoers file.

Find Defaults requiretty and put a # ifront of it to comment it out.
#Defaults requiretty

Then I re-installed. My Zimbra is up and running.

System Specs
Fedora Core 6
Zimbra 4.04_GA_457_FC5
Reply With Quote
  #3 (permalink)  
Old 11-29-2006, 06:46 AM
Advanced Member
 
Posts: 177
Default

I forgot to reply to this message. I opened another one in the admin section and got more views/responses there.

I assumed "wrongly" that setting SELinux to WARN was good enough. You actually have to disable it completely. That corrected my problem.

thanks for sharing your solution though ... it might me or others in the future
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.