zimbra郵件系統故障,請求幫助,謝謝!

←手機掃碼閱讀     火星人 @ 2014-03-04 , reply:0

zimbra郵件系統故障,請求幫助,謝謝!



頁面登錄zimbra郵件系統,發送郵件時提示以上錯誤。
$ zmcontrol status
Host mail.XXXX.com

antispam                Running

antivirus               Running

ldap                    Running

logger                  Running

mailbox                 Running

mta                     Stopped

postfix is not running

snmp                    Running

spell                   Running

stats                   Running

zmconfigd               Running

按網路上介紹的方法,埠25被sendmail佔用了,kill掉后關停並啟動相應服務
# su zimbra
$ zmcontrol stop
Host mail.XXX.com

Stopping stats...Done.

Stopping mta...Done.

Stopping spell...Done.

Stopping snmp...Done.

Stopping cbpolicyd...Done.

Stopping archiving...Done.

Stopping antivirus...Done.

Stopping antispam...Done.

Stopping imapproxy...Done.

Stopping memcached...Done.

Stopping mailbox...Done.

Stopping logger...Done.

Stopping zmconfigd...Done.

Stopping ldap...Done.
$ zmcontrol start
Host mail.XXX.com

Starting ldap...Done.

Starting zmconfigd...Done.

Starting logger...Done.

Starting mailbox...Done.

Starting antispam...Done.

Starting antivirus...Done.

Starting snmp...Done.

Starting spell...Done.

Starting mta...Done.

Starting stats...Done.
注意這裡mta是啟動了

但是查看運行狀態時,提示如下:
$ zmcontrol status
Host mail.XXXX.com

antispam                Running

antivirus               Running

ldap                    Running

logger                  Running

mailbox                 Running

mta                     Stopped

postfix is not running

snmp                    Running

spell                   Running

stats                   Running

zmconfigd               Running
登錄 頁面時又出現前述的報錯
《解決方案》

報錯詳細情況如下:
method:        
msg:        try again: Unable to connect to the MTA
code:        mail.TRY_AGAIN
detail:        soap:Receiver
trace:        com.zimbra.cs.mailbox.MailServiceException: try again: Unable to connect to the MTA ExceptionId:btpool0-6://www.XXX.com:8088/service/soap/SendMsgRequest:1390292054686:bad245732cdebf35 Code:mail.TRY_AGAIN at com.zimbra.cs.mailbox.MailServiceException.TRY_AGAIN(MailServiceException.java:479) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:628) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:425) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:385) at com.zimbra.cs.service.mail.SendMsg.doSendMessage(SendMsg.java:193) at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg.java:154) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:412) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:287) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158) at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:294) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:215) at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:208) at javax.servlet.http.HttpServlet.service(HttpServlet.java:814) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81) at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:218) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:422) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:946) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451) Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at com.zimbra.cs.mailclient.MailConnection.newSocket(MailConnection.java:416) at com.zimbra.cs.mailclient.MailConnection.connect(MailConnection.java:74) at com.zimbra.cs.mailclient.smtp.SmtpTransport.protocolConnect(SmtpTransport.java:180) at javax.mail.Service.connect(Service.java:291) at javax.mail.Service.connect(Service.java:172) at javax.mail.Service.connect(Service.java:121) at com.zimbra.cs.mailbox.MailSender.sendMessageToHost(MailSender.java:894) at com.zimbra.cs.mailbox.MailSender.sendMessage(MailSender.java:831) at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:565) ... 39 more
request:        

Body: {
  SendMsgRequest: {
    _jsns: "urn:zimbraMail",
    m: {
      e: [
        0: {
          a: "lwdy@163.com",
          add: "0",
          t: "t"
         },
        1: {
          a: "test@XXX.com",
          p: "測試帳號",
          t: "f"
         }
       ],
      idnt: "301f19c9-f157-4090-9792-08b31f2f56b5",
      mp: [
        0: {
          content: {
            _content: "to 163.com"
           },
          ct: "text/plain"
         }
       ],
      su: {
        _content: "to 163.com"
       }
     },
    suid: 1390290504345
   }
},
Header: {
  context: {
    _jsns: "urn:zimbra",
    account: {
      _content: "test@XXX.com",
      by: "name"
     },
    authToken: "(removed)",
    session: {
      _content: 12,
      id: 12
     },
    userAgent: {
      name: "ZimbraWebClient - FF3.0 (Win)",
      version: "7.1.1_GA_3196"
     }
   }
}
《解決方案》

