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 10-08-2007, 08:01 AM
Junior Member
 
Posts: 9
Default ldap replication problems in 4.5.8GA on Ubuntu 6.06

My basic setup is this:

Server A - runs everything. LDAP master.
Server B - only MTA, ldap. Configured as a replica.

My plan is to have Server A the primary MX record, and Server B the backup, which would queue mail until Server A becomes available again.

I followed the settings in LDAP - ZimbraWiki under LDAP replication for my config. I have both servers configured as MX hosts for my domain name.

Everything seems fine, except for the ldap replication. I cannot get zmprov gaa to run successfully against the ldap replica on Server B. If I run the command on Server B, against server A, it works fine.

The command I'm using, and the output, is as below. Any help would be greatly appreciated.

Quote:
zmprov -s ServerB -z -d -v gaa
========== SOAP SEND ==========
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Header>
<context xmlns="urn:zimbra"/>
</soap:Header>
<soap:Body>
<AuthRequest xmlns="urn:zimbraAdmin">
<name>zimbra</name>
<password>my_password_here</password>
</AuthRequest>
</soap:Body>
</soap:Envelope>
===============================
[] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
[] INFO: Retrying request
[] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
[] INFO: Retrying request
[] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
[] INFO: Retrying request
ERROR: zclient.IO_ERROR (invoke Connection refused, server: 70.85.16.92) (cause: java.net.ConnectException Connection refused)
com.zimbra.cs.zclient.ZClientException: invoke Connection refused, server: 70.85.16.92
at com.zimbra.cs.zclient.ZClientException.IO_ERROR(ZC lientException.java:44)
at com.zimbra.cs.account.soap.SoapProvisioning.invoke (SoapProvisioning.java:150)
at com.zimbra.cs.account.soap.SoapProvisioning.soapAd minAuthenticate(SoapProvisioning.java:118)
at com.zimbra.cs.account.ProvUtil.initProvisioning(Pr ovUtil.java:299)
at com.zimbra.cs.account.ProvUtil.ma<in(ProvUtil.java :1439)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl .java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSoc ketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.j ava:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.j ava:366)
at java.net.Socket.connect(Socket.java:518)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect (SSLSocketImpl.java:550)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.>init>( SSLSocketImpl.java:394)
at com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl. createSocket(SSLSocketFactoryImpl.java:123)
at com.zimbra.cs.httpclient.EasySSLProtocolSocketFact ory.createSocket(EasySSLProtocolSocketFactory.java :125)
at com.zimbra.cs.httpclient.EasySSLProtocolSocketFact ory.createSocket(EasySSLProtocolSocketFactory.java :166)
at org.apache.commons.httpclient.HttpConnection.open( HttpConnection.java:706)
at org.apache.commons.httpclient.HttpMethodDirector.e xecuteWithRetry(HttpMethodDirector.java:386) at org.apache.commons.httpclient.HttpMethodDirector.e xecuteMethod(HttpMethodDirector.java:170)
at org.apache.commons.httpclient.HttpClient.executeMe thod(HttpClient.java:396)
at org.apache.commons.httpclient.HttpClient.executeMe thod(HttpClient.java:324)
at com.zimbra.soap.SoapHttpTransport.invoke(SoapHttpT ransport.java:185)
at com.zimbra.soap.SoapTransport.invoke(SoapTransport .java:225)
at com.zimbra.cs.account.soap.SoapProvisioning.invoke (SoapProvisioning.java:146)
... 3 more

Last edited by encode : 10-08-2007 at 06:38 PM.
Reply With Quote
  #2 (permalink)  
Old 10-08-2007, 02:05 PM
Zimbra Employee
 
Posts: 538
Default

Since you don't have a mailbox/store server on server B you'll need to talk to ldap directly.

Code:
zmprov -l -s ServerB -z -d -v gaa
or
zmlocalconfig -e zimbra_prov_default_to_ldap=true
__________________
Bugzilla - Wiki - Downloads - Before posting... Search!
Reply With Quote
  #3 (permalink)  
Old 10-08-2007, 02:57 PM
Junior Member
 
Posts: 9
Default

Quote:
Originally Posted by brian View Post
Since you don't have a mailbox/store server on server B you'll need to talk to ldap directly.

Code:
zmprov -l -s ServerB -z -d -v gaa
or
zmlocalconfig -e zimbra_prov_default_to_ldap=true
Ok, I tried the first command - same result. Stopped the services using zmcontrol, changed zimbra_prov_default_to_ldap from false to true, started services, and tried the first command again. Still the same error.

Any other ideas?
Reply With Quote
  #4 (permalink)  
Old 10-08-2007, 06:24 PM
Junior Member
 
Posts: 9
Default

Interestingly, when I connect via the external ip address (ie not loopback adapter) I get a different message -
Quote:
ERROR: zclient.IO_ERROR (invoke Remote host closed connection during handshake, server: <ip address here>) (cause: javax.net.ssl.SSLHandshakeException Remote host closed connection during handshake)
Edit: Ok, thats because I added :389 to the end of the ip address. The same thing happens when I add :389 to the ip address of the master ldap server.

Last edited by encode : 10-08-2007 at 07:26 PM.
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