Loading ...
Sorry, an error occurred while loading the content.

RE: Tracking down an issue

Expand Messages
  • Gary V
    ... As I m sure you are aware, there is no problem with Postfix here (unless the issue is how you have integrated amavisd-new with Postfix). You need to see if
    Message 1 of 2 , Feb 1 7:19 AM
    • 0 Attachment
      >
      >Running Postfix 2.2.8 and looking for some help trying to track down an
      >issue recently come across. Last week, and again this morning, the queue
      >started piling up and found that amavisd 2.3.3 was refusing connections,
      >tried restarting and it kept complaining that the address was in use,
      >finally rebooted and all was well again.
      >
      >Now, trying to find what caused the problem is baffling me, seems to
      >have happened after 8:30am this morning, I have the last successfully
      >sent message to amavis on 127.0.0.1 at 08:38:42. After that, the next
      >message in the log, in the same second, is like this:
      >
      >esmtp# grep E7D2F7E977 /var/log/maillog
      >Jan 31 08:38:42 esmtp postfix/smtpd[33875]: E7D2F7E977:
      >client=athedsl-11816.otenet.gr[87.202.46.132]
      >Jan 31 08:38:47 esmtp postfix/cleanup[34418]: E7D2F7E977:
      >message-id=<481619702.20060131133840@...>
      >Jan 31 08:38:50 esmtp postfix/qmgr[68872]: E7D2F7E977:
      >from=<e_nagah31@...>, size=3772, nrcpt=1 (queue active)
      >Jan 31 08:57:43 esmtp postfix/qmgr[34694]: E7D2F7E977: skipped, still
      >being delivered
      >Jan 31 08:58:45 esmtp postfix/qmgr[34811]: E7D2F7E977: skipped, still
      >being delivered
      >Jan 31 08:58:50 esmtp postfix/smtp[33217]: E7D2F7E977:
      >to=<black@...>, relay=127.0.0.1[127.0.0.1], delay=1208,
      >status=deferred (conversation with 127.0.0.1[127.0.0.1] timed out while
      >sending end of data -- message may be sent more than once)
      >Jan 31 08:59:44 esmtp postfix/qmgr[34811]: E7D2F7E977:
      >from=<e_nagah31@...>, size=3772, nrcpt=1 (queue active)
      >Jan 31 09:03:50 esmtp postfix/qmgr[34811]: E7D2F7E977:
      >to=<black@...>, relay=none, delay=1508, status=deferred (delivery
      >temporarily suspended: connect to 127.0.0.1[127.0.0.1]: read timeout)
      >Jan 31 09:13:28 esmtp postfix/qmgr[898]: E7D2F7E977:
      >from=<e_nagah31@...>, size=3772, nrcpt=1 (queue active)
      >Jan 31 09:20:50 esmtp postfix/smtp[1019]: E7D2F7E977:
      >to=<black@...>, relay=127.0.0.1[127.0.0.1], delay=2528,
      >status=sent (250 2.5.0 Ok, id=01950-01-9, BOUNCE)
      >Jan 31 09:20:50 esmtp postfix/qmgr[898]: E7D2F7E977: removed
      >
      >You can see I was rebooted around 09:10 and the message then went out.
      >There are no errors between the one at 08:38 and this message, you'll
      >see the first line below is the last successfully sent message to
      >localhost and the last line is the message above:
      >
      >I cannot find any errors in todays log other than DNS lookup and other
      >standard errors. How can I find what happened?
      >
      >--
      >Robert
      >

      As I'm sure you are aware, there is no problem with Postfix here (unless the
      issue is how you have integrated amavisd-new with Postfix). You need to see
      if amavis reported any errors. If not, then a couple possible reasons (among
      many) could be you suffer from the 'Bayes Expiry Syndrome' where sa-learn is
      eating up all your CPU power when it tries to expire old Bayes tokens
      causing delays in amavisd processing. If you do not have sufficient physical
      ram, and amavisd starts running in swap space, it will run very slowly,
      causing timeouts. Run 'top' when this happens, check your swap space and CPU
      usage. Newer versions of amavisd-new also offer 'amavisd-nanny' that can
      monitor the situation. Moving Bayes to SQL, disabling auto-expire and
      running 'sa-learn --sync --force-expire' as a cron job at off-peak hours
      helps a lot. It could be a problem with an external module amavisd-new uses,
      raise the $log_level in amavisd.conf and monitor results when it slows. Grep
      for amavis error messages that contain text like TROUBLE or Can't or Failed.
      Read http://www.ijs.si/software/amavisd/README.postfix.txt and make sure you
      are following the instructions. I suggest the amavis-users list for this
      problem. The version of amavisd-new and the OS you are running this on is
      helpful information, as is startup output from amavisd (or amavisd debug)
      which shows the versions of external modules.

      Gary V

      _________________________________________________________________
      Don�t just search. Find. Check out the new MSN Search!
      http://search.msn.click-url.com/go/onm00200636ave/direct/01/
    Your message has been successfully submitted and would be delivered to recipients shortly.