[SOLVED] failed to start slapd after cloning

[bhwong]

As we are migrating our existing Zimbra from one ESXi to another ESXi server, and we want to keep a copy as a backup, so we clone the Zimbra into another ESXi. But when we startup the cloned Zimbra (the original Zimbra has already shutdown) and execute zmcontrol start, we receive an error message saying that it failed to start slapd. Any idea why this is happening?

[phoenix]

Originally Posted by bhwong

As we are migrating our existing Zimbra from one ESXi to another ESXi server, and we want to keep a copy as a backup, so we clone the Zimbra into another ESXi. But when we startup the cloned Zimbra (the original Zimbra has already shutdown) and execute zmcontrol start, we receive an error message saying that it failed to start slapd. Any idea why this is happening?

It could be any number of reasons, how about looking in the log files and give us a hint about what the problem might be?

[vizapata]

Well I am trying to recover an installation with similar trouble.

My problem started when I try to install a previous version.

I'll work on this topic, if there are good things, I will publish!

[vizapata]

The first thing to review is your DNS config. Maybe this info is useful for you Split DNS - Zimbra :: Wiki.

[psgandalf]

Most of the times the problem with cloning a virtual machine is the nic. Check /etc/network/interfaces
and do a ifconfig

[bhwong]

The problem has been resolved. I notice that vmware automatically amend the network setting from static IP to roaming mode (dynamic IP) for the cloned Linux VM, which is very impressive but not desirable. After re-configuring the network adaptor back to it's original IP address, slapd is able to startup.

btw, this does mean that we won't be able to amend our IP address if we intend to shift our Zimbra server to another site with difference subnet, isn't it?

[psgandalf]

It should work to move to another subnet. You have atleast to reconfigure the hostfile and bind information or other dns information on the mailserver. I dont recall if there is something in the Zimbra config that has to be updated when changeing the ipaddress of the server.

[bhwong]

My experience is that both Zimbra (especially ldap) and vmware vCenter varies services will break once IP address is changed. The only solution is to reinstall them to resolve it.