Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators
Reload this Page upgrade broke server :Unable to connect to the MTA

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
Page 1 of 2 1 2
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 02-02-2010, 01:49 PM
Junior Member
  
Posts: 8
Default upgrade broke server :Unable to connect to the MTA
I upgraded zcs from 5.0.2 to 6.0.4 by running the latest installer. The upgrade seemed to go without error and I was impressed with the installer's ability to find things previously installed during the upgrade. However, I and getting the following "Unable to connect to MTA" error on the upgraded system. No emails in or out after the upgrade.

So the error seems to be obvious from the attached zimbra.log file, no MTA service running. In fact, none of the previous services appear to be running after the upgrade like anti-spam, anti-virus, etc. Although, Apache is up and I can log into zimbra over http. You can see were I started the upgrade at 14:10. I reverted to a backup for now.

************************************************** **
An unknown error (mail.TRY_AGAIN) has occurred.
method: SendMsgRequest
msg: try again: Unable to connect to the MTA
code: mail.TRY_AGAIN
detail: soap:Receiver
....
************************************************** ***

Take care,
Ed
Attached Files
File Type: log zimbra.log (170.5 KB, 9 views)
Reply With Quote
  #2 (permalink)  
Old 02-02-2010, 08:40 PM
Moderator
  
Posts: 7,929
Default
Welcome to the forums

Please post the following information
Code:
cat /etc/hosts
cat /etc/resolv.conf
dig yourdomain mx
dig yourdomain any
host `hostname` <- note backticks and not single quotes
su - zimbra
zmhostname
__________________
Reply With Quote
  #3 (permalink)  
Old 02-03-2010, 08:50 AM
Junior Member
  
Posts: 8
Default
I put output from both old system and new system below.

************* zcs 5.0.2 before upgrade **************
************************************************** ***

root@zimbra:/home/mtsuser# cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 zimbra.microtechcorp.com zimbra
173.12.26.121 zimbra.microtechcorp.com mail.microtechcorp.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
root@zimbra:/home/mtsuser# cat /etc/resolv.conf
search microtechcorp.com inside
nameserver 10.1.60.32
nameserver 68.87.64.150
nameserver 68.87.75.198
root@zimbra:/home/mtsuser# dig microtechcorp.com mx

; <<>> DiG 9.4.2-P2 <<>> microtechcorp.com mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31998
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

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

;; ANSWER SECTION:
microtechcorp.com. 3600 IN MX 10 mail.microtechcorp.com.

;; AUTHORITY SECTION:
microtechcorp.com. 77414 IN NS ns4.nameresolve.com.
microtechcorp.com. 77414 IN NS ns2.nameresolve.com.
microtechcorp.com. 77414 IN NS ns3.nameresolve.com.
microtechcorp.com. 77414 IN NS ns1.nameresolve.com.

;; ADDITIONAL SECTION:
ns1.nameresolve.com. 102428 IN A 64.94.117.199
ns2.nameresolve.com. 102428 IN A 63.251.83.88
ns3.nameresolve.com. 102428 IN A 66.150.161.151
ns4.nameresolve.com. 102428 IN A 64.94.31.66

;; Query time: 117 msec
;; SERVER: 10.1.60.32#53(10.1.60.32)
;; WHEN: Wed Feb 3 11:08:48 2010
;; MSG SIZE rcvd: 204

root@zimbra:/home/mtsuser# dig microtechcorp.com any

; <<>> DiG 9.4.2-P2 <<>> microtechcorp.com any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26493
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 4, ADDITIONAL: 4

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

;; ANSWER SECTION:
microtechcorp.com. 3584 IN MX 10 mail.microtechcorp.com.
microtechcorp.com. 77398 IN NS ns1.nameresolve.com.
microtechcorp.com. 77398 IN NS ns4.nameresolve.com.
microtechcorp.com. 77398 IN NS ns2.nameresolve.com.
microtechcorp.com. 77398 IN NS ns3.nameresolve.com.

;; AUTHORITY SECTION:
microtechcorp.com. 77398 IN NS ns3.nameresolve.com.
microtechcorp.com. 77398 IN NS ns1.nameresolve.com.
microtechcorp.com. 77398 IN NS ns2.nameresolve.com.
microtechcorp.com. 77398 IN NS ns4.nameresolve.com.

;; ADDITIONAL SECTION:
ns1.nameresolve.com. 102412 IN A 64.94.117.199
ns2.nameresolve.com. 102412 IN A 63.251.83.88
ns3.nameresolve.com. 102412 IN A 66.150.161.151
ns4.nameresolve.com. 102412 IN A 64.94.31.66

;; Query time: 1 msec
;; SERVER: 10.1.60.32#53(10.1.60.32)
;; WHEN: Wed Feb 3 11:09:04 2010
;; MSG SIZE rcvd: 260

