Prod zimbra down due to name change on test server!

[jromo]

I was making a backup copy of the email server to do some testing. I have done this before with 7.0. I duplicated the virtual container (openvz). I then make the DNS changes and ran in the new container while the other was offline:

/opt/zimbra/libexec/zmsetservername -n <servername>

Then rebuild the SSL cert to self issued and deoply it.

Next I reboot the virtual machine. Next thing I know the production email server has the same start issues. It is now trying to use the mx4 name I set in the test server. Both the new test (mx3) and the production (mx3) give the same errors now.

When I start zimbra I get this error:

Starting logswatch...ERROR: account.NO_SUCH_SERVER (no such server: mx3.domain.com)
zimbra logger service is not enabled! failed.

Any ideas what it did to my production box?

Thanks in advance!

[LHammonds]

I'm new to Zimbra so take what I saw with a grain of salt.

Is this a self-contained single server? If so, I have no clue what would cause that but if not, I would imagine that when you brought up the test server and issued the name change, it contacted the same LDAP (?) server production uses. Just a blind guess though.

But regardless, I would reverse the name change on the virtual test server to the way it was, shut it down and see if the production server is corrected.

LHammonds

[jromo]

I see zmsetservername did change the production server ldap stuff.

zimbra@mx3:~$ zmprov -l gacf | grep mx4
zimbraLogHostname: mx4.domain.com
zimbraSmtpHostname: mx4.domain.com

I tried to change it back on the test. But it didn't change on the production. Is there a command to change on the box manually?

I can't seem to run:
zmprov gacf

I get error:
[] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection refused
[] INFO: Retrying request
ERROR: zclient.IO_ERROR (invoke Connection refused, server: localhost) (cause: java.net.ConnectException Connection refused)

I got log and server changed by doing it manually. Now I have:

zmprov -l gs mx4.domain.com

This should be mx3.domain.com I ldap is up, but I can't figure out how to change it.

[jromo]

Okay I got it working. I had to change the IP for mx4 to be the same as mx3. I then had to run:

/opt/zimbra/libexec/zmsetservername --force -n mx3.domain.com

about 4 times. It seems it was having issues connecting to the database. Also, make sure you don't have iptables up blocking the other machine. I didn't have it running at the time, but it did take running the command about 4 times to get it to make the ldap changes.

What a mess. I even stopped the service on the production server during this change. My guess is ldap didn't stop.

[LHammonds]

So this was a single server scenario?

I guess to future-proof this from happening in the future, it would be best to disable network access on the virtual copy before bringing it up. That would keep the virtual from even seeing anything outside of itself until you got everything changed that you needed before re-introducing it back on the network.

LHammonds

[jromo]

Yes this was a single server. I did stop Zimbra, but it seems LDAP was still up. Next time I will just block the test box on the production firewall to make sure it can't connect. Because for the name change it does require access to the DNS server which is on a different network.

Thanks for your help.

[jromo]

How do we mark this thread as SOLVED?

[LHammonds]

How do we mark this thread as SOLVED?

Edit your 1st post, click the "Go Advanced" button and add [SOLVED] to the beginning of the title.

LHammonds