atom feed2 messages in net.sourceforge.lists.courier-usersRE: [courier-users] What are the shut...
FromSent OnAttachments
Matthew T. BlackmonNov 3, 2003 11:47 pm 
David GomillionNov 4, 2003 6:51 am 
Subject:RE: [courier-users] What are the shutdown and wakeup timestamps in the log file?
From:David Gomillion (dgom@eyecarenow.com)
Date:Nov 4, 2003 6:51:49 am
List:net.sourceforge.lists.courier-users

I had this problem when I had installed it too. It was working really well from installation until one weekend, the weekend before it went into production (wouldn't you know it).

As any good systems engineer would do, before the server went onto the Internet, I installed a firewall. Hmmm, could they be related?

If you have a firewall, PLEASE be sure you allow existing and related connections. In my case, by adding that rule, the response went from ~30 secs to send a tiny email to immediate.

-----Original Message----- From: cour@lists.sourceforge.net [mailto:cour@lists.sourceforge.net] On Behalf Of Matthew T. Blackmon Sent: Tuesday, November 04, 2003 1:49 AM To: cour@lists.sourceforge.net Subject: [courier-users] What are the shutdown and wakeup timestamps in the log file?

So I have my 0.42.2 box up-and-running. But, I'm having some issues with system performance.

In my initial testing, I was able to pump through a 100KB email on SMTP in a second. That was much better than the 15-20 seconds that my previous mailserver was putting through. Excellent. So, I complete the upgrade, troubleshoot about 10 more issues that come down the pipeline, but now, performance is simply atrocious, up and down (so it seems).

In a search through the literature, I come across a piece about ESMTP timeouts. I go through the troubleshooting steps and determine that one of my internal DNS servers is failing on recursive lookups. OK, I don't have time to deal with that at the moment, so I pull the defective DNS server out of resolvers, and restart the services. Here's a log trace from me sending a 27K file to the server...

Between the client and server in this transaction is a 10Mbit connection with approx 2% RMS usage during the time in question.

Nov 4 02:39:02 debian30r1-3 courieresmtpd: started,ip=[::ffff:68.101.xx.xxx] Nov 4 02:39:48 debian30r1-3 courierd: newmsg,id=0001E95E.3FA7579B.000001DD: dns; wintermute (wsip-68-101-xx-xxx.dc.dc.cox.net [::ffff:68.101.xx.xxx]) Nov 4 02:39:48 debian30r1-3 courierd: started,id=0001E95E.3FA7579B.000001DD,from=<matt@mydomain.org>,module =esm tp,host=somedomain.com,addr=<matt@somedomain.com> Nov 4 02:39:48 debian30r1-3 courierd: Waiting. shutdown time=none, wakeup time=none, queuedelivering=1, inprogress=1 Nov 4 02:39:50 debian30r1-3 courieresmtp: id=0001E95E.3FA7579B.000001DD,from=<matt@mydomain.org>,addr=<matthew. blac km@somedomain.com>: 250 2.6.0 <cour@debian30r1-3.internal.mydomain.com> Queued mail for delivery Nov 4 02:39:50 debian30r1-3 courieresmtp: id=0001E95E.3FA7579B.000001DD,from=<matt@mydomain.org>,addr=<matthew. blac km@somedomain.com>,size=34471,success: delivered: smtp.somedomain.com [57.80.xx.xxx] Nov 4 02:39:50 debian30r1-3 courieresmtp: id=0001E95E.3FA7579B.000001DD,from=<matt@mydomain.org>,addr=<matthew. blac km@somedomain.com>,size=34471,status: success Nov 4 02:39:50 debian30r1-3 courierd: completed,id=0001E95E.3FA7579B.000001DD Nov 4 02:39:50 debian30r1-3 courierd: Waiting. shutdown time=Tue Nov 4 03:34:44 2003, wakeup time=Tue Nov 4 03:34:44 2003, queuedelivering=0, inprogress=0

My first question is does anyone have any additional ideas on troubleshooting the ESMTP response on this? As mentioned, when I first tested it, it was great! Secondly, I note in the log this:

Nov 4 02:39:50 debian30r1-3 courierd: Waiting. shutdown time=Tue Nov 4 03:34:44 2003, wakeup time=Tue Nov 4 03:34:44 2003

Am I reading this correctly? What are the shutdown time and wakeup times representing, and might this have something to do with my performance issues?

Kind regards, Matthew

PS - did anyone receive the Debian upgrading to 42.2 guide I sent earlier? It was during the switchover from my old server, and I was torturing the new mailserver.