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

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 10-02-2009, 01:47 PM
New Member
 
Posts: 4
Default zcs migration ldap error 256

Hey all,
I'm new to the forums and to Zimbra. I've heard about it and was excited to see it work! I have been asked by a client to essentially "recover" a ZCS 5.0.4 install and I'm having trouble getting it to run.

A little more background on this situation first, we don't need the new machine to send or receive mail, it just needs to be up for the users to retrieve their mail and then we're going to repurpose the server. I think they've migrated to Exchange (not my choice). There is an A record for the FQDN (same as original), but no MX record right now. It is on a different IP though.

I found this and followed the steps for the most part. I took a snapshot of the files from the old server (I think it was just a cp not an rsync though). I installed ZCS (Release 5.0.4_GA_2101.RHEL5_64_20080321154100 CentOS5_64) on the new server using the install.sh -s command, moved the /opt/zimbra directory out of the way and rsynced the old files to /opt/zimbra and ran zmfixperms. Upon running the install again (with --platform-override), I can't get passed the main menu configurations screen.

Even after I address those items with a <b>**</b> it will not let me continue. Here's a snippet of the setup.log:

zimbra-snmp is enabled
Checking ldap on zimbra.XXXXXX.org:389
Unable to startTLS: Transport endpoint is not connected
Couldn't bind to zimbra.XXXXXX.org as uid=zimbra,cn=admins,cn=zimbra
Checking ldap on zimbra.XXXXXX.org:389
Unable to startTLS: Transport endpoint is not connected
Couldn't bind to zimbra.XXXXXX.org as uid=zimbra,cn=admins,cn=zimbra
Checking ldap on zimbra.XXXXXX.org:389
Unable to startTLS: Transport endpoint is not connected
Couldn't bind to zimbra.XXXXXX.org as uid=zimbra,cn=admins,cn=zimbra

Any ideas? I don't know what the ldap root password was set up to be, and if I need to reset it, that's fine, I just need to know how (if that is the problem).

Thanks.
Reply With Quote
  #2 (permalink)  
Old 10-02-2009, 01:51 PM
Zimbra Consultant & Moderator
 
Posts: 19,653
Default

You need valid A & MX records pointing at the Zimbra server and a correct hosts file, I'd suggest a quick search through the forums for posts by me (and others) that describe a Split DNS set-up (which is what you need) and the tests for checking it.
__________________
Regards


Bill
Reply With Quote
  #3 (permalink)  
Old 10-02-2009, 02:03 PM
New Member
 
Posts: 4
Default

Hi Bill,
I just finished setting up the split dns and have verified that it's working using the page you referred to. I restarted slapd and it's still giving me the same "transport endpoint is not connected errors".

Also, I apologize that I put the wrong subject in my post. It should be something like "Transport endpoint is not connected".
Reply With Quote
  #4 (permalink)  
Old 10-02-2009, 11:45 PM
Zimbra Consultant & Moderator
 
Posts: 19,653
Default

Let's check the DNS before we go any further, post the output of the following (run on the Zimbra server):

Code:
cat /etc/hosts
cat /etc/resolv.conf
dig yourdomain.com mx
dig yourdomain.com any
host `hostname`  <-- use that exact command with backticks not single quotes
__________________
Regards


Bill
Reply With Quote
  #5 (permalink)  
Old 10-04-2009, 08:43 PM
New Member
 
Posts: 4
Default Here is the output, but I've changed the domain name from my client to XXXXXX.com

[root@zimbra ~]# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
# Auto-generated hostname. Please do not remove this comment.
69.72.194.149 zimbra.XXXXXX.com zim3.YYYYYY.com zim3

[root@zimbra ~]# cat /etc/resolv.conf
nameserver 127.0.0.1

[root@zimbra ~]# dig XXXXXX.com mx

; <<>> DiG 9.3.4-P1 <<>> XXXXXX.com mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39853
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;XXXXXX.com. IN MX

;; ANSWER SECTION:
XXXXXX.com. 43142 IN MX 10 wall01.imailcleaner.com.
XXXXXX.com. 43142 IN MX 20 wallbu01.peertopeer.net.

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Oct 4 22:39:32 2009
;; MSG SIZE rcvd: 103

[root@zimbra ~]# dig XXXXXX.com any

; <<>> DiG 9.3.4-P1 <<>> XXXXXX.com any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60381
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;XXXXXX.com. IN ANY

;; ANSWER SECTION:
XXXXXX.com. 43075 IN MX 20 wallbu01.peertopeer.net.
XXXXXX.com. 43075 IN MX 10 wall01.imailcleaner.com.
XXXXXX.com. 1672 IN A 69.72.194.155

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Oct 4 22:40:39 2009
;; MSG SIZE rcvd: 119



[root@zimbra ~]# host `hostname`
zimbra.XXXXXX.com has address 69.72.194.149
zimbra.XXXXXX.com mail is handled by 10 zimbra.XXXXXX.com.

Thanks again Bill.
Reply With Quote
  #6 (permalink)  
Old 10-05-2009, 01:50 AM
Moderator
 
Posts: 7,911
Default

Your MX record is not pointing at your ZCS server.
__________________
Reply With Quote
  #7 (permalink)  
Old 10-05-2009, 11:20 PM
New Member
 
Posts: 4
Default

Should it be the MX for the XXXXXX.com domain or for the host.XXXXXX.com domain?
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.