Trying to mirror our existing 5.0.18 NE server...

[swrightsls]

Originally Posted by phoenix

Moving ZCS to New Server - Zimbra :: Wiki
Preferred Method of Moving Users To New Machine (zmmailboxmove - Network Edition Only) - Zimbra :: Wiki

I've tried the 1st link above in an attempt to build a mirror of server in a VM, so we can test the 6.03 upgrade, but I can't get beyond the first step.

First, I installed 5.018NE on a fresh Ubuntu 8.04 64bit VM install, using the same hostname as the original server, and added an etc/hosts entry to match. I was able to login to the admin console fine. Then I ran:

zmrestoreldap -lb <label> ( Label of latest full backup )

after making a link to the backup path of the production server, and it appeared to restore all the accounts to the directory:

added: .....
added: "uid=academics,ou=people,dc=shawnigan,dc=ca" (00000375)
added: ....
Starting ldap...Started slapd: pid 28908
done.

Then I ran:

zmrestore -sys -ra -a all -c

Error occurred: system failure: Unable to connect to LDAP directory

zimbra@zimbra64:~$ zmcontrol status
Unable to determine enabled services from ldap.
Enabled services read from cache. Service list may be inaccurate.
Host mail.shawnigan.ca
        antispam                Running
        antivirus               Running
        convertd                Running
        ldap                    Running
        logger                  Running
        mailbox                 Running
        mta                     Running
        snmp                    Running
        spell                   Running
        stats                   Running
zimbra@zimbra64:~$ netstat -l
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 *:7780                  *:*                     LISTEN
tcp        0      0 mail.shawnigan.ca:ldap  *:*                     LISTEN
tcp        0      0 *:7047                  *:*                     LISTEN
tcp        0      0 localhost:10024         *:*                     LISTEN
tcp        0      0 localhost:10025         *:*                     LISTEN
tcp        0      0 localhost:7306          *:*                     LISTEN
tcp        0      0 localhost:7307          *:*                     LISTEN
tcp        0      0 *:netbios-ssn           *:*                     LISTEN
tcp        0      0 *:3310                  *:*                     LISTEN
tcp        0      0 *:ssmtp                 *:*                     LISTEN
tcp        0      0 *:smtp                  *:*                     LISTEN
tcp        0      0 *:microsoft-ds          *:*                     LISTEN
tcp6       0      0 [::]:7072               [::]:*                  LISTEN
tcp6       0      0 [::]:7777               [::]:*                  LISTEN
tcp6       0      0 [::]:imaps              [::]:*                  LISTEN
tcp6       0      0 [::]:pop3s              [::]:*                  LISTEN
tcp6       0      0 [::]:xmpp-client        [::]:*                  LISTEN
tcp6       0      0 [::]:5223               [::]:*                  LISTEN
tcp6       0      0 [::]:7335               [::]:*                  LISTEN
tcp6       0      0 [::]:pop3               [::]:*                  LISTEN
tcp6       0      0 [::]:imap2              [::]:*                  LISTEN
tcp6       0      0 [::]:www                [::]:*                  LISTEN
tcp6       0      0 [::]:7025               [::]:*                  LISTEN
tcp6       0      0 [::]:xmpp-server        [::]:*                  LISTEN
tcp6       0      0 [::]:ssh                [::]:*                  LISTEN
tcp6       0      0 [::]:10015              [::]:*                  LISTEN
tcp6       0      0 [::]:7071               [::]:*                  LISTEN
udp        0      0 10.4.1.23:netbios-ns    *:*
udp        0      0 *:netbios-ns            *:*
udp        0      0 10.4.1.23:netbios-dgm   *:*
udp        0      0 *:netbios-dgm           *:*
udp        0      0 *:bootpc                *:*

Where did I go wrong? I really need to get a mirror of our production server running, so I can test the 6.x upgrade, as I am not comfortable with 30+ minutes of downtime followed by a lack of certainty as to the sucess of the upgrade, and no experience with the rollback procedure if it fails. (as you might guess, this will be the first upgrade since we went live in July).

[ArcaneMagus]

I moved this to a new thread as it had nothing really to do with the old thread.

