Zimbra Upgrade Failure

[3RiversTechAdmin]

OS: Ubuntu 6.06 LTS (32-bit)

I had an upgrade failure today moving from 5.0.6_GA_2313 to 6.0.3_GA_1915.
First the installer said it did not like my host file (the one 5.0.6 is using) so I made changes until it was happy, and proceeded. After updating the database schema and in the process of updating ldap the install failed.

Here follow my original host file, the new host file accepted by the installer and the tail of the installer's log of the failure. Any ideas or suggestions would be appreciated.

Original hosts file

127.0.0.1 localhost localhost.localdomain  myServer.myDomain.com myServer mail mail.myDomain.com localhost.myDomain.com
# 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

New hosts file

192.168.7.6	myServer.myDomain.com	myServer 
192.168.7.6	mail.myDomain.com	mail
127.0.0.1 localhost.localdomain localhost

# 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

Note: I tried using 127.0.0.1 for all entries (as to match the first file), but that would not be accepted.

Install failure log

Sat Nov 28 14:23:57 2009 Stopping mysql...
Sat Nov 28 14:23:57 2009 *** Running as zimbra user: /opt/zimbra/bin/mysql.server stop
Stopping mysqld... done.
Sat Nov 28 14:24:12 2009 done.
Sat Nov 28 14:24:13 2009 Installing LDAP configuration database...
Sat Nov 28 14:24:13 2009 done.
Sat Nov 28 14:24:13 2009 Migrating ldap data...
Sat Nov 28 14:24:13 2009 *** Running as zimbra user: /opt/zimbra/openldap/sbin/slapadd -q -b '' -F /opt/zimbra/data/ldap/config -l /opt/zimbra/data/ldap/ldap.60
Sat Nov 28 14:24:14 2009 done.
Sat Nov 28 14:24:14 2009 Checking ldap status...
Sat Nov 28 14:24:14 2009 *** Running as zimbra user: /opt/zimbra/bin/ldap status
Sat Nov 28 14:24:14 2009 not running.
Sat Nov 28 14:24:14 2009 Running zmldapapplyldif...
Sat Nov 28 14:24:14 2009 *** Running as zimbra user: /opt/zimbra/libexec/zmldapapplyldif
IO::Socket::INET: connect: Connection refused at /opt/zimbra/libexec/zmldapapplyldif line 125.
Sat Nov 28 14:24:54 2009 failed.
Sat Nov 28 14:24:54 2009 Checking ldap status...
Sat Nov 28 14:24:54 2009 *** Running as zimbra user: /opt/zimbra/bin/ldap status
Sat Nov 28 14:24:54 2009 not running.
Sat Nov 28 14:24:54 2009 Starting ldap...
Sat Nov 28 14:24:54 2009 *** Running as zimbra user: /opt/zimbra/bin/ldap start
Failed to start slapd.  Attempting debug start to determine error.
daemon: bind(7) failed errno=99 (Cannot assign requested address)
slap_open_listener: failed on ldap://myServer.myDomain.com:389

Sat Nov 28 14:25:31 2009 failed with exit code: 256.
Sat Nov 28 14:27:07 2009 UPGRADE FAILED - exiting.

Any ideas would be great, I am guessing it might be some kind of ldap restriction based on accessing IP address?

[mmorse]

The old and new hostsfile you pasted match (probably just didn't copy properly the 2nd time) and I assume you corrected it too two lines.

Post the output of the following (mask names & IP's as you wish but give us the last part/digits or something so we know things match).

ifconfig
more /etc/resolv.conf 
dig mx domain.com
dig any domain.com
host `hostname` (as is and backticks not single quotes)

[3RiversTechAdmin]

Thank you for taking your time to help me.

Yes, I made a copy mistake, I have edited my original post.

ifconfig

eth0      Link encap:Ethernet  HWaddr XXXXXXXXXXXXX  
          inet addr:192.168.7.9  Bcast:192.168.7.255  Mask:255.255.255.0
          inet6 addr: fe80::213:20ff:fe17:f140/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:253403750 errors:0 dropped:0 overruns:0 frame:0
          TX packets:217249528 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2954167875 (2.7 GiB)  TX bytes:225199287 (214.7 MiB)
          Interrupt:169 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:503990694 errors:0 dropped:0 overruns:0 frame:0
          TX packets:503990694 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2944744144 (2.7 GiB)  TX bytes:2944744144 (2.7 GiB)

resolv.conf

search myDomain.com
nameserver 192.168.7.6
nameserver 207.230.192.251
nameserver 209.142.152.253
nameserver 209.206.184.249

dig mx

; <<>> DiG 9.3.2-P2.1 <<>> mx myDomain.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 785
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

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

;; AUTHORITY SECTION:
com.			900	IN	SOA	a.gtld-servers.net. nstld.verisign-grs.com. 1259444599 1800 900 604800 86400

;; Query time: 33 msec
;; SERVER: 192.168.7.6#53(192.168.7.6)
;; WHEN: Sat Nov 28 15:43:42 2009
;; MSG SIZE  rcvd: 105

dig any

dig any myDomain.com

; <<>> DiG 9.3.2-P2.1 <<>> any myDomain.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1305
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 2

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

;; ANSWER SECTION:
myDomain.com.	172800	IN	SOA	dns.myDomain.com. root.myDomain.com. 2006101862 86400 7200 604800 172800
myDomain.com.	172800	IN	NS	dns.myDomain.com.
myDomain.com.	600	IN	A	192.168.7.7
myDomain.com.	172800	IN	MX	10 mail.myDomain.com.
myDomain.com.	172800	IN	TXT	"v=spf1 a mx a:mail.myDomain.com ~all"

;; ADDITIONAL SECTION:
dns.myDomain.com.	172800	IN	A	192.168.7.6
mail.myDomain.com.	172800	IN	A	192.168.7.9

;; Query time: 0 msec
;; SERVER: 192.168.7.6#53(192.168.7.6)
;; WHEN: Sat Nov 28 15:45:51 2009
;; MSG SIZE  rcvd: 215

host `hostname`

badger.myDomain.com has address 192.168.7.9

[Klug]

As your server is on a private IP, I guess you're using splitDNS.
If you are, only the splitDNS server (192.168.7.6) should be in your resolv.conf file.

The "connection refused" LDAP error can be caused by a broken certificate or CA (too old).