Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: upgrade broke server :Unable to connect to the MTA

  1. #1
    esb123 is offline Junior Member
    Join Date
    Feb 2010
    Posts
    8
    Rep Power
    5

    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 Attached Files

  2. #2
    uxbod's Avatar
    uxbod is offline Moderator
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    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

  3. #3
    esb123 is offline Junior Member
    Join Date
    Feb 2010
    Posts
    8
    Rep Power
    5

    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

  4. #4
    esb123 is offline Junior Member
    Join Date
    Feb 2010
    Posts
    8
    Rep Power
    5

    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

  5. #5
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,585
    Rep Power
    57

    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


    Acompli: A new adventure for Co-Founder KevinH.

  6. #6
    esb123 is offline Junior Member
    Join Date
    Feb 2010
    Posts
    8
    Rep Power
    5

    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

  7. #7
    esb123 is offline Junior Member
    Join Date
    Feb 2010
    Posts
    8
    Rep Power
    5

    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.

  8. #8
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,585
    Rep Power
    57

    Default

    Shut down Zimbra and run this (as root) then restart Zimbra:

    Code:
    /opt/zimbra/libexec/zmfixperms
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  9. #9
    esb123 is offline Junior Member
    Join Date
    Feb 2010
    Posts
    8
    Rep Power
    5

    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.

  10. #10
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,585
    Rep Power
    57

    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


    Acompli: A new adventure for Co-Founder KevinH.

Page 1 of 2 12 LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Daily mail report always reports "No messages found"
    By McPringle in forum Installation
    Replies: 42
    Last Post: 06-13-2011, 08:57 AM
  2. Unable to connect to remote server
    By Xarz991 in forum Error Reports
    Replies: 1
    Last Post: 04-23-2009, 12:56 PM
  3. [SOLVED] Upgraded to 5.0 OSS - Sendmail Problem
    By Chewie71 in forum Installation
    Replies: 11
    Last Post: 12-28-2007, 07:07 PM
  4. [SOLVED] Unable to connect to pop server
    By marklindley in forum Installation
    Replies: 12
    Last Post: 10-17-2007, 09:10 AM
  5. need advice on configuring zimbra to work with fax server
    By pheonix1t in forum Administrators
    Replies: 0
    Last Post: 07-11-2007, 07:46 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •