Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

Thread: LMTP server closing connection - system non-responsive

  1. #11
    deepblue is offline Partner (VAR/HSP)
    Join Date
    Jul 2006
    Location
    Stuttgart / Germany
    Posts
    223
    Rep Power
    9

    Default

    Quote Originally Posted by stuartg.orion View Post
    The release statement above implies it's related to IMAP connections,
    Hmm. I really doubt that this is related to IMAP. The release statement you are referring to, is not a official Zimbra release statement as far as I can see.
    And I am still unable to find a bugreport for the problem (I searched for LMTP but all bugs I found are unrelated).

    I have attached 2 screenshots (from ZCS NE 7.1.1 p2). lmtp_conn.jpg shows that the number of LMTP processes is going to the max. /var/log/zimbra.log starts showing that Postfix can not connect to LMTP:

    Code:
    refused to talk to me: 421 zimbra.server.com Zimbra LMTP server closing connection; service busy
    I think that happens when the number of LMTP Processes is maxed out and all running LMTP Processes are busy. Question is: why are the LMTP processes "hanging"?

    The second screenshot imap_conn.jpg shows the current number of imap connections. The peeks are at the same time (the screenshots have different scaling).
    I have seen much more imap connections to that server, so I doubt, that IMAP is really the cause of the problem...

    My assumption is, that LMTP can not put the mail into the mailbox for some reason. That causes new LMTP processes to be spawned until the max. of 20 processes/threads.
    The only way fix this is to restart the mailboxd.
    However: I found no indication in the mailbox.log why LMTP can not deliver the mail.

    Regards
    Thomas
    Attached Images Attached Images

  2. #12
    chauvetp is offline Elite Member
    Join Date
    Apr 2008
    Location
    New Paltz, NY
    Posts
    333
    Rep Power
    7

    Default

    Having the same problem. Only happened twice over the last two weeks but one of them was just now (an extremely quiet time in terms of system load for us, 8-9PM local time).

    As other have reported, mailboxd fixes the issue, but isn't the most pleasant fix. I have not yet upgraded to 7.1.2 (but being the beginning of the semester, now isn't the greatest time - maybe next week).
    ---
    Paul Chauvet
    State University of New York at New Paltz

  3. #13
    sae65 is offline Active Member
    Join Date
    Mar 2009
    Posts
    46
    Rep Power
    6

    Default

    Opened a ticket with Zimbra today. They stated that mini-patch 5 for Zimbra 7.1.1 and 7.1.2 does fix the issue.

  4. #14
    bjquinn is offline Advanced Member
    Join Date
    Nov 2005
    Posts
    175
    Rep Power
    9

    Default

    Just wanted to add that in my case I was having the same symptoms in the log but it didn't seem to have anything to do with the number of connections or length of time the server had been up. Turned out I had a stray copy of freshclam running even after stopping all zimbra services. So, after stopping all the zimbra services, I killed the stray freshclam process, restarted zimbra and all was well.

Page 2 of 2 FirstFirst 12

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Replies: 6
    Last Post: 11-29-2010, 01:27 PM
  2. Zimbra fails after working for 2 weeks
    By Linsys in forum Administrators
    Replies: 10
    Last Post: 10-07-2008, 12:42 AM
  3. Connection refused from local mail server
    By Steve3 in forum Administrators
    Replies: 8
    Last Post: 06-02-2007, 10:09 AM
  4. system failure: getDirectContext
    By avisser in forum Installation
    Replies: 3
    Last Post: 10-12-2005, 05:32 AM
  5. Insallation failed (Debian server)
    By popui007 in forum Installation
    Replies: 5
    Last Post: 09-29-2005, 02:27 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
  •