(I also put in [code] tags so it wouldn't add random in there)

[ArcaneMagus]

Did you setup Split DNS - Zimbra :: Wiki on the VM?

Also what is the output of the following commands:

cat /etc/hosts
dig mail.shawnigan.ca A
lsof -i :389 | grep LISTEN
host `hostname`

The output of the lsof should show that slapd with zimbra as the user is hte program listening on port 389.

[swrightsls]

Thanks for the tip on the split DNS. I suspected that was part of it, but this article saved some time. I setup split DNS, and re-install ZCS, then re-ran the zmrestoreldap, which again re-created the accounts, but then failed to connect to LDAP when attempting a zmrestore.

Here is the output requested:

#cat /etc/hosts
127.0.0.1       localhost
127.0.1.1       mail.shawnigan.ca       mail

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

# dig mail.shawnigan.ca A

; <<>> DiG 9.4.2-P2 <<>> mail.shawnigan.ca A
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40713
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mail.shawnigan.ca.             IN      A

;; ANSWER SECTION:
mail.shawnigan.ca.      2592000 IN      A       127.0.0.1

;; AUTHORITY SECTION:
mail.shawnigan.ca.      2592000 IN      NS      127.0.0.1.mail.shawnigan.ca.

;; Query time: 2 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Dec  3 14:26:07 2009
;; MSG SIZE  rcvd: 75

# lsof -i :389 |grep LISTEN
slapd   30770 zimbra    7u  IPv4 677281       TCP mail.shawnigan.ca:ldap (LISTEN)

# host `hostname`
mail.shawnigan.ca has address 127.0.0.1
mail.shawnigan.ca mail is handled by 10 mail.shawnigan.ca.

zimbra.log shows this, but I'm not certain which credentials are referred to...

Dec  3 14:38:21 mail zimbramon[8070]: 8070:info: zmmtaconfig: Skipping getAllMtaAuthURLs ERROR: service.FAILURE (system failure: unable to list all servers) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])
Dec  3 14:38:24 mail zimbramon[8070]: 8070:info: zmmtaconfig: Skipping Configuration for server mail.shawnigan.ca update.
Dec  3 14:38:24 mail zimbramon[8070]: 8070:info: zmmtaconfig: gs:mail.shawnigan.ca ERROR: service.FAILURE (system failure: unable to lookup server by name: mail.shawnigan.ca message: [LDAP: error code 49 - Invalid Credentials]) (cause: javax.naming.AuthenticationException [LDAP: error code 49 - Invalid Credentials])

[ArcaneMagus]

Everywhere that you have 127.0.0.1, it should be 10.4.1.23 (assuming that is the LAN ip address)

The only place that should have 127.0.0.1 is the localhost line in /etc/hosts, which should look like this:

127.0.0.1 localhost.localdomain localhost

The invalid credentials would be referring to the ldap password that zmmtaconfig is trying to access the config with. Since you have restored the LDAP database from the main server, the password doesn't match the random one created on install. (I would assume the zmrestore process is supposed to fix the config files).

[rusty]

I'm having the same exact problem. I'm moving 5.0.18 to a new server, same OS (Ubuntu 8.04). I ran zmrestoreldap without problem. Now when I run zmrestore I get the same error as above, "Unable to connect to LDAP directory".

Can I manually change the new installation password to match the old server? If so, where do I edit the new password? Thanks!

[rusty]

I removed and reinstalled ZCS, this time setting the old ldap password in the configuration screen during install. This resolved the issue for me.

[swrightsls]

Still trying to tackle this issue. I've referred to the original config from the initial installation of the production server last year, and installed the VM machine in exactly the same way, after configuring splitdns correctly. I believe the ldap issue was related to a "zcsetservername" that was done to change the server name of the original box. So I followed the same steps - installed exactly as per the original, then changed the server name.

The ldaprestore then worked fine - all accounts were restored without error.
Then I got the following:

zimbra@mail:~$ zmrestoreoffline -sys -a all -c -br
mailboxd is not running.
zimbra@mail:~$ zmmailboxdctl start
Starting mailboxd...done.
zimbra@mail:~$ zmrestoreoffline -sys -a all -c -br
mailboxd is running.
Error: mailboxd still running. Stop mailboxd before running zmrestoreoffline.

Going back a step, I also got this error:

zimbra@mail:~$ zmconvertctl start
httpd: Could not reliably determine the server's fully qualified domain name, using 10.4.1.23 for ServerName
zimbra@mail:~$ nslookup 10.4.1.23
Server: 127.0.0.1
Address: 127.0.0.1#53

23.1.4.10.in-addr.arpa name = mail.shawnigan.ca.

dig -x 10.4.1.23

; <<>> DiG 9.4.2-P2 <<>> -x 10.4.1.23
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61154
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2

;; QUESTION SECTION:
;23.1.4.10.in-addr.arpa. IN PTR

;; ANSWER SECTION:
23.1.4.10.in-addr.arpa. 604800 IN PTR mail.shawnigan.ca.

The system is running bind to resolve A,MX,PTR queries correctly for the local machine, so this error doesn't make sense to me.

I've now opened a support ticket, as we can't wait any longer to sort this out. I need to see this upgrade from 5.0.18 to 6.0.5 complete in a testbed before I attempt it on a live system. I also would feel a *lot* better having some estimate of how long it will take to complete.

I'm waiting for a response to my ticket, and will post any relevant info here in case it helps others.

Thanks.