root@zimbra:/home/mtsuser# host `hostname`
zimbra.microtechcorp.com has address 173.12.26.121
root@zimbra:/home/mtsuser# su - zimbra
zimbra@zimbra:~$ zmhostname
zimbra.microtechcorp.com
zimbra@zimbra:~$


************* zcs 6.0.4 after upgrade **************
************************************************** ***
root@zimbra:/home/mtsuser# cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 zimbra.microtechcorp.com zimbra
173.12.26.121 zimbra.microtechcorp.com mail.microtechcorp.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
root@zimbra:/home/mtsuser# cat /etc/resolv.conf
search microtechcorp.com inside
nameserver 10.1.60.32
nameserver 68.87.64.150
nameserver 68.87.75.198
root@zimbra:/home/mtsuser# dig microtechcorp.com mx

; <<>> DiG 9.4.2-P2 <<>> microtechcorp.com mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26310
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

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

;; ANSWER SECTION:
microtechcorp.com. 1561 IN MX 10 mail.microtechcorp.com.

;; AUTHORITY SECTION:
microtechcorp.com. 75375 IN NS ns1.nameresolve.com.
microtechcorp.com. 75375 IN NS ns2.nameresolve.com.
microtechcorp.com. 75375 IN NS ns4.nameresolve.com.
microtechcorp.com. 75375 IN NS ns3.nameresolve.com.

;; ADDITIONAL SECTION:
ns1.nameresolve.com. 100389 IN A 64.94.117.199
ns2.nameresolve.com. 100389 IN A 63.251.83.88
ns3.nameresolve.com. 100389 IN A 66.150.161.151
ns4.nameresolve.com. 100389 IN A 64.94.31.66

;; Query time: 1 msec
;; SERVER: 10.1.60.32#53(10.1.60.32)
;; WHEN: Wed Feb 3 11:42:51 2010
;; MSG SIZE rcvd: 204

root@zimbra:/home/mtsuser# dig microtechcorp.com any

; <<>> DiG 9.4.2-P2 <<>> microtechcorp.com any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 320
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 4, ADDITIONAL: 4

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

;; ANSWER SECTION:
microtechcorp.com. 1851 IN A 173.12.26.124
microtechcorp.com. 1558 IN MX 10 mail.microtechcorp.com.
microtechcorp.com. 75372 IN NS ns3.nameresolve.com.
microtechcorp.com. 75372 IN NS ns1.nameresolve.com.
microtechcorp.com. 75372 IN NS ns2.nameresolve.com.
microtechcorp.com. 75372 IN NS ns4.nameresolve.com.

;; AUTHORITY SECTION:
microtechcorp.com. 75372 IN NS ns1.nameresolve.com.
microtechcorp.com. 75372 IN NS ns2.nameresolve.com.
microtechcorp.com. 75372 IN NS ns3.nameresolve.com.
microtechcorp.com. 75372 IN NS ns4.nameresolve.com.

;; ADDITIONAL SECTION:
ns1.nameresolve.com. 100386 IN A 64.94.117.199
ns2.nameresolve.com. 100386 IN A 63.251.83.88
ns3.nameresolve.com. 100386 IN A 66.150.161.151
ns4.nameresolve.com. 100386 IN A 64.94.31.66

;; Query time: 1 msec
;; SERVER: 10.1.60.32#53(10.1.60.32)
;; WHEN: Wed Feb 3 11:42:54 2010
;; MSG SIZE rcvd: 276

root@zimbra:/home/mtsuser# host `hostname`
zimbra.microtechcorp.com has address 173.12.26.121
root@zimbra:/home/mtsuser# su - zimbra
zimbra@zimbra:~$ zmhostname
zimbra.microtechcorp.com
Reply With Quote
  #4 (permalink)  
Old 02-03-2010, 09:20 AM
Junior Member
  
Posts: 8
Default
I forgot to mention that the system is 32-bit Ubuntu Server 8.0.4 LTS with all the latest updates. The installer came from here:

http://h.yimg.com/lo/downloads/6.0.4...1214184037.tgz


Ed
Reply With Quote
  #5 (permalink)  
Old 02-03-2010, 09:21 AM
Zimbra Consultant & Moderator
  
Posts: 20,317
Default
Your file as shown above is incorrect:
Code:
root@zimbra:/home/mtsuser# cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 zimbra.microtechcorp.com zimbra
173.12.26.121 zimbra.microtechcorp.com mail.microtechcorp.com
It should contain only the following (as per the Quick Start Installation Guide and numerous forum threads):

Code:
127.0.0.1 localhost.localdomain localhost
173.12.26.121 zimbra.microtechcorp.com zimbra
__________________
Regards


Bill
Reply With Quote
  #6 (permalink)  
Old 02-03-2010, 09:56 AM
Junior Member
  
