Thanks but now I get this. I doubt this is neither a dns or /etc/hosts problem.

Do you actually have the correct DNS records and hosts file? Confirmation would help determine if this is the case, run these commands on the zimbra server and post the results:

Code:

host `hostname`
dig yourdomain.com mx
dig yourdomain.com any

Originally Posted by james-m

daemon: bind(7) failed errno=98 (Address already in use)

That indicates there's another process running on that port. Do you have another LDAP server running? Did you kill off all the Zimbra services before running the upgrade again? There's also a Troubleshooting guide in the wiki, have you tried those steps.

Thanks! Below is what I was able to query
===================
mailadmin@mail:~/zcs$ host mail
mail.pb.co.za has address 10.0.0.101
mail.pb.co.za mail is handled by 10 mail.pb.co.za.
mailadmin@mail:~/zcs$ clear

I believe by default Ubuntu server will install as a LAMP server, therefore you will get a lot of port conflicts. IMHO best thing would be to clean out your installation and start again. Prior to this, once all Zimbra services are closed down, run a sudo netstat -an to see what ports are open eg. 80 and Apache instead of killing of the process, like what was done for slapd, actually use the /etc/init.d/apache2 stop functionality as this will tidy up the files, remove any necessary locks, and shut it down cleanly.

Ok thanks. Truth is I have in the past successfully installed and ran Zimbra on dapper (Ubuntu v. 6 that is). It's ease of use and rich Ajax interface were compelling reasons I tried it out and bragged about it to my clients. What I don't like is dapper's rather old kernel which I am trying to avoid. Otherwise excellent work on a more than compelling application.