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 Display Modes
  #1 (permalink)  
Old 02-23-2006, 05:19 PM
Intermediate Member
 
Posts: 15
Default Initializing ldap...FAILED (512)?

I've searched through and found many instances of this error. I tried all of the listed fixes I could find, installed openssl and openssl-devel, edited /opt/zmbra/bin/ldap.

Always get these 2 errors:

Initializing ldap...FAILED (256) or
Initializing ldap...FAILED (512)

In this context:
Code:
Save config in file: [/opt/zimbra/config.6157]
Saving config in /opt/zimbra/config.6157...Done
The system will be modified - continue? [No] Yes
Operations logged to /tmp/zmsetup.log.6157
Initializing ldap...FAILED (256)


ERROR



Configuration failed

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

Here are the last few lines from the zmsetup and install logs.

install.log:
Code:
COMMAND: zmlocalconfig -f -e zimbra_home='/opt/zimbra'
COMMAND: zmlocalconfig -f -e zimbra_index_directory='${zimbra_home}/index'
COMMAND: zmlocalconfig -f -e zimbra_index_idle_flush_time='600'
COMMAND: zmlocalconfig -f -e zimbra_index_lru_size='100'
COMMAND: zmlocalconfig -f -e zimbra_index_max_uncommitted_operations='200'
COMMAND: zmlocalconfig -f -e zimbra_java_home='${zimbra_home}/java'
COMMAND: zmlocalconfig -f -e zimbra_ldap_password='zimbra'
COMMAND: zmlocalconfig -f -e zimbra_ldap_userdn='uid=zimbra,cn=admins,cn=zimbra'
COMMAND: zmlocalconfig -f -e zimbra_log4j_properties='${zimbra_home}/conf/log4j.properties'
COMMAND: zmlocalconfig -f -e zimbra_log_directory='${zimbra_home}/log'
COMMAND: zmlocalconfig -f -e zimbra_logger_mysql_password='D54_BD_10Onaub_P3K8K3nV_60Y'
COMMAND: zmlocalconfig -f -e zimbra_mysql_connector_maxActive='10'
COMMAND: zmlocalconfig -f -e zimbra_mysql_password='t6wRXxUsLWuG1N4R0xSAIRCERRUi'
COMMAND: zmlocalconfig -f -e zimbra_mysql_user='zimbra'
COMMAND: zmlocalconfig -f -e zimbra_server_hostname='mail.fonestream.com'
COMMAND: zmlocalconfig -f -e zimbra_store_directory='${zimbra_home}/store'
COMMAND: zmlocalconfig -f -e zimbra_store_sweeper_max_age='480'
COMMAND: zmlocalconfig -f -e zimbra_uid='500'
COMMAND: zmlocalconfig -f -e zimbra_user='zimbra'
COMMAND: zmlocalconfig -f -e zimlet_directory='${tomcat_directory}/webapps/service/zimlet'
and zmsetup.log:
Code:
adding new entry "cn=(GMT\+09.00) Osaka / Sapporo / Tokyo,cn=timezones,cn=config,cn=zimbra"

adding new entry "cn=(GMT\+09.00) Seoul,cn=timezones,cn=config,cn=zimbra"

adding new entry "cn=(GMT\+09.00) Yakutsk,cn=timezones,cn=config,cn=zimbra"

adding new entry "cn=(GMT\+09.30) Adelaide,cn=timezones,cn=config,cn=zimbra"

adding new entry "cn=(GMT\+09.30) Darwin,cn=timezones,cn=config,cn=zimbra"

adding new entry "cn=(GMT\+10.00) Brisbane,cn=timezones,cn=config,cn=zimbra"

adding new entry "cn=(GMT\+10.00) Canberra / Melbourne / Sydney,cn=timezones,cn=config,cn=zimbra"

adding new entry "cn=(GMT\+10.00) Guam / Port Moresby,cn=timezones,cn=config,cn=zimbra"

adding new entry "cn=(GMT\+10.00) Hobart,cn=timezones,cn=config,cn=zimbra"

adding new entry "cn=(GMT\+10.00) Vladivostok,cn=timezones,cn=config,cn=zimbra"

adding new entry "cn=(GMT\+11.00) Magadan / Solomon Is. / New Calenodia,cn=timezones,cn=config,cn=zimbra"

adding new entry "cn=(GMT\+12.00) Auckland / Wellington,cn=timezones,cn=config,cn=zimbra"

adding new entry "cn=(GMT\+12.00) Fiji / Kamchatka / Marshall Is.,cn=timezones,cn=config,cn=zimbra"

adding new entry "cn=(GMT\+13.00) Nuku'alofa,cn=timezones,cn=config,cn=zimbra"
Any ideas? Anything else I should search for?

This is on CentOS 4.2 fresh install.
Reply With Quote
  #2 (permalink)  
Old 02-23-2006, 05:21 PM
Zimbra Employee
 
Posts: 2,073
Default

Run as the zimbra user:

