zmsetup.pl wrong server

[jwilson]

I have been testing a migration from one server to another. I accidently typed zmsetup.pl on the wrong server(my production server). Can I recover from this. I am running 3.0.1 open source on centos 4. Any help is appreciated

[jwilson]

wondering if I follow through will I lose everything?

[jholder]

oh man. 3.0.1?

It shouldn't wipe it, but You should create a backup by taring or cping, or rsyncing it to another local..

It should detect it as an upgrade, and that's it. The only thing it'll wipe (if you have one) is an ssl cert, so you'll have to regen a CSR.

Hope this helps,
john

[jwilson]

i followed through with it and got a bunch of erros saying the server name doesn't exist. I did copy the /opt/zimbra folder to another server. Should I just run an upgrade on it since it is down? I didn't set this one up how do I check if there is an ssl cert?

[jholder]

Originally Posted by jwilson

i followed through with it and got a bunch of erros saying the server name doesn't exist. I did copy the /opt/zimbra folder to another server. Should I just run an upgrade on it since it is down? I didn't set this one up how do I check if there is an ssl cert?

I hate to say this, and I'll get flamed, but 3.0.1 was a great release. . but a buggy release as well.

A lot has changed.

I can't really recommend anything until I see the errors you got. Can you paste them?

[jwilson]

This is what I am getting right now.

Setting defaults from saved config in /opt/zimbra/.saveconfig/config.save
HOSTNAME=mail.net
LDAPHOST=
LDAPPORT=
SNMPTRAPHOST=mail.net
SMTPSOURCE=admin@mail.net
SMTPDEST=admin@mail.net
SNMPNOTIFY=yes
SMTPNOTIFY=yes
LDAPROOTPW=********
LDAPZIMBRAPW=*******
Restoring existing configuration file from /opt/zimbra/.saveconfig/config.save...done
Operations logged to /tmp/zmsetup.log.15834
Setting defaults...Setting defaults from existing config...No results returned for MX lookup of vikings.net
Checked nameservers:
192.168.7.1


DNS ERROR resolving MX for vikings.net
It is suggested that the domain name have an MX record configured in DNS
Change domain name? [Yes] yes
Create Domain: [vikings.transolutions.net] mail.net
No results returned for MX lookup of mail.net
Checked nameservers:
192.168.7.1


DNS ERROR resolving MX for mail.net
It is suggested that the domain name have an MX record configured in DNS
Re-Enter domain name? [Yes] no
Done
Checking for port conflicts
Port conflict detected: 80 (zimbra-store)
Port conflict detected: 443 (zimbra-store)
Port conflicts detected! - Any key to continue
Starting ldap...Done
Setting defaults from ldap...ERROR: account.NO_SUCH_SERVER (no such server: mail.transolutions.net)
ERROR: account.NO_SUCH_SERVER (no such server: mail.net)
ERROR: account.NO_SUCH_SERVER (no such server: mail.net)
ERROR: account.NO_SUCH_SERVER (no such server: mail.net)
ERROR: account.NO_SUCH_SERVER (no such server: mail.net)
Done
Checking ldap on localhost:389...Success

[jholder]

I think your best bet is to restore your backup, and try to upgrade to the latest stable (457)

LDAP in 3.0.1 was one step away from horrendous.

[jwilson]

Maybe i'll upgrade to 4.0 I tried 4.5 on my test server and it wiped out my database completely. Right now I still have everyone in the database and all the mail. Please tell me there is a way this will work out.

[jwilson]

if i do a zmcontrol status everything is running except mta.

[jwilson]

this is the error i get from zmcontrol start


Host mail.transolutions.net
Starting antispam...Done.
Starting antivirus...Done.
Starting logger...Done.
Starting mailbox...Done.
Starting mta...FAILED
getService: sasl
getService: webxml
getService: perdition
DO: /opt/zimbra/postfix/sbin/postconf -e content_filter='smtp-amavis:[127.0.0.1]:10024'
DO: /opt/zimbra/postfix/sbin/postconf -e myhostname='mail.transolutions.net'
DO: /opt/zimbra/postfix/sbin/postconf -e recipient_delimiter=''
DO: /opt/zimbra/postfix/sbin/postconf -e smtpd_sasl_auth_enable='yes'
DO: /opt/zimbra/postfix/sbin/postconf -e smtpd_tls_auth_only='no'
DO: /opt/zimbra/postfix/sbin/postconf -e disable_dns_lookups='no'
DO: /opt/zimbra/postfix/sbin/postconf -e message_size_limit='20480000'
DO: /opt/zimbra/postfix/sbin/postconf -e relayhost=''
DO: /opt/zimbra/postfix/sbin/postconf -e smtpd_recipient_restrictions='reject_non_fqdn_reci pient, permit_sasl_authenticated, permit_mynetworks, reject_invalid_hostname, reject_non_fqdn_sender, reject_unauth_destination, permit'
postsuper: Requeued: 33 messages
saslauthd[30236] :set_auth_mech : failed to initialize mechanism zimbra


Starting snmp...Done.
Starting spell...Done.