Posts: 8
Default
I changed it, then reboot the system. I'm still getting the same error.

mtsuser@zimbra:~$ cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
173.12.26.121 zimbra.microtechcorp.com zimbra


# 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
Reply With Quote
  #7 (permalink)  
Old 02-03-2010, 10:02 AM
Junior Member
  
Posts: 8
Default
Here is a cat of my startup.log in /opt/zimbra/log/. It looks like mta is failing to start. Not sure why?

***********************************
Host zimbra.microtechcorp.com
Stopping stats...Done.
Stopping mta...Done.
Stopping spell...Done.
Stopping snmp...Done.
Stopping archiving...Done.
Stopping antivirus...Done.
Stopping antispam...Done.
Stopping imapproxy...Done.
Stopping memcached...Done.
Stopping mailbox...Done.
Stopping logger...Done.
Stopping ldap...Done.
Host zimbra.microtechcorp.com
Starting ldap...Done.
Starting logger...Failed.
Starting logswatch...failed.


Starting mailbox...Done.
Starting antispam...Done.
Starting antivirus...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...Failed.
Starting zmmtaconfig...zmmtaconfig is already running.
postmap: fatal: bad string length 0 < 1: mail_owner =
postalias: fatal: bad string length 0 < 1: mail_owner =
postfix failed to start
Starting saslauthd...done.


Starting stats...Done.
Host zimbra.microtechcorp.com
Starting ldap...Done.
Starting logger...Failed.
Starting logswatch...failed.


Starting mailbox...Done.
Starting antispam...Done.
Starting antivirus...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...Failed.
Starting zmmtaconfig...zmmtaconfig is already running.
postmap: fatal: bad string length 0 < 1: mail_owner =
postalias: fatal: bad string length 0 < 1: mail_owner =
postfix failed to start
Starting saslauthd...done.


Starting stats...Done.
Host zimbra.microtechcorp.com
Starting ldap...Done.
Starting logger...Failed.
Starting logswatch...failed.


Starting mailbox...Done.
Starting antispam...Done.
Starting antivirus...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...Failed.
Starting zmmtaconfig...zmmtaconfig is already running.
postmap: fatal: bad string length 0 < 1: mail_owner =
postalias: fatal: bad string length 0 < 1: mail_owner =
postfix failed to start
Starting saslauthd...done.


Starting stats...Done.
Host zimbra.microtechcorp.com
Starting ldap...Done.
Starting logger...Failed.
Starting logswatch...failed.


Starting mailbox...Done.
Starting antispam...Done.
Starting antivirus...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...Failed.
Starting zmmtaconfig...zmmtaconfig is already running.
postmap: fatal: bad string length 0 < 1: mail_owner =
postalias: fatal: bad string length 0 < 1: mail_owner =
postfix failed to start
Starting saslauthd...done.


Starting stats...Done.
Reply With Quote
  #8 (permalink)  
Old 02-03-2010, 10:09 AM
Zimbra Consultant & Moderator
  
Posts: 20,317
Default
Shut down Zimbra and run this (as root) then restart Zimbra:

Code:
/opt/zimbra/libexec/zmfixperms
__________________
Regards


Bill
Reply With Quote
  #9 (permalink)  
Old 02-03-2010, 10:30 AM
Junior Member
  
Posts: 8
Default
I ran /opt/zimbra/libexec/zmfixperms, then rebooted the system. MTA still does not start. I noticed that logger and logswatch also do not start? The installer did complain about sysstat not being installed, so I quit the install when prompted and did an apt-get install sysstat, then rerun the installer. Not sure if relevant? My latest tail on startup.log, look like the zmfixperms did not resolve the problem.


*********************************
Starting stats...Done.
Host zimbra.microtechcorp.com
Starting ldap...Done.
Starting logger...Failed.
Starting logswatch...failed.


Starting mailbox...Done.
Starting antispam...Done.
Starting antivirus...Done.
Starting snmp...Done.
Starting spell...Done.
Starting mta...Failed.
Starting zmmtaconfig...zmmtaconfig is already running.
postmap: fatal: bad string length 0 < 1: mail_owner =
postalias: fatal: bad string length 0 < 1: mail_owner =
postfix failed to start
Starting saslauthd...done.


Starting stats...Done.
Reply With Quote
  #10 (permalink)  
Old 02-03-2010, 10:34 AM
Zimbra Consultant & Moderator
  
Posts: 20,317
Default
Have a look in the log files and see if there's any other errors in there, post them if there is.
__________________
Regards


Bill
Reply With Quote
Reply
Page 1 of 2 1 2

« Previous Thread | Today's Posts or Week's Posts | Next Thread »

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode


Similar Threads

Product Information

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com


Home - Blog - Contact Us - Archive - Top


 

SEO by vBSEO ©2011, Crawlability, Inc.