mail postfix/postqueue[20397]: fatal: Queue report unavailable - mail system is down

[vortex566]

Up until this morning the server was sending and receiving mails. The log file has the following error mail postfix/postqueue[20397]: fatal: Queue report unavailable - mail system is down, however this was here when the mail was working.

I have tried to repair the permissions and an output of zmcontrol status:

zimbra@mail:/root$ zmcontrol status
Host mail.lordswoodgirls.school
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Running
mta Running
snmp Running
spell Running
stats Running

2010-03-09 09:40:05,363 INFO  [btpool0-10://mail.lordswoodgirls.co.uk/service/soap/SendMsgRequest] [name=l.gordo$
com.zimbra.cs.mailbox.MailServiceException: try again: Unable to connect to the MTA
ExceptionId:btpool0-10://mail.lordswoodgirls.co.uk/service/soap/SendMsgRequest:1268127605363:5a7e8dac7534b80b
Code:mail.TRY_AGAIN
        at com.zimbra.cs.mailbox.MailServiceException.TRY_AGAIN(MailServiceException.java:475)
        at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:490)
        at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:308)
        at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:265)
        at com.zimbra.cs.service.mail.SendMsg.doSendMessage(SendMsg.java:189)
        at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg.java:150)
        at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:419)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:273)
        at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291)
        at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        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:216)
        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:418)
        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:939)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
        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:409)
        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:333)
       at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:525)
        at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:265)
        at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:227)
        at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1511)
        at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:453)
        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:751)
        at com.zimbra.cs.mailbox.MailSender.sendMessage(MailSender.java:672)
        at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:415)
        ... 39 more

Does anyone have any ideas?

[uxbod]

Check /var/log/zimbra.log for any error messages from Postfix.

[tgiesela]

I'm having the same problem. I checked all the logs and I cannot find any errors. Restarting the services via 'zmcontrol restart' solves the problem.

Every night I stop zimbra, backup the mailboxes and start zimbra again. And sometimes this problem occurs. The probleem seems to be related to the latest upgrade of zimbra:

Release 6.0.8_GA_2661.UBUNTU8 UBUNTU8 FOSS edition.

This is very annoying because it is unpredictable if sending mail will function correctly or not.

[vortex566]

mail postfix/postqueue[10669]: fatal: Queue report unavailable - mail system is down
mail postfix/postqueue[10690]: fatal: Queue report unavailable - mail system is down

This has come back today and this is the only thing I get in zimbra.log a stop and a restart fixes the problem.

[phoenix]

This has come back today and this is the only thing I get in zimbra.log a stop and a restart fixes the problem.

Seems rather a long time between your original post and giving feedback on the problem.

This is with the version of Zimbra shown in your profile? For how long has this been happening? What else do you see in the log files round the time you see this message? What's the status of the services when this occurs?

[vortex566]

Good Morning,

Sorry, but I've forgotten how to change the information, so I'm running Release 7.1.0_GA_3140.UBUNTU8 UBUNTU8 FOSS edition.

The Zmcontrol is reporting all services as running. I've found three postfix.conf files are not owned by root, but changing these does not have any effect, as they just reset on a service stop and start. It really does seem to happen at random. The whole weekend was fine, but this morning I came into the same problem.

[phoenix]

Sorry, but I've forgotten how to change the information, so I'm running Release 7.1.0_GA_3140.UBUNTU8 UBUNTU8 FOSS edition.

You can change your profile by going to this link.

The Zmcontrol is reporting all services as running. I've found three postfix.conf files are not owned by root, but changing these does not have any effect, as they just reset on a service stop and start.

You do not change the permissions on those files, the settings for them are correct.

It really does seem to happen at random. The whole weekend was fine, but this morning I came into the same problem.

What are the exact errors you're seeing in the log files? Is there any other errors apart from the 'mail system down'? Are your certificates valid and in date?

[vortex566]

Thank you for the quick reply.

I can confirm that the certificutes are valid until 2012, so I don't think it's that.

Nov 21 04:44:40 mail postfix/postfix-script[31729]: stopping the Postfix mail system
Nov 21 04:44:40 mail postfix/master[686]: terminating on signal 15
Nov 21 04:44:50 mail zmmailboxdmgr[31883]: status requested
Nov 21 04:44:50 mail zmmailboxdmgr[31883]: status OK
Nov 21 04:44:51 mail zmmailboxdmgr[31888]: stop requested
Nov 21 04:44:51 mail zmmailboxdmgr[31888]: waiting for manager process 32482 to die
Nov 21 04:44:51 mail zmmailboxdmgr[32482]: shutdown requested, sending TERM signal to 32483
Nov 21 04:44:54 mail zmmailboxdmgr[32482]: mailboxd/JVM process exited (waitpid expected 32483 got 32483)
Nov 21 04:44:54 mail zmmailboxdmgr[32482]: manager woke up from wait on mailboxd/JVM with pid 32483
Nov 21 04:44:55 mail zmmailboxdmgr[31888]: manager process 32482 died, shutdown completed
Nov 21 04:46:04 mail zmmailboxdmgr[32197]: status requested
Nov 21 04:46:04 mail zmmailboxdmgr[32197]: file /opt/zimbra/log/zmmailboxd_manager.pid does not exist
Nov 21 04:46:04 mail zmmailboxdmgr[32197]: assuming no other instance is running
Nov 21 04:46:04 mail zmmailboxdmgr[32197]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Nov 21 04:46:04 mail zmmailboxdmgr[32197]: assuming no other instance is running
Nov 21 04:46:04 mail zmmailboxdmgr[32197]: no manager process is running
Nov 21 04:48:06 mail zmmailboxdmgr[32519]: status requested
Nov 21 04:48:06 mail zmmailboxdmgr[32519]: file /opt/zimbra/log/zmmailboxd_manager.pid does not exist
Nov 21 04:48:06 mail zmmailboxdmgr[32519]: assuming no other instance is running
Nov 21 04:48:06 mail zmmailboxdmgr[32519]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Nov 21 04:48:06 mail zmmailboxdmgr[32519]: assuming no other instance is running
Nov 21 04:48:06 mail zmmailboxdmgr[32519]: no manager process is running
Nov 21 04:50:03 mail postfix/postqueue[32651]: fatal: Queue report unavailable - mail system is down
Nov 21 04:50:05 mail zmmailboxdmgr[522]: status requested
Nov 21 04:50:05 mail zmmailboxdmgr[522]: file /opt/zimbra/log/zmmailboxd_manager.pid does not exist
Nov 21 04:50:05 mail zmmailboxdmgr[522]: assuming no other instance is running
Nov 21 04:50:05 mail zmmailboxdmgr[522]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Nov 21 04:50:05 mail zmmailboxdmgr[522]: assuming no other instance is running
Nov 21 04:50:05 mail zmmailboxdmgr[522]: no manager process is running
Nov 21 04:51:47 mail zmmailboxdmgr[1660]: status requested
Nov 21 04:51:47 mail zmmailboxdmgr[1660]: file /opt/zimbra/log/zmmailboxd_manager.pid does not exist
Nov 21 04:51:47 mail zmmailboxdmgr[1660]: assuming no other instance is running
Nov 21 04:51:47 mail zmmailboxdmgr[1660]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Nov 21 04:51:47 mail zmmailboxdmgr[1660]: assuming no other instance is running
Nov 21 04:51:47 mail zmmailboxdmgr[1660]: no manager process is running
Nov 21 04:51:47 mail zmmailboxdmgr[1670]: start requested
Nov 21 04:51:47 mail zmmailboxdmgr[1670]: checking if another instance of manager is already running
Nov 21 04:51:47 mail zmmailboxdmgr[1670]: file /opt/zimbra/log/zmmailboxd_manager.pid does not exist
Nov 21 04:51:47 mail zmmailboxdmgr[1670]: assuming no other instance is running
Nov 21 04:51:47 mail zmmailboxdmgr[1670]: file /opt/zimbra/log/zmmailboxd.pid does not exist
Nov 21 04:51:47 mail zmmailboxdmgr[1670]: assuming no other instance is running
Nov 21 04:51:47 mail zmmailboxdmgr[1671]: wrote manager pid 1671 to /opt/zimbra/log/zmmailboxd_manager.pid
Nov 21 04:51:47 mail zmmailboxdmgr[1672]: wrote java pid 1672 to /opt/zimbra/log/zmmailboxd_java.pid
Nov 21 04:51:47 mail zmmailboxdmgr[1671]: manager started mailboxd/JVM with pid 1672
Nov 21 04:52:04 mail zmmailboxdmgr[2065]: status requested
Nov 21 04:52:04 mail zmmailboxdmgr[2065]: status OK
Nov 21 04:52:30 mail postfix/postqueue[2832]: fatal: Queue report unavailable - mail system is down
Nov 21 04:53:00 mail postfix/postqueue[2949]: fatal: Queue report unavailable - mail system is down
Nov 21 04:53:30 mail postfix/postqueue[2969]: fatal: Queue report unavailable - mail system is down
Nov 21 04:54:00 mail postfix/postqueue[2978]: fatal: Queue report unavailable - mail system is down