tail -50 /var/log/maillog
# tail -50 maillog
Jan 21 16:10:10 mail zmmailboxdmgr: mailboxd/JVM process exited (waitpid expected 12430 got 12430)
Jan 21 16:10:10 mail zmmailboxdmgr: manager woke up from wait on mailboxd/JVM with pid 12430
Jan 21 16:10:11 mail zmmailboxdmgr: manager process 12429 died, shutdown completed
Jan 21 16:11:33 mail zmmailboxdmgr: status requested
Jan 21 16:11:33 mail zmmailboxdmgr: file /opt/zimbra/log/zmmailboxd_manager.pid does not exist
Jan 21 16:11:33 mail zmmailboxdmgr: assuming no other instance is running
Jan 21 16:11:33 mail zmmailboxdmgr: file /opt/zimbra/log/zmmailboxd.pid does not exist
Jan 21 16:11:33 mail zmmailboxdmgr: assuming no other instance is running
Jan 21 16:11:33 mail zmmailboxdmgr: no manager process is running
Jan 21 16:11:33 mail zmmailboxdmgr: start requested
Jan 21 16:11:33 mail zmmailboxdmgr: checking if another instance of manager is already running
Jan 21 16:11:33 mail zmmailboxdmgr: file /opt/zimbra/log/zmmailboxd_manager.pid does not exist
Jan 21 16:11:33 mail zmmailboxdmgr: assuming no other instance is running
Jan 21 16:11:33 mail zmmailboxdmgr: file /opt/zimbra/log/zmmailboxd.pid does not exist
Jan 21 16:11:33 mail zmmailboxdmgr: assuming no other instance is running
Jan 21 16:11:33 mail zmmailboxdmgr: wrote manager pid 20734 to /opt/zimbra/log/zmmailboxd_manager.pid
Jan 21 16:11:33 mail zmmailboxdmgr: wrote java pid 20735 to /opt/zimbra/log/zmmailboxd_java.pid
Jan 21 16:11:33 mail zmmailboxdmgr: manager started mailboxd/JVM with pid 20735
Jan 21 16:11:50 mail postfix/postfix-script: warning: not owned by root: /opt/zimbra/postfix-2.7.4.2z/conf/main.cf
Jan 21 16:11:50 mail postfix/postfix-script: warning: not owned by root: /opt/zimbra/postfix-2.7.4.2z/conf/master.cf
Jan 21 16:11:50 mail postfix/postfix-script: warning: not owned by root: /opt/zimbra/postfix-2.7.4.2z/conf/master.cf.in
Jan 21 16:11:50 mail postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/data/./master.lock
Jan 21 16:11:50 mail postfix/postfix-script: warning: not owned by postfix: /opt/zimbra/data/postfix/data/./prng_exch
Jan 21 16:11:50 mail postfix/postfix-script: starting the Postfix mail system
Jan 21 16:11:50 mail postfix/master: fatal: open lock file /opt/zimbra/data/postfix/data/master.lock: cannot open file: Permission denied
Jan 21 08:12:00 mail postfix/postqueue: fatal: Queue report unavailable - mail system is down
Jan 21 16:12:03 mail zmmailboxdmgr: status requested
Jan 21 16:12:03 mail zmmailboxdmgr: status OK
Jan 21 08:12:30 mail postfix/postqueue: fatal: Queue report unavailable - mail system is down
Jan 21 08:13:00 mail postfix/postqueue: fatal: Queue report unavailable - mail system is down
Jan 21 16:13:04 mail zmmailboxdmgr: status requested
Jan 21 16:13:04 mail zmmailboxdmgr: status OK
Jan 21 08:13:30 mail postfix/postqueue: fatal: Queue report unavailable - mail system is down
Jan 21 08:14:00 mail postfix/postqueue: fatal: Queue report unavailable - mail system is down
Jan 21 16:14:04 mail zmmailboxdmgr: status requested
Jan 21 16:14:04 mail zmmailboxdmgr: status OK
Jan 21 08:14:30 mail postfix/postqueue: fatal: Queue report unavailable - mail system is down
Jan 21 08:15:00 mail postfix/postqueue: fatal: Queue report unavailable - mail system is down
Jan 21 08:15:30 mail postfix/postqueue: fatal: Queue report unavailable - mail system is down
Jan 21 08:16:00 mail postfix/postqueue: fatal: Queue report unavailable - mail system is down
Jan 21 16:16:04 mail zmmailboxdmgr: status requested
Jan 21 16:16:04 mail zmmailboxdmgr: status OK
Jan 21 08:16:30 mail postfix/postqueue: fatal: Queue report unavailable - mail system is down
Jan 21 08:17:00 mail postfix/postqueue: fatal: Queue report unavailable - mail system is down
Jan 21 08:17:30 mail postfix/postqueue: fatal: Queue report unavailable - mail system is down
Jan 21 08:18:00 mail postfix/postqueue: fatal: Queue report unavailable - mail system is down
Jan 21 16:18:04 mail zmmailboxdmgr: status requested
Jan 21 16:18:04 mail zmmailboxdmgr: status OK
Jan 21 08:18:30 mail postfix/postqueue: fatal: Queue report unavailable - mail system is down
Jan 21 08:19:00 mail postfix/postqueue: fatal: Queue report unavailable - mail system is down
《解決方案》

fatal: Queue report unavailable - mail system is down
這個到底是什麼故障?




[火星人 ] zimbra郵件系統故障,請求幫助,謝謝!已經有1243次圍觀

http://coctec.com/docs/service/show-post-10817.html