免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 4892 | 回复: 7

[Mail] zimbra邮件系统故障,请求帮助,谢谢! [复制链接]

论坛徽章:
0
发表于 2014-01-23 16:39 |显示全部楼层


页面登录zimbra邮件系统,发送邮件时提示以上错误。
[zimbra@mail root]$ 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掉后关停并启动相应服务
[root@mail ~]# su zimbra
[zimbra@mail root]$ 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.
[zimbra@mail root]$ 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是启动了

但是查看运行状态时,提示如下:
[zimbra@mail root]$ 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
登录 页面时又出现前述的报错

论坛徽章:
0
发表于 2014-01-23 16:40 |显示全部楼层
报错详细情况如下:
method:        [unknown]
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:62 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:15 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:20 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:38 at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:21 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:21 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"
     }
   }
}

论坛徽章:
0
发表于 2014-01-23 16:40 |显示全部楼层
tail -50 /var/log/maillog
[root@mail log]# tail -50 maillog
Jan 21 16:10:10 mail zmmailboxdmgr[12429]: mailboxd/JVM process exited (waitpid expected 12430 got 12430)
Jan 21 16:10:10 mail zmmailboxdmgr[12429]: manager woke up from wait on mailboxd/JVM with pid 12430
Jan 21 16:10:11 mail zmmailboxdmgr[19807]: manager process 12429 died, shutdown completed
Jan 21 16:11:33 mail zmmailboxdmgr[20723]: status requested
Jan 21 16:11:33 mail zmmailboxdmgr[20723]: file /opt/zimbra/log/zmmailboxd_manager.pid does not exist
Jan 21 16:11:33 mail zmmailboxdmgr[20723]: assuming no other instance is running
Jan 21 16:11:33 mail zmmailboxdmgr[20723]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Jan 21 16:11:33 mail zmmailboxdmgr[20723]: assuming no other instance is running
Jan 21 16:11:33 mail zmmailboxdmgr[20723]: no manager process is running
Jan 21 16:11:33 mail zmmailboxdmgr[20733]: start requested
Jan 21 16:11:33 mail zmmailboxdmgr[20733]: checking if another instance of manager is already running
Jan 21 16:11:33 mail zmmailboxdmgr[20733]: file /opt/zimbra/log/zmmailboxd_manager.pid does not exist
Jan 21 16:11:33 mail zmmailboxdmgr[20733]: assuming no other instance is running
Jan 21 16:11:33 mail zmmailboxdmgr[20733]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Jan 21 16:11:33 mail zmmailboxdmgr[20733]: assuming no other instance is running
Jan 21 16:11:33 mail zmmailboxdmgr[20734]: wrote manager pid 20734 to /opt/zimbra/log/zmmailboxd_manager.pid
Jan 21 16:11:33 mail zmmailboxdmgr[20735]: wrote java pid 20735 to /opt/zimbra/log/zmmailboxd_java.pid
Jan 21 16:11:33 mail zmmailboxdmgr[20734]: manager started mailboxd/JVM with pid 20735
Jan 21 16:11:50 mail postfix/postfix-script[21087]: warning: not owned by root: /opt/zimbra/postfix-2.7.4.2z/conf/main.cf
Jan 21 16:11:50 mail postfix/postfix-script[21088]: warning: not owned by root: /opt/zimbra/postfix-2.7.4.2z/conf/master.cf
Jan 21 16:11:50 mail postfix/postfix-script[21089]: 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[21092]: warning: not owned by postfix: /opt/zimbra/data/postfix/data/./master.lock
Jan 21 16:11:50 mail postfix/postfix-script[21093]: warning: not owned by postfix: /opt/zimbra/data/postfix/data/./prng_exch
Jan 21 16:11:50 mail postfix/postfix-script[21108]: starting the Postfix mail system
Jan 21 16:11:50 mail postfix/master[21109]: fatal: open lock file /opt/zimbra/data/postfix/data/master.lock: cannot open file: Permission denied
Jan 21 08:12:00 mail postfix/postqueue[21796]: fatal: Queue report unavailable - mail system is down
Jan 21 16:12:03 mail zmmailboxdmgr[22214]: status requested
Jan 21 16:12:03 mail zmmailboxdmgr[22214]: status OK
Jan 21 08:12:30 mail postfix/postqueue[22340]: fatal: Queue report unavailable - mail system is down
Jan 21 08:13:00 mail postfix/postqueue[22394]: fatal: Queue report unavailable - mail system is down
Jan 21 16:13:04 mail zmmailboxdmgr[22668]: status requested
Jan 21 16:13:04 mail zmmailboxdmgr[22668]: status OK
Jan 21 08:13:30 mail postfix/postqueue[22788]: fatal: Queue report unavailable - mail system is down
Jan 21 08:14:00 mail postfix/postqueue[22864]: fatal: Queue report unavailable - mail system is down
Jan 21 16:14:04 mail zmmailboxdmgr[23161]: status requested
Jan 21 16:14:04 mail zmmailboxdmgr[23161]: status OK
Jan 21 08:14:30 mail postfix/postqueue[23282]: fatal: Queue report unavailable - mail system is down
Jan 21 08:15:00 mail postfix/postqueue[23336]: fatal: Queue report unavailable - mail system is down
Jan 21 08:15:30 mail postfix/postqueue[23347]: fatal: Queue report unavailable - mail system is down
Jan 21 08:16:00 mail postfix/postqueue[23360]: fatal: Queue report unavailable - mail system is down
Jan 21 16:16:04 mail zmmailboxdmgr[23689]: status requested
Jan 21 16:16:04 mail zmmailboxdmgr[23689]: status OK
Jan 21 08:16:30 mail postfix/postqueue[23813]: fatal: Queue report unavailable - mail system is down
Jan 21 08:17:00 mail postfix/postqueue[23826]: fatal: Queue report unavailable - mail system is down
Jan 21 08:17:30 mail postfix/postqueue[23874]: fatal: Queue report unavailable - mail system is down
Jan 21 08:18:00 mail postfix/postqueue[23888]: fatal: Queue report unavailable - mail system is down
Jan 21 16:18:04 mail zmmailboxdmgr[24298]: status requested
Jan 21 16:18:04 mail zmmailboxdmgr[24298]: status OK
Jan 21 08:18:30 mail postfix/postqueue[24418]: fatal: Queue report unavailable - mail system is down
Jan 21 08:19:00 mail postfix/postqueue[24433]: fatal: Queue report unavailable - mail system is down