host `hostname` (backticks, not quotes)
ps auxww | grep slapd
ldd /opt/zimbra/openldap/libexec/slapd
Reply With Quote
  #3 (permalink)  
Old 02-23-2006, 05:38 PM
Intermediate Member
 
Posts: 15
Default

Super fast response,

I think i see a problem now, heres what those commands give (stripping my domain and real ip):

[zimbra@mail ~]$ host `hostname`
mail.mydomain.com has address xx.xxx.xxx.225
[zimbra@mail ~]$ ps auxww | grep slapd
zimbra 15007 0.2 0.9 23436 4700 ? Ssl 16:31 0:00 /opt/zimbra/openldap-2.2.28/libexec/slapd -l LOCAL0 -4 -u zimbra -h ldaps:// ldap://:389/ -f /opt/zimbra/conf/slapd.conf
[zimbra@mail ~]$ ldd /opt/zimbra/openldap/libexec/slapd
libsasl2.so.2 => /opt/zimbra/cyrus-sasl/lib/libsasl2.so.2 (0x00392000)
libssl.so.4 => /lib/libssl.so.4 (0x00bda000)
libcrypto.so.4 => /lib/libcrypto.so.4 (0x009de000)
libresolv.so.2 => /lib/libresolv.so.2 (0x0099b000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00947000)
libc.so.6 => /lib/tls/libc.so.6 (0x007de000)
libdl.so.2 => /lib/libdl.so.2 (0x0090a000)
libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x009c8000)
libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00ac9000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0x0095b000)
libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00bb7000)
libz.so.1 => /usr/lib/libz.so.1 (0x00935000)
/lib/ld-linux.so.2 (0x007c5000)
[zimbra@mail ~]$

Problem is the IP that host resolves is a different IP than this machine. I added mail.mydomain.com with this machines ip to /etc/hosts in hopes it would use that (since I don't want to switch traffic to this machine until it's working). Is there a way I can get the zimbra user to think mail.mydomain.com is a certain IP until I change the real DNS?

Thanks again for such a quick reply.
Reply With Quote
  #4 (permalink)  
Old 02-23-2006, 05:43 PM
Zimbra Employee
 
Posts: 2,073
Default

ldap is a pain about this, it likes to use dns to connect, rather than /etc/hosts. You could bring up that interface on this box (unless the real server is on the same lan) or you could change the name.
Reply With Quote
  #5 (permalink)  
Old 02-23-2006, 05:45 PM
Intermediate Member
 
Posts: 15
Default

Hmm hmmm.... well i see the problem now. I guess I will poke around and try to find the best way to make it use the IP I want instead of taking down something I dont want to..

Maybe I could setupa temporary nameserver with fake dns info for mail.mydomain.com that points to this IP and then make resolv.conf only use that nameserver.
Reply With Quote
  #6 (permalink)  
Old 02-23-2006, 06:05 PM
Intermediate Member
 
Posts: 15
Default

Well I added the IP address to the machine and tried doign a full reinstall. Same issue.

I can even telnet to xx.xxx.xxx.225 and get a connection.

Anything else I might try? On a similar machine I was able to get 3.0.0 to work so I am going to go back to the previous release and try that just for the heck of it...
Reply With Quote
  #7 (permalink)  
Old 02-23-2006, 06:10 PM
Zimbra Employee
 
Posts: 2,073
Default

Is this an upgrade or a fresh install?

When you telnet, are you sure you're hitting the local host, and not the other one?

What's in your routing table?
Reply With Quote
  #8 (permalink)  
Old 02-23-2006, 06:27 PM
Intermediate Member
 
Posts: 15
Default

Fresh install.
I'm telnetting to the IP on the localhost. The IP is on the adapter with a 255.255.255.255 subnet mask. Pretty sure it's routing correct because I ping it at 0 - 1ms.

Heres something else strange. The 3.0.0 GA install worked flawlessly. No problem at all.

Not sure what's going on. I'll try to upgrade from a working 3.0.0 to 3.0.1 to see if that also works fine.
Reply With Quote
  #9 (permalink)  
Old 02-24-2006, 06:38 AM
Loyal Member
 
Posts: 76
Default IP / DNS problem

I had the same problem.
I think we will see this same problem on and on.

Only quick solution I can see is the one that I used.
Have a internal/test DNS server or keep configuring that /etc/hosts file.


Sam
Reply With Quote
  #10 (permalink)  
Old 02-24-2006, 12:33 PM
Intermediate Member
 
Posts: 15
Default

Well the /etc/hosts file did NOT work for me. Even adding the IP address of the domain to the machine did not work. May have been some fluke or something. I am installing a new CentOS 4.2 machine today and will try a fresh 3.0.1 install again.

Seemed odd that the 3.0.0 fresh install on the same machine worked fine. No problems at all.
Reply With Quote
Reply


Thread Tools
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.

Zimbrablog.com




 

Search Engine Optimization by vBSEO 3.1.0