Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation
Reload this Page LMTP causing mail to be deferred

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
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 04-15-2008, 06:52 AM
Starter Member
  
Posts: 1
Default LMTP causing mail to be deferred
Everything will run smoothly for some time, and then mail just starts getting deferred out of the blue.
If I telnet localhost 7025, I get no response.

In my log files I'm seeing:
Apr 14 07:39:10 cerberus postfix/error[6406]: 478CA199095: to=, relay=none, delay=877, delays=877/0.01/0/0.12, dsn=4.4.2, status=deferred (delivery temporarily suspended: conversation with cerberus.(edited).net[192.168.1.6] timed out while receiving the initial server greeting)

When this occurs, doing zmcontrol stop && zmcontrol start will bandaid the problem. I confirm by telnetting to 7025 again:
root@cerberus:/tmp# telnet localhost 7025
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 cerberus.(edited).net Zimbra LMTP ready

I'm running 5.0.4 on Ubuntu 7.10
Reply With Quote
  #2 (permalink)  
Old 04-15-2008, 08:17 AM
Moderator
  
Posts: 7,928
Default
Welcome to the forums

Any other error messages in your Log Files - Zimbra :: Wiki ?
__________________
Reply With Quote
  #3 (permalink)  
Old 05-04-2008, 03:54 PM
Active Member
  
Posts: 38
Default 7025 stops
I have the same issue, and cannot find any related error beside the:

Code:
May  5 01:16:55 localhost postfix/lmtp[17314]: 0BD09A7C007: to=, relay=zimbra.sopac.org[202.62.0.157]:7025, delay=0.29, delays=0.28/0/0/0, dsn=4.4.2, status=deferred (lost connection with zimbra.sopac.org[202.62.0.157] while receiving the initial server greeting)
a zmcontrol stop/start will fix the problem

It happens a couple of times now...

I found that in the log around that time:
Code:
2008-05-05 01:15:40,145 WARN  [ImapSSLServer-167] [name=franck@sopac.org;mid=3;ip=202.170.44.164;] imap - ignoring error during UID FETCH: 
com.zimbra.common.service.ServiceException: system failure: IOException while retrieving content for item 4729
ExceptionId:ImapSSLServer-167:1209906940145:5a06415bbe5f3934
Code:service.FAILURE
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
        at com.zimbra.cs.mailbox.MessageCache.getMimeMessage(MessageCache.java:252)
        at com.zimbra.cs.mailbox.Message.getMimeMessage(Message.java:284)
        at com.zimbra.cs.imap.ImapMessage.getMimeMessage(ImapMessage.java:176)
        at com.zimbra.cs.imap.ImapHandler.fetch(ImapHandler.java:2937)
        at com.zimbra.cs.imap.ImapHandler.doFETCH(ImapHandler.java:2788)
        at com.zimbra.cs.imap.ImapHandler.executeRequest(ImapHandler.java:402)
        at com.zimbra.cs.imap.TcpImapHandler.processCommand(TcpImapHandler.java:151)
        at com.zimbra.cs.tcpserver.ProtocolHandler.processConnection(ProtocolHandler.java:160)
        at com.zimbra.cs.tcpserver.ProtocolHandler.run(ProtocolHandler.java:128)
        at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Thread.java:619)
Caused by: java.io.FileNotFoundException: /opt/zimbra/store/0/3/msg/1/4729-3918.msg (Too many open files)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.(FileInputStream.java:106)
        at com.zimbra.cs.store.FileBlobStore.getContent(FileBlobStore.java:371)
        at com.zimbra.cs.store.FileBlobStore.getContent(FileBlobStore.java:365)
        at com.zimbra.cs.mailbox.MessageCache.fetchFromStore(MessageCache.java:270)
        at com.zimbra.cs.mailbox.MessageCache.getMimeMessage(MessageCache.java:214)
        ... 10 more
2008-05-05 01:15:40,146 WARN  [ImapSSLServer-167] [name=franck@sopac.org;mid=3;ip=202.170.44.164;] imap - ignoring error during UID FETCH: 
com.zimbra.common.service.ServiceException: system failure: IOException while retrieving content for item 4730
ExceptionId:ImapSSLServer-167:1209906940146:5a06415bbe5f3934
Code:service.FAILURE
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
        at com.zimbra.cs.mailbox.MessageCache.getMimeMessage(MessageCache.java:252)
        at com.zimbra.cs.mailbox.Message.getMimeMessage(Message.java:284)
        at com.zimbra.cs.imap.ImapMessage.getMimeMessage(ImapMessage.java:176)
        at com.zimbra.cs.imap.ImapHandler.fetch(ImapHandler.java:2937)
        at com.zimbra.cs.imap.ImapHandler.doFETCH(ImapHandler.java:2788)
        at com.zimbra.cs.imap.ImapHandler.executeRequest(ImapHandler.java:402)
        at com.zimbra.cs.imap.TcpImapHandler.processCommand(TcpImapHandler.java:151)
        at com.zimbra.cs.tcpserver.ProtocolHandler.processConnection(ProtocolHandler.java:160)
        at com.zimbra.cs.tcpserver.ProtocolHandler.run(ProtocolHandler.java:128)
        at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Thread.java:619)
Caused by: java.io.FileNotFoundException: /opt/zimbra/store/0/3/msg/1/4730-3919.msg (Too many open files)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.(FileInputStream.java:106)
        at com.zimbra.cs.store.FileBlobStore.getContent(FileBlobStore.java:371)
        at com.zimbra.cs.store.FileBlobStore.getContent(FileBlobStore.java:365)
        at com.zimbra.cs.mailbox.MessageCache.fetchFromStore(MessageCache.java:270)
        at com.zimbra.cs.mailbox.MessageCache.getMimeMessage(MessageCache.java:214)
        ... 10 more
2008-05-05 01:15:40,147 WARN  [ImapSSLServer-167] [name=franck@sopac.org;mid=3;ip=202.170.44.164;] imap - ignoring error during UID FETCH: 
com.zimbra.common.service.ServiceException: system failure: IOException while retrieving content for item 4731
ExceptionId:ImapSSLServer-167:1209906940147:5a06415bbe5f3934
Code:service.FAILURE
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:253)
        at com.zimbra.cs.mailbox.MessageCache.getMimeMessage(MessageCache.java:252)
        at com.zimbra.cs.mailbox.Message.getMimeMessage(Message.java:284)
        at com.zimbra.cs.imap.ImapMessage.getMimeMessage(ImapMessage.java:176)
        at com.zimbra.cs.imap.ImapHandler.fetch(ImapHandler.java:2937)
        at com.zimbra.cs.imap.ImapHandler.doFETCH(ImapHandler.java:2788)
        at com.zimbra.cs.imap.ImapHandler.executeRequest(ImapHandler.java:402)
        at com.zimbra.cs.imap.TcpImapHandler.processCommand(TcpImapHandler.java:151)
        at com.zimbra.cs.tcpserver.ProtocolHandler.processConnection(ProtocolHandler.java:160)
        at com.zimbra.cs.tcpserver.ProtocolHandler.run(ProtocolHandler.java:128)
        at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Thread.java:619)
Caused by: java.io.FileNotFoundException: /opt/zimbra/store/0/3/msg/1/4731-3920.msg (Too many open files)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.(FileInputStream.java:106)
        at com.zimbra.cs.store.FileBlobStore.getContent(FileBlobStore.java:371)
        at com.zimbra.cs.store.FileBlobStore.getContent(FileBlobStore.java:365)
        at com.zimbra.cs.mailbox.MessageCache.fetchFromStore(MessageCache.java:270)
        at com.zimbra.cs.mailbox.MessageCache.getMimeMessage(MessageCache.java:214)
        ... 10 more
So I will increase the number of allowed open files and see?
Last edited by Franck; 05-04-2008 at 04:03 PM..
Reply With Quote
  #4 (permalink)  
Old 05-04-2008, 04:30 PM
Active Member
  
Posts: 38
Default [fix]
[SOLVED] Too many open files error
Reply With Quote
  #5 (permalink)  
Old 01-11-2011, 05:42 AM
Active Member
  
Posts: 25
Default
Sorry for opening this old topic again but i've got the same problem.
Didn't have the problems in testing state, but when I let my 100+ users in, I get this error almost every day:

Code:
Jan 11 12:43:27 mail postfix/lmtp[18106]: 67D5E1FE18A1: to=, relay=xx.xxx.se[172.20.2.20]:7025, delay=1081, delays=781/0.39/300/0, dsn=4.4.2, status=deferred (conversation with xx.xxx.se[172.20.2.20] timed out while receiving the initial server greeting)
I've checked /etc/security/limits.conf but the limits are already increased there?:

Code:
# End of file
zimbra soft nofile 524288
zimbra hard nofile 524288
I have to manually restart the server with zmcontrol when this occurs.
I really need help with this. Quite a serious problem!

EDIT:

Checked the logs and found this occurring at that time:
Code:
2011-01-11 12:06:14,167 WARN  [btpool0-264://xx.xxx.se:8080/service/soap/NoOpRequest] [ip=78.72.250.150;] SoapEngine - unable to construct SOAP context
com.zimbra.common.service.ServiceException: system failure: ZimbraLdapContext
ExceptionId:btpool0-264://xx.xxx.se:8080/service/soap/NoOpRequest:1294743974167:1a7fa22d5f591681
Code:service.FAILURE
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:248)
        at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:416)
        at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:373)
        at com.zimbra.cs.account.ldap.LdapProvisioning.getAccountByQuery(LdapProvisioning.java:608)
        at com.zimbra.cs.account.ldap.LdapProvisioning.getAccountByNameInternal(LdapProvisioning.java:776)
        at com.zimbra.cs.account.ldap.LdapProvisioning.getAccountByName(LdapProvisioning.java:757)
        at com.zimbra.cs.account.ldap.LdapProvisioning.get(LdapProvisioning.java:668)
        at com.zimbra.cs.account.ldap.LdapProvisioning.get(LdapProvisioning.java:653)
        at com.zimbra.cs.account.Provisioning.get(Provisioning.java:692)
        at com.zimbra.soap.ZimbraSoapContext.(ZimbraSoapContext.java:218)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:203)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158)
        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: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: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:212)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:413)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
Caused by: javax.naming.CommunicationException: Bad file descriptor [Root exception is java.net.SocketException: Bad file descriptor]
        at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCtx.java:3213)
        at javax.naming.ldap.InitialLdapContext.extendedOperation(InitialLdapContext.java:164)
        at com.zimbra.cs.account.ldap.ZimbraLdapContext.(ZimbraLdapContext.java:406)
        ... 42 more
Caused by: java.net.SocketException: Bad file descriptor
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
        at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
        at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
        at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:396)
        at com.sun.jndi.ldap.LdapClient.extendedOp(LdapClient.java:1172)
        at com.sun.jndi.ldap.LdapCtx.extendedOperation(LdapCtx.java:3160)
        ... 44 more
I run Zimbra HTTP on port 8080, have not installed a proxy, just for information.
Last edited by Robin; 01-11-2011 at 06:17 AM..
Reply With Quote
  #6 (permalink)  
Old 01-13-2011, 03:13 AM
Zimbra Consultant & Moderator
  
Posts: 20,316
Default
Quote:
Originally Posted by Robin View Post
Sorry for opening this old topic again but i've got the same problem.
You really shouldn't do that, adding to a thread that's already marked as Solved (especially an old one) will usually get your post overlooked.

Quote:
Originally Posted by Robin View Post
Didn't have the problems in testing state, but when I let my 100+ users in, I get this error almost every day:
Did you follow all the instruction from the thread above and modify the /etc/pam.d/common-session file as well?
__________________
Regards


Bill
Reply With Quote
  #7 (permalink)  
Old 01-13-2011, 03:19 AM
Active Member
  
Posts: 25
Default
I'm sorry.

Yes, I did check common-session also and it says
session required pam_limits.so

Also
Code:
zimbra@mail:~$ ulimit -n
524288
zimbra@mail:~$
Reply With Quote
  #8 (permalink)  
Old 01-13-2011, 07:55 AM
Active Member
  
Posts: 25
Default
Got the same thing today (but not yesterday).
All of a sudden I get:


Jan 13 16:48:06 mail postfix/lmtp[11136]: 1D94B1FE1D84: to=, relay=xx.xxx.se[172.20.2.20]:7025, delay=300, delays=0.17/0/300/0, dsn=4.4.2, status=deferred (conversation with xx.xxx.se[172.20.2.20] timed out while receiving the initial server greeting)

A zmcontrol restart solves it once again.

Tried to telnet localhost 7025 and it worked.

What can be wrong?!
Reply With Quote
Reply

« 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.