论坛徽章:
0
发表于 2014-01-23 16:41 |显示全部楼层
fatal: Queue report unavailable - mail system is down
这个到底是什么故障?

论坛徽章:
0
发表于 2015-11-20 12:18 |显示全部楼层
遇到同样的问题,请问楼主有解决方案么

论坛徽章:
0
发表于 2015-11-20 12:18 |显示全部楼层
遇到同样的问题,请问楼主有解决方案么

论坛徽章:
23
天蝎座
日期:2014-05-13 18:05:59IT运维版块每日发帖之星
日期:2015-11-26 06:20:00操作系统版块每月发帖之星
日期:2015-12-02 14:57:54IT运维版块每月发帖之星
日期:2016-01-07 23:01:56IT运维版块每周发帖之星
日期:2016-01-07 23:04:2615-16赛季CBA联赛之青岛
日期:2016-01-23 07:58:272016猴年福章徽章
日期:2016-02-18 15:30:3415-16赛季CBA联赛之北控
日期:2016-03-23 14:20:06IT运维版块每日发帖之星
日期:2016-04-01 06:20:0015-16赛季CBA联赛之吉林
日期:2016-06-28 13:51:54IT运维版块每日发帖之星
日期:2015-11-23 06:20:00IT运维版块每日发帖之星
日期:2015-11-23 06:20:00
发表于 2015-11-20 14:16 |显示全部楼层
mta                     Stopped

1.我虽然没用过你的所谓的zimbra邮件系统,实质上我大概看了下,他还是基于postfix的^_^。
这里已经很明显的说明,你的MTA已经停止工作了。MTA就是SMTP邮件服务器,他都停止工作了,你当然无法发邮件。

2.postfix无法启动原因会有非常多。比如postfix的配置文件错误或权限问题,我大概注意了下你的日志,你应该重点放在这里,这下面报的错误可都是postfix的重要配置文件啊大哥,你确定你的权限设对了吗,宿主设对了吗?
Jan 21 16:11:50 mail postfix/postfix-script[21087]: warning: not owned by root: /opt/zimbra/postfix-2.7.4.2z/conf/main.cf
Jan 21 16:11:50 mail postfix/postfix-script[21088]: warning: not owned by root: /opt/zimbra/postfix-2.7.4.2z/conf/master.cf
Jan 21 16:11:50 mail postfix/postfix-script[21089]: 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[21092]: warning: not owned by postfix: /opt/zimbra/data/postfix/data/./master.lock
Jan 21 16:11:50 mail postfix/postfix-script[21093]: warning: not owned by postfix: /opt/zimbra/data/postfix/data/./prng_exch

所以你们习惯性用第三方超级打包型的邮件系统,一旦出了故障,你们根本无从下手,就是因为对postfix不了解。这个问题不难,按照我给你提示的,你能解决。

论坛徽章:
19
酉鸡
日期:2015-02-16 11:13:06操作系统版块每周发帖之星
日期:2015-12-02 15:01:04每日论坛发贴之星
日期:2015-11-28 06:20:00IT运维版块每日发帖之星
日期:2015-11-28 06:20:00每日论坛发贴之星
日期:2015-11-27 06:20:00IT运维版块每日发帖之星
日期:2015-11-27 06:20:00IT运维版块每日发帖之星
日期:2015-11-20 06:20:00每日论坛发贴之星
日期:2015-11-19 06:20:00IT运维版块每日发帖之星
日期:2015-11-19 06:20:00每日论坛发贴之星
日期:2015-11-15 06:20:00数据库技术版块每日发帖之星
日期:2015-11-15 06:20:00程序设计版块每日发帖之星
日期:2015-11-15 06:20:00
发表于 2015-11-25 14:40 |显示全部楼层
学习了
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

DTCC2020中国数据库技术大会

【架构革新 高效可控】2020年12月21日-23日第十一届中国数据库技术大会将在北京隆重召开。

大会设置2大主会场,20+技术专场,将邀请超百位行业专家,重点围绕数据架构、AI与大数据、传统企业数据库实践和国产开源数据库等内容展开分享和探讨,为广大数据领域从业人士提供一场年度盛会和交流平台。

http://dtcc.it168.com


大会官网>>
  

北京盛拓优讯信息技术有限公司. 版权所有 16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122
中国互联网协会会员  联系我们:huangweiwei@it168.com
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP